Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\080122-12390-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff803`6e400000 PsLoadedModuleList = 0xfffff803`6f02a230
Debug session time: Mon Aug 1 21:15:58.352 2022 (UTC + 8:00)
System Uptime: 0 days 0:05:38.046
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:
fffff803`6e7f8590 48894c2408 mov qword ptr [rsp+8],rcx ss:ffff8181`2ad24e20=0000000000000133
2: 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: fffff8036f0fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for mtkbtfilterx.sys
*************************************************************************
*** ***
*** ***
*** 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: 3155
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 225981
Key : Analysis.Init.CPU.mSec
Value: 717
Key : Analysis.Init.Elapsed.mSec
Value: 302635
Key : Analysis.Memory.CommitPeak.Mb
Value: 101
Key : Bugcheck.Code.DumpHeader
Value: 0x133
Key : Bugcheck.Code.Register
Value: 0x133
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
FILE_IN_CAB: 080122-12390-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff8036f0fb320
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: leigod.exe
STACK_TEXT:
ffff8181`2ad24e18 fffff803`6e84d1da : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff8181`2ad24e20 fffff803`6e6aa263 : 000000b8`d059dbde ffff8181`2ad0b180 00000000`00000000 ffff8181`2ad0b180 : nt!KeAccumulateTicks+0x1a071a
ffff8181`2ad24e80 fffff803`6e6a9d4a : ffffdb87`5fb240e0 ffffed0b`19246cb0 fffff803`70da3c00 00000000`0000b201 : nt!KeClockInterruptNotify+0x453
ffff8181`2ad24f30 fffff803`6e664785 : ffffdb87`5fb240e0 00000000`00000000 00000000`00000000 ffff9d45`cfc79c01 : nt!HalpTimerClockIpiRoutine+0x1a
ffff8181`2ad24f60 fffff803`6e7fa03a : ffffed0b`19246cb0 ffffdb87`5fb240e0 00000000`00220003 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff8181`2ad24fb0 fffff803`6e7fa5a7 : ffff7e8a`9f8dcfea 00000000`000000ff 00000000`00000000 00000000`000001b0 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffed0b`19246c30 fffff803`6e70b401 : ffffdb87`5f409500 00000000`00000030 ffffed0b`00000000 00000000`00000180 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffed0b`19246dc0 fffff803`70f21061 : 00000000`00000d4e 00000000`00000000 00000000`00001001 00000000`00000fff : nt!KeAcquireSpinLockRaiseToDpc+0x11
ffffed0b`19246df0 fffff803`6e630d45 : 00000000`00000007 00000000`00000000 ffffed0b`19246f19 ffffdb87`82967be0 : ACPI!ACPIDispatchIrp+0x51
ffffed0b`19246e70 fffff803`71b980d7 : 00000000`00000001 00000000`73556f49 ffffdb87`8219cdd0 00000000`00000000 : nt!IofCallDriver+0x55
ffffed0b`19246eb0 fffff803`70daa977 : ffffdb87`8f8eb920 ffffdb87`8f8eb920 ffffdb87`8f8eb920 ffffdb87`8219cdd0 : UsbHub3!HUBPDO_EvtDeviceWdmIrpPreprocess+0x11d7
ffffed0b`19246f80 fffff803`6e630d45 : 00000000`0000000a ffffdb87`82ea8e10 00000000`00000000 ffffdb87`8f8eb920 : Wdf01000!FxDevice::DispatchWithLock+0x267 [minkernel\wdf\framework\shared\core\fxdevice.cpp @ 1447]
ffffed0b`19246fe0 fffff803`70f2b58d : ffffdb87`82ea8e10 ffffdb87`8f8eb920 00000000`000000d0 fffff803`70f21093 : nt!IofCallDriver+0x55
ffffed0b`19247020 fffff803`70f210d6 : ffffdb87`825f0b20 00000000`00000007 ffffdb87`8f8ebde0 fffff803`6e62d89f : ACPI!ACPIIrpDispatchDeviceControl+0xad
ffffed0b`19247060 fffff803`6e630d45 : 00000000`00000007 ffffdb87`8f8eb920 ffffed0b`192471d9 ffffdb87`7ccc41b8 : ACPI!ACPIDispatchIrp+0xc6
ffffed0b`192470e0 fffff803`71a91dc5 : 00000000`00000001 ffffdb87`8f8eb920 ffffed0b`192471d9 00000000`00000100 : nt!IofCallDriver+0x55
ffffed0b`19247120 fffff803`71a919a6 : ffffdb87`7d6441f8 00000000`00000000 fffff803`71aac008 ffffdb87`7ccc41b8 : usbccgp!DispatchPdoUrb+0x2c5
ffffed0b`19247240 fffff803`71a91292 : ffffdb87`8f8eb920 ffffdb87`7ccc41b0 ffffdb87`7ccc41b8 fffff803`6e7fa500 : usbccgp!DispatchPdoInternalDeviceControl+0x1c6
ffffed0b`192472b0 fffff803`6e630d45 : ffffdb87`7ccc4060 fffff803`6e7fa501 ffffdb87`82ff1200 00000000`00000000 : usbccgp!USBC_Dispatch+0x282
ffffed0b`19247380 fffff803`8fcb58ab : ffffdb87`8f8eb920 fffff803`8fce3c20 00000000`00000000 00000000`00051f01 : nt!IofCallDriver+0x55
ffffed0b`192473c0 ffffdb87`8f8eb920 : fffff803`8fce3c20 00000000`00000000 00000000`00051f01 00000000`00000001 : mtkbtfilterx+0x58ab
ffffed0b`192473c8 fffff803`8fce3c20 : 00000000`00000000 00000000`00051f01 00000000`00000001 fffff803`6e722f01 : 0xffffdb87`8f8eb920
ffffed0b`192473d0 00000000`00000000 : 00000000`00051f01 00000000`00000001 fffff803`6e722f01 ffffed0b`00000000 : mtkbtfilterx+0x33c20
SYMBOL_NAME: mtkbtfilterx+58ab
MODULE_NAME: mtkbtfilterx
IMAGE_NAME: mtkbtfilterx.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 58ab
FAILURE_BUCKET_ID: 0x133_DPC_mtkbtfilterx!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {cea12796-23a5-2bf6-2372-629b4a216dd8}
Followup: MachineOwner
---------嗨,保罗,来帮助你解决你的问题的。这个文件“mtkbtfilterx.sys”是联发科蓝牙适配器驱动程序。我建议您检查最近的更新。如果问题仍然存在,请尝试从PC制造商的站点卸载并重新安装较旧/不同版本的驱动程序。我
嗨,保罗,来帮助你解决你的问题的。这个文件“mtkbtfilterx.sys”是联发科蓝牙适配器驱动程序。我建议您检查最近的更新。如果问题仍然存在,请尝试从PC制造商的站点卸载并重新安装较旧/不同版本的驱动程序。我