Windows server 2016 random bsod

  • Thread starter Thread starter Richard.001
  • Start date Start date
R

Richard.001

Guest
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

8700k Z370-p 64gb ram Windows server 2016 all latest windows updates

mini dumps

https://www.dropbox.com/s/8upsnxyg5006jln/bsodc.rar?dl=1

system tests

https://www.dropbox.com/s/u5g2dusfqn81u7u/systemtests.rar?dl=1


log of last bsod

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\051019-10703-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 = 0xfffff802`9661a000 PsLoadedModuleList = 0xfffff802`9691c180

Debug session time: Fri May 10 11:04:13.282 2019 (UTC + 2:00)

System Uptime: 0 days 0:16:05.985

Loading Kernel Symbols

...............................................................

................................................................

...................................

Loading User Symbols

Loading unloaded module list

.........................................

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



Use !analyze -v to get detailed debugging information.



BugCheck 101, {10, 0, ffff88819fe40180, 5}



Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )



Followup: MachineOwner

---------



0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



CLOCK_WATCHDOG_TIMEOUT (101)

An expected clock interrupt was not received on a secondary processor in an

MP system within the allocated interval. This indicates that the specified

processor is hung and not processing interrupts.

Arguments:

Arg1: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.

Arg2: 0000000000000000, 0.

Arg3: ffff88819fe40180, The PRCB address of the hung processor.

Arg4: 0000000000000005, The index of the hung processor.



Debugging Details:

------------------





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



DUMP_TYPE: 2



BUGCHECK_P1: 10



BUGCHECK_P2: 0



BUGCHECK_P3: ffff88819fe40180



BUGCHECK_P4: 5



BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_c_PROC



CPU_COUNT: c



CPU_MHZ: e70



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 9e



CPU_STEPPING: a



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT_SERVER



PROCESS_NAME: System



CURRENT_IRQL: d



ANALYSIS_SESSION_HOST: SINO_OFFICE



ANALYSIS_SESSION_TIME: 05-10-2019 11:57:10.0186



ANALYSIS_VERSION: 10.0.17763.132 amd64fre



STACK_TEXT:

fffff802`990b8d88 fffff802`966c3fc0 : 00000000`00000101 00000000`00000010 00000000`00000000 ffff8881`9fe40180 : nt!KeBugCheckEx

fffff802`990b8d90 fffff802`966c1609 : ffff8881`a1307080 00000000`00000000 fffff802`9693c840 fffff780`00000320 : nt!KeAccumulateTicks+0x3e0

fffff802`990b8df0 fffff802`96e38366 : ffff8881`a1307080 fffff802`96e833f0 00000000`00000001 0000034a`c45efc2e : nt!KeClockInterruptNotify+0x469

fffff802`990b8f40 fffff802`96676566 : fffff802`96e833f0 ffff8881`a0560200 ffff8881`a0560500 fffff802`00000000 : hal!HalpTimerClockInterrupt+0x56

fffff802`990b8f70 fffff802`9677813a : ffff8881`a1307100 00000000`06e0e0b4 00000000`00000000 ffffc18a`03a80000 : nt!KiCallInterruptServiceRoutine+0x106

fffff802`990b8fb0 fffff802`96778627 : ffffac8a`00000001 00000000`00000001 00000000`06e068db fffff802`966d981a : nt!KiInterruptSubDispatchNoLockNoEtw+0xea

