DPC_WATCHDOG_VIOLATION: 7 Causes of This Blue Screen and How to Fix Them

In this guide (10 sections)

• What exactly happens?
• Find the driver file first
• 1. A background app’s driver is hanging
• 2. The graphics driver is hanging
• 3. The SSD’s firmware or storage driver is out of date
• 4. The network, chipset or another motherboard driver is outdated
• 5. A USB device or its driver is misbehaving
• 6. Windows files are damaged or an update went wrong
• 7. A part is faulty
• Real cases: what other users ran into

DPC_WATCHDOG_VIOLATION (stop code 133) means a driverDriver: The software that lets Windows talk to a piece of hardware, like the graphics card. More in our Graphics cards & display glossary →Close ✕ (the software that lets Windows control a part of the PC) kept the processor busy for too long. Driver software often does quick, urgent jobs that can’t be interrupted, and Windows gives them a strict time limit. If one takes longer than that, Windows’ “watchdog” stops the whole PC rather than let it stay frozen. That’s why this blue screen often comes after a freeze of a few seconds, sometimes with the sound stuck in a loop. The cause is nearly always one driver, and finding it is the fix.

If you’re not sure which blue screen you have, start with our guide on how to find what caused a blue screen.

What exactly happens?

What you see	Most likely cause	Where to look
The crashes started after installing an app for lighting, a mouse or keyboard, audio or a VPN.	That app’s driver	Cause 1
The crashes happen while gaming, often after 30 minutes or more.	A background app, or the graphics driver	Causes 1 and 2
The crash dump shows the file nvlddmkm.sys, amdkmdag.sys or atikmpag.sys.	The graphics driver	Cause 2
The crash dump shows the file storahci.sys, stornvme.sys or iaStorAC.sys, or the crashes started after moving Windows to a new SSD.	The SSD’s firmware or storage driver	Cause 3
The crashes happen when the network connects, or the crash dump shows a network file.	Network or Wi-Fi driver	Cause 4
The crashes started after plugging in a new USB device, dock or hub.	That device’s driver	Cause 5
The crashes started right after a Windows update.	Damaged Windows files, or the update itself	Cause 6
Every software fix fails, and the crashes stop with a different graphics card or SSD.	A faulty part	Cause 7

Find the driver file first

At each blue screen Windows saves a small crash dump that records which driver was running. Reading it first saves you from trying every fix blindly.

How to check:

1. Install WhoCrashed (free for home use) or BlueScreenView (free) and open it.
2. Look at the driver named for each DPC_WATCHDOG_VIOLATION blue screen.
3. Search the file name if you don’t recognize it. Our guide on how to find what caused a blue screen lists the most common ones.

If the tool only names ntoskrnl.exe (the core of Windows), the real culprit is hidden. Work through the causes below in order.

1. A background app’s driver is hanging

Apps that control RGB lighting, mice, keyboards and headsets, audio “enhancers”, VPNs, fan controllers and game anti-cheat programs install their own drivers. These run deep inside Windows, and a buggy one can hang long enough to trigger this blue screen.

How to check: look at what you installed in the weeks before the crashes started, and at any file names in the crash dump that belong to an app.

Fix:

1. Uninstall these apps one at a time, starting with the most recent, and use the PC for a few days after each.
2. If the crashes stop, check the app’s website for an update, or use the hardware without the app.
3. If you can’t do without the app, reinstall the newest version and turn off the features you don’t need.

2. The graphics driver is hanging

The graphics driver is one of the drivers most often named in this blue screen, especially when it happens during games. An update that went wrong, leftovers from an older driver or a brand-new driver release can all cause it.

How to check: the crash dump shows the file nvlddmkm.sys (NVIDIA), amdkmdag.sys or atikmpag.sys (AMD), or igdkmd64.sys (Intel graphics).

Fix:

1. Do a clean reinstall of the graphics driver with DDU. Our guide on how to find what caused a blue screen has the step-by-step method.
2. If the newest driver crashes, install the previous version instead. On laptops, try the driver from the laptop maker’s website.
3. Reset any graphics card overclock to default.

If the crashes continue on several driver versions, see our guide on VIDEO_TDR_FAILURE, which covers the graphics card itself.

3. The SSD’s firmware or storage driver is out of date

The drivers that talk to your SSD and hard disks are among the most common causes of this blue screen. Bugs in an SSD’s firmware (the SSD’s own built-in software), and older Intel storage drivers, have caused it on many PCs.

How to check: the crash dump shows the file storahci.sys, stornvme.sys, iaStorA.sys or iaStorAC.sys, or the crashes started after installing a new SSD or moving Windows to one.

Fix:

1. Update the SSD’s firmware with its maker’s free app (for example Samsung Magician, WD Dashboard, Crucial Storage Executive, Kingston SSD Manager). Back up your files first.
2. Update the chipset driver from your motherboard’s support page, or from AMD or Intel.
3. If the crash dump shows the file iaStorA.sys or iaStorAC.sys (Intel Rapid Storage): try Windows’ own driver instead. In Device Manager, open IDE ATA/ATAPI controllers, double-click the SATA controller, go to Driver → Update driver → Browse my computer → Let me pick, choose Standard SATA AHCI Controller and restart.

4. The network, chipset or another motherboard driver is outdated

Network, Wi-Fi, Bluetooth and audio drivers can all hang. Windows Update sometimes installs older or generic versions.

How to check: the crashes happen when the PC connects to the internet or wakes from sleep, or the crash dump shows a file starting with rt (Realtek), Netwtw or e1 (Intel network).

