A
allenn083
Guest
Hello Support,
here comes a BSOD issue "Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+1cbfdd)" for WIN10.
could you please kindly advise what's the root-cause and how to solve it? thanks in advance.
please let me know what kind of information you still need to know.
post BSOD dump by WinDbg as follows.
Microsoft (R) Windows Debugger Version 10.0.15063.137 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\122019-99187-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*Symbol information
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff803`73600000 PsLoadedModuleList = 0xfffff803`73a48130
Debug session time: Thu Dec 19 19:00:11.682 2019 (UTC + 8:00)
System Uptime: 0 days 3:26:53.334
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, fffff80373b73358}
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+1cbfdd )
Followup: MachineOwner
---------
1: 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: fffff80373b73358, 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 ***
*** ***
*************************************************************************
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.18362.535 (WinBuild.160101.0800)
SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.
SYSTEM_SKU: To Be Filled By O.E.M.
SYSTEM_VERSION: To Be Filled By O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: P2.90
BIOS_DATE: 05/14/2018
BASEBOARD_MANUFACTURER: To Be Filled By O.E.M.
BASEBOARD_PRODUCT:
BASEBOARD_VERSION:
DUMP_TYPE: 2
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff80373b73358
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
CPU_COUNT: 4
CPU_MHZ: f48
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 8E'00000000 (cache) 8E'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: ALEX-CHANG-NB
ANALYSIS_SESSION_TIME: 01-16-2020 14:28:25.0225
ANALYSIS_VERSION: 10.0.15063.137 amd64fre
LAST_CONTROL_TRANSFER: from fffff803737eea3d to fffff803737c14e0
STACK_TEXT:
ffff9d80`3d439b08 fffff803`737eea3d : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9d80`3d439b10 fffff803`7361f897 : 00041904`842cbae9 ffff9d80`3d3fe180 00000000`00000286 ffffdb0b`1c62f5e0 : nt!KeAccumulateTicks+0x1cbfdd
ffff9d80`3d439b70 fffff803`740b91e1 : 00000000`00000000 ffffcb0d`b32a1400 ffffdb0b`1c62f660 ffffcb0d`b32a14b0 : nt!KeClockInterruptNotify+0xc07
ffff9d80`3d439f30 fffff803`73602a25 : ffffcb0d`b32a1400 00000000`00000000 00000000`00000000 ffffc3c2`eb8c7514 : hal!HalpTimerClockIpiRoutine+0x21
ffff9d80`3d439f60 fffff803`737c2f7a : ffffdb0b`1c62f660 ffffcb0d`b32a1400 00000000`80000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9d80`3d439fb0 fffff803`737c34e7 : ffffcb0d`b6fe7600 ffffdb0b`1c62f668 ffffdb0b`2382f2d8 fffff803`737c34f4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffdb0b`1c62f5e0 fffff803`7361ba2b : 00000000`00000010 00000000`00000286 ffffdb0b`1c62f798 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffdb0b`1c62f770 fffff803`7378cee3 : 00000000`00000000 00000000`00010001 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x1b
ffffdb0b`1c62f7a0 fffff803`7366ae95 : ffff9d80`3d400f80 00000000`1c707fc1 ffffdb0b`1c62f7a8 00000000`00000000 : nt!KiSwapDirectoryTableBaseTarget+0x53
ffffdb0b`1c62f7f0 fffff803`7366a4ef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x305
ffffdb0b`1c62f930 fffff803`737c5024 : ffffffff`00000000 ffff9d80`3d3fe180 ffff9d80`3d40f140 ffffcb0d`b7520080 : nt!KiRetireDpcList+0x1ef
ffffdb0b`1c62fb60 00000000`00000000 : ffffdb0b`1c630000 ffffdb0b`1c629000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 022edbe04e6c6e2a37d066a6680e7b27f43d61d7
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 46f2f8ba84a530acc83fd3c1c0b56694d3545acf
THREAD_SHA1_HASH_MOD: de26d798fe7dc370d1bae481b581f432e20583f4
FOLLOWUP_IP:
nt!KeAccumulateTicks+1cbfdd
fffff803`737eea3d cc int 3
FAULT_INSTR_CODE: f68445cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KeAccumulateTicks+1cbfdd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 12dcb470
IMAGE_VERSION: 10.0.18362.535
BUCKET_ID_FUNC_OFFSET: 1cbfdd
FAILURE_BUCKET_ID: OLD_IMAGE_ntkrnlmp.exe
BUCKET_ID: OLD_IMAGE_ntkrnlmp.exe
PRIMARY_PROBLEM_CLASS: OLD_IMAGE_ntkrnlmp.exe
TARGET_TIME: 2019-12-19T11:00:11.000Z
OSBUILD: 18362
OSSERVICEPACK: 535
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 1980-01-11 23:53:20
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.18362.535
ANALYSIS_SESSION_ELAPSED_TIME: f41
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km
ld_image_ntkrnlmp.exe
FAILURE_ID_HASH: {9c0c4046-5b69-0146-b800-16bdd4721e0b}
Followup: MachineOwner
---------
1: kd> !analyze –v –hang
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, fffff80373b73358}
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+1cbfdd )
Followup: MachineOwner
---------
More...
here comes a BSOD issue "Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+1cbfdd)" for WIN10.
could you please kindly advise what's the root-cause and how to solve it? thanks in advance.
please let me know what kind of information you still need to know.
post BSOD dump by WinDbg as follows.
Microsoft (R) Windows Debugger Version 10.0.15063.137 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\122019-99187-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*c:\symbols*Symbol information
Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff803`73600000 PsLoadedModuleList = 0xfffff803`73a48130
Debug session time: Thu Dec 19 19:00:11.682 2019 (UTC + 8:00)
System Uptime: 0 days 3:26:53.334
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, fffff80373b73358}
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+1cbfdd )
Followup: MachineOwner
---------
1: 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: fffff80373b73358, 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 ***
*** ***
*************************************************************************
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.18362.535 (WinBuild.160101.0800)
SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.
SYSTEM_SKU: To Be Filled By O.E.M.
SYSTEM_VERSION: To Be Filled By O.E.M.
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: P2.90
BIOS_DATE: 05/14/2018
BASEBOARD_MANUFACTURER: To Be Filled By O.E.M.
BASEBOARD_PRODUCT:
BASEBOARD_VERSION:
DUMP_TYPE: 2
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff80373b73358
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
CPU_COUNT: 4
CPU_MHZ: f48
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: 9
CPU_MICROCODE: 6,9e,9,0 (F,M,S,R) SIG: 8E'00000000 (cache) 8E'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: ALEX-CHANG-NB
ANALYSIS_SESSION_TIME: 01-16-2020 14:28:25.0225
ANALYSIS_VERSION: 10.0.15063.137 amd64fre
LAST_CONTROL_TRANSFER: from fffff803737eea3d to fffff803737c14e0
STACK_TEXT:
ffff9d80`3d439b08 fffff803`737eea3d : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9d80`3d439b10 fffff803`7361f897 : 00041904`842cbae9 ffff9d80`3d3fe180 00000000`00000286 ffffdb0b`1c62f5e0 : nt!KeAccumulateTicks+0x1cbfdd
ffff9d80`3d439b70 fffff803`740b91e1 : 00000000`00000000 ffffcb0d`b32a1400 ffffdb0b`1c62f660 ffffcb0d`b32a14b0 : nt!KeClockInterruptNotify+0xc07
ffff9d80`3d439f30 fffff803`73602a25 : ffffcb0d`b32a1400 00000000`00000000 00000000`00000000 ffffc3c2`eb8c7514 : hal!HalpTimerClockIpiRoutine+0x21
ffff9d80`3d439f60 fffff803`737c2f7a : ffffdb0b`1c62f660 ffffcb0d`b32a1400 00000000`80000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9d80`3d439fb0 fffff803`737c34e7 : ffffcb0d`b6fe7600 ffffdb0b`1c62f668 ffffdb0b`2382f2d8 fffff803`737c34f4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffdb0b`1c62f5e0 fffff803`7361ba2b : 00000000`00000010 00000000`00000286 ffffdb0b`1c62f798 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffdb0b`1c62f770 fffff803`7378cee3 : 00000000`00000000 00000000`00010001 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x1b
ffffdb0b`1c62f7a0 fffff803`7366ae95 : ffff9d80`3d400f80 00000000`1c707fc1 ffffdb0b`1c62f7a8 00000000`00000000 : nt!KiSwapDirectoryTableBaseTarget+0x53
ffffdb0b`1c62f7f0 fffff803`7366a4ef : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x305
ffffdb0b`1c62f930 fffff803`737c5024 : ffffffff`00000000 ffff9d80`3d3fe180 ffff9d80`3d40f140 ffffcb0d`b7520080 : nt!KiRetireDpcList+0x1ef
ffffdb0b`1c62fb60 00000000`00000000 : ffffdb0b`1c630000 ffffdb0b`1c629000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 022edbe04e6c6e2a37d066a6680e7b27f43d61d7
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 46f2f8ba84a530acc83fd3c1c0b56694d3545acf
THREAD_SHA1_HASH_MOD: de26d798fe7dc370d1bae481b581f432e20583f4
FOLLOWUP_IP:
nt!KeAccumulateTicks+1cbfdd
fffff803`737eea3d cc int 3
FAULT_INSTR_CODE: f68445cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KeAccumulateTicks+1cbfdd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 12dcb470
IMAGE_VERSION: 10.0.18362.535
BUCKET_ID_FUNC_OFFSET: 1cbfdd
FAILURE_BUCKET_ID: OLD_IMAGE_ntkrnlmp.exe
BUCKET_ID: OLD_IMAGE_ntkrnlmp.exe
PRIMARY_PROBLEM_CLASS: OLD_IMAGE_ntkrnlmp.exe
TARGET_TIME: 2019-12-19T11:00:11.000Z
OSBUILD: 18362
OSSERVICEPACK: 535
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 1980-01-11 23:53:20
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.18362.535
ANALYSIS_SESSION_ELAPSED_TIME: f41
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km
ld_image_ntkrnlmp.exeFAILURE_ID_HASH: {9c0c4046-5b69-0146-b800-16bdd4721e0b}
Followup: MachineOwner
---------
1: kd> !analyze –v –hang
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {0, 501, 500, fffff80373b73358}
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+1cbfdd )
Followup: MachineOwner
---------
More...