Driver Verifier | |
---|---|
![]() Driver Verifier in Windows 11 | |
Developer(s) | Microsoft |
Operating system | Microsoft Windows |
Website | docs![]() |
Driver Verifier is a tool included inMicrosoft Windows that replaces the default operating systemsubroutines with ones that are specifically developed to catchdevice driverbugs.[1] Once enabled, it monitors and stresses drivers to detect illegalfunction calls or actions that may be causing system corruption. It acts within thekernel mode and can target specific device drivers for continual checking or make driver verifier functionalitymultithreaded, so that several device drivers can be stressed at the same time.[1] It can simulate certain conditions such as low memory,I/O verification,pool tracking,IRQL checking,deadlock detection,DMA checks,IRP logging, etc.[1] The verifier works by forcing drivers to work with minimal resources, making potential errors that might happen only rarely in a working system manifest immediately. Typically fatal system errors are generated by the stressed drivers in the test environment, producingcore dumps that can be analysed anddebugged immediately; without stressing,intermittent faults would occur in the field, without propertroubleshooting facilities or personnel.
Driver Verifier (Verifier.exe) was first introduced as acommand-line utility inWindows 2000;[1] inWindows XP, it gained an easy-to-use graphical user interface, calledDriver Verifier Manager, that makes it possible to enable a standard or custom set of settings to select which drivers to test and verify. Each new Windows version has since introduced several new, more stringent checks for testing and verifying drivers and detecting new classes of driver defects.
Driver Verifier is not normally used on machines used in productive work. It can cause undetected and relatively harmless errors in drivers to manifest, especially ones not digitally signed byWindows Hardware Quality Labs, causingblue screen fatal system errors. It also causes resource-starved drivers to underperform and slow general operation if the constraints imposed by Verifier are not reversed after debugging. Microsoft recommends against verifying all drivers at the same time.[2]