Why You Shouldn’t Use the Driver Verifier in Windows 10

[OLDMAN]

by Chris Hoffman on August 22nd, 2018

Windows includes a “Driver Verifier” tool that can stress test your device drivers. It detects bad driver behavior, but any issue found triggers an immediate blue screen of death. Most PC users should stay away.

This utility has been around since Windows 2000 and XP, and it’s still part of Windows 10 today.
Driver Verifier is Mostly For Developers

As Microsoft’s developer documentation notes, Driver Verifier is a helpful tool for developers who are creating and testing device drivers. The tool helps developers find driver problems and fix them.

Driver Verifier can perform a variety of tests, which Microsoft lists on its site. For example, Driver Verifier can allocate most memory requests for the driver from a select pool of memory and monitor that memory for issues. Driver Verifier can cause memory requests to randomly fail to check if the driver works properly in low resource usage situations. Driver Verifier also has tests that can check for memory leaks, security vulnerabilities, and other issues.

While this is a useful tool for developers, you almost certainly don’t want to use it yourself. This tool only stress tests the device driver software itself. It doesn’t stress the hardware itself, so it may not find any problems even if you have a hardware component that’s failing.
Your PC’s Drivers Are Probably Well-Tested

On a modern Windows system, you’re almost certainly already using drivers that have been verified and signed. Modern 64-bit versions of Windows 10 require signed drivers. These signed drivers have gone through Windows Hardware Quality Labs (WHQL) testing, and they should be pretty stable.

When you run Driver Verifier, you can ask it only to test unsigned drivers. There’s a good chance Driver Verifier will inform you that you have no unsigned drivers on your system if you do so.

https://www.howtogeek.com/363500/why-you-shouldnt-use-the-driver-verifier-in-windows-10/

[Bad 💀 Motha]

Blue Screens dont harm anything; it's just a major fault; that gets stored in Event Viewer also so there really is no need to try and take down critical info from the blue screen. Unless it happens to be something that is actually preventing your OS from booting at all.

That kind of tool though is a complete waste of your time anyways.
What users should do is wipe previous driver fully before attempting to use a new one, or different version. It is not a good idea really to leave the old drivers, allowing users options for falling back to previous driver and such. The OS gets easily clogged up this way and so does the Registry.