What DPC_WATCHDOG_VIOLATION means
Drivers schedule short high-priority tasks called deferred procedure calls. If one runs too long, or the system spends too long at an elevated priority level, the watchdog timer stops Windows. Storage drivers and SSD firmware are among the most commonly reported triggers, but other drivers can cause it too.
Common causes
- Storage controller or SSD driver and firmware problems
- Outdated network, graphics or USB drivers
- A drive or its connection stalling under load
- Incompatible peripherals or old firmware
How to fix DPC_WATCHDOG_VIOLATION
Work through these in order and test after each one. Stopping as soon as the crashes stop tells you which change mattered.
- Update SSD firmware and chipset drivers. Use the SSD maker's utility to check for firmware updates, and install the chipset and storage package from the motherboard or laptop maker. Back up data before a firmware update.
- Try the Microsoft SATA AHCI driver. In Device Manager, expand IDE ATA/ATAPI controllers, right-click the SATA AHCI controller, choose Update driver, Browse my computer, Let me pick, then Standard SATA AHCI Controller. Vendor storage drivers trigger this stop for some PCs and the Microsoft driver is a common workaround. Note the original driver first so you can go back.
- Disconnect non-essential peripherals. Remove USB hubs, docks, capture devices and other add-ons, then see whether the crashes stop. Reconnect them one at a time.
- Check the health of the drive. Read the SMART data with the drive maker's tool or CrystalDiskInfo and look for reallocated or pending sectors, media errors and a low remaining-life figure. Back up important files first if the drive reports any warning.
- Undo the most recent change. If the blue screens began after a Windows update, a new driver or new software, remove that change first. Uninstall the update from Settings, Windows Update, Update history, or roll a driver back in Device Manager (right-click the device, Properties, Driver, Roll Back Driver).
If the crash occurs during heavy disk activity and the drive reports warnings, treat it as a failing drive and back up first.
Not sure this is your code?
The stop code appears as text on the blue screen. If the PC restarted before you could read it, open Event Viewer, then Windows Logs, then System, and look for a BugCheck event with ID 1001. You can also search all stop codes.
