Windows & BSOD · critical

How to fix DPC Watchdog Violation (0x133)

Windows & BSOD troubleshooting guide

What this error means

Windows stopped because a driver held the processor for too long. Drivers handle hardware events in short, high-priority routines (deferred procedure calls, DPCs), and a watchdog in Windows triggers this stop code when one of them runs far longer than allowed, or when the system spends too long at that priority level overall. In practice the driver is most often for storage (SATA/NVMe controller or SSD firmware), graphics, network or a USB device or dock. The PC may freeze for a few seconds before the blue screen appears.

Updated

Applies to
Windows 11 and Windows 10
Difficulty
Intermediate
Before changes
Changing the storage controller driver can stop Windows from starting on PCs that use RAID or Intel VMD; read the warning in step 3

Reviewed by Matyáš Rada · Documentation checked: 2026-10-30 · Checked against Microsoft's bug check documentation; not tested on every hardware configuration.

Before you begin

Back up important files and create a restore point (search for "Create a restore point" in the Start menu). Photograph the blue screen, including any file name shown next to "What failed". If Windows cannot start, see the startup guide.

Work through these checks

0 of 7 complete
01Note the driver named in the crash

The watchdog fires while a specific driver is running, and Windows often names it. That name points straight to the device to fix.

  1. Check your photo of the blue screen for "What failed: name.sys".
  2. Open Event Viewer (Win + R, eventvwr.msc), go to Windows Logs > System and look for the BugCheck error at the time of the crash, and for warnings or errors from disk, storahci, stornvme or iaStorA just before it.
  3. Search the .sys file name online to see which device it belongs to.
What to expect

You know which kind of driver is involved: storage, graphics, network, audio or USB.

If it does not help

Go straight to the matching step. If nothing is named, work through the steps in order.

Browse related errors
02Disconnect external devices

Drivers for USB hubs, docks, external drives, capture cards and controllers are a frequent and easy-to-test cause.

  1. Shut down and disconnect everything except the keyboard, mouse and monitor, including docks and USB hubs.
  2. Use the PC normally. If the crashes stop, reconnect devices one at a time over several days.
What to expect

The crashes stop, and return only when a particular device is connected.

If it does not help

Update that device's driver or firmware from its manufacturer, or connect it to a different USB port or controller.

Browse related errors
03Update the SSD firmware and storage controller driver

Storage is the most common source of this stop code: an SSD that answers too slowly, or an old SATA controller driver, keeps a DPC running past its limit.

  1. Update the SSD firmware with the drive maker's tool (for example Samsung Magician, WD Dashboard, Crucial Storage Executive or Kingston SSD Manager). Back up first.
  2. Install the latest chipset and storage drivers from your PC or motherboard maker's support page.
  3. On desktops with a SATA drive and an older Intel controller driver, you can switch to the Windows driver: Device Manager > IDE ATA/ATAPI controllers > right-click the SATA AHCI controller > Update driver > Browse my computer > Let me pick > Standard SATA AHCI Controller. Restart.

Do not change the storage controller driver if the PC uses RAID, Intel RST with Optane, or Intel VMD (common on newer laptops). Windows may stop starting. In that case only use the PC maker's driver.

What to expect

The drive and controller run current firmware and drivers, and the crashes stop.

If it does not help

If you switched the controller driver and see no improvement, you can switch back the same way.

Browse related errors
04Update chipset, graphics, network and audio drivers

These drivers also run DPCs constantly, and a faulty version can trigger the watchdog.

  1. Download current drivers from your PC or motherboard maker (chipset, network, Wi-Fi, audio) and from NVIDIA, AMD or Intel (graphics).
  2. If the crashes began right after a driver update, roll it back instead: Device Manager > right-click the device > Properties > Driver > Roll Back Driver.

Avoid driver-updater programs; use the manufacturers' websites.

What to expect

The crashes stop after the faulty driver is replaced.

If it does not help

If the same driver keeps appearing in crashes after an update, report it to its manufacturer with the stop code.

Browse related errors
05Install Windows and BIOS updates

Windows updates include fixed inbox drivers, and BIOS updates fix firmware timing problems with storage and USB controllers.

  1. Open Settings > Windows Update, install all updates including optional driver updates you trust, and restart.
  2. Install the latest BIOS/UEFI from your PC or motherboard maker's support page for your exact model (find it in msinfo32).

Do not switch off the PC during a BIOS update.

What to expect

Windows and firmware are current.

If it does not help

Watch whether the crashes return over the next few days.

Browse related errors
06Check the drive's health

A drive that is starting to fail can stop responding for seconds at a time, which looks to Windows like a stuck driver.

  1. Check the drive's health in its maker's tool or CrystalDiskInfo.
  2. Open Terminal (Admin) and run chkdsk C: /scan to check the file system without restarting.
What to expect

The drive reports good health and chkdsk finds no problems.

If it does not help

If health is poor or reallocated or media errors are reported, back up and replace the drive. The NVMe controller reset guide on this site covers drives that keep resetting.

Browse related errors
07Find a hidden driver or get support

When no driver is named and the steps above did not help, the faulty driver has to be identified from the crash dump.

  1. Collect the memory dumps from C:\Windows\Minidump and the BugCheck events.
  2. Ask the PC manufacturer's support or a technician to analyse them with WinDbg, or follow the Driver Verifier step in the 0x000000FC guide on this site if you are comfortable with repeated test crashes.
What to expect

The analysis names the driver to update or remove.

If it does not help

As a last resort, Settings > System > Recovery > Reset this PC with Keep my files removes third-party drivers while keeping your documents.

Browse related errors

Possible causes

  • Outdated storage controller driver or SSD firmware
  • Faulty or outdated graphics, network, audio or chipset driver
  • USB device, dock or external drive with a misbehaving driver
  • Missing Windows or BIOS updates
  • Failing drive that stops responding

Useful Windows tools

These commands open Windows tools. Review changes before applying them.

devmgmt.msc
eventvwr.msc
msinfo32

Sources & further reading