BSOD numerous different messages even after a fresh install of win7

[monkey314]

I never touched my RAM settings. As far as I know messing with RAM settings is messing with voltage and I wasn't going to risk frying my motherboard to have 2% faster RAM.

 

[writhziden]

Wise idea. Did loading defaults fix the settings and timings?

 

[monkey314]

No. I've been working and haven't had the gumption to mess with the bios without having a lot of free tim.

 

[writhziden]

Understandable; I was super busy yesterday with work/research, as well. Post back when you get a chance to load the defaults. Best of luck.

 

[monkey314]

So I have two options for loading defaults. Fail-safe default and optimized defaults.

I got another blue screen. File_System 0x00000022. I got it about 20 minutes after putting in my full 4 sticks of RAM. I tested all the sticks in the first and second slot of the motherboard and they all passed the memtest. I think one of the slots (slot 3 or 4) on my motherboard is bad.

I didn't get a minidump because it froze in the middle of the blue screen. I got the exact same event viewer item. kernel-power, event id 41, task category 63

 

[writhziden]

Alright, see if you get crashes with two modules running in slots 1 and 2. Then if you do not, check 3 and 4 with the same two modules. Let the system run by doing your normal routine for twice as long as it normally (on average) takes for you to get a crash. Post back how these tests go.

 

[monkey314]

You gotta be kidding me. Another blue screen. this time I wasn't home so I didn't get to see the message. And again, no minidump was created.

AND! another problem. Now my windows gadgets and ati's CCC.exe will just randomly stop working (both at the exact same time). It's a brand new problem. This has never happened before ever.

 

[writhziden]

This is starting to sound like software. Have you tried the steps to http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html?


You may also want to check for Windows corruption.

Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors with a restart in between each. Post back if it continues to show errors after a fourth run or if the first run comes back with no integrity violations. Use OPTION THREE of http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html to provide us with the sfcdetails.txt file if errors occur.


Have windows check your file system with a http://www.sevenforums.com/tutorials/433-disk-check.html

 

[monkey314]

Another brand new issue, my computer saw 4GB but only 2GB was usable. I can't run a disk check it says the type of file system is RAW. This is driving me nuts.

 

[writhziden]

It is never good when the system drive is suddenly seen as RAW. Can you post a screenshot of your Disk Management?

Start Menu -> Right click Computer -> Manage -> Disk Management (from the list on the left).

 

[monkey314]

More information. System maintenance keeps popping up. I scanned for issues and it came up with "disk volume errors" It says fix on reboot, but that's it. It doesn't do it by itself on restart. I've ran sfc /scannow twice with no integrity violations.

 

[monkey314]

 

[writhziden]

And you get the RAW message trying to run a disk check on C: ? Something is not right if that is the case... I have never seen that before.

Use http://www.sevenforums.com/tutorials/666-advanced-boot-options.html to select Repair Your Computer and get to the http://www.sevenforums.com/tutorials/668-system-recovery-options.html. Then select the command prompt. Do the following:

chkdsk /r c:
chkdsk /r d:
chkdsk /r e:
chkdsk /r f:​

.etc until you get the message that the volume could not be opened for direct access. For any drives that do not give the message:
Windows has checked the file system and found no problems
run chkdsk again as above. In other words, if it says:
Windows has made corrections to the file system
after running the disk check, run the disk check again.

I realize you may only have one disk show up in Windows explorer, but you may have more than one disk through recovery options. This is because the system creates a hidden boot partition (which will be C: in recovery), you may have a recovery partition for your PC that is hidden (which will be D: in recovery), and you will have your primary Windows partition (which may be E: in recovery). A custom PC will likely have at least C: and D: to scan.

 

[monkey314]

Oh, I have many many more hard drives and partitions. I kept my hard drives from my old computers because... why not and I kinda went crazy with buying hard drives when they were crazy cheap before the floods in Taiwan. I'm running chkdsk through a recovery disk I'm assuming that's ok. I'll run it again and unplug all my other drives.

 

[monkey314]

I have no idea if this is relevant, but when the blue screens first started (and it's still happening now) I would get a popup showing waiting for programs to close when I was shutting down my computer. I don't remember getting that unless a program was being really really stubborn about closing. And now it does it every time I shut down. It'll even show the message when there's no programs waiting be closed. It'll just be blank area where a list of programs should be listed.

 

[monkey314]

ummm so one thing I noticed when I booted into recovery it said that the operating system is located on disk J: if I had all my hard drives plugged in (WRONG!). Now with all of them unplugged it says the partition with the operating system is disk D: (STILL WRONG).

So in other words. The recovery CD says the operating system is located on a different partition than what windows explorer says.

This is really making my head hurt...

 

[writhziden]

The recovery environment does not show the system location the same way that Windows Explorer does. It is semi-random, but typically based on where partitions reside and disks reside. For instance, on my system, this is how it typically shows up:

View attachment 210561

The red letters are what the recovery environment sees for my partitions. The black letters are what Windows Explorer shows.

 

[monkey314]

Got a blue screen in the middle of the repair. Memory_management.

hurray... at least it was able to boot

 

[writhziden]

Hmmm... You were in the recovery environment, correct?

Getting a blue screen outside the Windows installation typically indicates hardware issues.

 

[monkey314]

Yep. Booted to the recovery CD. I'm running memtest86 like a madman. I also noticed my computer is now booting lightning quick. I don't know why. I know I unplugged them (my extra hard drives) before during troubleshooting and it didn't make a difference in boot time. Also, memtest86 seems to be testing my CPU...