Microsoft (R) Windows Debugger Version 10.0.22473.1005 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\112721-16609-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff801`6d000000 PsLoadedModuleList = 0xfffff801`6dc2a2d0 Debug session time: Sat Nov 27 20:00:41.286 2021 (UTC 8:00) System Uptime: 0 days 0:18:38.093 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: fffff801`6d3f72a0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffff9c80`43cbde20=0000000000000133 9: 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: fffff8016dcfb320, 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 SmbCo10X64.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: 2890 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 12560 Key : Analysis.Init.CPU.mSec Value: 749 Key : Analysis.Init.Elapsed.mSec Value: 98979 Key : Analysis.Memory.CommitPeak.Mb Value: 100 FILE_IN_CAB: 112721-16609-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff8016dcfb320 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: ffff9c80`43cbde18 fffff801`6d41f5fa : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffff9c80`43cbde20 fffff801`6d216953 : 00000242`b73cd768 ffff9c80`43cc0180 00000000`00000000 ffff9c80`43cc0180 : nt!KeAccumulateTicks 0x20644a ffff9c80`43cbde80 fffff801`6d21643a : ffffb70e`ed518780 ffffc90f`3e6ae0e0 ffffc90f`3e6afa00 00000000`00000000 : nt!KeClockInterruptNotify 0x453 ffff9c80`43cbdf30 fffff801`6d2de055 : ffffb70e`ed518780 00000000`00000000 00000000`00000000 fffffe9c`f58a3dd3 : nt!HalpTimerClockIpiRoutine 0x1a ffff9c80`43cbdf60 fffff801`6d3f8d4a : ffffc90f`3e6ae0e0 ffffb70e`ed518780 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffff9c80`43cbdfb0 fffff801`6d3f92b7 : ffffb70f`15bfa000 fffff801`6d28da84 ffffc90f`3e6ae2c8 fffff801`6d3f92c4 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffffc90f`3e6ae060 fffff801`6d280c67 : 00000000`00000010 00000000`00000202 ffffc90f`3e6ae218 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffffc90f`3e6ae1f0 fffff801`6d2c0dea : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KeYieldProcessorEx 0x17 ffffc90f`3e6ae220 fffff801`6d2c0daf : 00000000`1ca6dcd3 00000000`ffffffff 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip 0x2a ffffc90f`3e6ae250 fffff801`6fa0b41d : 00000000`000b77fd 00000000`00000000 ffffc90f`3e6ae470 ffffb70f`0e733180 : nt!KeAcquireInStackQueuedSpinLock 0x7f ffffc90f`3e6ae280 00000000`000b77fd : 00000000`00000000 ffffc90f`3e6ae470 ffffb70f`0e733180 ffffb70f`0fd8dc60 : SmbCo10X64 0x1b41d ffffc90f`3e6ae288 00000000`00000000 : ffffc90f`3e6ae470 ffffb70f`0e733180 ffffb70f`0fd8dc60 00000000`000000c0 : 0xb77fd SYMBOL_NAME: SmbCo10X64 1b41d MODULE_NAME: SmbCo10X64 IMAGE_NAME: SmbCo10X64.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 1b41d FAILURE_BUCKET_ID: 0x133_DPC_SmbCo10X64!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {b7ae26a3-5838-8ff0-cad2-fb40469d2555} Followup: MachineOwner --------- 9: 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: fffff8016dcfb320, 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: 2483 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2507 Key : Analysis.Init.CPU.mSec Value: 3640 Key : Analysis.Init.Elapsed.mSec Value: 111543 Key : Analysis.Memory.CommitPeak.Mb Value: 100 FILE_IN_CAB: 112721-16609-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff8016dcfb320 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: ffff9c80`43cbde18 fffff801`6d41f5fa : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffff9c80`43cbde20 fffff801`6d216953 : 00000242`b73cd768 ffff9c80`43cc0180 00000000`00000000 ffff9c80`43cc0180 : nt!KeAccumulateTicks 0x20644a ffff9c80`43cbde80 fffff801`6d21643a : ffffb70e`ed518780 ffffc90f`3e6ae0e0 ffffc90f`3e6afa00 00000000`00000000 : nt!KeClockInterruptNotify 0x453 ffff9c80`43cbdf30 fffff801`6d2de055 : ffffb70e`ed518780 00000000`00000000 00000000`00000000 fffffe9c`f58a3dd3 : nt!HalpTimerClockIpiRoutine 0x1a ffff9c80`43cbdf60 fffff801`6d3f8d4a : ffffc90f`3e6ae0e0 ffffb70e`ed518780 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffff9c80`43cbdfb0 fffff801`6d3f92b7 : ffffb70f`15bfa000 fffff801`6d28da84 ffffc90f`3e6ae2c8 fffff801`6d3f92c4 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffffc90f`3e6ae060 fffff801`6d280c67 : 00000000`00000010 00000000`00000202 ffffc90f`3e6ae218 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffffc90f`3e6ae1f0 fffff801`6d2c0dea : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KeYieldProcessorEx 0x17 ffffc90f`3e6ae220 fffff801`6d2c0daf : 00000000`1ca6dcd3 00000000`ffffffff 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip 0x2a ffffc90f`3e6ae250 fffff801`6fa0b41d : 00000000`000b77fd 00000000`00000000 ffffc90f`3e6ae470 ffffb70f`0e733180 : nt!KeAcquireInStackQueuedSpinLock 0x7f ffffc90f`3e6ae280 00000000`000b77fd : 00000000`00000000 ffffc90f`3e6ae470 ffffb70f`0e733180 ffffb70f`0fd8dc60 : SmbCo10X64 0x1b41d ffffc90f`3e6ae288 00000000`00000000 : ffffc90f`3e6ae470 ffffb70f`0e733180 ffffb70f`0fd8dc60 00000000`000000c0 : 0xb77fd SYMBOL_NAME: SmbCo10X64 1b41d MODULE_NAME: SmbCo10X64 IMAGE_NAME: SmbCo10X64.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 1b41d FAILURE_BUCKET_ID: 0x133_DPC_SmbCo10X64!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {b7ae26a3-5838-8ff0-cad2-fb40469d2555} Followup: MachineOwner --------- 9: 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: fffff8016dcfb320, 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: 2436 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2445 Key : Analysis.Init.CPU.mSec Value: 6186 Key : Analysis.Init.Elapsed.mSec Value: 594421 Key : Analysis.Memory.CommitPeak.Mb Value: 100 FILE_IN_CAB: 112721-16609-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff8016dcfb320 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: ffff9c80`43cbde18 fffff801`6d41f5fa : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffff9c80`43cbde20 fffff801`6d216953 : 00000242`b73cd768 ffff9c80`43cc0180 00000000`00000000 ffff9c80`43cc0180 : nt!KeAccumulateTicks 0x20644a ffff9c80`43cbde80 fffff801`6d21643a : ffffb70e`ed518780 ffffc90f`3e6ae0e0 ffffc90f`3e6afa00 00000000`00000000 : nt!KeClockInterruptNotify 0x453 ffff9c80`43cbdf30 fffff801`6d2de055 : ffffb70e`ed518780 00000000`00000000 00000000`00000000 fffffe9c`f58a3dd3 : nt!HalpTimerClockIpiRoutine 0x1a ffff9c80`43cbdf60 fffff801`6d3f8d4a : ffffc90f`3e6ae0e0 ffffb70e`ed518780 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffff9c80`43cbdfb0 fffff801`6d3f92b7 : ffffb70f`15bfa000 fffff801`6d28da84 ffffc90f`3e6ae2c8 fffff801`6d3f92c4 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffffc90f`3e6ae060 fffff801`6d280c67 : 00000000`00000010 00000000`00000202 ffffc90f`3e6ae218 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffffc90f`3e6ae1f0 fffff801`6d2c0dea : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!KeYieldProcessorEx 0x17 ffffc90f`3e6ae220 fffff801`6d2c0daf : 00000000`1ca6dcd3 00000000`ffffffff 00000000`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip 0x2a ffffc90f`3e6ae250 fffff801`6fa0b41d : 00000000`000b77fd 00000000`00000000 ffffc90f`3e6ae470 ffffb70f`0e733180 : nt!KeAcquireInStackQueuedSpinLock 0x7f ffffc90f`3e6ae280 00000000`000b77fd : 00000000`00000000 ffffc90f`3e6ae470 ffffb70f`0e733180 ffffb70f`0fd8dc60 : SmbCo10X64 0x1b41d ffffc90f`3e6ae288 00000000`00000000 : ffffc90f`3e6ae470 ffffb70f`0e733180 ffffb70f`0fd8dc60 00000000`000000c0 : 0xb77fd SYMBOL_NAME: SmbCo10X64 1b41d MODULE_NAME: SmbCo10X64 IMAGE_NAME: SmbCo10X64.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 1b41d FAILURE_BUCKET_ID: 0x133_DPC_SmbCo10X64!unknown_function OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {b7ae26a3-5838-8ff0-cad2-fb40469d2555} Followup: MachineOwner
嗨，保罗，来帮助您解决问题的。小型转储文件指示驱动程序“SmbCo10X64.sys”。它是Killer网卡的设备驱动程序。如果可用，我建议您更新驱动程序。如果没有，只需卸载并重新安装它。我
