The error message is triggered by the DPC Watchdog Timer when it detects a DPC (Deferred Procedure Call) is running past its predetermined runtime.

DPC Watchdog Violation Errors

This error is also known by its STOP code 0x00000133 (0x133 for short). You might see the error message or STOP code at seemingly random times or during a particular situation, like when the computer is first booting up or about to shut down, shortly after a Windows or other software update or installation, or while using a particular program or device. Since DPC Watchdog Violation errors are more often than not caused by a faulty device driver, addressing that is usually the fix. The particular driver to blame isn’t the same for everyone; some people have had luck fixing the storage driver or video card driver.

How to Fix DPC Watchdog Violation Error in Windows 10

Follow these suggestions to address the easier possible fixes first before moving on to the more advanced steps.

Need More Help?

If you don’t want to fix this problem yourself, see How Do I Get My Computer Fixed? for a complete list of your support options, plus help with everything along the way like figuring out repair costs, getting your files off, choosing a repair service, and a lot more. If you can’t restart due to the error, hold down the physical power button until the system shuts down, and then wait a minute before starting back up. Depending on the situation, some users have had luck fixing the error by:

Uninstalling a program Plugging a USB device into a different port Rolling back a driver Running System Restore Undoing an overclock

If you’re able to identify the device throwing the error, go there first. For example, if using your laptop touchpad causes the blue screen, use a mouse or the keyboard to uninstall that driver, and then download the most up-to-date one from the manufacturer’s website. If you’re unsure which driver to update, check all of them with a driver updater tool like Driver Booster. Try unplugging it or disabling it in Device Manager to see if the BSOD repeats.