Frequent Blue Screen (BSOD) DPC_WATCHDOG_VIOLATION. Stuck on what the cause might be.

[brandscill]

Hello,

 

Hopefully someone here can point me in the right direction. I've been getting frequent blue screens with the error DPC_WATCHDOG_VIOLATION.

 

To date I've checked that the BIOS is up to date, all drivers are up to date and the SSD Firmware is up to date. None of these things seems to have resolved the issue.

 

Last night I ran Memtest86 and it turned up no problems with the RAM specifically.

 

I've got the minidump files and a speccy to share as well.

 

MiniDump files:

14/01/2020 20:22 GMT: http://s000.tinyupload.com/index.php?file_id=52089196158959972910

14/01/2020 20:28 GMT: http://s000.tinyupload.com/index.php?file_id=22506597807516513438

15/01/2020 22:04 GMT: http://s000.tinyupload.com/index.php?file_id=08388054449728680908

17/01/2020 16:26 GMT: http://s000.tinyupload.com/index.php?file_id=83571318657513343569

17/01/2020 16:28 GMT: http://s000.tinyupload.com/index.php?file_id=04389708683869368176

 

Speccy:

http://speccy.piriform.com/results/VBGvZe8hYgSbDAnodMAF568

[Radium_Angel]

Just now, brandscill said:

Hello,

 

Hopefully someone here can point me in the right direction. I've been getting frequent blue screens with the error DPC_WATCHDOG_VIOLATION.

 

To date I've checked that the BIOS is up to date, all drivers are up to date and the SSD Firmware is up to date. None of these things seems to have resolved the issue.

 

Last night I ran Memtest86 and it turned up no problems with the RAM specifically.

 

I've got the minidump files and a speccy to share as well.

 

MiniDump files:

14/01/2020 20:22 GMT: http://s000.tinyupload.com/index.php?file_id=52089196158959972910

14/01/2020 20:28 GMT: http://s000.tinyupload.com/index.php?file_id=22506597807516513438

15/01/2020 22:04 GMT: http://s000.tinyupload.com/index.php?file_id=08388054449728680908

17/01/2020 16:26 GMT: http://s000.tinyupload.com/index.php?file_id=83571318657513343569

17/01/2020 16:28 GMT: http://s000.tinyupload.com/index.php?file_id=04389708683869368176

 

Speccy:

http://speccy.piriform.com/results/VBGvZe8hYgSbDAnodMAF568

Give me some time, I'll deconstruct the crash dumps and tell you what's going on.

[brandscill]

3 minutes ago, Radium_Angel said:

Give me some time, I'll deconstruct the crash dumps and tell you what's going on.

Thanks!

[Radium_Angel]

4 minutes ago, brandscill said:

Hello,

 

Hopefully someone here can point me in the right direction. I've been getting frequent blue screens with the error DPC_WATCHDOG_VIOLATION.

 

To date I've checked that the BIOS is up to date, all drivers are up to date and the SSD Firmware is up to date. None of these things seems to have resolved the issue.

 

Last night I ran Memtest86 and it turned up no problems with the RAM specifically.

 

I've got the minidump files and a speccy to share as well.

 

MiniDump files:

14/01/2020 20:22 GMT: http://s000.tinyupload.com/index.php?file_id=52089196158959972910

14/01/2020 20:28 GMT: http://s000.tinyupload.com/index.php?file_id=22506597807516513438

15/01/2020 22:04 GMT: http://s000.tinyupload.com/index.php?file_id=08388054449728680908

17/01/2020 16:26 GMT: http://s000.tinyupload.com/index.php?file_id=83571318657513343569

17/01/2020 16:28 GMT: http://s000.tinyupload.com/index.php?file_id=04389708683869368176

 

Speccy:

http://speccy.piriform.com/results/VBGvZe8hYgSbDAnodMAF568

I'm going to post the basic dumps here, and then we can talk about them

___

 

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: fffff80331efa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout
 

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED
PROCESS_NAME:  Discord.exe

 

SYMBOL_NAME:  BTHUSB!BthUsb_ScoUrbStart+226

MODULE_NAME: BTHUSB

IMAGE_NAME:  BTHUSB.sys

IMAGE_VERSION:  10.0.19041.656

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  226

FAILURE_BUCKET_ID:  0x133_DPC_BTHUSB!BthUsb_ScoUrbStart

 

 

 

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: fffff803366fa320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
    additional information regarding this single DPC timeout
 

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

PROCESS_NAME:  EpicWebHelper.exe

 

SYMBOL_NAME:  ucx01000!Urb_LegacyTransferUrbCompletion+2

MODULE_NAME: ucx01000

IMAGE_NAME:  ucx01000.sys

IMAGE_VERSION:  10.0.19041.1030

FAILURE_BUCKET_ID:  0x133_DPC_ucx01000!Urb_LegacyTransferUrbCompletion
 

 

The other crash dumps are the same. Seems your main culprit is BTHUSB.sys which Google says is a bluetooth driver, ensure that's got an up to date driver (may have to go beyond what the vendor provides) or replace it entirely.

 

 

 

 

[brandscill]

Thanks for the information! 

 

It's an Intel Bluetooth adapter on the latest driver. Least I now know it's nothing expensive and worse case scenario I'll replace it.