DRIVER_VERIFIER_DETECTED_VIOLATION, the blue screen, explained and fixed

This stop code (0x000000C4) is unusual: it is not Windows crashing, it is Windows’ Driver Verifier catching a driver in the act of breaking a rule, such as corrupting memory or misusing a lock, and stopping the system on purpose. It only appears when Driver Verifier is enabled, which someone or something turned on: a troubleshooting guide, a support session, or software that enables it. The blue screen usually names the offending driver file.

The fix, in order

  1. Write down the driver named on the screen. That .sys file belongs to the driver Verifier caught. It is the answer the tool was run to get, so do not lose it in the rush to reboot.
  2. If the PC blue-screens in a loop, boot into Safe Mode. Hold Shift while choosing Restart → Troubleshoot → Advanced options → Startup Settings → Safe Mode. Verifier’s checks do not force the crash in Safe Mode the same way, and you can work there.
  3. Turn Driver Verifier off. From an admin Command Prompt (in Safe Mode if needed) run verifier /reset and restart. This stops the stress tests and the boot loop with them. Verifier is a diagnostic, not a permanent setting, and it should not stay on during normal use.
  4. Fix the named driver. Update it from the manufacturer, roll it back if it just changed, or uninstall the software it belongs to. A Verifier catch is a genuine bug in that driver, not a false alarm, so “turn Verifier off and ignore it” leaves the original crash unsolved.
  5. Repair system files for completeness. DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow.
  6. Confirm Verifier is off afterwards. Run verifier /query; it should report that no drivers are being verified. If flags remain, verifier /reset again and restart.
Do not leave Driver Verifier running on a PC you rely on. It intentionally makes drivers slower and crashes the system at the first violation. It is a workshop tool: turn it on to find a culprit, record the answer, turn it off. If you did not enable it, check whether tuning, monitoring, or security software did.

If it still happens

If the named driver is part of Windows itself rather than a third-party product, the likely story is memory corruption from elsewhere: run Windows Memory Diagnostic and test sticks individually. If the loop prevents even Safe Mode, use the recovery menu’s Command Prompt and run verifier /reset there, then Startup Repair.

Common questions

I never turned on Driver Verifier. Why is it running? Common paths: a troubleshooting guide or support technician enabled it and it was never reset, a driver package or utility enabled it, or it was turned on while chasing an earlier crash and forgotten. On a stable PC, resetting it with verifier /reset is the right move; just keep the driver name it caught, because that part is real information.

Does a DRIVER_VERIFIER_DETECTED_VIOLATION prove that driver is faulty? It proves the driver did something Verifier prohibits, such as touching memory it had freed. That is a genuine defect, though on rare occasions the driver is the victim of corruption caused by another component or bad RAM. Updating or removing the named driver is still the correct first response.

Related errors

BAD_POOL_CALLER · DRIVER_IRQL_NOT_LESS_OR_EQUAL · BAD_POOL_HEADER · SYSTEM_THREAD_EXCEPTION_NOT_HANDLED