Windows 10: DPC_WATCHDOG_VIOLATION on new PC

I put together a new PC over the summer, and I've been battling Blue Screen of Death ever since the beginning. All that I have been able to narrow it down is that it is related to entering a power-save/sleep mode or coming out of it. It doesn't happen frequent enough for me to A/B test it (remove XYZ component and see if it happens still).


It NEVER happens while I am playing a video game. It mostly happens when I leave the PC idle (hibernate is turned off). It somewhat fequently happens while I am just browsing or reading.


I have some dump logs, but I'm not sure how useful. Honestly it seems like my system enters DPC IRQL level and then tries to grab a spin lock that it never can acquire. Why? Who has the lock? I have no idea.


https://1drv.ms/u/s!AiLxI_Am_4ODnQqJZqgqSaDQh21r

https://1drv.ms/u/s!AiLxI_Am_4ODnQwea8D858oAdMMd

https://1drv.ms/u/s!AiLxI_Am_4ODnQuxtUetiQlvwUap
https://1drv.ms/u/s!AiLxI_Am_4ODnQ028pcQMFA6boy8

It has crashed more than these times, but most the time it does not generate a dump file.


Here are some additional hardware live kernel events from the event log:


Problem Event Name: LiveKernelEvent

Code: 144

Parameter 1: 3003

Parameter 2: ffff918ca28bf5b0

Parameter 3: 40010000

Parameter 4: 0

OS version: 10_0_18362

Service Pack: 0_0

Product: 256_1

OS Version: 10.0.18362.2.0.0.256.48

Locale ID: 1033


Problem signature

Problem Event Name: LiveKernelEvent

Code: 144

Parameter 1: 1003

Parameter 2: ffff8d87e081f860

Parameter 3: 0

Parameter 4: 0

OS version: 10_0_18362

Service Pack: 0_0

Product: 256_1

OS Version: 10.0.18362.2.0.0.256.48

Locale ID: 1033




Due to the callstacks, and the live kernel events noted... I think it's related to sleep and USB. Anyone have any ideas? I have a corsair AIO water cooler that is plugged directly into my motherboard USB. I also have a NZXT CAM fan controller... which I am not using (in favor of the Corsair stuff). I just realized I left this plugged in, so I'm going to remove the USB from my motherboard.


Also, the device manager listed my NZXT CAM fan controller as "Unable to read device descriptor" in the device manager.


Could one bad USB device cause all this chaos?


Another note... one time I unplugged a USB device from my PC and it immediately triggered the issue.


Here are a couple of callstacks from the 133 DPC check dump files (for those who may not want to open in WinDbg):



From 082719-7171-01.dmp:


DPC_WATCHDOG_VIOLATION (133)

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

or above.

Arguments:

Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending

component can usually be identified with a stack trace.

Arg2: 0000000000000501, The DPC time count (in ticks).

Arg3: 0000000000000500, The DPC time allotment (in ticks).

Arg4: fffff80130171350, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

additional information regarding this single DPC timeout





STACK_TEXT:

fffff801`35c17af8 fffff801`2fdedb41 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

fffff801`35c17b00 fffff801`2fc1ebaf : 0002b2b1`25626b08 fffff801`2d166180 00000000`00000286 00000000`00cdfda1 : nt!KeAccumulateTicks+0x1cb841

fffff801`35c17b60 fffff801`2fb601e1 : 00000000`00000000 fffff801`2fbcbbf0 fffff801`35c07f40 fffff801`2fbcbca0 : nt!KeClockInterruptNotify+0xcf

fffff801`35c17f30 fffff801`2fc029e5 : fffff801`2fbcbbf0 00000000`00000010 ffff69ea`83abe02b ffffb081`42bfab78 : hal!HalpTimerClockIpiRoutine+0x21

fffff801`35c17f60 fffff801`2fdc175a : fffff801`35c07f40 fffff801`2fbcbbf0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5

fffff801`35c17fb0 fffff801`2fdc1cc7 : 00000000`00000808 fffff801`2fc4ba50 00000001`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

fffff801`35c07ec0 fffff801`2fca2170 : 00000000`00000103 00000000`00000000 ffffb081`35e02100 fffff801`2fc45777 : nt!KiInterruptDispatchNoLockNoEtw+0x37

fffff801`35c08050 fffff801`2fca1d57 : ffffb081`42bfab78 fffff801`2d166180 00000000`00000202 fffff801`2fc48a54 : nt!KxWaitForSpinLockAndAcquire+0x30

fffff801`35c08080 fffff801`3396352c : ffffb081`42bfab70 00000000`00000000 00000000`00000103 00000000`00000000 : nt!KeAcquireSpinLockRaiseToDpc+0x87

fffff801`35c080b0 fffff801`49ef7e64 : ffffb081`4348e5c0 ffffb081`5161a9a0 ffffb081`578df100 00000000`00000000 : SleepStudyHelper!SleepstudyHelper_ComponentInactive+0x3c

fffff801`35c080e0 fffff801`49ef9a4a : ffffb081`4348e5a0 ffffb081`4348e5a0 00000000`00000000 ffffb081`578df100 : HIDCLASS!HidpFdoReleasePoFxPowerReferenceWithTag+0x64

fffff801`35c08160 fffff801`2fc47079 : ffffb081`5161a9a0 fffff801`35c08299 ffffb081`42919450 ffffb081`5161ae63 : HIDCLASS!HidpInterruptWriteComplete+0x14a

fffff801`35c081f0 fffff801`2fc46f47 : ffffb081`428dc8d0 fffff801`4bac8f00 00000000`00000001 00000000`00000001 : nt!IopfCompleteRequest+0x119

fffff801`35c08300 fffff801`33a083fd : 00000000`00000000 ffffb081`4dbc4020 00000000`00000002 fffff801`4bab9700 : nt!IofCompleteRequest+0x17

fffff801`35c08330 fffff801`33a07ecb : ffffb081`4dbc4102 fffff801`35c08451 ffffb081`5161a9a0 00000000`00000000 : Wdf01000!FxRequest::CompleteInternal+0x22d [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]

fffff801`35c083c0 fffff801`4bac7e80 : 00000000`ffffff02 ffffb081`4dbc4020 ffffb081`434d6dc0 ffffb081`434d6dc0 : Wdf01000!imp_WdfRequestComplete+0x8b [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]

fffff801`35c08420 fffff801`4bac5cf4 : ffffb081`4dbc41c0 ffffb081`434d6e20 ffffb081`4dbc4250 fffff801`35c086f8 : USBXHCI!Bulk_Transfer_CompleteCancelable+0x19c

fffff801`35c08480 fffff801`4bac4460 : 00000000`00000000 ffffb081`42b77030 ffffb081`42b77100 fffff801`3397208d : USBXHCI!Bulk_ProcessTransferEventWithED1+0x464

fffff801`35c08540 fffff801`4bab98d3 : 00000000`00000000 fffff801`49e38c31 00000000`00c00100 fffff801`35c08670 : USBXHCI!Bulk_EP_TransferEventHandler+0x10

fffff801`35c08570 fffff801`4baaba4f : 00000000`0000002b fffff801`35c08661 ffffb081`41e908a0 fffff801`4ba934b9 : USBXHCI!TR_TransferEventHandler+0x17

fffff801`35c085a0 fffff801`4bacc2be : fffff801`35c086f8 fffff801`35c086c8 00000000`00000000 fffff801`35c086d0 : USBXHCI!Endpoint_TransferEventHandler+0x167

fffff801`35c08620 fffff801`4baaea3c : ffffb081`43072e30 fffff801`35c08719 00000000`00000000 ffffb081`42c314b0 : USBXHCI!UsbDevice_TransferEventHandler+0xa6

fffff801`35c08680 fffff801`4baaf55c : 00000000`00000000 00000000`00000001 00000000`00000000 ffffb081`43072c30 : USBXHCI!Interrupter_DeferredWorkProcessor+0x578

fffff801`35c08780 fffff801`33a026ad : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc

fffff801`35c087b0 fffff801`2fc6a985 : fffff801`2d166180 00000000`00000001 fffff801`35c087a8 00000000`00000000 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x9d [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 410]

fffff801`35c087f0 fffff801`2fc69fdf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x305

fffff801`35c08930 fffff801`2fdc3804 : 00000000`00000000 fffff801`2d166180 fffff801`3018f400 ffffb081`517b0080 : nt!KiRetireDpcList+0x1ef

fffff801`35c08b60 00000000`00000000 : fffff801`35c09000 fffff801`35c02000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84



From 081419-7578-01.dmp:



DPC_WATCHDOG_VIOLATION (133)

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

or above.

Arguments:

Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending

component can usually be identified with a stack trace.

Arg2: 0000000000000501, The DPC time count (in ticks).

Arg3: 0000000000000500, The DPC time allotment (in ticks).

Arg4: fffff80235571350, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

additional information regarding this single DPC timeout





STACK_TEXT:

ffffdc81`e7592af8 fffff802`351edb41 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

ffffdc81`e7592b00 fffff802`3501f1a4 : 000001c6`17d5fbcf 00000000`00000000 00000000`0000768a ffffdc81`e7a40180 : nt!KeAccumulateTicks+0x1cb841

ffffdc81`e7592b60 fffff802`35ab64b7 : 00000000`00000000 ffffd580`9a43f5c0 ffffd580`9a43f640 00000000`00000002 : nt!KeClockInterruptNotify+0x6c4

ffffdc81`e7592f30 fffff802`350029e5 : 00000001`1ab56fdc ffffc50f`1ced2000 ffffc50f`1ced20b0 ffffe487`d485f19c : hal!HalpTimerClockInterrupt+0xf7

ffffdc81`e7592f60 fffff802`351c175a : ffffd580`9a43f640 ffffc50f`1ced2000 00000000`00000000 ffffc50f`1ced2000 : nt!KiCallInterruptServiceRoutine+0xa5

ffffdc81`e7592fb0 fffff802`351c1cc7 : 00000000`00000000 ffffdc81`e7a40180 ffffc50f`2fb47e10 fffff802`351c1cd4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

ffffd580`9a43f5c0 fffff802`3501b87b : ffffffff`ffffffd1 fffff802`355a9573 00000000`00000010 00000000`00000282 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffffd580`9a43f750 fffff802`355a9585 : 00000000`00000000 00000000`00000001 00000000`00000000 00000001`0ec85b2b : nt!KeYieldProcessorEx+0x1b

ffffd580`9a43f780 fffff802`355a86e5 : 00000000`2520f49a ffffdc81`e7a40180 ffffc50f`2fb47e10 00000000`00000000 : nt!IopLiveDumpProcessCorralStateChange+0x2d

ffffd580`9a43f7b0 fffff802`3506a985 : ffffdc81`e7a42f80 00000000`00000001 ffffd580`9a43f7a8 00000000`00000000 : nt!IopLiveDumpCorralDpc+0x55

ffffd580`9a43f7f0 fffff802`35069fdf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x305

ffffd580`9a43f930 fffff802`351c3804 : ffffffff`00000000 ffffdc81`e7a40180 ffffdc81`e7a51440 ffffc50f`1d71a080 : nt!KiRetireDpcList+0x1ef

ffffd580`9a43fb60 00000000`00000000 : ffffd580`9a440000 ffffd580`9a439000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84


From 081419-7484-01.dmp :



DPC_WATCHDOG_VIOLATION (133)

The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL

or above.

Arguments:

Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending

component can usually be identified with a stack trace.

Arg2: 0000000000000501, The DPC time count (in ticks).

Arg3: 0000000000000500, The DPC time allotment (in ticks).

Arg4: fffff80159f71350, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains

additional information regarding this single DPC timeout



STACK_TEXT:

ffffdf00`3e191af8 fffff801`59bedb41 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

ffffdf00`3e191b00 fffff801`59a1f1a4 : 000002af`4e0df018 00000000`00000000 00000000`0000c91f ffffdf00`3e640180 : nt!KeAccumulateTicks+0x1cb841

ffffdf00`3e191b60 fffff801`5a4b64b7 : 00000000`00000000 ffffa00f`7be3f5c0 ffffa00f`7be3f640 00000000`00000002 : nt!KeClockInterruptNotify+0x6c4

ffffdf00`3e191f30 fffff801`59a029e5 : 00000001`df996c6f ffff8f8d`eb6d2000 ffff8f8d`eb6d20b0 ffffff34`6a13e372 : hal!HalpTimerClockInterrupt+0xf7

ffffdf00`3e191f60 fffff801`59bc175a : ffffa00f`7be3f640 ffff8f8d`eb6d2000 00000000`00000000 ffff8f8d`eb6d2000 : nt!KiCallInterruptServiceRoutine+0xa5

ffffdf00`3e191fb0 fffff801`59bc1cc7 : 00000000`00000000 00000000`00000000 ffff8f8d`fb943a90 fffff801`59bc1cd4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

ffffa00f`7be3f5c0 fffff801`59a1b87b : ffffffff`ffffffd1 fffff801`59fa9573 00000000`00000010 00000000`00000282 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffffa00f`7be3f750 fffff801`59fa9585 : 00000000`00000000 00000000`00000001 00000000`00000000 00000001`d3ac9ac1 : nt!KeYieldProcessorEx+0x1b

ffffa00f`7be3f780 fffff801`59fa86e5 : 00000000`2520b4e3 ffffdf00`3e640180 ffff8f8d`fb943a90 00000000`00000000 : nt!IopLiveDumpProcessCorralStateChange+0x2d

ffffa00f`7be3f7b0 fffff801`59a6a985 : ffffdf00`3e642f80 00000000`00000001 ffffa00f`7be3f7a8 00000000`00000000 : nt!IopLiveDumpCorralDpc+0x55

ffffa00f`7be3f7f0 fffff801`59a69fdf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x305

ffffa00f`7be3f930 fffff801`59bc3804 : ffffffff`00000000 ffffdf00`3e640180 ffffdf00`3e651440 ffff8f8e`014a1040 : nt!KiRetireDpcList+0x1ef

ffffa00f`7be3fb60 00000000`00000000 : ffffa00f`7be40000 ffffa00f`7be39000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84




Does anyone have any guidance? Do these kind of errors surrounding USB suggest any specific hardware failure? My PC went a whole month without crashing once... and then it started back up again lately - specifically after I updated Corsair iCue software. However, I want more hard evidence that Corsair stuff is bad before I throw it all away. Do I need to try clean Windows install?



Any help would be appreciated.

:)

 

DPC_WATCHDOG_VIOLATION

Hi,

It is possible that the error DPC_WATCHDOG_VIOLATION may occur if the iastor.sys driver is incompatible with Windows 10. To isolate your issue, we'd like to gather more information:

• Have you made any recent changes before this issue occurred?
• What troubleshooting steps have you done so far?

Any response will be highly appreciated.

 

DPC_Watchdog_Violation

Hi,

In most cases, faulty drivers are the reason why DPC_Watchdog_Violation BSOD occurs. To further assist your issue, kindly answer these following questions:

• What are the specifications of your PC?
• Is your PC up-to-date?
• Have you made any changes to your PC prior to the issue?

We'll be looking forward for your reply.

Regards.

 

Blue screen: DPC_WATCHDOG_VIOLATION

After a recent updating, my machine has blue screen every 5 - 10 minutes.

The error code is DPC_WATCHDOG_VIOLATION

I saw another post here which suggest to use "iastor.sys". But I don't have that in the driver list. Mine is storahci.sys.

Please advise! Thanks,