DPC_WATCHDOG_VIOLATION is bug check 0x00000133. A driver held the CPU at high priority for longer than Windows allows, so the watchdog stopped the system. On most PCs the culprit is the storage controller: an SSD running old firmware, or the wrong SATA driver.
Take that last sentence seriously. Of all the blue screen codes, this is the one where a single specific fix resolves most cases, and it takes two minutes in Device Manager.
What the stop code actually means
A deferred procedure call is a short job a driver queues to run at high priority once an interrupt has been handled. It is meant to be brief. Microsoft’s documentation states that DPCs should not run longer than 100 microseconds and ISRs should not run longer than 25 microseconds, although the timeouts Windows actually enforces are set considerably higher.
When something blows past the limit, the watchdog assumes the machine is wedged and halts it. The crash itself breaks nothing.
There are two flavours, distinguished by the first bug check parameter:
| Parameter 1 | What Windows is reporting |
|---|---|
0 | A single DPC or ISR exceeded its time allotment. One driver stalled badly, once. Usually identifiable. |
1 | The system cumulatively spent an extended period at IRQL DISPATCH_LEVEL or above. No single offender, harder to pin down. |
You can read that parameter without a debugger. Open Event Viewer:
eventvwr.mscGo to Windows Logs → System and find a BugCheck event with ID 1001. Its description lists the stop code followed by the four parameters in brackets. If the first one after 0x00000133 is all zeros, a single driver is responsible.
Work out which situation you’re in
Crash timing narrows this down faster than any tool.
| When it crashes | Most likely cause | Start with |
|---|---|---|
| Copying large files, installing games, heavy disk activity | SATA controller driver or SSD firmware | Fix 1, then Fix 2 |
| Soon after boot, or on waking from sleep | Storage or chipset driver | Fix 1, then Fix 3 |
| Only when an external drive, dock or hub is connected | USB or Thunderbolt bridge chip | Fix 4 |
| During large downloads, online games or on a VPN | Network driver | Fix 5 |
| Starting right after a Windows feature update | Vendor driver replaced or mismatched | Fix 3 |
| No pattern at all | Needs identifying properly | The identification section below |
If the blue screen named a file under What failed, write it down. That name is the answer, and the rest is working out which vendor owns it. The same technique applies to every Windows stop code and what it means, and there’s more on reading a blue screen if the text vanishes too quickly.
Fix 1: Switch to the Microsoft Standard SATA AHCI Controller
This is the classic fix, and it is classic because it works. Many PCs ship with a vendor storage driver, most often Intel Rapid Storage Technology, whose file appears as iaStorA.sys or iaStorAC.sys. On some configurations it stalls and trips the watchdog. Windows has its own AHCI driver, storahci.sys, which Microsoft describes as a Storport miniport supporting SATA AHCI controllers with no change in functionality or performance from the driver it replaced. Swapping costs you nothing measurable.
Make a restore point first. Open PowerShell as administrator and run:
Checkpoint-Computer -Description "Before AHCI driver change" -RestorePointType "MODIFY_SETTINGS"Then open Device Manager:
devmgmt.msc- Expand IDE ATA/ATAPI controllers.
- Double-click the entry containing SATA AHCI Controller.
- Go to the Driver tab and click Driver Details.
- If the listed file is
storahci.sys, you already have Microsoft’s driver, so skip to Fix 2. If it isiaStorA.sys,iaStorAC.sysor another vendor file, continue. - Close that window, click Update Driver → Browse my computer for drivers → Let me pick from a list of available drivers on my computer.
- Select Standard SATA AHCI Controller, click Next, and restart.
Two situations where you should not do this. If Standard SATA AHCI Controller is missing or greyed out, do not force anything. And if your firmware is set to Intel RST or RAID mode rather than AHCI mode, replacing the vendor driver can leave Windows unable to see its own boot drive. Check the storage mode in your BIOS first.
An NVMe SSD has no SATA AHCI controller at all. It appears under Storage controllers as Standard NVM Express Controller, so there is nothing to swap. Go straight to Fix 2.
Fix 2: Update the SSD firmware
SSD firmware bugs produce this exact stop code, usually under sustained writes, and no driver change will help because the fault sits inside the drive. Every major manufacturer ships a free tool that checks for firmware updates: Samsung Magician, Crucial Storage Executive, WD Dashboard, SanDisk Dashboard, Kingston SSD Manager and SeaTools for Seagate.
Install the one matching your drive and apply any firmware update it offers. Plug a laptop into mains power first. A flash interrupted halfway is one of the few ways to genuinely destroy an SSD.
While the tool is open, check the drive’s health and its reallocated sector or media error counts. This stop code and a failing drive look identical from the outside, so if the health reading is anything other than good, back up before troubleshooting further.
Fix 3: Get chipset and storage drivers from your PC maker
Windows Update supplies generic drivers that are safe rather than correct. The versions tuned to your exact board come from the manufacturer. Go to the support page for your model on Dell, HP, Lenovo, ASUS, Acer or MSI. Install the chipset package first, reboot, then the storage or Intel RST driver. On AMD systems the equivalent is the AMD chipset package.
If the crashes started right after a Windows feature update, this is nearly always why: the update replaced a tuned vendor driver with a generic one, or left a half-matched pair behind.
Fix 4: Unplug external drives, docks and hubs
USB and Thunderbolt bridge chips run their own firmware, and a bad one can hold the bus long enough to trip the watchdog. The usual suspects are cheap USB 3 enclosures, docking stations, and hubs with storage built in.
Disconnect everything except your keyboard and mouse, then run the PC normally for a day. If the crashes stop, reconnect one device at a time with a few hours between each. The enclosure is usually at fault rather than the drive inside it, so try a different caddy before writing the drive off.
Fix 5: Network drivers
Crashes that only happen during downloads, in online games, or while a VPN is connected point at the network adapter instead. Killer, Intel and Realtek adapters have all produced this stop code at various driver versions.
In Device Manager, expand Network adapters, open your Wi-Fi or Ethernet adapter’s properties, and use the Driver tab. If the crashes began after a driver update, use Roll Back Driver. Otherwise install the current driver from your PC maker. Uninstall any bundled management suite from Settings → Apps separately, keeping the plain driver.
Identifying the driver yourself
If the first five fixes have not landed, stop guessing.
Boot into Safe Mode and use the PC normally for a while. Safe Mode loads a minimal driver set, so no crash there is strong evidence that a third-party driver is responsible. That rules out most hardware theories in one step.
To list installed non-Microsoft drivers, run this as administrator and look for old published dates against storage, chipset or network entries:
pnputil /enum-driversThe definitive tool is Driver Verifier, which stresses drivers until the guilty one faults. Microsoft is blunt: running Driver Verifier could cause the computer to crash, so it belongs only on machines you are prepared to have crash repeatedly. Start it with verifier, select Create standard settings, then Select driver names from a list with only non-Microsoft drivers ticked. When you have your answer, or if the PC becomes unbootable, boot to Safe Mode and run:
verifier /resetThen restart. Never leave Verifier enabled on a machine you actually rely on.
What does not fix this
Several widely repeated suggestions do nothing for 0x133.
| Suggestion | Reality |
|---|---|
sfc /scannow | Repairs Windows’ own protected system files. Third-party drivers are not among them. |
chkdsk | Checks the file system and disk surface. It cannot alter driver behaviour. |
| Registry tweaks that raise the watchdog timeout | Suppresses the crash without fixing the stall. The driver still hangs the machine, silently. |
| Reinstalling Windows | Stops it temporarily by reverting to inbox drivers, then it returns when the vendor driver reinstalls. |
Microsoft’s own guidance for a repeating stop code is simpler than any of these: update, disable or uninstall the device driver, remove recently added hardware, and use a restore point if the fault is new.
Common questions
Can DPC_WATCHDOG_VIOLATION damage my SSD?
The crash itself causes no hardware damage. Windows halts deliberately to prevent worse problems. Files being written at that moment can be left corrupted, so repeated crashes gradually damage data rather than the drive. If the drive is genuinely failing, the crashes are a symptom, not the cause.
Is DPC_WATCHDOG_VIOLATION a hardware or software problem?
Usually software. Microsoft states the stop code is generally caused by faulty driver code that does not finish its work within the allotted time. Storage controller drivers and SSD firmware account for most cases. Genuine hardware faults do produce it, but only after the driver and firmware fixes have been ruled out.
Does switching to the Standard SATA AHCI Controller slow my PC down?
No measurable difference for normal use. Microsoft states there is no change in functionality or performance between StorAHCI and the driver it replaced. You lose vendor features such as Intel RST caching and RAID management, so do not make the change if your drives are configured in a RAID array.
Why does it only crash when my external drive is plugged in?
The USB or Thunderbolt bridge chip inside the enclosure runs its own firmware, and a poor implementation can hold the bus long enough to trip the watchdog. Move the drive into a different enclosure to confirm it. The bare drive is usually fine, and the caddy is the part that needs replacing.
Will reinstalling Windows fix DPC_WATCHDOG_VIOLATION?
Often only temporarily. A clean install reverts to Microsoft’s built-in drivers, which is why crashing stops at first. Once Windows Update or the manufacturer’s software reinstalls the vendor storage driver, it usually returns. Treat that outcome as a diagnostic result rather than a cure.
Do Fix 1 first. Check whether your SATA controller is running a vendor driver, switch it to the Microsoft Standard SATA AHCI Controller, then update your SSD firmware. Those two steps resolve the large majority of 0x133 crashes. Everything else here is for the minority they miss.
