Driver Verifier-- tracking down a mis-behaving driver.

Technical Level : Intermediate

Driver verifier is a utility built into the OS (Vista, WIN 7, Win 8, and win 10) that will often find the driver/drivers that are the underlying cause of BSOD/Crashes It is an "iffy" proposition because it will not ALWAYS tell us which driver it was, but it is the best way to narrow down the possibilities

Most times it will crash and tell you what the driver is, but sometimes it will crash and not tell you the driver.

Other times it will crash before you can log in to Windows. In Any case please note what you see on the screen and upload the DMP files to us for analysis. 

I'd suggest that you first backup your data just in case

You should not be running verifier in safe mode because many drivers do not load in safe mode.    If you want to add safe mode to the boot menu You can enable this here

Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Be sure you can get back into safe mode to turn off verifier or you may may brick your computer  The command to turn verifier off is
verifier /reset launched from an elevated command prompt

Here is the procedure:
Go to Start and type in "verifier" (without the quotes) and press Enter (win 10 may be different when it is released)
Select "Create custom settings (for code developers)" and click "Next"

Select everything.  For Win 8 and win 10  dont checkDDI compliance checking and randomized low resource simulation, then click "Next"

 "Select driver names from a list" and click "Next"

Then select all drivers NOT provided by Microsoft and click "Next"

Select "Finish"

Please make sure it is running by opening an elevated command prompt and typing verifier /querysettings  It should return a list of drivers (we do not care which ATM).  If it does not it is NOT running

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.

When it crashes use these instructions to find & upload the log files (called DMP files) to us

When it crashes it will say something like DRIVER_VERIFIED_DETECTED_VIOLATION (xxxxx.sys)  The xxxx.sys is the name of the driver that caused the crash.  If it is listed please note it and tell us what it is.

If you can't get into Windows because it crashes too soon, try it in Safe Mode. (For win 8 try msconfig here is how) and to disable verifier type the following.  Verifier /reset

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.

Further Reading

About Driver Verifier

When the problem has been fixed be sure to turn off verifier by typing verifier /reset from an elevated command prompt

‘If you have a question about this topic, Ask the community’. 

If this wiki has proved helpful please click me too at the bottom of the wiki.

Other Wiki's you may be interested in

System file check (SFC)  Scan & repair System files

Email Systems... Differences explained
BugCheck Code 124

Backing up your important email data .

BCC101 Clock watchdog timeout Troubleshooting

Event Viewer What's going on in your computer?

Updating drivers

BCC116/7 Your video driver has stopped

HD Checking how to test yours

Driver View A very handy utility for examining drivers

Safe mode in win 10 (before you need it)

Outlook Mail (also known as Outlook on the web)

Co-Authored JMH3143/ ZigZag3143

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Reply In reply to deleted message
This is only for comments on the wiki.  If you have started a thread post this there.  If you have not start one.

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
Excellent Work !!!
MicrosoftMVP.Support Engineer@IBM-Directory Service & Exchange(,MCSE. MCP .MCSA, CCNA ,RHCE)

Please be sure to use punctuation, as some instructions like this "Select everything EXCEPT FOR "Low Resource Simulation" For Win 8 dont check Concurrency stress test, and DDI compliance checking click "Next"" can get pretty confusing without it.

Thank you helpfuls wiki :)
Bu ileti veya öneriler size yardımcı olduysa “Yanıt olarak işaretle” linkine tıklatınız.
Reply In reply to deleted message

Hi MatheusMarquesS

This area is for comments on the Wiki only.

Please start your own thread to seek help in the appropriate Forum category.

Microsoft MVP.
Windows Consumer Apps,
Windows Experience,
Windows Insider.

To confirm that Driver Verifier is running, should one type verifier /query ? Or verifier /querysettings ?

I tried the first command and it tells me "No drivers are currently verified". However, typing the second command gives me a list of drivers.


Either will work.  If query says no drivers are being verified, then verifier /querysettings will also (see snip)

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT

Hmm. Ok.

When I was in safe mode, for some reason /querysettings would give me a list of drivers, but /query would give nothing.

Once I exited safe mode, both /query and /querysettings gave me the list.


You should not run it in safe mode because half the drivers are not loaded in safe mode.  You want to find the driver that is mis-behaving and if it does not load in safe mode it will not crash the system (which is what we want)

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT

I see. That makes sense.

In red text at the top of this wiki, it says to run in safe mode for Win 8; this is why I was in safe mode.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.


Forum Article Info

Last updated November 29, 2020 Views 848,241 Applies to: