What is DRIVER-VERIFIER-DETECTED-VIOLATION?
This medium-severity issue affects the system driver. Driver Verifier detected a violation in a running kernel-mode driver. Use the steps below to track down and fix the cause.
Common Causes
- Buggy device driver
- Driver Verifier active configuration
- Incompatible hardware driver
Step-by-Step Fix Guide
-
1
Disable Driver Verifier via cmd
Start with Disable Driver Verifier via cmd — it clears the most frequent root cause behind 0x000000C4 in the majority of cases we've seen.
-
2
Update the offending driver
If the fault persists, continue with the next steps, which account for less common drivers instability causes.
-
3
Perform clean install of drivers
For lingering DRIVER-VERIFIER-DETECTED-VIOLATION cases, "Perform clean install of drivers" is worth running through.
Commands & Diagnostics
verifier /reset
verifier /query
Frequently Asked Questions
Buggy device driver accounts for the majority of DRIVER-VERIFIER-DETECTED-VIOLATION reports; driver Verifier active configuration and incompatible hardware driver come up less often but are documented.
"Disable Driver Verifier via cmd" clears up most DRIVER-VERIFIER-DETECTED-VIOLATION reports by itself. The remaining steps above cover what's left.
As a medium-severity issue, DRIVER-VERIFIER-DETECTED-VIOLATION is more of a stability annoyance than a hardware risk — the steps above should clear it up.
Usually. DRIVER-VERIFIER-DETECTED-VIOLATION is fixable with the steps above; a full Windows reinstall is rarely necessary unless everything else has failed.
Sometimes. Microsoft regularly releases patches that fix known BSOD triggers including DRIVER-VERIFIER-DETECTED-VIOLATION. Make sure Windows is fully up to date via Settings → Windows Update before attempting more advanced fixes.
Still Need Help?
Search our full database of 535+ documented PC errors for more solutions and step-by-step repair guides.
Search Error Database