Edit

DDI Compliance Rules

  • Article

This section lists and describes the Windows Device Driver Interface (DDI) Compliance Rules that you can use to verify Windows Driver Model (WDM), Kernel Mode Driver Framework (KMDF), Audio (PortCls), AVStream (KS), NDIS, and Storport drivers. The DDI Compliance rules define requirements for the proper interaction between a driver and the kernel interface of the operating system.

Rules for Audio Drivers
Rules for AVStream Drivers
Rules for WDM Drivers
Rules for KMDF Drivers
Rules for NDIS Drivers
Rules for Storport Drivers

Important

Windows Hardware Compatibility Program requires CodeQL for Static Tool Logo (STL) Tests on our Client and Server Operating Systems. We will continue to maintain support for SDV and CA on older products. Partners are highly encouraged to review the CodeQL requirements for the Static Tool Logo Test. For more information about using CodeQL, see CodeQL and the Static Tools Logo Test.

Driver Verification Tools

You can use the code analysis tools, Static Driver Verifier and Driver Verifier to test a driver for compliance to the DDI usage rules. Static Driver Verifier (SDV) performs static analysis on the driver source code, so you can use SDV early in development cycle. Driver Verifier is integrated with the operating system, so you can test a driver at runtime after it has been built, deployed, and installed.

Using the driver source code, Static Driver Verifier creates a model of the driver and the operating system. In this model, SDV places the driver in a hostile environment and systematically tests code paths through the driver by looking for violations of a formalized set of the driver compliance rules (Static Driver Verifier rules).

Starting in Windows 8, you can configure Driver Verifier to run some of the same compliance checks on installed drivers by enabling DDI compliance checking.

Driver Verifier

Static Driver Verifier