BSOD on startup, several startups and repairs required to boot Windows

I don't know what just happened but my desktop just went nuts with errors. Everything error out and error reports were flying like mad. Could this be related to the changes? I didn't change anything other than the volts.

Attached are the minidumps:

Analysis:

Crashes still point to memory. Given the extent of the crashes and what you have described for repairs, I suspect a bad module is at work.

Test the memory slots and modules as follows.

1. Shut down and turn off your computer.
2. Unplug all power sources to the tower (unplug the power from the outlet/surge protector or PSU).
3. Hold down the power button for 30 seconds (for your safety and the safety of the components) to close the circuit and drain all power from components.
4. Remove the casing.
5. Remove all but one memory module making sure you are grounded while doing so.
6. Replace the casing and put the remaining memory modules in a safe, static free environment.
7. If the problem persists, repeat steps 1-4 and move the memory module to another slot (while staying grounded, of course).

Do this until all slots have been tested. If all slots fail, the memory module may be bad. Test with one of the remaining modules. Continue one module at a time in one slot at a time until you find a good module and good slot. Test remaining modules in the good slot, test good modules in other slots to find bad slots, etc.


Test by doing your normal routine in Windows for twice as long as it takes to get a crash or until you get a crash, whichever comes first. You can also test by doing the tasks that generally cause crashes.

Wow, you really have 11,000 posts! Wow, I'll try your steps but had to comment

I was trying your steps yesterday and decided to run Memtest one more time overnight on the first stick of RAM. No errors came up. However, when I tried restarting chkdsk came up and populated several lines of

"Deleting Corrupt Attribute Record......"
"Recovering Orphaned File...."
"Inserting Data attribute into file....."

Is something corrupt? I don't see any minidumps associated from it and from what I can tell my files look okay.

I was literally typing my "Resolved" post when I got another BSOD....

For sure one stick is bad. I put too much faith in Memtest. Each slot gave a BSOD on startup for the first stick. I tested one a day for the last week and a half as my problems came when the computer was off for an extended period of time. The second stick was able to boot into Windows without any problems in each slot. Today was the last test and it booted fine.

I was just downloading a few updates, specifically a new AMD video drivers from the Vision Center, when everything crashed. This happened twice today and I've attached the minidumps.

Any thoughts? Should I buy entirely new RAM or is this related to a different issue like the video card? I'm extremely happy that I'm able to boot without error as I've never been able to do that. However, it seems as though the problem is not fully resolved.

Or would anything be related to the "Deleting Corrupt Attribute Record" that I typed earlier? I've been testing my hard drive and it looks okay. However, I have noticed certain things are either gone or partially missing.

Do I need to re-install something?

writhziden said:

Analysis:

Crashes still point to memory. Given the extent of the crashes and what you have described for repairs, I suspect a bad module is at work.



Test the memory slots and modules as follows.

1. Shut down and turn off your computer.
2. Unplug all power sources to the tower (unplug the power from the outlet/surge protector or PSU).
3. Hold down the power button for 30 seconds (for your safety and the safety of the components) to close the circuit and drain all power from components.
4. Remove the casing.
5. Remove all but one memory module making sure you are grounded while doing so.
6. Replace the casing and put the remaining memory modules in a safe, static free environment.
7. If the problem persists, repeat steps 1-4 and move the memory module to another slot (while staying grounded, of course).

Do this until all slots have been tested. If all slots fail, the memory module may be bad. Test with one of the remaining modules. Continue one module at a time in one slot at a time until you find a good module and good slot. Test remaining modules in the good slot, test good modules in other slots to find bad slots, etc.


Test by doing your normal routine in Windows for twice as long as it takes to get a crash or until you get a crash, whichever comes first. You can also test by doing the tasks that generally cause crashes.

I found that one module is fine and the slots don't seem to be the problem yet. Did you have any feedback?

I think writhziden is MIA, does anyone have any ideas?