Windows 7 driver verification tool




















This option can also exhaust the resources available for Special Pool and some resource tracking. Testing all drivers can also adversely affect system performance. Select a single driver if you are running a test scenario that measures system or driver performance metrics, or if you want to allocate the greatest number of resources available for detecting memory corruption or resource tracking issues such as deadlocks or mutexes. If you chose Select driver names from a list , select Next , and then select one or more specific drivers.

For example, to run Driver Verifier with the standard settings on a driver called myDriver. For more information about command line options, see Driver Verifier Command Syntax. In Driver Verifier Manager , select Display information about the currently verified drivers , and then select Next. Continuing to select Next displays additional information. To get the most benefit from Driver Verifier, you should use a kernel debugger and connect it to the test computer.

If Driver Verifier detects a violation, it generates a bug check to stop the computer. This is to provide you with the most information possible for debugging the issue.

When you have a kernel debugger connected to a test computer that is running Driver Verifier, and Driver Verifier detects a violation, Windows breaks into the debugger and displays a brief description of the error. All violations detected by Driver Verifier result in bug checks. Common bug check codes include the following:. When you start a new debugging session, use the debugger extension command,!

In kernel mode, the! In addition to! For example:. In Windows 7, Driver Verifier tries to capture these stack traces:. In Windows 7, the meaningful information about these driver defects is saved by Driver Verifier in memory.

Driver Verifier is a tool for monitoring Windows kernel-mode drivers and graphics drivers. Microsoft strongly encourages hardware manufacturers to test their drivers with Driver Verifier to ensure that drivers are not making illegal function calls or causing system corruption. New Verifier command line options The verifier. Online help is also available.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Submit and view feedback for This product This page. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy.

The following verification tools are described in the WDK and recommended for use by driver developers and testers. They are listed in the order in which they are typically used.

Code Analysis for Drivers is a static verification tool that runs at compile time. It examines the code in each function of a driver independently, so you can run it as soon as you can build your driver. It runs relatively quickly and uses few resources. The basic features of the Code Analysis tool in Visual Studio detect general coding errors, such as not checking return values.

The driver-specific features detect more subtle driver coding errors, such as leaving uninitialized fields in a copied IRP and failing to restore a changed IRQL by the end of a routine. Based on a set of interface rules and a model of the operating system, Static Driver Verifier determines whether the driver properly interacts with the Windows operating system kernel.

Static Driver Verifier is extremely thorough -- it explores all reachable paths in the driver source code and executes them symbolically.

As such, it finds bugs that are not detected by using any other conventional method of driver testing. Use the following dynamic verification tools as soon as the driver is built and is running without obvious errors. Driver Verifier is a dynamic verification tool written especially for Windows drivers.

It includes multiple tests that can be run on several drivers simultaneously.



0コメント

  • 1000 / 1000