Multiple BSOD randomly (PAGE_FAULT, MEMORY_MANAGEMENT, DRIVER_IRQL...)

If the ram successfully passed 6-8 memtest passes, it is probably ok. It is more likely a driver and running these tests should ID which.

SFC /SCANNOW Command - System File Checker

How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7




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 stuff 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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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.
Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


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.

Thanks to JGriff2 & Usasma.

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

Driver Verifier

Using Driver Verifier (Windows Drivers)

Thanks for response. I'll try all ideas you suggest before posting results

sfc reported errors

Hakama21 said:

sfc reported errors

Was it able to repair them?

didn't repair a font archive... don't think that is the issue right?

Hakama21 said:

didn't repair a font archive... don't think that is the issue right?

Correct. You could even delete the font if it isnt being used by some app.

Uploaded Windows_NT6_BSOD_jcgriff2

Hakama21 said:

Uploaded Windows_NT6_BSOD_jcgriff2

Still memory exception, still a driver. None of the recent Dmps were driver verified

Just got BSOD with verifier, 042512-16988-01 driver verifier attached.
Windows_NT6_BSOD_jcgriff2 archives from this last BSOD attached too.