TheDriver Verifierruns in the background during startup and scans the system for corruption todetect illegal function calls.
Running the verifier on all drivers makes it unstable and usuallyreturns a bug check errornamedDRIVER_VERIFIER_DETECTED_VIOLATION.
The solution is simple –disable driver verifier settings. But if you cannot access Windows due to the BSOD boot loop, disable it via theAdvanced Startup menu.
Since this error occurs mainly due to driver violations,updating device driverscan sometimes help.
Well, most users even reported getting the same BSOD error after connecting a USB device. If you are also in a similar situation,connecting to a different portshould fix it.
Disable Driver Verifier
You do not need a Driver Verifier unless you are adevice driver programmer. Even they use this tool only to stress test a single driver. General users are advised to keep it disabled.
I’ve seen many websites recommending to enable this for driver issues or to detect BSOD. The truth is that running Driver Verifier on all drivers will make thesystem unstableand might give you a series of driver verifier BSOD.
Tip:Before disabling, it is a good idea torun the SFC command. Since the error is due to complications with the drivers, running SFC will attempt to find and fix driver problems.
If you may boot into Windows,
If you arestuck in a boot loop, try the aforementioned steps afterentering safe mode. Also, this is directly possible from the Windows RE. Here’s how:
Another rare scenario could also occur whereyou cannot even bootinto the Advanced Startup Menu. In that case, you need to access this menu using bootable media:
Deleting existing driver verifier settings should work unless one of your drivers is corrupted. In that case, the smart option is toupdate them.
Since any driver can lead to this error, I highly recommend updating/reinstalling each of them.
While this may not always fix the issue, the latest drivers usually come with more features and are more reliable.
