This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above. The value of Parameter 1 indicates whether a single DPC exceeded a timeout, or whether the system cumulatively spent an extended period of time at IRQL DISPATCH_LEVEL or above.

The user ends with the a DPC_WATCHDOG_VIOLATION BSOD. Generally the machine can be rebooted. If the machine continues to crash, reinstalling Windows may be the only options.

This has been seen with Windows Vista and above rarely. It seems to be provoked with CPU saturation combined with flakey drivers. This BSOD has been seen with desktop and laptop machines alike.

It’s advisable to check for an updated BIOS for the motherboard as a first step. Much of the hardware on a modern machine is integrated into the motherboard. Our I3-2100 box has an Asus P8H81-M motherboard and the update software crashes with Windows 10. Worse was the fact that the Asus support site did not have the correct BIOS versions posted. Eventually we found the proper BIOS update on their forum, which fixed some of the festering problems. With the updated BIOS we finally are able to get secure boot working and the crashing stopped.

MSFT has indicated it has been seen with iastore.sys among other possible faults. The Bug Check code for this bluescreen is 0x00000133. Lots more BSOD codes where this came from.