Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Things to consider before you enable Driver Verifier Manager on production servers
Article ID: 251233 - View products that this article applies to.
This article was previously published under Q251233
Microsoft Windows 2000, Microsoft Windows XP and Microsoft Windows Server 2003 include Driver Verifier Manager. This is a tool that you can use to troubleshoot new drivers. The tool stresses one or more binaries in an attempt to make them not work. If a binary is not written properly and Driver Verifier finds a problem, an error message is displayed on a blue screen.
Driver Verifier is designed for use in conjunction with the Windows 2000 and Windows Server 2003 Device Driver Kit (DDK) to allow you to simulate certain conditions (for example, low memory conditions, I/O verification, pool tracking, and so on) on drivers you have written. You should use Driver Verifier to help test new kernel mode drivers in a test environment, but in some situations you may need to run the tool on a production server. When you use this tool on a production server and a problem is identified, an error message on a blue screen is displayed.
The following list shows things to consider before you enable Driver Verifier Manager. Be sure to evaluate the information and include other contingencies that are unique to your environment. If you suspect a driver is causing a problem, Microsoft recommends that you stress the computer in a test environment.
(http://support.microsoft.com/kb/216417/ )How to install the Windows 2000 Recovery Console
(http://support.microsoft.com/kb/229903/ )Partial list of possible error codes with Driver Verifier
Article ID: 251233 - Last Review: May 17, 2007 - Revision: 5.4