Multiple BSOD's - Seems Random

Just recently finished my PC build but have gotten numerous BSOD's since booting it up for the 1st time yesterday. Really driving me mad at this stage. They seem to come in at random, couple happened while using the restore function on Steam. One or two happened while updating windows and some happened while watching videos on youtube, browser is the latest of Firefox btw.

Really hope someone can help, have put all my system in my profile, need anymore info then let me know.

Sorry also if I have not included anything in this thread that's needed.

EDIT: Another BSOD happened just after posting so I uploaded a new zip

mursh said:

Just recently finished my PC build but have gotten numerous BSOD's since booting it up for the 1st time yesterday. Really driving me mad at this stage. They seem to come in at random, couple happened while using the restore function on Steam. One or two happened while updating windows and some happened while watching videos on youtube, browser is the latest of Firefox btw.

Really hope someone can help, have put all my system in my profile, need anymore info then let me know.

Sorry also if I have not included anything in this thread that's needed.

EDIT: Another BSOD happened just after posting so I uploaded a new zip

These crashes were caused by memory 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.


**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.

RAM - Test with Memtest86+



**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

If I get errors early in the memtest test, is it necessary to run it for the 7 passes?

mursh said:

If I get errors early in the memtest test, is it necessary to run it for the 7 passes?

Nope if you get errors it is pretty clear. You might want to run the ram one stick at a time to find out which one is bad.

zigzag3143 said:

mursh said:

If I get errors early in the memtest test, is it necessary to run it for the 7 passes?

Nope if you get errors it is pretty clear. You might want to run the ram one stick at a time to find out which one is bad.

Thanks, think I've found the suspect stick. Was the 1st one I tested which was nice, usually when I do this type of thing it's the last one that is the problem. Just about to enable Verifier now, will be back with a status report.

Thanks for the help so far.

mursh said:

zigzag3143 said:

mursh said:

If I get errors early in the memtest test, is it necessary to run it for the 7 passes?

Nope if you get errors it is pretty clear. You might want to run the ram one stick at a time to find out which one is bad.

Thanks, think I've found the suspect stick. Was the 1st one I tested which was nice, usually when I do this type of thing it's the last one that is the problem. Just about to enable Verifier now, will be back with a status report.

Thanks for the help so far.

If your ram failed you may not need to run verifier but it is always a good idea. Just make sure you have a backup

Enabled Verifier, rebooted and got a BSOD. New zip attached.

mursh said:

Enabled Verifier, rebooted and got a BSOD. New zip attached.

Ok the most recent 2 crashes were Related to gdrv.sys Microsoft Register Server.. Since this is an OS file please run a system file check to verify and repair the OS files.

I am assuming the OS has not been moded in any way.


Run a system file check to verify and repair your system files.
To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

It may need to be run up to three times before successful

Read here for more information SFC /SCANNOW Command - System File Checker

Let us know the results from the report at the end.

mursh said:

Nope no mods.

Have run it 3 times now and it's saying there's nothing wrong. Running in safe mode atm, will I disable Verifier and reboot to normal?

Yes but if there is nothing wrong in SFC, there must be something else wrong.