Driver Verifier - Enable and Disable

How to Enable or Disable Driver Verifier in Windows 7​

Contents

• To Enable Driver Verifier
• To Disable Driver Verifier

   Information

Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

OPTION ONE

To Enable Driver Verifier

1. Start typing verifier.exe into the start menu, and open Verifier.



2. Select "Create custom settings (for code developers)", and hit Next.



3. Make sure Standard settings, Force pending I/O requests, and IRP Logging are selected, and hit Next.



4. Select "Select driver names From a list", and hit Next.



5. Click on "Provider" at the top to sort the list by manufacturer; select all drivers not provided by Microsoft Corporation.


6. Press Next, and OK to the resulting window.



After a reboot, driver verifier should be enabled. Use your computer as you normally would, although expect frequent BSODs if there are driver issues. If the system doesn't crash after 24 hours, disable driver verifier.

OPTION TWO

To Disable Driver Verifier

1. Start typing verifier.exe into the start menu, and open Verifier.


​

2. Select "Delete existing settings"

​

If you cannot get into Windows to turn off Verifier, try using Safe Mode.

Related Tutorials

---

• How to Uninstall a Device and Device Driver in Vista and Windows 7
• How to Roll Back a Device Driver in Device Manager

 

[Jonathan_King]

Hello Jonathan,

Should this be run in Safe Mode?

You can enable Driver Verifier from Safe Mode, but it will not actually run in Safe Mode. Thus, if Driver Verifier is preventing system bootup, you can boot into Safe Mode and disable it. To actually test the drivers, reboot into Normal Mode.

 

[Influx]

Hello Jonathan,

Should this be run in Safe Mode?

You can enable Driver Verifier from Safe Mode, but it will not actually run in Safe Mode. Thus, if Driver Verifier is preventing system bootup, you can boot into Safe Mode and disable it. To actually test the drivers, reboot into Normal Mode.

I did hear someone say that it's meant to be run on safe mode. Thanks for clarifying things up Jonathan.

 

[Dave76]

You might consider to add any driver with 'dump' as a prefix to Option one #5, for example; dump_dumpfve.sys and dump_iastor.sys. these should be unchecked also.
They are drivers created to provide disk access during crash dump file generation.

 

[Chronox]

You might consider to add any driver with 'dump' as a prefix to Option one #5, for example; dump_dumpfve.sys and dump_iastor.sys. these should be unchecked also.
They are drivers created to provide disk access during crash dump file generation.

Wow thanks for the info, I tought I wasnt doing anything wrong.

 

[vincent1028]

i've followed all the steps given but i think i ticked dump_dumpfve.sys and dump_iastor.sys.Is it matter?Now i running it for 5 hours already.So should i restart the process?

 

[Dave76]

No, I would leave it running.

If Driver Verifier generates a BSOD and blames dump_dumpfve.sys and/or dump_iastor.sys, then disable them and let it run again.
These two drivers aren't blamed very often, but there isn't any necessity to stress them so they don't need to be included in the testing.

 

[hamine]

This didn't work for me. I applied all settings as described, it said I needed to restart so I told it "OK" and nothing happened. I manually restarted, and it just booted up normally without any special screen or status report for the verification. i tried it again but nothing happened.

What should I do to try and force this to work?

 

[derekimo]

This didn't work for me. I applied all settings as described, it said I needed to restart so I told it "OK" and nothing happened. I manually restarted, and it just booted up normally without any special screen or status report for the verification... I'm having BSODs though so that could be it.

What should I do to try and force this to work?

It's probably working, it just doesn't show anything.

Open a command prompt and enter verifier /query.

This didn't work for me. I applied all settings as described, it said I needed to restart so I told it "OK" and nothing happened. I manually restarted, and it just booted up normally without any special screen or status report for the verification. i tried it again but nothing happened.

What should I do to try and force this to work?

Have a look at the authors response to a previous question like yours.

 

[bash818]

i did this and my computer would lock up everytime i started it up windows would briefly start then log off and lock....why is this?

 

[Raikku]

I tried to use this and that was impossible because my pc crashed with brief flash of bscreen before Windows even started to load. Had to do recovery in there start screen to get normally in Windows. So this verifier-program seem to be quite hazardous to use.

 

[Lostlam]

I tried to use this and that was impossible because my pc crashed with brief flash of bscreen before Windows even started to load. Had to do recovery in there start screen to get normally in Windows. So this verifier-program seem to be quite hazardous to use.

Same thing happened to me. Do you know what might be causing this?

 

[skrillek]

hey i just followed your instructions which are very goodbtw
what will this do? will it test all the drivers i have selected for problem or what?

 

[epson1]

I tried to use this and that was impossible because my pc crashed before Windows even started to load. Had to Go into safe mode to disable Verifier.exe for my PC to boot into windows Any help please..

 

[Useless User]

I tried to use this and that was impossible because my pc crashed before Windows even started to load. Had to Go into safe mode to disable Verifier.exe for my PC to boot into windows Any help please..

That's the whole idea: any bad driver will instantly crash your system and generate a minidump file with crash information, if you enabled minidump files to be written to your Windows folder before using verifier. To switch verifier off, simply boot in Safe Mode open verifier again and disable it.

 

[gixr750]

Ran the verifier and had to restart manually. Upon restart Windows didn't start normally and had to perform a Repair and then a System Restore. Any ideas? :shock:

 

[Useless User]

In the end, in my case, it was bad memory...

 

[gixr750]

I put off the memory test since it's new but there's still the possibility it may be bad. I'll run MEMTEST to check. Thanx for the info.

 

[mikedee]

Hi, I followed the instructions but the computer was unable to restart normally.
I started in Safe Mode and changed the settings back
Not sure where to go from here any advice appreciated
a copy of the Whocrashed report as follows

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Fri 08/08/2014 09:40:31 GMT your computer crashed
crash dump file: C:\Windows\Minidump\080814-16754-01.dmp
This was probably caused by the following module: netbt.sys (netbt+0x24D30)
Bugcheck code: 0xC9 (0xC, 0xFFFFFFFF8891B380, 0xFFFFFFFF9D6B8F68, 0x0)
Error: DRIVER_VERIFIER_IOMANAGER_VIOLATION
file path: C:\Windows\system32\drivers\netbt.sys
product: Microsoft? Windows? Operating System
company: Microsoft Corporation
description: MBT Transport driver
Bug check description: This is the bug check code for all Driver Verifier
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

 

[Brink]

Hello Mike, and welcome to Seven Forums.

See if you may be able to do a system restore (in safe mode or at boot) using a restore point dated before this happened to hopefully undo and fix it for you.

Hope this helps for now,
Shawn

 

[mikedee]

Hi Brink, thanks for your response, I am still working on the problem ( when I do not need the computer )
My next move was to decrease the amount of drivers selected to just the first 10 and the result was the same
Next time I shall limit it to the first 5

Iam also checking/updating drivers