ffff8881`a1307080 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37





THREAD_SHA1_HASH_MOD_FUNC: 5e958d63ed6cce864bfe4c595207e0e484aa7e7c



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: b75e436aa33e904b48dabe0b39dc64ac6b704b61



THREAD_SHA1_HASH_MOD: e2266a530ca7fbace00cfa9add8dc0ac4504d759



SYMBOL_NAME: ANALYSIS_INCONCLUSIVE



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: Unknown_Module



IMAGE_NAME: Unknown_Image



DEBUG_FLR_IMAGE_TIMESTAMP: 0



STACK_COMMAND: .thread ; .cxr ; kb



FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE!unknown_function



BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE!unknown_function



PRIMARY_PROBLEM_CLASS: CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE!unknown_function



TARGET_TIME: 2019-05-10T09:04:13.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: 3b57



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:clock_watchdog_timeout_c_proc_analysis_inconclusive!unknown_function



FAILURE_ID_HASH: {8f25f9a6-1a62-707c-2c62-9b2aa8e883ad}



Followup: MachineOwner

---------



0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************



CLOCK_WATCHDOG_TIMEOUT (101)

An expected clock interrupt was not received on a secondary processor in an

MP system within the allocated interval. This indicates that the specified

processor is hung and not processing interrupts.

Arguments:

Arg1: 0000000000000010, Clock interrupt time out interval in nominal clock ticks.

Arg2: 0000000000000000, 0.

Arg3: ffff88819fe40180, The PRCB address of the hung processor.

Arg4: 0000000000000005, The index of the hung processor.



Debugging Details:

------------------





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



DUMP_TYPE: 2



BUGCHECK_P1: 10



BUGCHECK_P2: 0



BUGCHECK_P3: ffff88819fe40180



BUGCHECK_P4: 5



BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_c_PROC



CPU_COUNT: c



CPU_MHZ: e70



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 9e



CPU_STEPPING: a



CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT_SERVER



PROCESS_NAME: System



CURRENT_IRQL: d



ANALYSIS_SESSION_HOST: SINO_OFFICE



ANALYSIS_SESSION_TIME: 05-10-2019 11:57:25.0380



ANALYSIS_VERSION: 10.0.17763.132 amd64fre



STACK_TEXT:

fffff802`990b8d88 fffff802`966c3fc0 : 00000000`00000101 00000000`00000010 00000000`00000000 ffff8881`9fe40180 : nt!KeBugCheckEx

fffff802`990b8d90 fffff802`966c1609 : ffff8881`a1307080 00000000`00000000 fffff802`9693c840 fffff780`00000320 : nt!KeAccumulateTicks+0x3e0

fffff802`990b8df0 fffff802`96e38366 : ffff8881`a1307080 fffff802`96e833f0 00000000`00000001 0000034a`c45efc2e : nt!KeClockInterruptNotify+0x469

fffff802`990b8f40 fffff802`96676566 : fffff802`96e833f0 ffff8881`a0560200 ffff8881`a0560500 fffff802`00000000 : hal!HalpTimerClockInterrupt+0x56

fffff802`990b8f70 fffff802`9677813a : ffff8881`a1307100 00000000`06e0e0b4 00000000`00000000 ffffc18a`03a80000 : nt!KiCallInterruptServiceRoutine+0x106

fffff802`990b8fb0 fffff802`96778627 : ffffac8a`00000001 00000000`00000001 00000000`06e068db fffff802`966d981a : nt!KiInterruptSubDispatchNoLockNoEtw+0xea

ffff8881`a1307080 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37





THREAD_SHA1_HASH_MOD_FUNC: 5e958d63ed6cce864bfe4c595207e0e484aa7e7c



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: b75e436aa33e904b48dabe0b39dc64ac6b704b61



THREAD_SHA1_HASH_MOD: e2266a530ca7fbace00cfa9add8dc0ac4504d759



SYMBOL_NAME: ANALYSIS_INCONCLUSIVE



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: Unknown_Module



IMAGE_NAME: Unknown_Image



DEBUG_FLR_IMAGE_TIMESTAMP: 0



STACK_COMMAND: .thread ; .cxr ; kb



FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE!unknown_function



BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE!unknown_function



PRIMARY_PROBLEM_CLASS: CLOCK_WATCHDOG_TIMEOUT_c_PROC_ANALYSIS_INCONCLUSIVE!unknown_function



TARGET_TIME: 2019-05-10T09:04:13.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: 3b1e



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:clock_watchdog_timeout_c_proc_analysis_inconclusive!unknown_function



FAILURE_ID_HASH: {8f25f9a6-1a62-707c-2c62-9b2aa8e883ad}



Followup: MachineOwner

---------

Continue reading...
 
Back
Top