BSOD Anlysis help

Question

I'm dealing with recurring BSODs.
These happen when I have a Bluetooth headset connected.
I've tried changing my headphones, but it still continues.
I'm adding here the dump file log.
It would be great if some would be able to shed some light regarding how I can resolve this issue.
Thanks in advance,
Itai

Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\WINDOWS\Minidump\061721-151125-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff80681a00000 PsLoadedModuleList = 0xfffff8068262a230
Debug session time: Thu Jun 17 15:13:22.683 2021 (UTC + 3:00)
System Uptime: 2 days 19:55:55.391
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80681df6c20 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff806877d0c90=0000000000000133
0: kd> !analyze -v
ERROR: FindPlugIns 80070015

---

• *
• 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: fffff806826fb320, 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
**

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3437

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 32352

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

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

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

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff806826fb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff806877d0c88 fffff80681e1ed32 : 0000000000000133 0000000000000000 0000000000000501 0000000000000500 : nt!KeBugCheckEx
fffff806877d0c90 fffff80681c1c53d : 0000d2a137ec3487 fffff8067f542180 0000000000000246 0000000000eed2d9 : nt!KeAccumulateTicks+0x205a12
fffff806877d0cf0 fffff80681c1cae1 : 0000000000000000 00000000008e5997 fffff8067f542180 0000000000000001 : nt!KiUpdateRunTime+0x5d
fffff806877d0d40 fffff80681c16953 : fffff8067f542180 0000000000000000 fffff80682631568 0000000000000000 : nt!KiUpdateTime+0x4a1
fffff806877d0e80 fffff80681c1f312 : fffff806877c0e80 fffff806877c0f00 fffff806877c0f00 0000000000000002 : nt!KeClockInterruptNotify+0x2e3
fffff806877d0f30 fffff80681c7e795 : 0000023974836eef fffff806826f39a0 fffff806826f3a50 ffffd04770672c52 : nt!HalpTimerClockInterrupt+0xe2
fffff806877d0f60 fffff80681df86ca : fffff806877c0f00 fffff806826f39a0 0000000000000000 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806877d0fb0 fffff80681df8c37 : fffff80693dda000 ffff9788e6950d80 0000000000000000 ffff9788f7ea8a20 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff806877c0e80 fffff806853c1216 : 0000000000000020 0000000000000202 ffff9788e69689e8 0000000000000202 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff806877c1010 fffff806918817e7 : 0000000003ec0418 fffff806877c1120 00000000043c0464 fffff806877c1130 : WppRecorder!WppAutoLogTrace+0xe6
fffff806877c1080 fffff8069188641e : ffff9788f7509c60 ffff9788e6968960 ffff9788e55de050 fffff806853c129b : BTHUSB!WPP_RECORDER_AND_TRACE_SF_qq+0xaf
fffff806877c10e0 fffff80691886615 : ffff9788e6968760 ffff9788f7509c68 0000000000000016 fffff806877c1200 : BTHUSB!BthUsb_ScoFreeTransferContextImpl+0x6e
fffff806877c1180 fffff8069188cb89 : ffff9788f7509c60 0000000000000000 0000000000000000 fffff806877c1280 : BTHUSB!BthUsb_ScoReuseTransferCtxImpl+0xa5
fffff806877c11f0 fffff80691889579 : ffff9788f7509c60 0000000000000000 ffff9788e6968760 0000000000000001 : BTHUSB!RefObj_ReleaseEx+0x179
fffff806877c1230 fffff806918880c2 : ffff9788e6968700 ffff978800000003 ffff9788f6dd5a20 ffff9788eaf5ac00 : BTHUSB!BthUsb_ScoReadUrbDone+0x389
fffff806877c12e0 fffff8069188915e : 0000000000000001 ffff9788e6968760 ffff9788f750a0e0 ffff9788f0f09a20 : BTHUSB!BthUsb_ScoUrbComplete+0xfe
fffff806877c1350 fffff80681d0dede : ffff9788f0f09a20 fffff806877c1449 0000000000000000 ffff9788f0f09e9b : BTHUSB!BthUsb_ScoReadTransferCallback+0xbe
fffff806877c13c0 fffff80681d0dda7 : 0000000000000001 0000000000000000 ffff9788f414ca30 0000000000000002 : nt!IopfCompleteRequest+0x11e
fffff806877c14b0 fffff806852b811a : 00000000c0000120 ffff9788e54c4d50 ffff9788f0f09a20 fffff806877c1598 : nt!IofCompleteRequest+0x17
fffff806877c14e0 fffff806852b5bbf : ffff9788e5933b02 fffff80600000002 ffff9788f0f09a20 00000000c0000120 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869]
fffff806877c1570 fffff8068ce42181 : 00000000c0010002 ffff9788f6002a70 ffff9788f6002c10 ffff9788f414ce70 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436]
fffff806877c15d0 fffff8068ce409b7 : 0000000000000000 ffff9788f414ce10 fffff806877c16d0 ffff9788f6002c10 : USBXHCI!Isoch_Transfer_CompleteCancelable+0x215
fffff806877c1630 fffff8068ce4162d : ffff9788f414ce10 fffff806877c1800 ffff9788f414ce70 fffff80681d240a9 : USBXHCI!Isoch_CompleteTransfers+0x19b
fffff806877c1690 fffff8068ce424ba : ffff9788f01f84a0 fffff806877c1860 fffff806877c1a50 ffff9788de3f8000 : USBXHCI!Isoch_ProcessTransferCompletion+0xed
fffff806877c16f0 fffff806852c940b : 0000000000000f44 0000000000400a02 0000000000000000 0000d298d613228f : USBXHCI!Isoch_WdfEvtDpcForTransferCompletion+0x2a
fffff806877c1720 fffff80681d230ce : fffff8067f545240 ffff9788de1e6000 fffff806877c1a40 ffff978800000002 : Wdf01000!FxDpc::FxDpcThunk+0x5b [minkernel\wdf\framework\kmdf\src\core\fxdpc.cpp @ 361]
fffff806877c1760 fffff80681d223b4 : 0000000000000000 0000000000000000 0000000000140001 00000000008e56b4 : nt!KiExecuteAllDpcs+0x30e
fffff806877c18d0 fffff80681dfa78e : 0000000000000000 fffff8067f542180 fffff80682727a00 ffff9788f41c2080 : nt!KiRetireDpcList+0x1f4
fffff806877c1b60 0000000000000000 : fffff806877c2000 fffff806877bb000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME: WppRecorder!WppAutoLogTrace+e6

MODULE_NAME: WppRecorder

IMAGE_NAME: WppRecorder.sys

IMAGE_VERSION: 10.0.19041.1030

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: e6

FAILURE_BUCKET_ID: 0x133_DPC_WppRecorder!WppAutoLogTrace

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {fd1da68d-ab73-baaf-a7e9-f0c09fd6a112}

Followup: MachineOwner

Answer 1

Please run V2 > post a share link into this thread

https://www.windowsq.com/resources/v2-log-collector.8/
https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.

Answer 2

Hi,
Try to reinstall Intel® Management Engine (Intel® ME) driver，Motherboard and USB driver from the manufacturer's official website.
Hope this helps and please help to accept as Answer if the response is useful.
Best Regards,
Carl