I'm having issues with the VMware Workstation User Interface crashing when switching between VMs. The timing of the UI crash appears to be random, in that it will run fine for a period (sometimes days) and I can switch between VMs without problem but then all of sudden, it will crash. Once the crash happens once, it reoccurs frequently until I reboot or run a repair using the original install source. When the UI crashes, I can restart the UI and reconnect to the VMs immediately, as in the VMs remain running after the UI has crashed.
I'm currently running version 10.0.2 (build-1744117), however this issue also happened with the previous version 10.0.1.
When the crash occurs, there is an entry added to the Windows Application Event Log on the Host OS:
Faulting application name: vmware.exe, version: 10.0.2.46408, time stamp: 0x534c700c
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000041d
Fault offset: 0x77081a91
Faulting process id: 0x70d4
Faulting application start time: 0x01cf9083c70460c8
Faulting application path: C:\Program Files (x86)\VMware\VMware Workstation\vmware.exe
Faulting module path: unknown
Report Id: 4a93d863-fc78-11e3-826c-00268317d0da
Faulting package full name:
Faulting package-relative application ID:
and this in the vmware.log of the VM that caused the crash:
vmx| I120: SOCKET 5 (1884) recv detected client closed connection
vmx| I120: Vix: [1612 mainDispatch.c:2907]: VMAutomation: Connection Error (4) on connection 3.
vmx| I120: SOCKET 4 (1108) recv error 10054: An existing connection was forcibly closed by the remote host
vmx| I120: Vix: [1612 mainDispatch.c:2907]: VMAutomation: Connection Error (1) on connection 2.
vmx| I120: VmdbPipeStreamsOvlError Couldn't read: (10054) An existing connection was forcibly closed by the remote host.
vmx| I120: VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#164/' (-32)
vmx| I120: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#164/'
mks| I120: MKS-SWB: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 1.
mks| I120: GDI-Backend: stopped by HWinMux to do window composition.
mks| I120: MKS-SWB: Number of MKSWindows changed: 0 rendering MKSWindow(s) of total 0.
vmx| I120: SOCKET 6 (1980) recv detected client closed connection
vmx| I120: Vix: [1612 mainDispatch.c:2907]: VMAutomation: Connection Error (4) on connection 4.
vmx| I120: VmdbAddConnection: cnxPath=/db/connection/#24a/, cnxIx=4
Is anyone else experiencing this or similar and/or have any ideas about a root cause/solution? I came across this post here but no responses as yet - Workstation 10.x.x.x User Interface Crashes when switching VMs
Appreciate any help / advice!
Full support logs attached.
The Host consists of:
- Windows 8.1 Pro (x64) with Update
- Intel Core i7-2600k @ 3.40Ghz
- AMD Radeon HD 6900 Series
- 32GB DDR3 RAM
- 1 x OCZ 240GB SSD (running the OS)
- 1 x SanDisk 480GB SSD (running the VMs)
- 1 x WDC 3TB HDD
The Guests consist of:
- 5 x Windows Server 2012 R2 Standard
- 1 x Windows 8 Enterprise (x64)
- 1 x Windows 7 Enterprise SP1 (x64)