Driver Verifier Command Syntax

The following syntax is used when running the Verifier utility in a Command Prompt window.

You can type several options on the same single line. For example:

verifier /flags 7 /driver beep.sys disksdd.sys

Windows 11 Syntax

You can use the /volatile parameter with some Driver Verifier /flags options. For details, see Using Volatile Settings.

  verifier /standard /all
  verifier /standard /driver NAME [NAME ...]
  verifier {/ruleclasses | /rc | dif} <options> [<ruleclass_1> <ruleclass_2> ...] /all
  verifier {/ruleclasses | /rc | dif} <options> [<ruleclass_1> <ruleclass_2> ...] /driver NAME [NAME ...]
  verifier /flags <options> /all
  verifier /flags <options> /driver NAME [NAME ...]
  verifier /rules [OPTION ...]
  verifier /dif [<ruleclass_1> <ruleclass_2> ...] /now /driver NAME [NAME ...]
  verifier /query
  verifier /querysettings
  verifier /bootmode [persistent | resetonbootfail | resetonunusualshutdown | oneboot]
  verifier /bc <number_of_reboots>
  verifier /reset
  verifier /faults [Probability] [PoolTags] [Applications] [DelayMins]
  verifier /faultssystematic [OPTION ...]
  verifier /log LOG_FILE_NAME [/interval SECONDS]
  verifier /volatile /flags <options>
  verifier /volatile /adddriver NAME [NAME ...]
  verifier /volatile /removedriver NAME [NAME ...]
  verifier /volatile /faults [Probability] [PoolTags] [Applications] [DelayMins]
  verifier /domain <types> <options> /driver ... [/logging | /livedump]
  verifier /logging
  verifier /livedump
  verifier /?
  verifier /help

Windows 10 Syntax

You can use the /volatile parameter with some Driver Verifier /flags options and with /standard. You cannot use /volatile with the /flags options for DDI compliance checking, Power Framework Delay Fuzzing or Storport Verification. For details, see Using Volatile Settings.

  verifier /standard /all
  verifier /standard /driver NAME [NAME ...]
  verifier {/ruleclasses | /rc} <options> [<ruleclass_1> <ruleclass_2> ...] /all
  verifier /flags <options> /all
  verifier /flags <options> /driver NAME [NAME ...]
  verifier /rules [OPTION ...]
  verifier /query
  verifier /querysettings
  verifier /bootmode [persistent | resetonbootfail | resetonunusualshutdown | oneboot]
  verifier /reset
  verifier /faults [Probability] [PoolTags] [Applications] [DelayMins]
  verifier /faultssystematic [OPTION ...]
  verifier /log LOG_FILE_NAME [/interval SECONDS]
  verifier /volatile /flags <options>
  verifier /volatile /adddriver NAME [NAME ...]
  verifier /volatile /removedriver NAME [NAME ...]
  verifier /volatile /faults [Probability] [PoolTags] [Applications] [DelayMins]
  verifier /domain <types> <options> /driver ... [/logging | /livedump]
  verifier /logging
  verifier /livedump
  verifier /?
  verifier /help

Windows 8.1 Syntax

You can use the /volatile parameter with some Driver Verifier /flags options and with /standard. You cannot use /volatile with the /flags options for DDI compliance checking, Power Framework Delay Fuzzing, Storport Verification. For details, see Using Volatile Settings.

  verifier /standard /all
  verifier /standard /driver NAME [NAME ...]
  verifier /flags <options> /all
  verifier /flags <options> /driver NAME [NAME ...]
  verifier /rules [OPTION ...]
  verifier /faults [Probability] [PoolTags] [Applications] [DelayMins]
  verifier /faultssystematic [OPTION ...]
  verifier /log LOG_FILE_NAME [/interval SECONDS]
  verifier /query
  verifier /querysettings
  verifier /bootmode [persistent | disableafterfail | oneboot]
  verifier /reset
  verifier /volatile /flags <options>
  verifier /volatile /adddriver NAME [NAME ...]
  verifier /volatile /removedriver NAME [NAME ...]
  verifier /volatile /faults [Probability] [PoolTags] [Applications] [DelayMins]
  verifier /?

Windows 8, Windows 7 Syntax

You can use the /volatile parameter with some Driver Verifier /flags options and with /standard. You cannot use /volatile with the /flags options for DDI compliance checking, Power Framework Delay Fuzzing, Storport Verification, SCSI Verification or with /disk. For details, see Using Volatile Settings.

verifier [/volatile] [/standard | /flags Options ] [ /all | /driver DriverList ]
verifier /volatile /faults [Probability PoolTags Applications DelayMins] /driver DriverList
verifier /volatile {/adddriver | /removedriver} DriverList
verifier /reset
verifier /querysettings
verifier /query
verifier /log LogFileName [/interval Seconds]
verifier /?

Parameters

Verifier Command-Line Syntax

/all Directs Driver Verifier to verify all installed drivers after the next boot.

/bc <number_of_reboots> Sets the number of reboots for which verification should be active.

This option automatically sets the ResetOnUnusualShutdown boot mode.

/bootmode mode Controls whether the settings for Driver Verifier are enabled after a reboot. To set or change this option, you must reboot the computer.

/dif DifEnabledRule Enable checking using a DIF enabled rule. Checking will take effect the next time the system is rebooted. Added in Windows 11.

/dif DifEnabledRule /now Immediately enable checking using a DIF enabled rule. Enables the rule classes immediately without needing reboot. This option is only valid if no rule classes are already running. See the Windows 11 rule class descriptions for the rule classes capable of immediate activation.

/driver DriverList Specifies one or more drivers that will be verified. DriverList is a list of drivers by binary name, such as Driver.sys. Use a space to separate each driver name. Wildcard values, such as n*.sys, are not supported.

