Using Driver Verifier to identify issues with Drivers

You may try a startup repair: Startup Repair

While you're in the recovery environment, open up a command prompt and enter:

Code:

chkdsk /r

pdxuser said:

Ok, I followed the instructions, got the BSOD and restored my machine. Now what? How do I tell which driver is the culprit?

Hello,

You might create a jcgriff2 report and upload it for one of us to debug: https://www.sevenforums.com/crashes-d...tructions.html

Very nice,
Just wondering - What could cause a driver to suddenly go corrupt?

Best Regards,
FredeGail

A driver itself won't "go corrupt" like that. Usually, it's updates to Windows or programs that cause conflicts or incompatibilities with existing drivers. Every now and then, you'll see someone who just reinstalled the same version of the driver, and the problem was solved. I expect those are caused by other programs changing some setting, such as a registry cleaner.

Jonathan_King said:

A driver itself won't "go corrupt" like that. Usually, it's updates to Windows or programs that cause conflicts or incompatibilities with existing drivers. Every now and then, you'll see someone who just reinstalled the same version of the driver, and the problem was solved. I expect those are caused by other programs changing some setting, such as a registry cleaner.

I see, thank you.

Best Regards,
FredeGail

I'm trying to identify the driver that's causing my system to crash. When I run driver verifier with everything except the microsoft drivers checked, it crashes with a BSOD saying that a driver was caught, but it doesn't tell me the driver. When I try and run with all drivers checked (including microsoft drivers), windows freezes on startup and I have to press the power button to restart it. No BSOD comes up.

What does this mean? Does it mean that one of the microsoft drivers is corrupt and it's not detecting it because it was unchecked when I ran driver verifier when I got the BSOD? Or is it a problem with the non-microsoft drivers?

Would checking 1 driver at a time and waiting for it to crash on each one tell me specifically which driver is causing the problem? Or can it crash with the "driver caught" BSOD without it being checked meaning this process this is a waste of time?

I really want to find the cause of this.

main thread for my issue is here:

https://www.sevenforums.com/crashes-d...bccode-1e.html

EmperorNortonI said:

I'm trying to identify the driver that's causing my system to crash. When I run driver verifier with everything except the microsoft drivers checked, it crashes with a BSOD saying that a driver was caught, but it doesn't tell me the driver. When I try and run with all drivers checked (including microsoft drivers), windows freezes on startup and I have to press the power button to restart it. No BSOD comes up.

What does this mean? Does it mean that one of the microsoft drivers is corrupt and it's not detecting it because it was unchecked when I ran driver verifier when I got the BSOD? Or is it a problem with the non-microsoft drivers?

Would checking 1 driver at a time and waiting for it to crash on each one tell me specifically which driver is causing the problem? Or can it crash with the "driver caught" BSOD without it being checked meaning this process this is a waste of time?

I really want to find the cause of this.

main thread for my issue is here:

https://www.sevenforums.com/crashes-d...bccode-1e.html

Posted there..!

Thanks for the tutorial Capt. :)

seth500 said:

Thanks for the tutorial Capt. :)

Your Welcome! :)