Quick answer

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.

Fix steps

5 steps

Diagnostic workbench
Contents

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 violationWhat Arg2 & Arg3 hold, and how easy it is to solve
0x0A single DPC or ISR exceeded its time allotmentArg2 = 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
0x1Cumulative time spent at DISPATCH_LEVEL or above exceeded the watchdog periodArg2 = 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)

  1. Install WinDbg from the Microsoft Store.
  2. Copy the newest .dmp file from C:\Windows\Minidump to your Desktop, open it in WinDbg, and run:
    !analyze -v
    
  3. Look directly at IMAGE_NAME and SYMBOL_NAME (for example, Microsoft’s own 0x133 documentation sample shows IMAGE_NAME: BthA2DP.sys—a Bluetooth audio driver!). If IMAGE_NAME only shows ntkrnlmp.exe on a Parameter 1 = 0x1 dump, type k to scan the call stack for any third-party .sys module 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):

  1. Run a clean WHQL driver install with DDU in Safe Mode: follow our GPU driver crash, nvlddmkm & VIDEO_TDR_FAILURE guide step by step rather than doing an express in-place upgrade over a broken shader/driver cache.
  2. Revert any GPU core/VRAM overclock or aggressive undervolt in MSI Afterburner or Adrenalin to stock clocks and test the same game.
  3. 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)):

  1. 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 of stornvme.sys 0x133 hangs.
  2. 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.sys from your motherboard maker’s support page).
  3. Turn PCIe Link State Power Management to Off as a test: open powercfg.cpl -> Change plan settings -> Change advanced power settings -> PCI Express > Link State Power Management -> Off.
  4. Verify SMART drive health (Media and Data Integrity Errors 0E = 0 and 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):

  1. 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).
  2. 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) if ndis.sys or tcpip.sys appears in the 0x133 dump.
  3. Unplug external USB DACs, wireless headset dongles, or cheap unpowered USB hubs for one session if USBXHCI.SYS or usbaudio.sys is 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?

  1. 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 toward 0x133.
  2. 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)?
Hardware drivers handle urgent interrupts in two stages: a tiny Interrupt Service Routine (ISR) followed by a Deferred Procedure Call (DPC) running at DISPATCH_LEVEL. Microsoft’s Bug Check 0x133 page notes that DPCs are meant to finish in under 100 microseconds; when a buggy GPU, NVMe/SATA storage, Wi-Fi, Bluetooth or audio driver loops or waits on hung hardware for seconds instead, the DPC watchdog halts Windows with 0x133.
Why does my screen and mouse freeze for 5–10 seconds right before DPC_WATCHDOG_VIOLATION?
While a driver is stuck inside a DPC at DISPATCH_LEVEL (IRQL 2) or higher on a processor core, the Windows thread scheduler cannot preempt it on that core. Input, audio buffers and frames stall during the watchdog countdown, and when the tick counter in Parameter 2 exceeds the allotment in Parameter 3, the blue screen fires.
What is the difference between Parameter 1 = 0 and Parameter 1 = 1 on 0x133?
According to Microsoft Learn’s 0x133 parameter table, Parameter 1 = 0x0 means a single DPC or ISR exceeded its tick allotment—making it straightforward to spot because the offending .sys driver is still on the stack when the dump is written. Parameter 1 = 0x1 means cumulative DPCs kept the core at DISPATCH_LEVEL too long, where multiple drivers or an interrupt storm can contribute.
How is DPC_WATCHDOG_VIOLATION (0x133) different from CLOCK_WATCHDOG_TIMEOUT (0x101)?
0x133 is almost always a device driver or SSD/GPU firmware stall at DISPATCH_LEVEL, whereas 0x101 (CLOCK_WATCHDOG_TIMEOUT) means a CPU core stopped answering hardware clock interrupts altogether—typically from an unstable CPU overclock, Curve Optimizer undervolt, or BIOS microcode issue.
Can an old SSD firmware or SATA driver cause DPC_WATCHDOG_VIOLATION?
Yes—it is one of the classic 0x133 triggers. When an NVMe or SATA SSD temporarily stops responding to I/O commands (often from outdated SSD firmware or PCIe Link State Power Management sleep transitions), stornvme.sys, storahci.sys or iaStorVD.sys spins waiting on the controller until the DPC watchdog trips.

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.
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.

About the author

I am Lowell K. Wood IV. I research, write and maintain everything on TechFuelHQ from St. Louis County, Missouri.