DPC_WATCHDOG_VIOLATION
Windows
High severity
DPC Watchdog Violation — Blue Screen Fix
A driver or firmware spent too long at high IRQL. Most often outdated SSD firmware or the wrong SATA AHCI controller driver.
Last reviewed 2026-08-29 by the Tech Issue Guide team.
Symptoms
- Sudden blue screen reading DPC_WATCHDOG_VIOLATION, often minutes after boot.
- Random restarts under disk activity (copying files, launching games).
- The PC runs fine in Safe Mode but crashes on a normal boot.
What causes DPC_WATCHDOG_VIOLATION
- The SATA controller is using a third-party or mismatched driver instead of Microsoft’s storahci.
- Outdated SSD firmware with a known DPC latency bug.
- An old chipset, network or graphics driver holding the CPU too long in a deferred procedure call.
- A recently attached USB or Thunderbolt device with a buggy driver.
How to fix it — 3 steps
- In Device Manager → IDE ATA/ATAPI controllers, change the SATA AHCI Controller driver to the “Standard SATA AHCI Controller” (storahci) and reboot.
- Update your SSD firmware and motherboard chipset drivers from the vendor’s site; update or roll back any driver changed just before the crashes started.
- Run DISM RestoreHealth and sfc /scannow (command below), then check Reliability History for the faulting driver.
Terminal / CLI command
DISM /Online /Cleanup-Image /RestoreHealth && sfc /scannowElevated Command Prompt. If you cannot boot normally, do this from Safe Mode.
How to confirm the fix: The PC runs a full day of normal use — including disk-heavy tasks — with no blue screen.
Prevent it from coming back
Keep SSD firmware and chipset drivers current, and prefer Microsoft’s in-box storage driver unless the vendor specifically requires theirs.
Frequently asked questions
Which driver exactly do I switch to?
Right-click the SATA AHCI Controller → Update driver → Browse my computer → Let me pick → choose “Standard SATA AHCI Controller.” If it is not listed, your platform needs the vendor driver and the cause is elsewhere.
Could bad RAM cause this?
Rarely, but possible. If storage fixes do not help, run Windows Memory Diagnostic (mdsched) and MemTest86 overnight.