/driver.exclude DriverList Specifies one or more drivers that will be excluded from verification. This parameter is applicable only if all drivers are selected for verification. DriverList is a list of drivers by binary name, such as Driver.sys. Use a space to separate each driver name. Wildcard values, such as n*.sys, are not supported.

/faults Enables the Low Resources Simulation feature in Driver Verifier. You can use /faults in place of /flags 0x4. However, you cannot use /flags 0x4 with the /faults subparameters.

You can use the following subparameters of the /faults parameter to configure Low Resources Simulation.

/faultssystematic Specifies the options for Systematic low resources simulation. Use the 0x40000 flag to select Systematic low resources simulation option.

/flags Options Activates the specified options after the next reboot. This number can be entered in decimal or in hexadecimal (with an 0x prefix) format. Any combination of the following values is allowed.

You cannot use this method to activate the Storport Verification options. For information, see Storport Verification.

/flags VolatileOptions Specifies the Driver Verifier options that are changed immediately without rebooting.

You can use the /volatile parameter with all /flags values.)

Enter a number in decimal or in hexadecimal format (with an 0x prefix).

Any combination of the following values is permitted.

/ruleclasses or /rc <ruleclass_1> <ruleclass_2> ... <ruleclass_k>

The ruleclasses parameter is available starting with Windows Version 1803.

The ruleclasses parameter encompasses a larger set of verification classes than the /flags parameter above. While /flags is limited to a 32 bit bitmap expression, this option can include more than 32 verification classes. Each positive decimal integer represents a verification class. Multiple classes can be expressed by separating each class id with a space character. The following rule classes IDs are available.

Standard Rule Classes

Additional Rule Classes

These rule classes are intended for specific scenario testing. Rule classes marked with (*) require I/O Verification (5) and automatically enable it. Rule classes marked with (**) support disabling of individual rules. Rule classes marked with (***) are in logging mode by default and require /onecheck in order to crash upon violation.

Flags marked with (!) require DIF mode (rule class 36) to be enabled.

Windows 11 Rule Classes

Starting with Windows 11 the following standard rule classes are available. These rule classes are all enabled when using the /standard option.

The /now column indicates which rule classes can be enabled without a reboot using the /dif DifEnabledRule /now option.

Standard Rule Classes

Note that rule class 37 (File System Filter verification) requires that rule class 5 (I/O verification) also be enabled. Please see File System Filter verification for more information about this rule class.

Additional Rule Classes

The following additional rule classes are available.

• The /now column indicates which rule classes can be enabled without a reboot using the /dif DifEnabledRule /now option.
• The Rule classes required column indicates which rule classes must also be enabled to use the given rule class. Note that the /dif command automatically includes rule class 36 (DIF mode) but /ruleclasses and /rc do not.
• Rule classes marked with (**) support disabling of individual rules.
• Rule classes marked with (***) are in logging mode by default and require the /onecheck option to crash upon violation.

/log LogFileName [/interval|Seconds] Creates a log file with name LogFileName. Driver Verifier periodically writes statistics to this file. For details, see Creating Log Files.

If a verifier /log command is typed at the command line, the command prompt does not return. To close the log file and return a prompt, use the CTRL+C key. After a reboot, to create a log, you must submit the verifier /log command again.

/rules Option Options for rules that can be disabled (advanced).

/standard Activates the "standard" or default Driver Verifier options after the next boot. The standard options are Special Pool, Force IRQL Checking, Pool Tracking, I/O Verification, Deadlock Detection, DMA Verification. and WDF Verification The standard options also include Security Checks, Miscellaneous Checks and DDI compliance checking.

/stop Disables rule classes enabled via '/dif /now' to halt verification.

/volatile /flags Changes the settings without rebooting the computer. Volatile settings take effect immediately. You can use the /volatile parameter with the /flags parameter to enable and disable some options without rebooting. You can also use /volatile with the /adddriver and /removedriver parameters to start or stop the verification of a driver without rebooting, even if Driver Verifier is not already running.

Specifies the Driver Verifier options that are changed immediately without rebooting. Only the following flags can be used with volatile:

0x00000004 (bit 2) - Randomized low resources simulation 0x00000020 (bit 5) - Deadlock detection 0x00000080 (bit 7) - DMA checking 0x00000200 (bit 9) - Force pending I/O requests 0x00000400 (bit 10) - IRP logging

For details, see Using Volatile Settings.

/reset Clears all Driver Verifier settings. After the next boot, no drivers will be verified.

/querysettings Displays a summary of the options that will be activated and drivers that will be verified after the next boot. The display does not include drivers and options added by using the /volatile parameter. For other ways to view these settings, see Viewing Driver Verifier Settings.

/query Displays a summary of Driver Verifier's current activity. The Level field in the display is the hexadecimal value of options set with the /volatile parameter. See Monitoring Global Counters and Monitoring Individual Counters for explanations of each statistic.

/domain Types **** Options Controls the verifier extension settings. The following verifier extension types are supported.

The following extension options are supported.

/logging Enables logging for violated rules detected by the selected verifier extensions.

/livedump Enables live memory dump collection for violated rules detected by the selected verifier extensions.

/? Displays command-line help.

For more information about the use of these commands, see Controlling Driver Verifier and Monitoring Driver Verifier.

/help Displays command-line help.

For more information about the use of these commands, see Controlling Driver Verifier and Monitoring Driver Verifier.

Return Codes

The following values are returned after driver verifier has run.

0: EXIT_CODE_SUCCESS

1: EXIT_CODE_ERROR

2: EXIT_CODE_REBOOT_NEEDED