用windbg 显示问题是ntknlmp.exe 求求各位大佬帮忙看看 下面是代码 Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\minidump\083022-20312-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 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff805`51400000 PsLoadedModuleList = 0xfffff805`51848150
Debug session time: Tue Aug 30 21:38:53.754 2022 (UTC + 8:00)
System Uptime: 4 days 18:37:28.375
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:
fffff805`515c2380 48894c2408 mov qword ptr [rsp+8],rcx ss:ffffca00`009b6b10=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: fffff80551973358, 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: 3280
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 3369
Key : Analysis.Init.CPU.mSec
Value: 921
Key : Analysis.Init.Elapsed.mSec
Value: 49836
Key : Analysis.Memory.CommitPeak.Mb
Value: 114
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: 083022-20312-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff80551973358
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: r5apex.exe
STACK_TEXT:
ffffca00`009b6b08 fffff805`5163d82d : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffca00`009b6b10 fffff805`514b8e3c : 0002b7bb`89cafcfd ffffca00`00997180 00000000`0192fa18 00000000`0192fa18 : nt!KeAccumulateTicks+0x1815ad
ffffca00`009b6b70 fffff805`5135e4b7 : 00000000`00000000 ffff8308`22247a30 ffff8308`22247ab0 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
ffffca00`009b6f30 fffff805`5142cc75 : 000003c0`d2e725a9 ffff8a8f`a7eb3000 ffff8a8f`a7eb30b0 ffffc664`13ade55e : hal!HalpTimerClockInterrupt+0xf7
ffffca00`009b6f60 fffff805`515c3e1a : ffff8308`22247ab0 ffff8a8f`a7eb3000 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffca00`009b6fb0 fffff805`515c4387 : 00000000`00000000 00000000`00000000 00000000`80000000 fffff805`515c4394 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8308`22247a30 fffff805`514b524b : ffffffff`ffffffd1 fffff805`51446c40 00000000`00000010 00000000`00000282 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8308`22247bc0 fffff805`51446c59 : ffff8a80`04112140 00000000`00000000 ffffca00`00997180 00000000`00000000 : nt!KeYieldProcessorEx+0x1b
ffff8308`22247bf0 fffff805`514c116a : ffffca00`00999f80 00000000`18c8cc78 00000000`00000000 00000000`00000000 : nt!ExpGetPoolTagInfoTarget+0x139
ffff8308`22247c40 fffff805`514c07bf : 00000000`00000006 00000000`00989680 ffff8308`22247e80 00000000`00000082 : nt!KiExecuteAllDpcs+0x30a
ffff8308`22247d80 fffff805`515c93c5 : 00000000`00000000 ffffca00`00997180 00000000`00000000 0000000d`fef8ea70 : nt!KiRetireDpcList+0x1ef
ffff8308`22247fb0 fffff805`515c91b0 : ffff8a80`04112140 00000000`00000000 00000000`0000168c 00000000`02964300 : nt!KxRetireDpcList+0x5
ffff8308`2365f9d0 fffff805`515c8880 : 000001af`ef2476e0 ffff8308`2365fa80 00000000`00000000 000001b0`6152caf0 : nt!KiDispatchInterruptContinue
ffff8308`2365fa00 00007ff9`87b62f4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2f0
0000000d`fef8e920 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`87b62f4a
SYMBOL_NAME: nt!KeAccumulateTicks+1815ad
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.720
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1815ad
FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}
Followup: MachineOwner
---------
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: fffff80551973358, 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: 2812
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 2826
Key : Analysis.Init.CPU.mSec
Value: 4202
Key : Analysis.Init.Elapsed.mSec
Value: 53208
Key : Analysis.Memory.CommitPeak.Mb
Value: 114
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: 083022-20312-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff80551973358
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: r5apex.exe
STACK_TEXT:
ffffca00`009b6b08 fffff805`5163d82d : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffca00`009b6b10 fffff805`514b8e3c : 0002b7bb`89cafcfd ffffca00`00997180 00000000`0192fa18 00000000`0192fa18 : nt!KeAccumulateTicks+0x1815ad
ffffca00`009b6b70 fffff805`5135e4b7 : 00000000`00000000 ffff8308`22247a30 ffff8308`22247ab0 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
ffffca00`009b6f30 fffff805`5142cc75 : 000003c0`d2e725a9 ffff8a8f`a7eb3000 ffff8a8f`a7eb30b0 ffffc664`13ade55e : hal!HalpTimerClockInterrupt+0xf7
ffffca00`009b6f60 fffff805`515c3e1a : ffff8308`22247ab0 ffff8a8f`a7eb3000 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffca00`009b6fb0 fffff805`515c4387 : 00000000`00000000 00000000`00000000 00000000`80000000 fffff805`515c4394 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8308`22247a30 fffff805`514b524b : ffffffff`ffffffd1 fffff805`51446c40 00000000`00000010 00000000`00000282 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8308`22247bc0 fffff805`51446c59 : ffff8a80`04112140 00000000`00000000 ffffca00`00997180 00000000`00000000 : nt!KeYieldProcessorEx+0x1b
ffff8308`22247bf0 fffff805`514c116a : ffffca00`00999f80 00000000`18c8cc78 00000000`00000000 00000000`00000000 : nt!ExpGetPoolTagInfoTarget+0x139
ffff8308`22247c40 fffff805`514c07bf : 00000000`00000006 00000000`00989680 ffff8308`22247e80 00000000`00000082 : nt!KiExecuteAllDpcs+0x30a
ffff8308`22247d80 fffff805`515c93c5 : 00000000`00000000 ffffca00`00997180 00000000`00000000 0000000d`fef8ea70 : nt!KiRetireDpcList+0x1ef
ffff8308`22247fb0 fffff805`515c91b0 : ffff8a80`04112140 00000000`00000000 00000000`0000168c 00000000`02964300 : nt!KxRetireDpcList+0x5
ffff8308`2365f9d0 fffff805`515c8880 : 000001af`ef2476e0 ffff8308`2365fa80 00000000`00000000 000001b0`6152caf0 : nt!KiDispatchInterruptContinue
ffff8308`2365fa00 00007ff9`87b62f4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2f0
0000000d`fef8e920 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`87b62f4a
SYMBOL_NAME: nt!KeAccumulateTicks+1815ad
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.720
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1815ad
FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}
Followup: MachineOwner
---------
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: fffff80551973358, 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: 2796
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 2841
Key : Analysis.Init.CPU.mSec
Value: 7015
Key : Analysis.Init.Elapsed.mSec
Value: 56038
Key : Analysis.Memory.CommitPeak.Mb
Value: 114
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: 083022-20312-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff80551973358
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: r5apex.exe
STACK_TEXT:
ffffca00`009b6b08 fffff805`5163d82d : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffca00`009b6b10 fffff805`514b8e3c : 0002b7bb`89cafcfd ffffca00`00997180 00000000`0192fa18 00000000`0192fa18 : nt!KeAccumulateTicks+0x1815ad
ffffca00`009b6b70 fffff805`5135e4b7 : 00000000`00000000 ffff8308`22247a30 ffff8308`22247ab0 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
ffffca00`009b6f30 fffff805`5142cc75 : 000003c0`d2e725a9 ffff8a8f`a7eb3000 ffff8a8f`a7eb30b0 ffffc664`13ade55e : hal!HalpTimerClockInterrupt+0xf7
ffffca00`009b6f60 fffff805`515c3e1a : ffff8308`22247ab0 ffff8a8f`a7eb3000 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffca00`009b6fb0 fffff805`515c4387 : 00000000`00000000 00000000`00000000 00000000`80000000 fffff805`515c4394 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8308`22247a30 fffff805`514b524b : ffffffff`ffffffd1 fffff805`51446c40 00000000`00000010 00000000`00000282 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8308`22247bc0 fffff805`51446c59 : ffff8a80`04112140 00000000`00000000 ffffca00`00997180 00000000`00000000 : nt!KeYieldProcessorEx+0x1b
ffff8308`22247bf0 fffff805`514c116a : ffffca00`00999f80 00000000`18c8cc78 00000000`00000000 00000000`00000000 : nt!ExpGetPoolTagInfoTarget+0x139
ffff8308`22247c40 fffff805`514c07bf : 00000000`00000006 00000000`00989680 ffff8308`22247e80 00000000`00000082 : nt!KiExecuteAllDpcs+0x30a
ffff8308`22247d80 fffff805`515c93c5 : 00000000`00000000 ffffca00`00997180 00000000`00000000 0000000d`fef8ea70 : nt!KiRetireDpcList+0x1ef
ffff8308`22247fb0 fffff805`515c91b0 : ffff8a80`04112140 00000000`00000000 00000000`0000168c 00000000`02964300 : nt!KxRetireDpcList+0x5
ffff8308`2365f9d0 fffff805`515c8880 : 000001af`ef2476e0 ffff8308`2365fa80 00000000`00000000 000001b0`6152caf0 : nt!KiDispatchInterruptContinue
ffff8308`2365fa00 00007ff9`87b62f4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2f0
0000000d`fef8e920 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`87b62f4a
SYMBOL_NAME: nt!KeAccumulateTicks+1815ad
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.720
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1815ad
FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}
Followup: MachineOwner
---------
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: fffff80551973358, 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: 2796
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 2845
Key : Analysis.Init.CPU.mSec
Value: 9812
Key : Analysis.Init.Elapsed.mSec
Value: 58882
Key : Analysis.Memory.CommitPeak.Mb
Value: 114
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: 083022-20312-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff80551973358
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: r5apex.exe
STACK_TEXT:
ffffca00`009b6b08 fffff805`5163d82d : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffca00`009b6b10 fffff805`514b8e3c : 0002b7bb`89cafcfd ffffca00`00997180 00000000`0192fa18 00000000`0192fa18 : nt!KeAccumulateTicks+0x1815ad
ffffca00`009b6b70 fffff805`5135e4b7 : 00000000`00000000 ffff8308`22247a30 ffff8308`22247ab0 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
ffffca00`009b6f30 fffff805`5142cc75 : 000003c0`d2e725a9 ffff8a8f`a7eb3000 ffff8a8f`a7eb30b0 ffffc664`13ade55e : hal!HalpTimerClockInterrupt+0xf7
ffffca00`009b6f60 fffff805`515c3e1a : ffff8308`22247ab0 ffff8a8f`a7eb3000 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffca00`009b6fb0 fffff805`515c4387 : 00000000`00000000 00000000`00000000 00000000`80000000 fffff805`515c4394 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8308`22247a30 fffff805`514b524b : ffffffff`ffffffd1 fffff805`51446c40 00000000`00000010 00000000`00000282 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8308`22247bc0 fffff805`51446c59 : ffff8a80`04112140 00000000`00000000 ffffca00`00997180 00000000`00000000 : nt!KeYieldProcessorEx+0x1b
ffff8308`22247bf0 fffff805`514c116a : ffffca00`00999f80 00000000`18c8cc78 00000000`00000000 00000000`00000000 : nt!ExpGetPoolTagInfoTarget+0x139
ffff8308`22247c40 fffff805`514c07bf : 00000000`00000006 00000000`00989680 ffff8308`22247e80 00000000`00000082 : nt!KiExecuteAllDpcs+0x30a
ffff8308`22247d80 fffff805`515c93c5 : 00000000`00000000 ffffca00`00997180 00000000`00000000 0000000d`fef8ea70 : nt!KiRetireDpcList+0x1ef
ffff8308`22247fb0 fffff805`515c91b0 : ffff8a80`04112140 00000000`00000000 00000000`0000168c 00000000`02964300 : nt!KxRetireDpcList+0x5
ffff8308`2365f9d0 fffff805`515c8880 : 000001af`ef2476e0 ffff8308`2365fa80 00000000`00000000 000001b0`6152caf0 : nt!KiDispatchInterruptContinue
ffff8308`2365fa00 00007ff9`87b62f4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2f0
0000000d`fef8e920 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`87b62f4a
SYMBOL_NAME: nt!KeAccumulateTicks+1815ad
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.720
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1815ad
FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}
Followup: MachineOwner
---------
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: fffff80551973358, 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: 2859
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 2876
Key : Analysis.Init.CPU.mSec
Value: 12609
Key : Analysis.Init.Elapsed.mSec
Value: 61731
Key : Analysis.Memory.CommitPeak.Mb
Value: 114
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: 083022-20312-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff80551973358
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: r5apex.exe
STACK_TEXT:
ffffca00`009b6b08 fffff805`5163d82d : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffca00`009b6b10 fffff805`514b8e3c : 0002b7bb`89cafcfd ffffca00`00997180 00000000`0192fa18 00000000`0192fa18 : nt!KeAccumulateTicks+0x1815ad
ffffca00`009b6b70 fffff805`5135e4b7 : 00000000`00000000 ffff8308`22247a30 ffff8308`22247ab0 00000000`00000002 : nt!KeClockInterruptNotify+0x98c
ffffca00`009b6f30 fffff805`5142cc75 : 000003c0`d2e725a9 ffff8a8f`a7eb3000 ffff8a8f`a7eb30b0 ffffc664`13ade55e : hal!HalpTimerClockInterrupt+0xf7
ffffca00`009b6f60 fffff805`515c3e1a : ffff8308`22247ab0 ffff8a8f`a7eb3000 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffca00`009b6fb0 fffff805`515c4387 : 00000000`00000000 00000000`00000000 00000000`80000000 fffff805`515c4394 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8308`22247a30 fffff805`514b524b : ffffffff`ffffffd1 fffff805`51446c40 00000000`00000010 00000000`00000282 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8308`22247bc0 fffff805`51446c59 : ffff8a80`04112140 00000000`00000000 ffffca00`00997180 00000000`00000000 : nt!KeYieldProcessorEx+0x1b
ffff8308`22247bf0 fffff805`514c116a : ffffca00`00999f80 00000000`18c8cc78 00000000`00000000 00000000`00000000 : nt!ExpGetPoolTagInfoTarget+0x139
ffff8308`22247c40 fffff805`514c07bf : 00000000`00000006 00000000`00989680 ffff8308`22247e80 00000000`00000082 : nt!KiExecuteAllDpcs+0x30a
ffff8308`22247d80 fffff805`515c93c5 : 00000000`00000000 ffffca00`00997180 00000000`00000000 0000000d`fef8ea70 : nt!KiRetireDpcList+0x1ef
ffff8308`22247fb0 fffff805`515c91b0 : ffff8a80`04112140 00000000`00000000 00000000`0000168c 00000000`02964300 : nt!KxRetireDpcList+0x5
ffff8308`2365f9d0 fffff805`515c8880 : 000001af`ef2476e0 ffff8308`2365fa80 00000000`00000000 000001b0`6152caf0 : nt!KiDispatchInterruptContinue
ffff8308`2365fa00 00007ff9`87b62f4a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2f0
0000000d`fef8e920 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`87b62f4a
SYMBOL_NAME: nt!KeAccumulateTicks+1815ad
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.18362.720
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 1815ad
FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}
Followup: MachineOwner
---------欢迎访问本站！。建议卸载一下Apex英雄。然后更新系统导致最新的版本，看下是否还会蓝屏。可以参考以下链接使用MediaCreationTool进行系统的无损修复/覆盖安装：【这不是重装系统：正常情况下文件、设置、应用等将保持原样，并将系统更新到最新的Windows10正式版。】https://answers.microsoft.com/zh-hans/windows/f.（相关视频教程：https://www.microsoft.com/en-us/videoplayer/emb.）
欢迎访问本站！。建议卸载一下Apex英雄。然后更新系统导致最新的版本，看下是否还会蓝屏。可以参考以下链接使用MediaCreationTool进行系统的无损修复/覆盖安装：【这不是重装系统：正常情况下文件、设置、应用等将保持原样，并将系统更新到最新的Windows10正式版。】https://answers.microsoft.com/zh-hans/windows/f.（相关视频教程：https://www.microsoft.com/en-us/videoplayer/emb.）
微信小程序
微信扫一扫体验
投稿
微信公众账号
微信扫一扫加关注
评论 返回
顶部