Fix Driver Verifier Detected Violation Error

Driver Verifier is a built-in Windows tool that stresses drivers to find faulty ones. When it detects a violation, you get a blue screen with the error “DRIVER_VERIFIER_DETECTED_VIOLATION.” This guide walks you through the steps to identify the problem driver and get your system stable again. You’ll need to be comfortable with Windows recovery options and command prompt.

What You’ll Need

A Windows PC that can boot to the Recovery Environment (WinRE) or a Windows installation USB drive.
Administrator access to your system.
Patience – the process may involve several reboots.

Step-by-Step

Boot into Windows Recovery Environment. If you can reach the login screen, hold Shift and click Restart. If not, power cycle your PC three times – turn it on, let it start, then hold the power button to force off. On the third restart, Windows should enter WinRE.
Open Command Prompt. In WinRE, go to Troubleshoot > Advanced options > Command Prompt.
Disable Driver Verifier. At the command prompt, type verifier /reset and press Enter. This clears all Driver Verifier settings. Wait for it to complete, then type exit and restart your PC. If Windows boots normally, you’re done – the issue was a false positive or a one-time glitch.
If the error persists, re-enable Driver Verifier for a targeted test. Boot back into WinRE, open Command Prompt, and type verifier /standard /driver <driver.sys> (replace <driver.sys> with the name of the driver you suspect, e.g., nvlddmkm.sys for NVIDIA graphics). Restart and see if the error occurs. If it does, that driver is the culprit.
If you don’t know which driver, use Driver Verifier to test all unsigned drivers. In WinRE Command Prompt, type verifier /standard /all and restart. This will likely cause a crash – that’s expected. The crash dump will point to the offending driver.
Analyze the crash dump. After the crash, boot into WinRE again and open Command Prompt. Use dir C:\Windows\Minidump to see if a dump file exists. You can use a tool like BlueScreenView (on another PC) to read it, or you can use the command verifier /querysettings to see which drivers are being tested. If you have access to the Windows SDK, you can use !analyze -v in WinDbg to get the exact driver name.
Once you identify the driver, update or roll it back. Boot into Safe Mode (hold Shift while clicking Restart, then Troubleshoot > Advanced options > Startup Settings > Restart > press 4 for Safe Mode). In Safe Mode, go to Device Manager, find the device, right-click, and choose Update driver or Properties > Driver > Roll Back Driver. If that doesn’t work, uninstall the device and let Windows reinstall it, or download the latest driver from the manufacturer’s website.
After updating, disable Driver Verifier again. Open Command Prompt as Administrator (right-click Start > Command Prompt (Admin)) and type verifier /reset. Restart normally.

Common Mistakes

Not disabling Driver Verifier after testing. Leaving it enabled can cause random BSODs. Always run verifier /reset when done.
Testing all drivers when you only need to test one. This can cause a crash that’s hard to diagnose. Start with a specific driver if you have a suspicion.
Ignoring the crash dump. The dump is your best clue. Without it, you’re guessing.
Using an outdated driver update. Make sure you download the latest version from the official source, not a third-party site.

Tips

Write down the stop code. The BSOD often shows a parameter that can hint at the issue (e.g., 0x1 means a memory corruption, 0x2 means a spinlock error).
Check for Windows updates. Sometimes a Windows update fixes a driver issue. Install all pending updates before diving into manual driver troubleshooting.
Use System Restore. If you recently installed a driver, a system restore point might undo the damage. In WinRE, go to Troubleshoot > Advanced options > System Restore.
Keep a record of your steps. If you’re going through multiple drivers, note which ones you’ve tested to avoid repetition.

Troubleshooting

If the steps above don’t work, try these additional measures:

If you can’t boot into WinRE at all: Use a Windows installation USB. Boot from it, select your language, then click “Repair your computer” in the bottom-left corner.
If the error occurs even in Safe Mode: This suggests a fundamental driver issue. Try running sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an elevated Command Prompt to repair system files.
If the crash dump is empty or unreadable: Ensure that minidump creation is enabled. In WinRE Command Prompt, type reg add "HKLM\SYSTEM\CurrentControlSet\Control\CrashControl" /v CrashDumpEnabled /t REG_DWORD /d 2 /f and restart to enable small memory dumps.
If you suspect hardware (e.g., RAM): Run Windows Memory Diagnostic (type mdsched.exe in Run). Memory issues can trigger Driver Verifier violations.

Frequently Asked Questions

What exactly is Driver Verifier?

It’s a Windows tool that stresses drivers by forcing them to handle unusual conditions. It’s designed to catch driver bugs before they cause system crashes.

Why did this error appear out of nowhere?

Often it’s after a Windows update or a new driver installation. The driver might have been fine before but now violates a rule that Driver Verifier checks.

Can I just ignore the error and turn off Driver Verifier?

Yes, but the underlying driver issue may still cause crashes later. It’s better to fix the driver.

How do I know which driver is causing the problem?

The crash dump is the most reliable way. You can also use the Event Viewer (under Windows Logs > System) to look for warnings about specific drivers.

Is it safe to run Driver Verifier with /all?

It’s safe but will likely cause a crash. That’s the point – it forces the bad driver to reveal itself. Just make sure you have a backup of important files.

What if the error still happens after updating all drivers?

Try a system restore to a point before the issue started. If that fails, consider a clean reinstall of Windows as a last resort.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →