Windows 10: BSOD: DPC_WATCHDOG VIOLATON (Windows Update Triggered)

Hello there,

Up until recently I've had no hiccups with Windows 10 (Enterprise).

Unfortunately lately I've had to manually disable the Windows Update Service as otherwise a non-optional update seems to automatically get pushed through and triggers a BSOD with the error: "DPC_WATCHDOG_VIOLATION"

Once the error is triggered my system is doomed to a BSOD loop, the only recourse for which I've found is to "reset this PC" using the startup recovery options...

It took quite some time for me to narrow down the cause to Windows Update but since disabling the service I've been BSOD free for almost a week. - The downside of course is I'm now blind to any updates which is always a security issure.

Any advice? Tips? Points of reference for further reading?

Much obliged,
Namaste,
Kaga.

:)

 

Windows 10 DPC_Watchdog service BSODs high GPU counts for compute work

This is becoming a very serious problem as Microsoft continues to strong-arm intel into releasing windows 10 only chips like Kaby Lake and Skylake-X.

the DPC watchdog service triggers a BSOD when compute loads like Octane or Redshift render take more than a couple seconds to return CUDA work from Nvidia cards. The chances of BSOD increase exponentially above 4 GPUs. 7 GPUs causes BSOD in under a minute.

This is not a hardware problem. Installing Windows 7 fixes everything and stops bluescreens because Windows 7 pre-dates the watchdog service.

I haven't found any way to disable DPC_Watchdog, and guides on how to tune tdrDelay in the registry are too vague, and windows 10 ignores the settings anyway.

This is not a hardware or driver problem.... This is a windows 10 problem.

please? begging you guys. Please make it so users can disable the DPC_Watchdog service.

 

Windows 10 - Bug Check 0x133 DPC_WATCHDOG

In order to stop all these BSOD's, I had to go back to Windows 8. I tried reinstalling Windows 7 but windows 10 would not let me go back to that version. I have not had a BSOD with DPC_watchdog since going back to Windows 8, so I really think the problem
is in Windows 10 somewhere.

 

Follow the instructions in the notice at the top of your thread please:

Attachment 107753