Why you should not use Driver Verifier in Windows 10

Windows includes a tool called Driver Verifier, which can do stress-test on device drivers.

Verifier

Driver Verifier detects bad divers behavior, but with any issue detected, it immediately activates a blue screen (BSOD). Most computer users should not try it. This utility came to us around Windows 2000 and XP and is still a part of Windows 10 even today.

The Driver Verifier is primarily for developers
The Developer documentation notes Microsoft report that Driver Verifier is a useful tool for developers who create and test device drivers. The tool helps developers find driver problems and fix them.

Driver Verifier can perform a variety of tests that Microsoft has she lists on her website. For example, Driver Verifier may create too many from a selected memory pool memory for a driver and monitor that memory for problems. The Driver Verifier can cause memory requests to fail randomly to check if the driver is working properly in low resource usage situations. It also has tests that can check for memory leaks, security vulnerabilities, and other issues.

While it's a useful tool for developers, you almost certainly don't want to use it yourself. This tool only tests the of a device driver. It doesn't check the hardware itself, so it might not detect any problems even if you have some problematic hardware.

His drivers you are already well tested
In a modern Windows system, it is almost certain that you are already using verified and signed drivers. Modern 64-bit versions of Windows 10 require signed drivers. These signed guides have passed the Windows Lab Quality Labs (WHQL) tests and must be fairly stable.

Even though you run the Driver Authenticator, you can only ask for unchecked drivers to check. If you do, then Driver Verifier is very likely to let you know that you do not have unapproved drivers on your system.

The driver's verifier may cause a shutdown
If your computer is already working well, there is no reason to run the Driver Verifier unless you deploy your own driver. Even if it reveals problems, Driver Verifier's purpose is to strain drivers. This kind of rigorous testing is almost certain to find some problems with the driver, but these are unlikely to cause real problems in your regular daily use of your computer.

Driver Verifier can also cause Windows to crash. If it detects a problem with the driver, you will see a blue screen (BSOD). The Microsoft documentation states that you should not run this tool on your regular computer, saying that "you should only run Driver Verifier on test computers or computers that you are testing and debugging." It is not intended as a tool to help regular users experience driver problems on production systems.

If the Driver Verifier settings cause a blue screen whenever your computer starts booting, you may not be able to boot it normally. You may need to try restarting in safe mode and disabling Driver Verifier.

If you want to run the Driver Verifier
If you are experiencing a blue screen interruption and other problems in your system and you suspect a driver problem, you can run the Driver Verifier for more information. For example, if you run the Driver Program Verifier and you see a blue screen error message, the BSOD screen can tell you the file name of the driver, which in turn tells you which driver caused the crash. This driver may be the driver that causes other issues on your system.

But there are two problems with this. First, you are informed about a driver in a set of proven drivers. A system error is more likely to be caused by failed hardware malware or operating system corruption than a troublesome device driver. Secondly, you can investigate the reason for the initial BSOD that started the whole mess, and it will probably lead you to the defective driver, and you need to call the driver verifier.

If you recently updated a certain driver and are having problems, that driver may be the cause. But you may well roll back the driver to a previous version or perform a system restore. Both are better uses of your time from messing with Driver Verifier.

If you can find a bad driver that is causing you problems, all you can do is try another version of the device driver and hope the driver issue will be repaired. Or remove the relevant hardware device from your computer.

How to Run the Driver Verifier
If you really want to run this tool (and we warn you, you probably do not need it) you can do it.

Step 1: It would be nice before you do anything, create one first Windows restore point because there is a great chance of blocking their boot and you find yourself in a situation where your computer will constantly start with blue screens.

Step 2 : To run it, open a window command prompt or a PowerShell window as an administrator. In Windows 10, right-click the Start button and select “Windows PowerShell (Admin)”.

Step 3: Type the verifier command at the command prompt, and then press Enter. Alternatively, you can write the same command in a Windows run-in window

Step 4: Select “Create standard settings” and then click “Next”.

You can then select "Create custom settings (for code developers)" if you want to select individual tests to be applied to drivers.

Choose which drivers you want to try. "Automatically select unsigned drivers" will check for each unsigned driver on your system. "Automatically select drivers built for older versions of Windows" will check for all drivers designed for older versions of Windows. After selecting this command a list of each type of driver will be displayed. On a modern computer, there is a good chance that Windows will tell you that you do not have such drivers installed.

You can also select “Select driver names from a list” to view a list of installed drivers and select individually.

For the most extreme test, you can even select "Automatically select all drivers installed on this computer" to automatically stress-test all your drivers.

You may not need to try any of the Microsoft drivers included in Windows. To avoid Microsoft drivers, select “Select driver names from a list” and select drivers that are not provided by Microsoft Corporation.

After selecting the driver or drivers you want to try, click the "Finish" button. You must restart your computer before the test can begin.

After restart, Driver Verifier will start testing in the background in your drivers. Some types of driver issues will lead to a direct problem, while others may not appear until you have used your computer for a while.

If a problem is detected i understand it because your computer will shut off and you will see a blue screen error message. The on-screen error will most likely show more information about the exact driver file that caused the problem, and you can also find information about the blue screen by looking at the Windows memory dummies created after the BSOD has appeared on your computer.

How to Disable the Driver Verifier
To turn off Driver Check and return to normal settings, reopen Driver Verifier, select "Delete Existing Settings", click "Finish" and restart your computer.

If your computer crashes every time it starts up and you can not disable Driver Authenticator, try starting in safe mode , start the Driver Authenticator and let it delete the existing settings. You should be able to boot your computer properly.

If this is not possible, you may have to boot from a Windows installation disc or from a recovery drive. From here, you can restore it to a previous system restore point or repair your system.

iGuRu.gr The Best Technology Site in Greecefgns

every publication, directly to your inbox

Join the 2.100 registrants.

Written by Dimitris

Dimitris hates on Mondays .....

Leave a reply

Your email address is not published. Required fields are mentioned with *

Your message will not be published if:
1. Contains insulting, defamatory, racist, offensive or inappropriate comments.
2. Causes harm to minors.
3. It interferes with the privacy and individual and social rights of other users.
4. Advertises products or services or websites.
5. Contains personal information (address, phone, etc.).