How To Check For Bad Drivers Windows 10

Windows includes a "Commuter Verifier" tool that can stress exam your device drivers. It detects bad driver beliefs, but any upshot found triggers an firsthand blue screen of death. Most PC users should stay away.

This utility has been around since Windows 2000 and XP, and information technology's nevertheless role of Windows 10 today.

Driver Verifier is Mostly For Developers

As Microsoft'south developer documentation notes, Commuter Verifier is a helpful tool for developers who are creating and testing device drivers. The tool helps developers detect driver problems and fix them.

Driver Verifier can perform a diverseness of tests, which Microsoft lists on its site. For instance, Commuter Verifier tin can allocate most memory requests for the driver from a select pool of memory and monitor that memory for bug. Commuter Verifier can crusade memory requests to randomly neglect 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, y'all most certainly don't want to use it yourself. This tool only stress tests the device commuter software itself. It doesn't stress the hardware itself, so it may not discover any problems even if you lot have a hardware component that's failing.

Your PC'south Drivers Are Probably Well-Tested

On a modern Windows organization, you're almost certainly already using drivers that accept been verified and signed. Modern 64-flake versions of Windows 10 crave 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 simply to examination unsigned drivers. There's a good take a chance Driver Verifier will inform you lot that you have no unsigned drivers on your system if y'all practice so.

Driver Verifier Can Cause Crashes

If your calculator is running fine already, at that place's no reason to run Commuter Verifier—unless you're developing a driver. Fifty-fifty if it uncovers problems, the whole point of Driver Verifier is to stress the drivers. That kind of rigorous testing near certainly will find some issues with the driver, but those are unlikely to cause any real problems in the regular, mean solar day-to-day utilise of your computer.

Driver Verifier can besides crusade Windows to crash. If it finds a driver problem, you'll see a blueish screen of death. Microsoft's documentation says you should not run this tool on your regular calculator, maxim "you should only run Driver Verifier on test computers, or computers yous are testing and debugging." It's not meant as a tool for helping regular users examination driver problems on their production systems.

If your Driver Verifier settings cause a blue screen of decease every time your PC boots, you may exist unable to boot normally. You can endeavour restarting in Prophylactic Mode and disabling Driver Verifier.

RELATED: Everything You Demand To Know About the Blue Screen of Death

When You Might Desire to Run Driver Verifier (Mayhap)

If you are having blueish-screen crashes and other system problems and yous suspect a buggy driver may exist the trouble, you could run Driver Verifier for more information. For case, if y'all run Driver Verifier and see a blueish screen error message, that BSOD may tell you the file name of the driver, which in turn tells you which commuter caused the crash. This driver is potentially the driver that's causing other issues on your system.

There are two problems with that, though. First, it's a flake of a stretch in this historic period of well-tested drivers. A system error is more likely to be caused by failing hardware, malware, or operating system corruption than a buggy device driver. 2d, you tin can investigate the reason for the original BSOD that started the whole mess, and information technology will likely lead you to the faulty driver anyhow if there is 1.

If you did recently update a particular driver and you're having bug, that driver could exist the cause. Only you could just as easily curl dorsum the driver or perform a Arrangement Restore. Both are better uses of your time than messing around with Driver Verifier.

If you lot do manage to identify a bad commuter causing you problems, all you can do is try another version of the device driver and hope the driver issue is fixed—or remove the associated hardware device from your PC.

How to Run Commuter Verifier

Warning: Before running this tool, we recommend creating a System Restore signal. Yous can restore from this signal if you experience a serious trouble.

If you really desire to run this tool—and we're warning y'all, you probably shouldn't—you can. To do so, open a Control Prompt or PowerShell window as Administrator. On Windows x, right-click the First button and select "Windows PowerShell (Admin)."

Type verifier at the prompt and and so press Enter.

(You can likewise but open the Start menu on Windows 10, type verifier into the search box in the Start menu, and printing Enter—but Microsoft's official documentation recommends going through the command line for some reason.)

Select "Create standard settings" and then click "Next."

You can instead select "Create custom settings (for code developers)" if you want to choose the private tests that are applied to your drivers.

Select which drivers you want to stress test. "Automatically select unsigned drivers" will check for any unsigned drivers on your system. "Automatically select drivers congenital for older versions of Windows" will check for any drivers designed for an older version of Windows. A list of either type of driver will be displayed after y'all select this pick. On a modern PC, at that place'southward a good chance Windows volition say you take no such drivers installed.

You can also choose "Select commuter names from a list" to see a listing of your installed drivers and select individual ones.

For the almost extreme examination, you tin even select "Automatically select all drivers installed on this computer" to stress examination everything,

Y'all probably won't need to stress test any of the Microsoft drivers included with Windows. To avoid Microsoft drivers, select pick "Select driver names from a list" and select drivers that weren't provided by "Microsoft Corporation."

Later you've selected the driver or drivers yous desire to stress test, click "End." Yous'll have to reboot your computer earlier the testing begins.

Afterward the reboot, Driver Verifier volition start stress-testing your drivers in the background. Some types of driver issues will consequence in an immediate trouble, while others may non appear until after you've used your PC for a while.

You'll know if there's a problem found because your calculator volition crash and you lot'll encounter a blue screen error message. The error on the screen volition likely display more than data most the exact driver file that caused the trouble, and you can besides find data near the blue screen by examining the Windows memory dump created after your figurer shows a BSOD.

RELATED: Windows Retentivity Dumps: What Exactly Are They For?

How to Disable Driver Verifier

To disable Driver Verifier and go back to normal settings, open the Driver Verifier application over again, select "Delete Existing Settings," click "Stop," and reboot your PC.

If your computer crashes every time it boots and you tin can't disable Commuter Verifier, try booting into Prophylactic Mode, launching Commuter Verifier, and telling it to delete existing settings. You should then be able to boot your PC normally.

If this doesn't piece of work, y'all may be forced to kicking from a Windows installation disc or recovery drive. From here, you can restore to a previous System Restore bespeak or repair your system.

RELATED: How to Boot Into Safe Mode on Windows x or 8 (The Easy Way)