|
|
|
When Low Resources Simulation is enabled, Driver Verifier will cause a random selection of the driver's memory allocations to fail. This tests the driver's ability to react properly to low-memory and other low-resource conditions.
To accurately simulate a low-memory condition, these allocation faults are not injected until seven minutes after system startup. Therefore, any driver errors that are exposed by this action should be treated as legitimate run-time problems, not as unrealistic scenarios.
Driver Verifier can verify selected drivers or all drivers at the same time.
The number of times Driver Verifier deliberately fails resource allocations can be monitored. This statistic can be displayed by the Driver Verifier Manager graphical interface, the verifier.exe command line, or in a log file. See Monitoring Global Counters for details.
The kernel debugger extension !verifier can also be used to monitor this statistic. It presents similar information to that of Driver Verifier Manager. In Windows XP and later, the !verifier 0x4 extension will display a log of faults injected by Driver Verifier. For information about debugger extensions, see Debugging Tools for NT-Based Operating Systems.
The Low Resources Simulation option can be activated by using the Driver Verifier Manager graphical interface or the verifier.exe command line. This activation will take effect after the next boot. See Selecting Driver Verifier Options for details.
This option can also be turned on and off without an intervening reboot. See Using Volatile Settings for details.
See Low Resources Simulation for Graphics Drivers for details on how this option affects display drivers and kernel-mode printer drivers.