Multiple BSOD, Different Every Time. Memtest Passes.

[SkurvyPirate]

So over the past few months I have started getting blue screens. It started out slow, then got more and more progressive. I have run memtest a number of time and let it run for 24+ hours with no errors. I have reinstalled windows twice. It seems like I go for a while with no problems then one day it will crash a bunch of times. Today it kept crashing a few minutes after startup with errors like "Modification of system code or a critical data structure was detected" and common ones like "Bad pool header" or something.

I am really at a loss because I haven't installed any new hardware recently, all I can think of is Avira is causing it, but it used to work fine for years so I don't know....

I have attached the logs, any suggestions or ideas is greatly appreciated! Its getting annoying haha.

Thanks!

 

[JMH]

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


If you are overclocking anything reset to default before running these tests.
In other words STOP!!!


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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html



2-Driver verifier

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable 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.

http://www.sevenforums.com/tutorials/101379-driver-verifier-enable-disable.html


Further Reading

Using Driver Verifier to identify issues with Windows drivers for advanced users

 

[SkurvyPirate]

1) I have run Memtest+ multiple times for 40+ hours and it has reported no errors.
2) Driver verifier has been active for 24 hours and no crashes yet.

 

[JMH]

1) I have run Memtest+ multiple times for 40+ hours and it has reported no errors.
.

Ah!
> > But did you run it as requested this time??? {AFTER your DMP had been analyzed}

 

[SkurvyPirate]

You caught me, I did not. Due to the previous runs that I have done I ruled it out. I will run it again for 24+ hours and report back...

 

[JMH]

Thank you!