Enabling Driver Verifier for the graphics drivers is identical to the other drivers. For more information, see the Enable Driver Verifier section. Unsupported flags such as IRQL checking are ignored. In addition, you can use the! You should only use the random allocation failure setting for robustness testing. Use of this setting may cause rendering error messages, so you should not use this setting with verification tests to check the correctness of the graphics driver's implementation for example, by comparing the graphics driver output to a reference image.
The Driver Verifier Manager tool Verifier. Start the Driver Verifier Manager by using verifier. Whenever switches are included, the command-line based version of the utility is used. For help with configuring Driver Verifier, run verifier. The Driver Status property page gives you an image of the current status of Driver Verifier.
You can see what drivers the verifier detects. The status can be one of the following values:. Select the list header to sort the list by driver names or status. In the upper-right area of the dialog box, you can view the current types of the verification that are in effect.
The status of the drivers is updated automatically if you don't switch to manual refresh mode. You can modify the refresh rate using the radio buttons in the lower-left area of the dialog box.
To force an update of the status, select Update Now. If you enable the Special Pool flag, and less than 95 percent of the pool allocations went to the special pool, a warning message is displayed on this page. It means that you need to select a smaller set of drivers to verify, or add more physical memory to the computer to obtain better coverage of the pool allocations verification.
This property page shows the current value of some counters maintained by Driver Verifier. A zero value for a counter can indicate that the associated Driver Verifier flag isn't enabled.
You can monitor the activity of the verifier because the values of the counters are updated automatically by default. You can change the refresh rate, switch to manual refresh, or force a refresh using the group of controls in the lower-left area of the dialog box. This property page shows more statistics gathered from Driver Verifier.
All of the counters shown on this page are related to the Pool Tracking flag of the verifier. Most of them are per-driver counters, such as current allocations, current allocated bytes, and so on. You must select a driver name from the top combination box to view the counters for that specific driver. You can use this page to create and modify Driver Verifier settings.
The settings are saved in the registry and you must restart the computer for the settings to take effect. You can use the list to view the currently installed drivers. Each driver can be in one of the following states:. You can select one or several drivers from the list and switch the status using the two buttons under the list. You can also right-click a driver name to display the context menu, which lets you perform state toggling.
In the bottom of the dialog box, you can specify more drivers separated by spaces that you want verified after the next restart. You typically use this edit control when you want to install a new driver that is not already loaded. If the radio button group on the top of the list is set to Verify all drivers , the list and the Verify and Don't Verify buttons and the edit control are unavailable.
It means that after the next restart, all the drivers in the system are verified. You can set the verification type using the check boxes in the upper-right area of the dialog box. Level 2 verification is stronger than level 1. Random failures are supported for the following graphics DDI callback functions:. In addition, the use of special pool and pool tracking is supported for EngAllocMem.
Enabling Driver Verifier for the graphics drivers is identical to the other drivers refer to the "Enabling Driver Verifier" section of this article for additional information. Unsupported flags such as IRQL checking are ignored. In addition, you can use the!
NOTE: You should only use the random allocation failure setting for robustness testing. Use of this setting may cause rendering error messages, so you should not use this setting with verification tests to check the correctness of the graphics driver's implementation for example, by comparing the graphics driver output to a reference image.
The Driver Verifier Manager tool Verifier. Start the Driver Verifier Manager by using verifier. Whenever switches are included, the command-line based version of the utility is used. For help with configuring Driver Verifier, run verifier.
The Driver Status property page gives you an image of the current status of Driver Verifier. You can see what drivers the verifier detects. The status can be one of the following:. Unloaded: The driver is not currently loaded but it was loaded at least once since you restarted the computer. Never Loaded: The driver was never loaded. This status can indicate that the driver's image file is corrupted or that you specified a driver name that is missing from the system.
You can click the list header to sort the list by driver names or status. In the upper-right area of the dialog box, you can view the current types of the verification that are in effect.
The status of the drivers is updated automatically if you do not switch to manual refresh mode. You can modify the refresh rate using the radio buttons in the lower-left area of the dialog box. You can also force an update of the status by clicking Update Now.
If you enable the Special Pool flag and less than 95 percent of the pool allocations went to the special pool, a warning message is displayed on this page.
This means that you need to select a smaller set of drivers to verify or add more physical memory to the computer to obtain better coverage of the pool allocations verification. The Global Counters property page shows the current value of some counters maintained by Driver Verifier.
A zero value for a counter can indicate that the associated Driver Verifier flag is not enabled. You can monitor the activity of the verifier because the values of the counters are updated automatically by default.
You can change the refresh rate, switch to manual refresh, or force a refresh using the group of controls in the lower-left area of the dialog box. This property page shows more statistics gathered from Driver Verifier. All of the counters shown on this page are related to the Pool Tracking flag of the verifier.
Most of them are per-driver counters for example, current allocations, current allocated bytes, and so on. This means you must select a driver name from the top combination box to view the counters for that specific driver.
You can use this page to create and modify Driver Verifier settings. The settings are saved in the registry and you must restart the computer for the settings to take effect. You can use the list to view the currently installed drivers.
Each driver can be in one of the following states:. Verify Disabled Reboot Needed : The driver is currently verified but is not verified after the next restart. You can select one or several drivers from the list and switch the status using the two buttons under the list. You can also right-click a driver name to display the context menu, which lets you perform state toggling.
In the bottom of the dialog box, you can specify additional drivers separated by spaces that you want verified after the next restart.
You typically use this edit control when you want to install a new driver that is not already loaded. If the radio button group on the top of the list is set to Verify all drivers, the list and the Verify and Don't Verify buttons and the edit control are unavailable. This means that after the next restart, all the drivers in the system are verified. You can set the verification type using the check boxes in the upper-right area of the dialog box. Level 2 verification is stronger than level 1.
You must save any modification to the settings by clicking Apply. There are two more buttons in this page:. For example:. RuleID is always the first argument to the bug check. Driver Verifier: What's New. Driver Verifier Command Syntax. Controlling Driver Verifier. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.
Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Caution Running Driver Verifier could cause the computer to crash.
You should only run Driver Verifier on computers that you are using for testing and debugging. You must be in the Administrators group on the computer to use Driver Verifier.
Submit and view feedback for This product This page. View all page feedback. In this article. In most cases, you will want to specify which drivers to test.