DPC_WATCHDOG_VIOLATION (stop code 0x133) means Windows’ DPC watchdog caught either a single Deferred Procedure Call running past its tick limit (Parameter 1 = 0x0) or cumulative DPC execution stalling a core at DISPATCH_LEVEL or higher (Parameter 1 = 0x1). Notice the 3-to-10 second cursor freeze right before the blue screen: read Parameter 1 in Event Viewer, open the minidump in WinDbg (!analyze -v names the exact .sys module on Parameter 1 = 0x0), update NVMe/SATA SSD firmware, clean-reinstall your GPU driver, and update Wi-Fi/Bluetooth drivers.
At a glance
- Applies to
- Windows 11 and Windows 10, stop code 0x00000133
- Classic symptom
- Mouse and audio freeze solid for several seconds right before the BSOD
- Parameter 1
- 0x0 = single hung DPC (WinDbg names the .sys) · 0x1 = cumulative DPC storm
- Top 3 culprits
- NVMe/SATA SSD firmware & ASPM, GPU driver (nvlddmkm), Wi-Fi/Bluetooth driver
Provenance
- Nov 21, 2026Published
You can almost feel DPC_WATCHDOG_VIOLATION (0x00000133) coming before the blue screen appears: your mouse cursor freezes in place, game audio buzzes or cuts out for several seconds, and then Windows drops to 0x133.
That multi-second freeze is the Windows DPC Watchdog counting ticks while a hardware driver hogs a CPU core. As Microsoft’s 0x133 documentation explains, Deferred Procedure Calls (DPCs) are supposed to finish in under 100 microseconds (and Interrupt Service Routines in under 25 microseconds). Because DPCs execute at DISPATCH_LEVEL (IRQL 2), normal threads cannot interrupt them—so if a GPU, SSD, Wi-Fi, or Bluetooth driver hangs waiting on unresponsive hardware for several full seconds, Windows halts the machine to break the lockup.
(Did your blue screen say CLOCK_WATCHDOG_TIMEOUT (0x101) instead of DPC_WATCHDOG_VIOLATION (0x133)? Switch to our CLOCK_WATCHDOG_TIMEOUT (0x101) guide—0x101 is CPU voltage/clock instability, whereas 0x133 is driver/device I/O.)
Step 1. Check Parameter 1 (0x0 vs 0x1) and read the exact .sys culprit in WinDbg
Open Event Viewer > Windows Logs > System, click the Kernel-Power (Event ID 41) entry from the crash (BugcheckCode 307 decimal = 0x133 hex), and check BugcheckParameter1:
Parameter 1 (Arg1) | Official Microsoft violation | What Arg2 & Arg3 hold, and how easy it is to solve |
|---|---|---|
0x0 | A single DPC or ISR exceeded its time allotment | Arg2 = actual tick count (e.g. 0x501); Arg3 = allowed tick limit (e.g. 0x500). Easiest case: the hung .sys driver was still executing when the dump snapped, so WinDbg’s IMAGE_NAME usually names it outright |
0x1 | Cumulative time spent at DISPATCH_LEVEL or above exceeded the watchdog period | Arg2 = watchdog period; Arg3 = pointer to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK. Often caused by an interrupt storm from a Wi-Fi/USB controller, storage timeout loop, or GPU TDR failure |
Read IMAGE_NAME in 2 minutes (saves guessing across five drivers)
- Install WinDbg from the Microsoft Store.
- Copy the newest
.dmpfile fromC:\Windows\Minidumpto your Desktop, open it in WinDbg, and run:!analyze -v - Look directly at
IMAGE_NAMEandSYMBOL_NAME(for example, Microsoft’s own0x133documentation sample showsIMAGE_NAME: BthA2DP.sys—a Bluetooth audio driver!). IfIMAGE_NAMEonly showsntkrnlmp.exeon aParameter 1 = 0x1dump, typekto scan the call stack for any third-party.sysmodule sitting underneath.
Step 2. Fix Culprit #1 — Graphics driver stalls (nvlddmkm.sys, amdkmdag.sys, dxgkrnl.sys)
When 0x133 hits mid-game, while alt-tabbing out of fullscreen video, or while waking monitors from sleep—and WinDbg names nvlddmkm.sys (NVIDIA), amdkmdag.sys (AMD), or igdkmdn64.sys (Intel):
- Run a clean WHQL driver install with DDU in Safe Mode: follow our GPU driver crash,
nvlddmkm&VIDEO_TDR_FAILUREguide step by step rather than doing an express in-place upgrade over a broken shader/driver cache. - Revert any GPU core/VRAM overclock or aggressive undervolt in MSI Afterburner or Adrenalin to stock clocks and test the same game.
- Test Hardware-Accelerated GPU Scheduling (
HAGS) off (Settings > System > Display > Graphics > Advanced graphics settings) if the freeze happens specifically while watching hardware-decoded browser video on a second monitor during a game.
Step 3. Fix Culprit #2 — NVMe / SATA SSD controller freezes (stornvme.sys, storahci.sys, iaStorVD.sys)
If 0x133 freezes the desktop during file copies, game level loads, or coming out of idle—or Event Viewer logs stornvme Event ID 129 / disk Event ID 153 right before the reboot (and sometimes fails to save a minidump at all, just like UNEXPECTED_STORE_EXCEPTION (0x154)):
- Update your SSD’s controller firmware inside the manufacturer’s official tool (Samsung Magician, SanDisk/WD Dashboard, Crucial Storage Executive, Kingston SSD Manager). Firmware bugs around Windows 11 NVMe queue resets and host-memory-buffer (
HMB) allocation are a leading cause ofstornvme.sys0x133hangs. - Check Device Manager’s IDE ATA/ATAPI / Storage controllers: if an older SATA system still runs a legacy OEM SATA driver from 2018–2021, switch it to Microsoft’s built-in Standard SATA AHCI Controller (or update Intel Rapid Storage Technology / VMD
iaStorVD.sysfrom your motherboard maker’s support page). - Turn PCIe Link State Power Management to
Offas a test: openpowercfg.cpl-> Change plan settings -> Change advanced power settings -> PCI Express > Link State Power Management -> Off. - Verify SMART drive health (
Media and Data Integrity Errors0E=0and normal temperatures under load) using our SSD health check guide.
Step 4. Fix Culprit #3 — Wi-Fi, Bluetooth, USB audio & network packet filters
Network and wireless drivers execute heavy traffic handling inside DPCs (ndis.sys, Netwtw14.sys, rtwlane6.sys, mtkwl6ex.sys, BthA2DP.sys, USBXHCI.SYS):
- Download the newest Wi-Fi, Bluetooth, Ethernet, and Chipset drivers directly from your motherboard OEM, laptop OEM, or
intel.com/amd.com(Windows Update frequently leaves older MediaTek RZ616/MT7922 and Realtek wireless drivers installed). - Temporarily uninstall third-party “game network boosters” and VPN split-tunnel drivers (
cfosspeed/ Gigabyte Speed / MSI LAN Manager / ASUS GameFirst, or outdated WireGuard/OpenVPN TAP adapters) ifndis.sysortcpip.sysappears in the0x133dump. - Unplug external USB DACs, wireless headset dongles, or cheap unpowered USB hubs for one session if
USBXHCI.SYSorusbaudio.sysis named on the stack.
Step 5. Check live DPC latency and repair OS files
What if your PC experiences micro-freezes and audio crackles even before 0x133 trips?
- Run Resplendence LatencyMon (free read-only diagnostic) for 10 minutes during normal desktop/gaming load and open its Drivers tab sorted by
Highest execution (ms). Any driver spiking into multi-millisecond territory (10–200+ ms) is the exact candidate pushing your system toward0x133. - Once the offending driver or SSD firmware is updated, clean up any file corruption caused by the hard lockups in Terminal (Admin):
DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow
Frequently asked questions
What causes DPC_WATCHDOG_VIOLATION (0x133)?
Why does my screen and mouse freeze for 5–10 seconds right before DPC_WATCHDOG_VIOLATION?
What is the difference between Parameter 1 = 0 and Parameter 1 = 1 on 0x133?
How is DPC_WATCHDOG_VIOLATION (0x133) different from CLOCK_WATCHDOG_TIMEOUT (0x101)?
Can an old SSD firmware or SATA driver cause DPC_WATCHDOG_VIOLATION?
Sources and corrections
- Last updated
- Methodology
- See our methodology for research and review standards. It draws on 4 cited sources, listed below, each checked against the original page on the date above. All bug-check parameter definitions (Parameter 1 = 0 single DPC timeout vs Parameter 1 = 1 cumulative DISPATCH_LEVEL timeout, Parameter 2/3 tick counts, 100-microsecond DPC / 25-microsecond ISR design targets, and WinDbg !analyze -v stack analysis) come directly from Microsoft Learn’s Bug Check 0x133 reference opened November 21, 2026 (UTC), paired with Microsoft’s Event ID 41 and System File Checker guides.
- Sources
- Microsoft Learn: Bug Check 0x133 DPC_WATCHDOG_VIOLATION accessed 2026-11-21
- Microsoft Learn: Event ID 41 when the system restarts unexpectedly accessed 2026-11-21
- Microsoft Support: Troubleshooting Windows unexpected restarts and stop code errors accessed 2026-11-21
- Microsoft Support: Using System File Checker in Windows accessed 2026-11-21
- Corrections
- Spotted an error? Email a correction with the affected line and what you found. The draft includes this page’s address. Verified changes are recorded here. Contact details.