/standard
switch when you configure Driver Verifier by using the command line.!analyze -v
is the best command to use when starting a new debug session. This command will print out useful information and attempt to pinpoint the faulting driver.!verifier
will dump captured Driver Verifier statistics. !verifier -?
will show all of the available options.!deadlock
dumps information related to locks or objects tracked by the Deadlock detection. !deadlock -?
will show all of the available options.!iovirp [address]
will dump information related to an IRP tracked by I/O Verifier.!ruleinfo [RuleID]
will dump information related to the DDI Compliance Checking rule that was violated (RuleID is always the first argument to the bug check, all DDI Compliance Checking rule IDs are in the form 0x200nn).!gdikdx.verifier
kernel-debugger command to examine current Driver Verifier state and pool traces for graphics drivers.verifier.exe /?
from an Administrator CMD window.verifier /?
output.HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerMemory ManagementVerifyDrivers
REG_SZ
key.REG_SZ
key to the case-insensitive names of the drivers that you want to test. You can specify multiple drivers, but only use one driver. By doing so, you can make sure that available system resources are not prematurely exhausted. Premature exhaustion of resources does not cause any system reliability problems, but it can cause some driver checking to be bypassed.REG_SZ
key:HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerMemory ManagementVerifyDriverLevel