Random VMware Workstation 10.0.1 Crash/Hang, Windows 7 Host and Windows 7 Client

[soutbarr]

When running VMware Workstation 10.0.1, the client OS occasionally freezes up and stops responding.

It can happen to any of my virtual machines, but it happens to some more than others and I don't know why.

I enabled Gather Debugging Information Full and Log Virtual Machine Progress Periodically.  After a hang occurs this is in the log file

2013-11-22T06:40:52.050-07:00| vcpu-0| I120: AIOWIN32C: WaitForSingleObject failed: 00000102, err=00000000

2013-11-22T06:40:52.050-07:00| vcpu-0| I120: NOT_TESTED d:/build/ob/bora-1379776/bora/lib/aioManagers/aioWin32Completion.c:3201

2013-11-22T06:40:53.050-07:00| vcpu-0| I120: AIOWIN32C: WaitForSingleObject failed: 00000102, err=00000000

2013-11-22T06:40:53.050-07:00| vcpu-0| I120: NOT_TESTED d:/build/ob/bora-1379776/bora/lib/aioManagers/aioWin32Completion.c:3201

before that it is logging

halted progress=4802208

2013-11-22T06:21:28.914-07:00| vcpu-5| I120: VMSAMPLE: cs=0x10, rip=0xfffff880048449c2 halted progress=8016438

2013-11-22T06:21:28.914-07:00| vcpu-0| I120: VMSAMPLE: cs=0x10, rip=0xfffff880048449c2 halted progress=5921238

2013-11-22T06:21:28.914-07:00| vcpu-1| I120: VMSAMPLE: cs=0x10, rip=0xfffff880048449c2 halted progress=5311748

2013-11-22T06:21:28.914-07:00| vcpu-3| I120: VMSAMPLE: cs=0x10, rip=0xfffff880048449c2 halted progress=1944095

2013-11-22T06:21:28.914-07:00| vcpu-4| I120: VMSAMPLE: cs=0x10, rip=0xfffff880048449c2 halted progress=3180000

Attached is the log file.

[ruby12]

Hi

Welcome to the communities.

First please check HCL and latest drivers

There is no limit to courage.

[soutbarr]

Where is the Vmware workstation HCL?  Also which drivers in particular?  All of them, or are there drivers involved in workstation that aren't normally thought of?

[soutbarr]

Hardware wise I'm running an intel i7.  I can't find any hardware that isn't incompatible.  Not sure what you meant on drivers, do you mean the drivers on my host machine which are all up to date, or driver in the virtual machine?

[soutbarr]

Alright, I installed the windows SDK and debugging tools as well as process explorer, so that I could get a dump of it and look at it next time.  As a side note, I did not debug the thing itself.  I merely waited for it to freeze and dumped it's memory.  The breakpoint error is not from a debugger.

FAULTING_THREAD:  0000000000000ff0 - That thread belongs to the vmx itself. not to the operating system or any application in it.

*******************************************************************************

*                                                                             *

*                        Exception Analysis                                   *

*                                                                             *

*******************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for vmware-vmx.exe -

FAULTING_IP:

+577d520

00000000`00000000 ??              ???

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)

ExceptionAddress: 0000000000000000

   ExceptionCode: 80000003 (Break instruction exception)

  ExceptionFlags: 00000000

NumberParameters: 0

CONTEXT:  0000000000000000 -- (.cxr 0x0;r)

rax=000000000000000d rbx=000000000016f520 rcx=0000000077c8186a

rdx=0000000000000000 rsi=0000000000000001 rdi=0000000000000002

rip=0000000077c8186a rsp=000000000016f3e8 rbp=0000000000000002

r8=000000000016ed38  r9=000000000000000e r10=0000000000000000

r11=0000000000000246 r12=0000000000000000 r13=000000000016f490

r14=0000000000000000 r15=000000000389d140

iopl=0         nv up ei pl zr na po nc

cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246

ntdll!NtWaitForMultipleObjects+0xa:

00000000`77c8186a c3              ret

FAULTING_THREAD:  0000000000000ff0

DEFAULT_BUCKET_ID:  STATUS_BREAKPOINT

PROCESS_NAME:  vmware-vmx.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

APP:  vmware-vmx.exe

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

PRIMARY_PROBLEM_CLASS:  STATUS_BREAKPOINT

BUGCHECK_STR:  APPLICATION_FAULT_STATUS_BREAKPOINT