Fix: install the newest drivers for your exact motherboard or laptop model from its maker’s support page: chipset first, then network, Wi-Fi, Bluetooth and audio. Intel Driver & Support Assistant and AMD’s chipset driver page help with the parts they make.

5. A USB device or its driver is misbehaving

Docks, hubs, capture cards, controllers and cheap adapters bring their own drivers, and some of them hang.

How to check: unplug everything except the keyboard and mouse for a few days. If the crashes stop, plug the devices back in one at a time.

Fix: update the driver for the device you found, plug it into a different USB port (preferably on the back of the PC), or replace it if no fix exists.

6. Windows files are damaged or an update went wrong

A damaged Windows file, or a problem with a specific update, can make Windows’ own drivers misbehave.

How to check: the crashes started right after a Windows update, or a large update failed or was interrupted.

Fix:

1. Repair Windows files with DISM and SFCSystem file check (SFC and DISM): Built-in Windows commands that find and repair damaged Windows files. More in our Windows & performance glossary →Close ✕: right-click the Start button, open Terminal (Admin) and run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow.
2. Install all pending updates. If the crashes started with one specific update, uninstall it from Settings → Windows Update → Update history → Uninstall updates until a newer one arrives.

7. A part is faulty

Sometimes the driver software is fine and the part it controls isn’t. A failing SSD or graphics card can stop responding, leaving its driver waiting until the watchdog stops the PC.

How to check: the crashes continue after a clean graphics driver install, firmware updates and removing extra apps, and they stop when you test with a different graphics card or SSD.

Fix: check the SSD’s health with CrystalDiskInfo (free). If the crashes stop with a different part, contact its maker or the store where you bought it about a warranty replacement.

Real cases: what other users ran into

These are real threads from PC forums, summarized in our own words. Each one links to the original.

Real caseROG Chakram X Origin mouse · ROG Strix Scope II RX keyboardSolvedBlue screens in games caused by a mouse and keyboard appRead what happened

In a post from April 2025, a gamer described a PC that had been freezing and restarting during some games for a while. The person who posted analyzed the crash with Microsoft’s debugger: it was DPC_WATCHDOG_VIOLATION, pointing to an agent of ASUS Armoury Crate (the app for their mouse, keyboard and headset) and Windows’ mouse driver. Reinstalling Armoury Crate and even Windows didn’t help. After uninstalling Armoury Crate and testing for months, they confirmed the problem was gone, although without the app they couldn’t use their mouse and keyboard macros.

Takeaway: a peripheral app’s driver can crash the whole PC. See cause 1.

Source: ASUS ROG Forum

Real caseRyzen 9 7950X · ROG Strix X670E-F · 4 × 16 GB DDR5-5600 · Zotac RTX 4090 · Seasonic Prime TX-1000Solved by replacing hardwareConstant crashes that stopped only with a replacement graphics cardRead what happened

In September 2023, a PC whose RTX 4090 had worked well for its first few months was crashing with DPC_WATCHDOG_VIOLATION whenever a game or 3D app ran, and later within seconds of starting Windows. The crash dumps pointed to the NVIDIA driver, and the blue screen itself showed graphical glitches. Windows reinstalls, a minimal setup, another motherboard, a BIOS and chipset update and a clean driver install with DDU changed nothing, while the PC never crashed with the card removed. Forum members also suspected the power supply and the four RAM modules. In November, the person who posted reported that they had got the card refunded and that a new card fixed all their problems.

Takeaway: if every software fix fails and the crashes follow one part, it may be faulty. See cause 7.

Source: Linus Tech Tips Forum

Real caseRyzen 9 5900X · ROG Crosshair VIII Dark Hero · RTX 4070 Ti · ROG Strix 1000WNot solved by the userBlue screens that continued after changing almost every partRead what happened

In January 2024, a PC started having blue screens and sudden restarts several times a day, sometimes in games and sometimes at random. The person who posted removed Armoury Crate and Riot Vanguard, updated the BIOS and chipset driver and reinstalled the NVIDIA driver, which helped only for a day. A forum helper found that the crash dumps, DPC_WATCHDOG_VIOLATION, pointed to the NVIDIA driver, with two driver versions installed at once. By April, the graphics card had been sent to its maker for repair, and a new power supply, another processor of the same model and a different motherboard had been tried, without success. Swapping in an older GTX 1080 stopped the blue screens, but the root cause was still unknown.

Takeaway: some cases take many swaps, so test the cheapest suspects first. See cause 2.

Source: Windows 11 Forum

Frequently asked questions

Is DPC_WATCHDOG_VIOLATION a hardware or software problem?

Usually software: a driver from an app, the graphics card or the storage. Hardware is the cause less often, typically a failing SSD or graphics card that makes its driver software wait.

Why does the PC freeze before the blue screen?

Because a piece of driver software is stuck doing a job that can’t be interrupted. Windows waits for its time limit, which feels like a freeze of a few seconds, often with looping sound, and then stops the PC.

What’s the difference between DPC_WATCHDOG_VIOLATION and CLOCK_WATCHDOG_TIMEOUT?

Both are watchdog errors, but CLOCK_WATCHDOG_TIMEOUT means a processor core stopped responding, which points more to processor settings, overclocks or the BIOS. Our guide on WHEA_UNCORRECTABLE_ERROR covers those checks.

Will reinstalling Windows fix it?

If the cause is an app or its driver, yes, until you install it again. That’s why it’s better to find the driver file first. If the crashes continue on a fresh Windows with only essential drivers, suspect the hardware.