Persistent BSOD - various exception codes

Hi,

This is quite a complicated one, I think. About a year ago, my dad and I decided to update our old household PC. We bought a new motherboard, new processors, new RAM, new graphics card - everything. Since then I've had the occasional BSOD, maybe once a week - never with a regular cause that I can see - and every time decided that trying to sort it out was for another day. Well, today I've had four BSODs, and enough is enough. If hardware information is required, then just say and I'll upload it.

Exception codes are numerous but the most common is 0xc0000005.

Computer information:

- Windows 7 Professional X64
- Full retail
- Hardware setup is roughly a year old.
- If memory serves, the OS has not been re-installed since then.

robbro7 said:

Hi,

This is quite a complicated one, I think. About a year ago, my dad and I decided to update our old household PC. We bought a new motherboard, new processors, new RAM, new graphics card - everything. Since then I've had the occasional BSOD, maybe once a week - never with a regular cause that I can see - and every time decided that trying to sort it out was for another day. Well, today I've had four BSODs, and enough is enough. If hardware information is required, then just say and I'll upload it.

Exception codes are numerous but the most common is 0xc0000005.

Computer information:

- Windows 7 Professional X64
- Full retail
- Hardware setup is roughly a year old.
- If memory serves, the OS has not been re-installed since then.

These crashes were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


1-Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5 or 6 passes.

Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.

Test the sticks individually, and if you find a good one, test it in all slots.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.

Driver Verifier - Enable and Disable