LAST_CONTROL_TRANSFER:  from 000007fefdd81430 to 0000000077c8186a

STACK_TEXT:

00000000`0016f3e8 000007fe`fdd81430 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!NtWaitForMultipleObjects+0xa

00000000`0016f3f0 00000000`77b32ce3 : 00000000`0016f530 00000000`0016f520 00000000`00000000 00000000`00000000 : KERNELBASE!WaitForMultipleObjectsEx+0xe8

00000000`0016f4f0 00000000`77a28f7d : 00000000`0016f5b0 00000000`ffffffff 00000000`00000001 00000000`00000024 : kernel32!WaitForMultipleObjectsExImplementation+0xb3

00000000`0016f580 00000000`77a262b2 : 00000000`00440018 00000000`00000000 00000001`3fdb2b30 00000000`00000064 : user32!RealMsgWaitForMultipleObjectsEx+0x12a

00000000`0016f620 00000001`3f697fad : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : user32!MsgWaitForMultipleObjectsEx+0x46

00000000`0016f660 00000001`3f69810e : 00000000`0000021c 00000000`00000000 00000000`00000000 00000000`00000000 : vmware_vmx!opus_decoder_destroy+0x2c230d

00000000`0016f6d0 00000001`3f50acf7 : 00000000`00447828 00000001`3f3c507b 00000000`031f0080 00000000`00000000 : vmware_vmx!opus_decoder_destroy+0x2c246e

00000000`0016f700 00000001`3f50ae01 : 00000000`00000000 00000001`3f3bad27 00000000`cfa12900 00000000`00000000 : vmware_vmx!opus_decoder_destroy+0x135057

00000000`0016f730 00000001`3f3c10b3 : 00000000`00000000 00000000`00000000 00000000`03898bd0 00000000`00000000 : vmware_vmx!opus_decoder_destroy+0x135161

00000000`0016f760 00000001`3f37a25e : 00000000`00000000 00000000`00000000 00000001`3fdb2b30 00000001`3f8f2f5e : vmware_vmx+0x710b3

00000000`0016f790 00000001`3f37a831 : 00000000`0389d140 00000000`00000000 00000000`0041b200 00000000`033eae30 : vmware_vmx+0x2a25e

00000000`0016f7e0 00000001`3f35318f : 00000000`00418730 00000000`033eae30 00000000`00000002 00001068`037e00cb : vmware_vmx+0x2a831

00000000`0016f8c0 00000001`3f35322a : 00000000`00000000 00000000`00000001 00000000`00000000 00000000`00000000 : vmware_vmx+0x318f

00000000`0016f8f0 00000001`3f3511de : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vmware_vmx+0x322a

00000000`0016f940 00000000`77b2652d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vmware_vmx+0x11de

00000000`0016f9f0 00000000`77c5c541 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd

00000000`0016fa20 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d

STACK_COMMAND:  ~0s; .ecxr ; kb

FOLLOWUP_IP:

vmware_vmx!opus_decoder_destroy+2c230d

00000001`3f697fad 8bd0            mov     edx,eax

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  vmware_vmx!opus_decoder_destroy+2c230d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: vmware_vmx

IMAGE_NAME:  vmware-vmx.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  52618ae3

FAILURE_BUCKET_ID:  STATUS_BREAKPOINT_80000003_vmware-vmx.exe!opus_decoder_destroy

BUCKET_ID:  X64_APPLICATION_FAULT_STATUS_BREAKPOINT_vmware_vmx!opus_decoder_destroy+2c230d

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:status_breakpoint_80000003_vmware-vmx.exe!opus_decoder_destroy

FAILURE_ID_HASH:  {64157de2-2e8b-5e04-f5f6-d6096f19e433}

[Clearify]

Did you ever find a solution to this?

I am having the same problem, and I did a memory dump using systernals, I get the same messages.  I also did a dump when it was working, as well as when it hung. (trying to find a program that will compare the differences, if you know of any - they are 4 gig memory dumps.)

VMWare has told me this I was 'an isolated incident', but we have the same issue here.  I have literally spent 2 months with untold hours, trying to troubleshoot - and even with VMWare support.

However they claim, that the debugs don't show them any information.  I find that hard to believe - especially when you and I have the same problem, and can see the same information doing a memory dump.

Here is my post - if you are able to draw any comparisons or advice on this.

Re: Virtual machines using Version 10.x on Windows 8.1 host freeze intermittently