Windows BSOD Error 0x000001C4 — What It Means & How to Fix It

What Does This Error Mean?

Windows BSOD 0x000001C4 (DRIVER_VERIFIER_DETECTED_VIOLATION_LIVEDUMP) means Driver Verifier caught a driver behaving incorrectly. Driver Verifier is a Windows tool that monitors drivers for rule violations. When it catches a violation, it triggers a blue screen to prevent system damage. This error is most common when Driver Verifier is intentionally enabled for debugging purposes.

Affected Models

Windows 10
Windows 11
Windows 8.1

Common Causes

Driver Verifier is enabled and caught a driver accessing memory it should not touch
A recently installed driver has a bug that violates Windows kernel rules
A third-party antivirus or security driver is behaving incorrectly
Driver Verifier was enabled by a previous troubleshooting session and not turned off
A hardware driver for your GPU, network adapter, or USB controller has a compatibility issue

How to Fix It

Check if Driver Verifier is currently enabled. Open Command Prompt as Administrator and type: verifier /query. If it shows drivers being monitored, this is the source of your BSODs. You can disable it with: verifier /reset and then restart your PC.

Driver Verifier is a developer debugging tool. Regular users should not have it enabled. If you never turned it on, a program or previous troubleshooting may have enabled it.
Disable Driver Verifier completely. Open Command Prompt as Administrator and type: verifier /reset — then restart your PC. If the BSODs stop, Driver Verifier was the cause. The underlying driver bug may still exist but will no longer trigger blue screens.

Disabling Driver Verifier does not fix the driver bug — it just stops actively checking for it. However, many systems run fine with a slightly buggy driver as long as Verifier is not provoking it.
Identify the faulty driver from the crash dump. Open Event Viewer (search for it in the Start menu). Go to Windows Logs > System and look for critical errors around the time of each crash. The driver name is usually listed.

Crash dump files in C:\Windows\Minidump contain detailed information about the crash. Programs like WhoCrashed (free) can read these files and name the specific driver.
Update or reinstall the suspected driver. Once you know which driver is at fault, go to Device Manager (right-click Start > Device Manager), find the device, right-click it, and select Update Driver. If updating does not help, uninstall and reinstall it.

Outdated drivers are a very common cause of Driver Verifier violations. Always check the manufacturer's website for the latest version rather than relying on Windows Update alone.
Run System File Checker to repair any corrupted Windows system files. Open Command Prompt as Administrator and type: sfc /scannow — let it complete, then restart your PC.

Corrupted Windows system files can cause drivers to behave incorrectly. SFC repairs them automatically without any risk to your data.

When to Call a Professional

If you cannot identify the offending driver and BSODs continue, take the computer to a repair technician. They have tools to analyze the crash dump files and identify the exact driver causing the problem. For business computers, contact your IT department — Driver Verifier may have been enabled by a group policy or IT tool.

Frequently Asked Questions

What is Driver Verifier and should I turn it off?

Driver Verifier is a built-in Windows tool designed for software developers. It monitors drivers and deliberately triggers a blue screen the moment a driver breaks a rule. For regular users, it should be turned off. If you never turned it on and it is currently active, a program or repair tool may have enabled it without your knowledge. Disable it with 'verifier /reset' in an Administrator Command Prompt.

How do I find out which driver caused the BSOD?

Windows saves a crash report (called a minidump) in C:\Windows\Minidump each time a BSOD occurs. Download a free tool called WhoCrashed from resplendence.com. Point it at your minidump folder and it will read the crash reports and name the driver responsible. This is the fastest way to pinpoint the problem.

Can a BSOD damage my files or data?

Generally, no. A BSOD forces Windows to restart safely, which protects most files. However, any unsaved work in open programs will be lost. Repeated BSODs over time can occasionally cause file system errors. After multiple BSODs, it is worth running chkdsk on your hard drive to check for errors.