R
Richard.001
Hi
im having issues with one of our server it often randomly crash with blue screen. Runned memtest and installed all latest updates, sfc didnt found any error what can fix this? Thanks
www.dropbox.com/s/8upsnxyg5006jln/bsodc.rar?dl=1
Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Administrator\Desktop\bsodc\051719-5656-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 14393 MP (12 procs) Free x64
Product: Server, suite: TerminalServer
Built by: 14393.2906.amd64fre.rs1_release_inmarket.190401-1809
Machine Name:
Kernel base = 0xfffff803`06e7b000 PsLoadedModuleList = 0xfffff803`0717d180
Debug session time: Fri May 17 09:26:44.193 2019 (UTC + 2:00)
System Uptime: 0 days 0:40:40.906
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, fffff8030721f540, 0}
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+42a )
Followup: MachineOwner
---------
6: 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: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8030721f540, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
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
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 14393.2906.amd64fre.rs1_release_inmarket.190401-1809
SYSTEM_MANUFACTURER: System manufacturer
SYSTEM_PRODUCT_NAME: System Product Name
SYSTEM_SKU: SKU
SYSTEM_VERSION: System Version
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 1002
BIOS_DATE: 07/02/2018
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: PRIME Z370-P
BASEBOARD_VERSION: Rev X.0x
DUMP_TYPE: 2
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8030721f540
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CPU_COUNT: c
CPU_MHZ: e70
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: a
CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 96'00000000 (cache) 96'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT_SERVER
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: SINO_OFFICE
ANALYSIS_SESSION_TIME: 05-17-2019 16:25:00.0956
ANALYSIS_VERSION: 10.0.17763.132 amd64fre
LAST_CONTROL_TRANSFER: from fffff80306f2500a to fffff80306fd7940
STACK_TEXT:
ffffe601`466f2d88 fffff803`06f2500a : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`0721f540 : nt!KeBugCheckEx
ffffe601`466f2d90 fffff803`06f22258 : 0000084b`0fe70212 00000000`00000000 00000000`00000001 fffff780`00000320 : nt!KeAccumulateTicks+0x42a
ffffe601`466f2df0 fffff803`06e094e5 : ffffd308`dcecb400 ffffd308`dcecb400 00000000`00000001 ffffd308`dcecb400 : nt!KeClockInterruptNotify+0xb8
ffffe601`466f2f40 fffff803`06ed7566 : ffff1b96`de05a300 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x15
ffffe601`466f2f70 fffff803`06fd913a : ffffe601`466b4ad0 ffffe601`466d0300 00000000`000002ec ffffe601`466d3000 : nt!KiCallInterruptServiceRoutine+0x106
ffffe601`466f2fb0 fffff803`06fd9627 : 00000000`00000000 ffffe601`466c0180 ffffe601`466d0300 00000000`00000001 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffe601`466b4a50 fffff803`06fdaff4 : ffffffff`00000000 ffffe601`466c0180 ffffe601`466d0300 ffffd308`eb566080 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffe601`466b4be0 00000000`00000000 : ffffe601`466b5000 ffffe601`466ae000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0xb4
THREAD_SHA1_HASH_MOD_FUNC: 6235c709cc46302df662a70875be3140e0151eff
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 485d6e3027486466366d0f9e7ad6f9ab3d66a6ac
THREAD_SHA1_HASH_MOD: 77b99fd8d0bba6459fea0474c255a54ffe46d91a
FOLLOWUP_IP:
nt!KeAccumulateTicks+42a
fffff803`06f2500a cc int 3
FAULT_INSTR_CODE: cccccccc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KeAccumulateTicks+42a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5ca2e100
IMAGE_VERSION: 10.0.14393.2906
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 42a
FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
PRIMARY_PROBLEM_CLASS: 0x133_ISR_nt!KeAccumulateTicks
TARGET_TIME: 2019-05-17T07:26:44.000Z
OSBUILD: 14393
OSSERVICEPACK: 2906
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 16
PRODUCT_TYPE: 3
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 Server TerminalServer
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2019-04-02 06:11:44
BUILDDATESTAMP_STR: 190401-1809
BUILDLAB_STR: rs1_release_inmarket
BUILDOSVER_STR: 10.0.14393.2906.amd64fre.rs1_release_inmarket.190401-1809
ANALYSIS_SESSION_ELAPSED_TIME: e94
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_isr_nt!keaccumulateticks
FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
Followup: MachineOwner
---------
Continue reading...
im having issues with one of our server it often randomly crash with blue screen. Runned memtest and installed all latest updates, sfc didnt found any error what can fix this? Thanks
www.dropbox.com/s/8upsnxyg5006jln/bsodc.rar?dl=1
Microsoft (R) Windows Debugger Version 10.0.17763.132 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Administrator\Desktop\bsodc\051719-5656-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 14393 MP (12 procs) Free x64
Product: Server, suite: TerminalServer
Built by: 14393.2906.amd64fre.rs1_release_inmarket.190401-1809
Machine Name:
Kernel base = 0xfffff803`06e7b000 PsLoadedModuleList = 0xfffff803`0717d180
Debug session time: Fri May 17 09:26:44.193 2019 (UTC + 2:00)
System Uptime: 0 days 0:40:40.906
Loading Kernel Symbols
...............................................................
................................................................
....................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 133, {1, 1e00, fffff8030721f540, 0}
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+42a )
Followup: MachineOwner
---------
6: 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: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8030721f540, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
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
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 14393.2906.amd64fre.rs1_release_inmarket.190401-1809
SYSTEM_MANUFACTURER: System manufacturer
SYSTEM_PRODUCT_NAME: System Product Name
SYSTEM_SKU: SKU
SYSTEM_VERSION: System Version
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 1002
BIOS_DATE: 07/02/2018
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: PRIME Z370-P
BASEBOARD_VERSION: Rev X.0x
DUMP_TYPE: 2
BUGCHECK_P1: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8030721f540
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
CPU_COUNT: c
CPU_MHZ: e70
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 9e
CPU_STEPPING: a
CPU_MICROCODE: 6,9e,a,0 (F,M,S,R) SIG: 96'00000000 (cache) 96'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT_SERVER
BUGCHECK_STR: 0x133
PROCESS_NAME: System
CURRENT_IRQL: d
ANALYSIS_SESSION_HOST: SINO_OFFICE
ANALYSIS_SESSION_TIME: 05-17-2019 16:25:00.0956
ANALYSIS_VERSION: 10.0.17763.132 amd64fre
LAST_CONTROL_TRANSFER: from fffff80306f2500a to fffff80306fd7940
STACK_TEXT:
ffffe601`466f2d88 fffff803`06f2500a : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`0721f540 : nt!KeBugCheckEx
ffffe601`466f2d90 fffff803`06f22258 : 0000084b`0fe70212 00000000`00000000 00000000`00000001 fffff780`00000320 : nt!KeAccumulateTicks+0x42a
ffffe601`466f2df0 fffff803`06e094e5 : ffffd308`dcecb400 ffffd308`dcecb400 00000000`00000001 ffffd308`dcecb400 : nt!KeClockInterruptNotify+0xb8
ffffe601`466f2f40 fffff803`06ed7566 : ffff1b96`de05a300 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalpTimerClockIpiRoutine+0x15
ffffe601`466f2f70 fffff803`06fd913a : ffffe601`466b4ad0 ffffe601`466d0300 00000000`000002ec ffffe601`466d3000 : nt!KiCallInterruptServiceRoutine+0x106
ffffe601`466f2fb0 fffff803`06fd9627 : 00000000`00000000 ffffe601`466c0180 ffffe601`466d0300 00000000`00000001 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffe601`466b4a50 fffff803`06fdaff4 : ffffffff`00000000 ffffe601`466c0180 ffffe601`466d0300 ffffd308`eb566080 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffe601`466b4be0 00000000`00000000 : ffffe601`466b5000 ffffe601`466ae000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0xb4
THREAD_SHA1_HASH_MOD_FUNC: 6235c709cc46302df662a70875be3140e0151eff
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 485d6e3027486466366d0f9e7ad6f9ab3d66a6ac
THREAD_SHA1_HASH_MOD: 77b99fd8d0bba6459fea0474c255a54ffe46d91a
FOLLOWUP_IP:
nt!KeAccumulateTicks+42a
fffff803`06f2500a cc int 3
FAULT_INSTR_CODE: cccccccc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!KeAccumulateTicks+42a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 5ca2e100
IMAGE_VERSION: 10.0.14393.2906
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 42a
FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks
PRIMARY_PROBLEM_CLASS: 0x133_ISR_nt!KeAccumulateTicks
TARGET_TIME: 2019-05-17T07:26:44.000Z
OSBUILD: 14393
OSSERVICEPACK: 2906
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 16
PRODUCT_TYPE: 3
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 Server TerminalServer
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2019-04-02 06:11:44
BUILDDATESTAMP_STR: 190401-1809
BUILDLAB_STR: rs1_release_inmarket
BUILDOSVER_STR: 10.0.14393.2906.amd64fre.rs1_release_inmarket.190401-1809
ANALYSIS_SESSION_ELAPSED_TIME: e94
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x133_isr_nt!keaccumulateticks
FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}
Followup: MachineOwner
---------
Continue reading...