It started begin of this year that I got a bluescreen cause of vmware workstation vmx86.sys
i m not sure, if it was the moment, where i upgraded to 15.5
but it is now 2 or 3 times per week, since i upgraded to 15.5.2
surely all 40gb ram and also the processor have had done checks under highload, without any fault
google found this error several times over the last years, but never a solution
i lost now 2 times my database running inside, one time even ubuntun was damaged
maybe now someone can fix it please...
Microsoft (R) Windows Debugger Version 10.0.19528.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff802`55000000 PsLoadedModuleList = 0xfffff802`55448150
Debug session time: Sat Apr 11 15:12:43.332 2020 (UTC + 2:00)
System Uptime: 2 days 4:52:55.718
Loading Kernel Symbols
...............................................................
................................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`551c2380 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff802`5a075b10=0000000000000101
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: ffffa48079820180, The PRCB address of the hung processor.
Arg4: 0000000000000001, The index of the hung processor.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.Sec
Value: 4
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on CHAOS10
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 7
Key : Analysis.Memory.CommitPeak.Mb
Value: 66
Key : Analysis.System
Value: CreateObject
ADDITIONAL_XML: 1
BUGCHECK_CODE: 101
BUGCHECK_P1: 10
BUGCHECK_P2: 0
BUGCHECK_P3: ffffa48079820180
BUGCHECK_P4: 1
FAULTING_PROCESSOR: 1
PROCESS_NAME: vmware-vmx.exe
FAULTING_THREAD: ffffb588a7940080
STACK_TEXT:
ffff9f84`164bc4a8 fffff802`5b148308 : ffffa480`79820180 fffff802`55121385 ffffb588`98a68220 00000000`00000000 : vmx86+0x100a
ffff9f84`164bc4b0 fffff802`5b14abd3 : ffffb588`a8050160 00000000`00000000 ffffa480`7bd28000 00000000`0000006b : vmx86+0x8308
ffff9f84`164bc5f0 fffff802`5b141f4e : ffff9f84`164bc978 00000000`00000000 ffff9f84`164bc978 ffffb588`86e02000 : vmx86+0xabd3
ffff9f84`164bc6c0 fffff802`5b14298e : 00000000`00000000 fffff802`553543a9 ffffb588`abe58cc0 fffff802`551132e4 : vmx86+0x1f4e
ffff9f84`164bc8a0 fffff802`556b24eb : 00000000`000003e4 00000000`00000001 00000000`00000000 ffffb588`ab9b07a0 : vmx86+0x298e
ffff9f84`164bc900 fffff802`556b1db6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x71b
ffff9f84`164bca20 fffff802`551d3c18 : 00000000`00000000 ffff9f84`00000001 00000000`000003e4 ffff9f84`164bcb80 : nt!NtDeviceIoControlFile+0x56
ffff9f84`164bca90 00007ffc`d5bdc1a4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
000000c0`c61ffcd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`d5bdc1a4
STACK_COMMAND: .thread 0xffffb588a7940080 ; kb
SYMBOL_NAME: vmx86+100a
MODULE_NAME: vmx86
IMAGE_NAME: vmx86.sys
BUCKET_ID_FUNC_OFFSET: 100a
FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_vmx86!unknown_function
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {e206f958-3924-e3cb-af92-ab296be9b5e9}
Followup: MachineOwner