Static Driver Verifier

Static Driver Verifier (also known as "StaticDV" or "SDV") is a static verification tool that systematically analyzes the source code of Windows kernel-mode drivers. SDV is a compile time tool that is capable of discovering defects and design issues in a driver. Based on a set of interface rules and a model of the operating system, SDV determines whether the driver correctly interacts with the Windows operating system kernel.

Installing Static Driver Verifier

Static Driver Verifier is available as part of the Windows Driver Kit (WDK) in both the full WDK experience and in the standalone Enterprise WDK. In addition, the Visual C++ Redistributable Packages for Visual Studio are required for SDV to run. See the following:

• Visual Studio 2019 Redistribution
• Visual C++ Redistributable Packages for Visual Studio 2017
• Visual C++ Redistributable Packages for Visual Studio 2013

For versions of SDV available in the WDK for Windows 10, Version 1809 or earlier, the Visual C++ Redistributable Packages for Visual Studio 2012 should be installed instead of the 2017 packages.

Visual Studio Integration

Static Driver Verifier is integrated into Visual Studio. You can run static analysis on your Visual Studio driver project. You can launch, configure, and control Static Driver Verifier from the Driver menu in Visual Studio.

Static Driver Verifier Documentation

• Static Driver Verifier Known Issues: Lists latest known issues for Static Driver Verifier
• Using Static Driver Verifier to Find Defects in Drivers: Tells you what you need to get started analyzing your driver code in the Visual Studio environment.
• Static Driver Verifier commands (MSBuild): Lists the MSBuild commands to use to run SDV in a Visual Studio Command Prompt window.
• Introducing Static Driver Verifier: Provides an overview of the static analysis tool.
• Using Static Driver Verifier: Provides the details about using and configuring the static analysis tool.
• Static Driver Verifier Report: Describes the viewer that displays the detailed trace of the static code analysis.
• Static Driver Verifier Rules: The rules define the requirements for proper interaction between a driver model and the kernel interface of the operating system.
• Static Driver Verifier Reference: Provides reference information about the function role types, SDV configuration files, error, and warning messages.

Finding Bugs in Windows Driver Code

Microsoft uses SDV to test the kernel-mode drivers that are included with the Microsoft Windows operating system and to test the sample drivers in the WDK. By using the DDI compliance rules for specific driver models, SDV can verify correct driver behavior. For example, SDV can verify that the driver:

• Calls functions at the correct IRQL
• Acquires and releases locks in the correct sequence
• Correctly uses functions that handle I/O request packets (IRP)

SDV examines all possible paths through the driver code. It is designed to find serious errors in obscure paths that are unlikely to be encountered even in thorough testing.

Additional resources

For specific information about the drivers that SDV can verify, see Supported Drivers

For more information and tips about using Static Driver Verifier, see the following:

• Windows Hardware Certification blog
• Windows Kernel community site
• Windows Hardware Testing and Certification forum