This special pool is monitored for memory overruns, memory underruns, and memory that's accessed after it's freed. When this option is active, Driver Verifier allocates most of the driver's memory requests from a special pool. Dereferencing an object that already has a reference count of 0.Trying to call KeWaitXxx at IRQL >= DISPATCH_LEVEL.Verifies that the driver doesn't have pending operations while unloading, such as pending DPCs or worker threads.Freed allocations aren't pointing to active timer objects.No random (uninitialized) values are specified to these application programming interfaces (APIs).Non-paged pool allocations/frees are made at the correct IRQL (DISPATCH_LEVEL or below).Paged pool allocations/frees are made at the correct IRQL (APC_LEVEL or below).Spin lock acquisitions/releases are made at the appropriate IRQL.A lowered IRQL (meaning that the current IRQL is more than the target IRQL).

A raised IRQL (meaning that the current IRQL is less than the target IRQL).These checks are always done on a driver that's being verified, no matter what options have been selected. These options are enabled when you choose to enable standard settings in the Driver Verifier GUI or you specify the /standard switch when you configure Driver Verifier by using the command line. The following options together represent the rules that all drivers in the system shouldn't violate. They represent similar concepts.)įor detailed information about each flag, see Driver Verifier options and rule classes. (The terms options, settings, and flags are typically interchangeable in Driver Verifier documentation. These capabilities are grouped into options or settings that are enabled by the use of flags. Your user account requires Administrator privileges to run Verifier.exe.ĭriver Verifier can check many different aspects of a driver's behavior. You don't have to make any other changes to begin analyzing drivers in the system. To use Driver Verifier, run Verifier.exe, and then restart your computer.

This article describes how to use Driver Verifier to isolate and troubleshoot a driver in the system.Īpplies to: Windows Server 2012 Foundation, Windows Server 2012 Essentials, Windows Server 2012 Standard, Windows Server 2012 Datacenter Original KB number: 244617 Driver Verifier capabilities It's used to detect and troubleshoot many driver issues that are known to cause system corruption, failures, or other unpredictable behavior. The Driver Verifier tool is included in every version of Windows since Windows 2000.

How to install granblue fantasy android