VMware Communities
LiuShi01
Enthusiast
Enthusiast

crash

2020-04-12T09:48:28.034+08:00| mks| I125: MKS-VMDB: VMDB requested a screenshot

2020-04-12T09:48:28.034+08:00| svga| I125: MKSScreenShotMgr: Taking a screenshot

2020-04-12T09:48:28.095+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 2 rendering MKSWindow(s) of total 2.

2020-04-12T09:48:28.113+08:00| mks| I125: SWBWindow: Window #0 validation failed: no valid host window or host surface.

2020-04-12T09:48:28.113+08:00| mks| I125: SWBVmdb: Destroy SWB Window Id #0 because an invalid MKSWindow definition is received from UI over VMDB.

2020-04-12T09:48:28.119+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 1.

2020-04-12T09:48:28.119+08:00| mks| I125: SWBWindow: Window #1 validation failed: no valid host window or host surface.

2020-04-12T09:48:28.119+08:00| mks| I125: SWBVmdb: Destroy SWB Window Id #1 because an invalid MKSWindow definition is received from UI over VMDB.

2020-04-12T09:48:28.122+08:00| mks| I125: GDI-Backend: stopped by HWinMux to do window composition.

2020-04-12T09:48:28.122+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 0.

2020-04-12T09:48:33.319+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 1.

2020-04-12T09:48:33.319+08:00| mks| I125: GDI-Backend: successfully started by HWinMux to do window composition.

2020-04-12T09:48:33.323+08:00| mks| I125: MKS-HWinMux: Started GDI presentation backend

2020-04-12T09:48:33.323+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 1 rendering MKSWindow(s) of total 2.

2020-04-12T09:48:45.724+08:00| vcpu-0| I125: Triple fault.

2020-04-12T09:48:45.724+08:00| vcpu-0| I125: MsgHint: msg.monitorEvent.tripleFault

2020-04-12T09:48:45.724+08:00| vcpu-0| I125+ A fault has occurred causing a virtual CPU to enter the shutdown state. If this fault had occurred outside of a virtual machine, it would have caused the physical machine to restart. The shutdown state can be reached by incorrectly configuring the virtual machine, a bug in the guest operating system, or a problem in VMware Workstation.---------------------------------------

2020-04-12T09:48:52.943+08:00| vcpu-0| I125: CPU reset: hard (mode 0)

2020-04-12T09:48:52.943+08:00| vmx| I125: Stopping VCPU threads...

2020-04-12T09:48:52.944+08:00| vcpu-3| I125: CPU reset: hard (mode 1)

2020-04-12T09:48:52.944+08:00| vcpu-1| I125: CPU reset: hard (mode 1)

2020-04-12T09:48:52.944+08:00| vcpu-2| I125: CPU reset: hard (mode 1)

2020-04-12T09:48:52.957+08:00| svga| I125: SVGA thread is exiting

2020-04-12T09:48:52.962+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 1.

2020-04-12T09:48:52.971+08:00| mks| I125: GDI-Backend: stopped by HWinMux to do window composition.

2020-04-12T09:48:52.972+08:00| mks| I125: SWBWindow: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 0.

2020-04-12T09:48:52.972+08:00| vmx| I125: MKS thread is stopped

Reply
0 Kudos
2 Replies
dariusd
VMware Employee
VMware Employee

If this has occurred more than once, it would help if you set the Gather Debugging Information option to Full​ and see if the problem occurs again.  This will gather much more information in the vmware.log file next time the guest OS fails, and that information might give us a clue about what happened.

Thanks,

--

Darius

Reply
0 Kudos
nkaufman
Enthusiast
Enthusiast

Your error seems to be quite similar to what I've been getting for quite some time now..

See - WS15.5 VM crashes on resume

Reply
0 Kudos