Fix DPC Watchdog Violation

DPC_WATCHDOG_VIOLATION (bug check 0x00000133) means a driver did not finish its work in the time Windows allows, so the watchdog stopped the system. Update or disable the driver named on the stop screen or in Event Viewer, starting with storage, graphics and Bluetooth drivers. Microsoft's bug check 0x133 reference explains the two failure types.

Checked November 3, 2026 against the manufacturer's own pages.

The short version

What to install and where it comes from. Every link goes to the manufacturer or Microsoft, never to a copy.

Bug check value0x00000133
Parameter 1 = 0One DPC or ISR ran past its time allotment
Parameter 1 = 1Too much total time spent at DISPATCH_LEVEL
Microsoft's stated causeDriver code that does not finish in time
Microsoft Learn: Bug Check 0x133 DPC_WATCHDOG_VIOLATIONlearn.microsoft.comMicrosoft Learn: Stop code error troubleshootinglearn.microsoft.comMicrosoft Support: Troubleshoot blue screen errorssupport.microsoft.com

Official files only, nothing bundled

Step by step

  1. Write down any .sys file on the screen

    Microsoft's first step for 0x133 is simple: if a driver is identified in the message, disable it to isolate the issue and ask its maker for an update. The file name is printed under the stop code when Windows knows it.

  2. Search the System log

    Open Event Viewer and go to Windows Logs, System. Filter for Critical and Error events around the crash time. A disk, controller or Bluetooth warning just before the stop is a strong hint.

  3. Update the storage controller and SSD

    Open Device Manager and expand Storage controllers and IDE ATA/ATAPI controllers. Get the current controller driver from Windows Update or your PC maker, and check the SSD maker's site for a firmware update.

  4. Update graphics, audio and Bluetooth drivers

    Install Windows Update items under Optional updates first, then the PC maker's drivers for the model. These device classes spend a lot of time at high priority, so a slow driver there can trip the watchdog.

  5. Unplug or check new hardware

    Remove any device added before the crashes began, such as a USB hub, dock, capture card or second drive. Microsoft asks you to confirm new hardware is compatible with your version of Windows.

  6. Update the BIOS and chipset

    Ask your PC maker for the latest BIOS and chipset drivers. Microsoft's general stop error guidance puts current BIOS and firmware next to current Windows updates.

Faster option: update drivers automatically

The steps above fix this one device. If several drivers are old, a driver updater finds and installs them all in one go, and backs up the current ones first.

  1. Driver Updater scan listing outdated drivers1. Scan. Download the free version and run a scan.
  2. Missing driver found with the newest version2. Review. See each old or missing driver with its newer version.
  3. Update complete with every driver updated3. Update. Update one driver free, or all at once with Pro.

Update this driver automatically

Finds and updates this driver and every other outdated driver on your PC.

Auslogics Driver Updater · Free scan · Windows 11, 10, 8, 7 · Backup before every change

What triggers the DPC watchdog?

Windows runs a timer that watches how long drivers spend at high priority. It fires in two cases, told apart by parameter 1. A value of 0 means a single DPC or interrupt routine went over its own time allotment. A value of 1 means the processor spent too long in total at DISPATCH_LEVEL or above, which can come from many short calls added together.

Microsoft’s guide to the error says a value of 1 is harder to trace, because the crash may not stop in the code that caused the delay. That is why the System log and recent changes matter so much here.

Which drivers show up in 0x133 crash dumps?

Microsoft’s own worked example names BthA2DP.sys, the Windows Bluetooth audio (A2DP) driver, as the code running when the watchdog fired. Files you may see on your screen include:

File named What it is First place to update
iaStorA.sys Intel Rapid Storage Technology PC maker, then intel.com
storahci.sys or storport.sys Microsoft storage drivers Windows Update
nvlddmkm.sys NVIDIA graphics PC maker, then nvidia.com
BthA2DP.sys Windows Bluetooth audio Windows Update, Bluetooth driver from the PC maker

When a Microsoft file such as storport.sys is named, the fault is often in the device or the maker’s driver beneath it, so update the controller, the drive firmware and the BIOS rather than trying to replace the Windows file.

Windows 10 and Windows 11 differences

The code and steps are the same on both. On Windows 11 the controller list sits in Device Manager under the same headings. If you use Windows 10, install the last updates it received, since Microsoft’s stop error guidance starts with current cumulative updates.

Questions

Is DPC_WATCHDOG_VIOLATION a hardware or a driver problem?

Microsoft says it is generally caused by faulty driver code that does not complete its work in the allotted time. A failing drive or a device that stops answering can make a driver wait too long, so hardware can be the trigger.

Is it caused by my SSD?

It can be. The storage driver is a frequent suspect because it waits on the drive. Microsoft does not single out SSDs, so update the controller driver and SSD firmware first, then run the drive maker's diagnostic.

Should I switch the SATA driver to the Microsoft one?

Windows includes its own SATA AHCI driver, storahci.sys, alongside makers' drivers such as Intel's iaStorA.sys. If the dump names the maker's storage driver and no update exists, switching to the inbox driver is a test. Never change the SATA mode in the BIOS to do it.

What does DPC mean?

A deferred procedure call is short work a driver schedules to run at high priority after an interrupt. Microsoft says DPCs should not run longer than 100 microseconds; the real timeouts are set much higher.