BSOD while video conferencing

Question

My laptop, Asus VivoBook X542U, Windows 10 Pro, crashes (BSOD) while I video conference.
This happens on Zoom and also on Microsoft Teams.
Sometimes it happens the minute I enter the meeting. Other times it doesn't crash at all. But usually, it crashes after 20-30 minutes into the meeting.

I tried analyzing the dump file but unfortunately, I don't understand it. Can some help me figure out the cause of the failure?

Thanks in advance,

Itai

I've included the file itself here.

Here is the content of the file:

Loading Dump File [C:\Windows\Minidump\020721-75531-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 = 0xfffff802`1c400000 PsLoadedModuleList = 0xfffff802`1d02a2f0
Debug session time: Sun Feb  7 11:13:37.487 2021 (UTC + 2:00)
System Uptime: 1 days 21:55:02.281
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
...................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`1c7f5780 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff802`211cfe20=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: fffff8021d0fa320, 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: 2890

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-1LOSAGB

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 11177

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

    Key  : Analysis.System
    Value: CreateObject

ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8021d0fa320

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:  
fffff802`211cfe18 fffff802`1c83a988     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff802`211cfe20 fffff802`1c66f9a3     : 00002890`ecb422f3 fffff802`1957c180 00000000`00000000 fffff802`1957c180 : nt!KeAccumulateTicks+0x1c8788
fffff802`211cfe80 fffff802`1c66f48a     : fffff802`1d0f3880 fffff802`211c00f0 fffff802`23953e00 00000000`00006101 : nt!KeClockInterruptNotify+0x453
fffff802`211cff30 fffff802`1c727ef5     : fffff802`1d0f3880 fffff802`211cff40 00000000`00000010 ffff669b`0f9ebf21 : nt!HalpTimerClockIpiRoutine+0x1a
fffff802`211cff60 fffff802`1c7f722a     : fffff802`211c00f0 fffff802`1d0f3880 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`211cffb0 fffff802`1c7f7797     : 00000000`00000000 fffff802`2aa817e7 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff802`211c0070 fffff802`1c6e4799     : 00000000`00000004 00000000`00000000 fffff802`2aa90860 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`211c0200 fffff802`2aa89336     : ffffd103`e50d5920 ffffd103`eb635a60 ffffd103`e50d5920 fffff802`211c02d0 : nt!KeAcquireSpinLockRaiseToDpc+0x59
fffff802`211c0230 fffff802`2aa880c2     : ffffd103`e50d5900 ffffd103`00000003 ffffd103`f00b3a20 ffffd103`dceefd60 : BTHUSB!BthUsb_ScoReadUrbDone+0x146
fffff802`211c02e0 fffff802`2aa8915e     : 00000000`00000001 ffffd103`e50d5920 ffffd103`eb636420 ffffd103`f006ca20 : BTHUSB!BthUsb_ScoUrbComplete+0xfe
fffff802`211c0350 fffff802`1c64885e     : ffffd103`f006ca20 fffff802`211c0449 00000000`00000000 ffffd103`f006ce9b : BTHUSB!BthUsb_ScoReadTransferCallback+0xbe
fffff802`211c03c0 fffff802`1c648727     : 00000000`00000001 00000000`00000000 ffffd103`f005ba30 00000000`00000002 : nt!IopfCompleteRequest+0x11e
fffff802`211c04b0 fffff802`1f1a811a     : 00000000`c0000120 ffffd103`def54950 ffffd103`f006ca20 fffff802`211c0598 : nt!IofCompleteRequest+0x17
fffff802`211c04e0 fffff802`1f1a5bbf     : ffffd103`e4104d02 fffff802`00000001 ffffd103`f006ca20 00000000`c0000120 : Wdf01000!FxRequest::CompleteInternal+0x23a [minkernel\wdf\framework\shared\core\fxrequest.cpp @ 869] 
fffff802`211c0570 fffff802`29ce2181     : 00000000`c0010002 ffffd103`efaa2b30 ffffd103`efaa2cd0 ffffd103`f005be70 : Wdf01000!imp_WdfRequestComplete+0x8f [minkernel\wdf\framework\shared\core\fxrequestapi.cpp @ 436] 
fffff802`211c05d0 fffff802`29ce09b7     : 00000000`00000000 ffffd103`f005be10 fffff802`211c06d0 ffffd103`efaa2cd0 : USBXHCI!Isoch_Transfer_CompleteCancelable+0x215
fffff802`211c0630 fffff802`29ce162d     : ffffd103`f005be10 fffff802`211c0800 ffffd103`f005be70 fffff802`1c6087f9 : USBXHCI!Isoch_CompleteTransfers+0x19b
fffff802`211c0690 fffff802`29ce24ba     : ffffd103`efaf87b0 fffff802`211c0860 fffff802`211c0a60 ffffd103`dcaf9000 : USBXHCI!Isoch_ProcessTransferCompletion+0xed
fffff802`211c06f0 fffff802`1f1b940b     : 00000000`00000f44 00000000`00400a02 00000000`00000000 00002888`8919171a : USBXHCI!Isoch_WdfEvtDpcForTransferCompletion+0x2a
fffff802`211c0720 fffff802`1c60781e     : fffff802`1957f240 ffffd103`dc9ea000 fffff802`211c0a50 fffff802`00000002 : Wdf01000!FxDpc::FxDpcThunk+0x5b [minkernel\wdf\framework\kmdf\src\core\fxdpc.cpp @ 361] 
fffff802`211c0760 fffff802`1c606b04     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffff802`211c08d0 fffff802`1c7f92ee     : 00000000`00000000 fffff802`1957c180 fffff802`1d126600 ffffd103`de892080 : nt!KiRetireDpcList+0x1f4
fffff802`211c0b60 00000000`00000000     : fffff802`211c1000 fffff802`211ba000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

SYMBOL_NAME:  BTHUSB!BthUsb_ScoReadUrbDone+146

MODULE_NAME: BTHUSB

IMAGE_NAME:  BTHUSB.sys

IMAGE_VERSION:  10.0.19041.656

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  146

FAILURE_BUCKET_ID:  0x133_DPC_BTHUSB!BthUsb_ScoReadUrbDone

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {9227ad98-5276-40d5-224c-d392ecf1e1f1}

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

Answer 1

Hi Itai, glad to Help!

Answer 2

Hi Dave,

Thanks for your informative advice.

As a matter of fact, I am using a Bluetooth headset while video conferencing. I'll look into the drivers of the device.

Thanks for your generous help,

Itai

Answer 3

Hi ItaiSeri

I am Dave, an Independent Advisor, I will help you with this . . .

Your dump file seems to indicate it is the Bluetooth driver in Windows 10 that is causing the crashing, are you using a Bluetooth headset or any other Bluetooth device when you are on Teams and Zoom?

If so, try re-installing the device drivers for that device, form the support page for that device . . .