New
#1
Using Driver Verifier to identify issues with Drivers
Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.
The Verifier utility, Verifier.exe, activates and monitors Driver Verifier. This utility is located in the %windir%\system32 directory of Windows.
There are two ways to use the Verifier utility.
- Command line. To use Driver Verifier at the command-line, in a Command Prompt window, type verifier followed by at least one command-line parameter. Refer this link for more info Verifier Command Line
- Driver Verifier Manager. To open the Driver Verifier Manager graphic user interface, in a Command Prompt window, type verifier. Refer this link for more info Driver Verifier Manager (Windows XP and later)
Warning
- Please don't follow these steps without the help/Recommendation of an expert
- If the Driver Verifier finds a violation, it will result in a BSOD
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.
So, 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/Windows 7 Startup Repair feature).
Then, here's the procedure:
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).
- 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 "Force Pending I/O Requests" 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 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.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.
Code:Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):Note: If Norton Antivirus is installed, do not enable Driver Verifier's Deadlock Detection because of the recommendations in Microsoft Knowledge Base article 325672.Code:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel
Information provided by John (usasma)
Thanks to Vir Gnarus for his recommendation here
For more information:
Using Driver Verifier to identify issues with Windows drivers for advanced users
Driver Verifier in Windows 7
Driver Verifier Options
Last edited by Capt.Jack Sparrow; 15 Jun 2013 at 11:06.