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
8700k Z370-p 64gb ram Windows server 2016 all latest windows updates
mini dumps
system tests
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:
------------------
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
8700k Z370-p 64gb ram Windows server 2016 all latest windows updates
mini dumps
system tests
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:
------------------
Continue reading...