Logging= "FALSE" | vmware.exe and vmware-unity-helper.exe | Windows Fault - Exception code: 0xc0000005 | MSVCR90.dll | VMware Workstation 9.0.2-1031769 | 9.0.1-894247

[harmandeep]

Issue: Whenever we exit VMware Workstation (vmware.exe), we receive PROMPT stating

"VMware Workstation has stopped responding" |  "VMware Unity Helper has stopped working"

http://www.imagebam.com/image/55a2fb245934855

PROMPT is received when using 9.0.2-1031769. If we are running 9.0.1-894247, then we won't
receive a PROMPT, but still, Windows logs Application Fault for these binaries - vmware.exe | vmware-unity-helper.exe ... as seen below

http://www.imagebam.com/image/bd755a245934888

http://www.imagebam.com/image/509e61245934873

VMware.exe also stops responding when we click HELP > ABOUT VMWARE WORKSTATION

Interestingly, this issue only OCCURS when we have defined Logging= "FALSE" parameter in Global Config file. If we define this parameter

in the Individual VM - VMX --- then this Issue doesn't occur.

We tested this issue with 9.0.2-1031769 & 9.0.1-894247 on Multiple Systems - and ISSUE persists on all the tested Systems.

So apparently this issue seems to be persisting when -  "Logging = "FALSE" Directive - is defined in the Global Config.ini PATH.

Tested System Specs:

Host System: Windows 7 Sp1 x64 Sp1
User Account Control (UAC): Enabled
Tested VMware Workstation Binary Package:

VMware-workstation-full-9.0.2-1031769.exe |  b4db8858e5dc06e50a800c53c1431963

VMware-workstation-full-9.0.1-894247.exe |  dc3f15d6c5fc153b7f91405e4d9a2596
Model: Dell 14R 5420 - 16GB RAM | HP DV6-3225DX - 4GB RAM  (no PageFile.sys on either of these Systems)

Global Config.ini:

.encoding = "windows-1252"
authd.client.port = "902"
authd.proxy.vim = "vmware-hostd:hostd-vmdb"
authd.proxy.nfc = "vmware-hostd:ha-nfc"
installerDefaults.autoSoftwareUpdateEnabled = "no"
installerDefaults.autoSoftwareUpdateEnabled.epoch = "805"
installerDefaults.componentDownloadEnabled = "no"
installerDefaults.dataCollectionEnabled = "no"
installerDefaults.dataCollectionEnabled.epoch = "805"

MemTrimRate=0
sched.mem.pshare.enable = "FALSE"
prefvmx.useRecommendedLockedMemSize = "FALSE"
prefvmx.minVmMemPct = "100"
mainMem.useNamedFile = "FALSE"
mainMem.writeZeros = "TRUE"
MemAllowAutoScaleDown = "FALSE"
prefvmx.allVMMemoryLimit = "14000" DELL SYSTEM ||| prefvmx.allVMMemoryLimit = "2000" HP SYSTEM
Logging="FALSE"

Event Viewer Logs:

CASE I  - Logging = "FALSE" in Global Config.ini - and then we try to exit/close VMware.exe

Faulting application name: vmware.exe, version: 9.0.2.35902, time stamp: 0x512c8c3e
Faulting module name: MSVCR90.dll, version: 9.0.30729.4940, time stamp: 0x4ca2ef57
Exception code: 0xc0000005
Fault offset: 0x000374da
Faulting process id: 0x180
Faulting application start time: 0x01ce2bb9db49f655
Faulting application path: C:\Program Files (x86)\VMware\VMware Workstation\vmware.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4940_none_50916076bcb9a742\MSVCR90.dll
Report Id: 20761429-97ad-11e2-b145-005056c00008

Faulting application name: vmware-unity-helper.exe, version: 9.0.2.35902, time stamp: 0x512c79ad
Faulting module name: MSVCR90.dll, version: 9.0.30729.4940, time stamp: 0x4ca2ef57
Exception code: 0xc0000005
Fault offset: 0x000374da
Faulting process id: 0xb58
Faulting application start time: 0x01ce2bb9dd24feda
Faulting application path: C:\Program Files (x86)\VMware\VMware Workstation\vmware-unity-helper.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4940_none_50916076bcb9a742\MSVCR90.dll
Report Id: 2075ed19-97ad-11e2-b145-005056c00008

CASE II  - Logging = "FALSE" in Global Config.ini - and then we click HELP > ABOUT VMWARE WORKSTATION

Faulting application name: vmware-unity-helper.exe, version: 9.0.2.35902, time stamp: 0x512c79ad
Faulting module name: MSVCR90.dll, version: 9.0.30729.4940, time stamp: 0x4ca2ef57
Exception code: 0xc0000005
Fault offset: 0x000374da
Faulting process id: 0x13a8
Faulting application start time: 0x01ce2bba716b8dbf
Faulting application path: C:\Program Files (x86)\VMware\VMware Workstation\vmware-unity-helper.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4940_none_50916076bcb9a742\MSVCR90.dll
Report Id: a5aebbff-97b0-11e2-b145-005056c00008

VC++ Packages installed on Dell System: http://www.imagebam.com/image/1834e5245936065

vm-support.vbs [executed with ADMIN privileges] - in attachment - [From DELL System]: http://www.mediafire.com/?krqj047pn25uf5a

So can we get a fix for this ???

[mfelker]

Did a search on  your dll found this

http://pcsupport.about.com/od/findbyerrormessage/a/msvcr90-dll-not-found-missing-error.htm

Maybe it will maybe not.  Instead of re-installing VMware I run the installer and choose the repair option.  If that fails start a Google search like that above (just put the name of dll as a search term).  BTW  the author recommends NOT to download the the dll from what may be a warez of scam site.

[JDidwedw]

I have had the same problem with VMware Workstation 10.0.3 build 1895310.

My PC is running Windows 7 (64-bit).

I used an editor to edit the file „C:\ProgramData\VMware\VMware Workstation\config.ini“.

I have put a „#“ in front of the line „logging=FALSE“.

After this the vmware.exe and vmware-unity-helper.exe did not crash any more with the MSVCR90.dll problem.

It seems to be a bug in VMware Workstation.