DRIVER_VERIFIER_DETECTED_VIOLATION — stop code 0x000000C4 — is Windows’ driver police doing its job a little too well. Driver Verifier is a built-in tool that stress-tests drivers by monitoring them for illegal operations, and when it catches one breaking the rules, it crashes the system on purpose to protect your data.

If you are seeing this screen, Verifier is (or was) running on your machine — usually because someone enabled it while hunting a previous crash. The good news: this error practically hands you the culprit. Here is how to find the bad driver, fix it, and get Verifier turned off.

Why this happens

  • Driver Verifier is actively monitoring drivers. The single prerequisite — without Verifier running, this stop code cannot occur.
  • A driver performs an illegal operation. Releasing memory twice, accessing freed pool, calling functions at the wrong interrupt level — Verifier catches all of it.
  • A recent driver update introduced the bug. New driver versions sometimes ship with violations that only Verifier’s strict checks expose.
  • Beta or unsigned drivers. Test-signed and unsigned drivers have not passed Microsoft’s validation and fail Verifier checks more often.
  • Verifier was left on after old troubleshooting. Someone enabled it weeks ago, forgot, and now every boot risks a crash when the buggy driver loads.
  • Corrupted driver binaries. A damaged .sys file on disk can behave in ways Verifier flags as violations.

How to fix it

Work through these in order, from least to most invasive. The minidump tells you exactly which driver to target, so start there.

Fix 1: Read the minidump to name the driver

This is the whole point of Verifier — the dump identifies the offender. Read it before changing anything.

  1. Press Win + R, type %SystemRoot%\Minidump, and press Enter.
  2. Open the newest .dmp file in WinDbg Preview (free from the Microsoft Store).
  3. Type !analyze -v and press Enter.
  4. Look at MODULE_NAME and IMAGE_NAME — they name the violating .sys file, for example e1d65x64.sys (Intel network) or dxgkrnl.sys (DirectX graphics kernel).
  5. Google the file name if the device is not obvious — the results will tell you which hardware it belongs to.
  6. For the full walkthrough with context, our Driver Verifier I/O manager violation guide covers the same dump-reading process.

Fix 2: Update the offending driver

The straightforward fix: replace the buggy driver with a newer, fixed version.

  1. Open Device Manager and locate the device matching the .sys file from the dump.
  2. Right-click it and choose Update driver > Search automatically for drivers.
  3. If Windows finds nothing, download the latest driver from your laptop maker’s support page.
  4. For Intel-based network or graphics drivers, the Intel Driver & Support Assistant pulls the newest validated versions automatically.
  5. Restart and confirm the crashes stop over a day or two of normal use.

Fix 3: Roll back if the violation is new

When the crashes started right after a driver update, the new version is the problem until proven otherwise.

  1. In Device Manager, right-click the device and open Properties.
  2. Go to the Driver tab and click Roll Back Driver.
  3. Pick a reason, confirm, and restart.
  4. If rollback is unavailable, uninstall the device with Attempt to remove the driver checked, then restart and let Windows install its built-in driver.

Fix 4: Disable Driver Verifier to stop the crashes now

If the crash loop is preventing you from working, turn Verifier off first, then fix the driver at your own pace.

  1. Boot into Safe Mode if normal boot keeps crashing (interrupt boot three times to reach recovery, then Troubleshoot > Advanced options > Startup Settings).
  2. Open an elevated Command Prompt and run verifier /reset.
  3. Restart normally — the 0xC4 crashes will stop because nothing is stress-testing drivers anymore.
  4. Now go back to Fix 2 and fix the actual driver without the pressure of constant crashes.
  5. Microsoft documents Verifier’s behavior on the Windows support hub if you want the official background.

Fix 5: Replace beta or unsigned drivers with stable releases

Verifier is merciless with test-signed drivers, and rightly so.

  1. In the dump analysis, check whether the offending driver is a beta, preview, or unsigned build.
  2. Visit the vendor’s site and install the latest WHQL-certified (stable) release instead.
  3. Remove any driver-updater utilities that installed the beta in the first place — they tend to push bleeding-edge versions.
  4. Restart and verify stability for several days before considering the issue closed.

Fix 6: Run SFC and DISM for corrupted driver files

Sometimes the driver is fine but its files on disk are damaged.

  1. Open an elevated Command Prompt.
  2. Run sfc /scannow and wait for it to complete.
  3. Then run DISM /Online /Cleanup-Image /RestoreHealth.
  4. Restart. If the dump named a Windows inbox driver rather than a third-party one, this fix is the most likely to resolve it.

Fix 7: Clean-install the driver and confirm Verifier is off

The final cleanup: make sure the driver install is clean and Verifier is truly disabled.

  1. Use Display Driver Uninstaller (DDU) in Safe Mode for graphics drivers, or a standard uninstall with driver removal for other devices.
  2. Install the stable driver version fresh and restart.
  3. Run verifier /query in an elevated Command Prompt — it should report that no drivers are being verified.
  4. If anything is still listed, run verifier /reset again and reboot.
  5. Use the laptop normally for a week. No crashes with Verifier off and a clean driver means you are done.

Closing

DRIVER_VERIFIER_DETECTED_VIOLATION is Verifier doing exactly what it was turned on to do: catching the bad driver red-handed. Read the dump, fix that specific driver with an update or rollback, and then disable Verifier with verifier /reset so it stops crashing your machine on purpose. The error is the diagnosis — the fix is just following through on it. For Verifier’s memory-corruption cousin, see our SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION guide .

Frequently asked questions

What is DRIVER_VERIFIER_DETECTED_VIOLATION?
It is a blue screen stop code (0x000000C4) raised when Driver Verifier — Windows’ built-in driver stress tool — catches a driver breaking the rules. It means a specific driver is misbehaving, and Verifier is telling you exactly that.
Did I accidentally turn on Driver Verifier?
Probably not accidentally — it is usually enabled deliberately during troubleshooting, either by you following another guide or by a technician. Check with verifier /query in an elevated Command Prompt to see if it is running.
Can I just turn off Driver Verifier to stop the crashes?
Yes, running verifier /reset and rebooting stops the crashes immediately. But the bad driver is still bad — it will likely cause subtler problems later. Identify and fix the driver first, then disable Verifier.
Why do YouTube tutorials say to delete the driver?
Many video guides take the shortcut of deleting whatever driver the dump names. That can work if Windows has a good inbox driver to fall back on, but updating or rolling back is safer. Deletion is a last resort, not a first step.