DDI compliance checking
The Device Driver Interface (DDI) compliance checking option determines whether the driver correctly interacts with the Windows operating system kernel.
Note This option is available starting with Windows 8. Starting in Windows 8.1, you can test additional rules, by selecting Activating the DDI compliance checking (additional) option.
| DDI compliance checking |
|---|
The DDI compliance checking option applies the same device driver interface (DDI) usage rules that Static Driver Verifier uses to verify that your driver makes function calls at the required IRQL for the function, or correctly acquires and releases spinlocks.
When this option is active and Driver Verifier detects that the driver violates one of the DDI compliance rules, Driver Verifier issues bug check 0xC4 (with Parameter 1 equal to the identifier of the specific compliance rule).
When you select the DDI compliance checking option, the following rules are included.
GuardedRegions (Starting in Windows 8.1)
IoSetCompletionExCompleteIrp (Starting in Windows 8.1)
IrqlReturn (Starting in Windows 8.1)
NdisOidComplete (Starting in Windows 8.1)
NdisOidDoubleComplete (Starting in Windows 8.1)
PnpRemove (Starting in Windows 8.1)
RequestedPowerIrp (Starting in Windows 8.1)
QueuedSpinLock (Starting in Windows 8.1)
SpinLock (Starting in Windows 8.1)
These two rules are currently optional, but recommended.
(Optional) IrqlNtifsApcPassive
Activating the DDI compliance checking option
You can activate the DDI compliance checking feature for one or more drivers by using Driver Verifier Manager or the Verifier.exe command line. For details, see Selecting Driver Verifier Options. You must restart the computer to activate or deactivate the DDI compliance checking option. The DDI compliance checking feature is activated when you use the standard settings (/standard).
At the command line
At the command line, DDI compliance checking is represented by verifier /flags 0x00020000 (Bit 17). To activate DDI compliance checking, use a flag value of 0x00020000 or add 0x00020000 to the flag value. For example:
verifier /flags 0x00020000 /driver MyDriver.sysThe feature will be active after the next boot.
Using Driver Verifier Manager
- Start Driver Verifier Manager. Type Verifier in a Command Prompt window.
- Select Create custom settings (for code developers) and then click Next.
- Select Select individual settings from a full list.
- Select (check) DDI compliance checking.
- Restart the computer.
| DDI compliance checking (additional) |
|---|
Starting in Windows 8.1, the DDI compliance checking (additional) option option provides additional rules to determine whether the driver correctly interacts with the Windows operating system kernel. When you select the DDI compliance checking (additional) option, the following rules are tested:
Activating the DDI compliance checking (additional) option
Note
This check is deprecated starting in Windows 10 Build 19042 and above
You can activate the DDI compliance checking (additional) rules for one or more drivers by using Driver Verifier Manager or the Verifier.exe command line. For details, see Selecting Driver Verifier Options. You must restart the computer to activate or deactivate the DDI compliance checking (additional) option.
At the command line
At the command line, DDI compliance checking is represented by verifier /flags 0x00080000 (Bit 19). To activate DDI compliance checking (additional), use a flag value of 0x00080000 or add 0x00080000 to the flag value. For example:
verifier /flags 0x00080000 /driver MyDriver.sysThe feature will be active after the next boot.
Using Driver Verifier Manager
- To start Driver Verifier Manager, type Verifier in a Command Prompt window.
- Select Create custom settings (for code developers) and then click Next.
- Select Select individual settings from a full list.
- Select (check) DDI compliance checking (additional).
- Restart the computer.
Activating the DDI compliance checking (additional IRQL) option
You can activate the DDI Compliance additional IRQL rules for one or more drivers by using the Verifier.exe command line. For details, see Selecting Driver Verifier Options. You must restart the computer to activate or deactivate the DDI Compliance additional IRQL rules.
At the command line, DDI Compliance additional IRQL checking is represented by a rule class value of 35. For example:
verifier /ruleclasses 35 /driver MyDriver.sys
OR
verifier /rc 35 /driver MyDriver.sys
The additional IRQL rule set consists of the following two rules.