Question Computer randomly restarts about once per day. Possibly from Bluetooth dongle

NelsonTheSmith

Distinguished
Apr 11, 2015
26
0
18,530
0
Hi,

I have had this issue for about a week now. Every day at a random time my computer will completely restart instantly with no warning or BSOD. I got a minidump from the first time that it happened but windows has not given me another since the first time.

This is what I get when I analyze the minidump

0: kd> !analyze -v
***
  • *
  • Bugcheck Analysis *
  • *
***

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

Debugging Details:
------------------

*
* *
* *
* Either you specified an unqualified symbol, or your debugger *
* doesn't have full symbol information. Unqualified symbol *
* resolution is turned off by default. Please either specify a *
* fully qualified symbol module!symbolname, or enable resolution *
* of unqualified symbols by typing ".symopt- 100". Note that *
* enabling unqualified symbol resolution with network symbol *
* server shares in the symbol path may cause the debugger to *
* appear to hang for long periods of time when an incorrect *
* symbol name is typed or the network symbol server is down. *
* *
* For some commands to work properly, your symbol path *
* must point to .pdb files that have full type information. *
* *
* Certain .pdb files (such as the public OS symbols) do not *
* contain the required information. Contact the group that *
* provided you with these symbols if you need this command to *
* work. *
* *
* Type referenced: TickPeriods *
* *
*
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3233

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 3855

Key : Analysis.Init.CPU.mSec
Value: 312

Key : Analysis.Init.Elapsed.mSec
Value: 2483

Key : Analysis.Memory.CommitPeak.Mb
Value: 113

Key : Bugcheck.Code.DumpHeader
Value: 0x133

Key : Bugcheck.Code.Register
Value: 0x133

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: 071422-12437-01.dmp

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff804408fb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff80443c92fe0 -- (.trap 0xfffff80443c92fe0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff8e09b93fe270 rbx=0000000000000000 rcx=ffffdc0132401000
rdx=000000000022aab1 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8044f561bc1 rsp=fffff80443c93170 rbp=ffff8e09c934ec20
r8=00000000000003e9 r9=0000000000000009 r10=ffff8e09b9a93970
r11=ffffcbfac7800000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
USBXHCI!Controller_UcxEvtGetCurrentFrameNumber+0x81:
fffff8044f561bc1 41ffc0 inc r8d
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff804
43ca2e18 fffff8044004d1da : 0000000000000133 0000000000000000 0000000000000501 0000000000000500 : nt!KeBugCheckEx
fffff804
43ca2e20 fffff8043feaa263 : 000007e625aaf456 fffff8043b822180 0000000000000000 fffff8043b822180 : nt!KeAccumulateTicks+0x1a071a
fffff804
43ca2e80 fffff8043fea9d4a : fffff804408f3880 fffff80443c93060 fffff80442a50500 0000000000006001 : nt!KeClockInterruptNotify+0x453
fffff804
43ca2f30 fffff8043fe64785 : fffff804408f3880 0000000000000000 0000000000000000 ffff45f32569e797 : nt!HalpTimerClockIpiRoutine+0x1a
fffff804
43ca2f60 fffff8043fffa03a : fffff80443c93060 fffff804408f3880 ffff8e09c40a63c0 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff804
43ca2fb0 fffff8043fffa5a7 : ffff8e09c7807010 ffff8e09c40a8340 fffff8043fff4680 fffff8043ff2397a : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff804
43c92fe0 fffff8044f561bc1 : 0000000000000008 000000000000001e 0000000000000002 fffff8044fa017e7 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff804
43c93170 fffff8044f609169 : ffff8e09b9c648e0 fffff8043cca129b 0000000000000008 fffff80443c93238 : USBXHCI!Controller_UcxEvtGetCurrentFrameNumber+0x81
fffff804
43c931b0 fffff8044fa07e00 : ffff8e09bfaf39c0 ffff8e09c934ec20 0000000000000000 0000000000000020 : ucx01000!Usbd_BusQueryBusTime+0x79
fffff804
43c93200 fffff8044fa08f58 : ffff8e09c934ec20 0000000000000000 0000000000000051 0000000000000001 : BTHUSB!BthUsb_ScoUrbStart+0x80
fffff804
43c93280 fffff8044fa0955b : ffff8e09c934e860 0000000000000000 ffff8e09bfaf3760 0000000000000001 : BTHUSB!BthUsb_ScoReadData+0x160
fffff804
43c932f0 fffff8044fa080c1 : ffff8e09bfaf3700 ffff8e0900000003 ffff8e09cbdbe010 ffff8e09c64fcab0 : BTHUSB!BthUsb_ScoReadUrbDone+0x36b
fffff804
43c933a0 fffff8044fa0915e : 0000000000000001 ffff8e09bfaf3760 ffff8e09c934eaa0 ffff8e09ca31a560 : BTHUSB!BthUsb_ScoUrbComplete+0xfd
fffff804
43c93410 fffff8043fe260ce : ffff8e09ca31a560 fffff80443c93509 0000000000000000 ffff8e09ca31a9db : BTHUSB!BthUsb_ScoReadTransferCallback+0xbe
fffff804
43c93480 fffff8043fe25f97 : 0000000000000001 0000000000000000 ffff8e09c7808020 0000000000000002 : nt!IopfCompleteRequest+0x11e
fffff804
43c93570 fffff804423b811a : 00000000c0000120 ffff8e09b91bda20 ffff8e09ca31a560 fffff80443c93658 : nt!IofCompleteRequest+0x17
fffff804
43c935a0 fffff804423b5bbf : ffff8e09bce9fd02 fffff80400000003 ffff8e09ca31a560 00000000c0000120 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
fffff804
43c93630 fffff8044f5a3678 : 00000000c0010002 ffff8e09c56f29c0 ffff8e09c56f2b60 ffff8e09c7808460 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
fffff804
43c93690 fffff8044f5a1f97 : 0000000000000000 ffff8e09c7808400 fffff80443c93790 ffff8e09c56f2b60 : USBXHCI!Isoch_Transfer_CompleteCancelable+0x214
fffff804
43c936f0 fffff8044f5a2c0d : ffff8e09c7808400 fffff80443c93900 ffff8e09c7808460 fffff8043fecb509 : USBXHCI!Isoch_CompleteTransfers+0x19b
fffff804
43c93750 fffff8044f5a39aa : ffff8e09c36fca20 fffff80443c93920 fffff80443c93af0 ffff8e09b38e5000 : USBXHCI!Isoch_ProcessTransferCompletion+0xed
fffff804
43c937b0 fffff804423c940a : 0000000000000f44 0000000000400a02 0000000000000000 000007d46e4c4914 : USBXHCI!Isoch_WdfEvtDpcForTransferCompletion+0x2a
fffff804
43c937e0 fffff8043feca52e : fffff8043b825240 ffff8e09b36e5000 fffff80443c93ae0 0000000000000002 : Wdf01000!FxDpc::FxDpcThunk+0x5a [minkernel\wdf\framework\kmdf\src\core\fxdpc.cpp @ 354]
fffff804
43c93820 fffff8043fec9814 : 0000000000000000 fffff8043ff2397a fffff80443c939d0 0000000000000000 : nt!KiExecuteAllDpcs+0x30e
fffff804
43c93990 fffff8043fffc0fe : 0000000000000000 fffff8043b822180 fffff80440927a00 ffff8e09caccd040 : nt!KiRetireDpcList+0x1f4
fffff804
43c93c20 0000000000000000 : fffff80443c94000 fffff80443c8d000 0000000000000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: BTHUSB!BthUsb_ScoUrbStart+80

MODULE_NAME: BTHUSB

IMAGE_NAME: BTHUSB.sys

IMAGE_VERSION: 10.0.19041.1865

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 80

FAILURE_BUCKET_ID: 0x133_DPC_BTHUSB!BthUsb_ScoUrbStart

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7d170e63-0f67-a070-2760-456bc604cb13}

Followup: MachineOwner
---------

After seeing this I assumed it was an issue caused by the USB Bluetooth dongle I have in my computer that I use for headphones. I have tried reinstalling the drivers for it but the issue is still happening.

If anyone has any ideas on how to resolve this or if you need any more info about my system I am happy to provide it. Thank you!
 

Lutfij

Titan
Moderator
Can you pass a link to the BT adapter that you're working with? To me, it looks like a driver issue with your USB port(s). Might want to also include the make and model of your motherboard and it's BIOS version at the time of writing. Make and model of your PSU and it's age?
 

NelsonTheSmith

Distinguished
Apr 11, 2015
26
0
18,530
0
Can you pass a link to the BT adapter that you're working with? To me, it looks like a driver issue with your USB port(s). Might want to also include the make and model of your motherboard and it's BIOS version at the time of writing. Make and model of your PSU and it's age?
Hey there sorry for the late reply. The BT dongle is a "Kinivo BTD-400 Bluetooth 4.0" (I think). My MOBO is an MSI B450 Tomahawk Max running on bios version 3.E0. I also have a 1000 watt EVGA PSU. Not sure of the exact model but it is less than a year old.
 

ASK THE COMMUNITY