Ok, today hasn't fun running a Windows 7 guest on a Windows 7 host.
Everything seems to be running fine, then I'll open a folder, start a program, open an e-mail, etc. and the VM will crash with a VMware dialog displaying the bad news. The VM was working fine yesterday morning. I didn't install any Windows updates or new programs yesterday and no restore point was created, but I can't say for sure that no automatic update of any application occurred. The failures throughout the day just seem so random and inexplicable.
The log files says this at the point of the error:
2014-01-23T16:11:51.706-06:00| vcpu-4| I120: hread 7316 57802014-01-23T16:13:24.464-06:00| vthread-22| W110: ----Win32 exception detected, exceptionCode 0xc0000005 (access violation)----
VTHREAD initialize thread 22 "vthread-22" host id 6700
hread-22" host id 6700
" host id 6700
| d 6700
| I120: FILE: FileCreateDirectoryRetry: Non-retriable error encountered (C:\ProgramData\VMware): Cannot create a file when that file already exists (183)
2014-01-23T16:13:24.464-06:00| vthread-22| W110: ExceptionAddress 0x7feddb74daf eflags 0x00010206
2014-01-23T16:13:24.464-06:00| vthread-22| W110: rwFlags 0 badAddr 0xc0
2014-01-23T16:13:24.464-06:00| vthread-22| W110: rax 0x1d899380 rbx 0x826e2d8 rcx 0
2014-01-23T16:13:24.464-06:00| vthread-22| W110: rdx 0x1d899380 rsi 0x1d8c0000 rdi 0x20809440
2014-01-23T16:13:24.464-06:00| vthread-22| W110: r8 0 r9 0 r10 0x7feddee8350
2014-01-23T16:13:24.464-06:00| vthread-22| W110: r11 0x1d8c0000 r12 0x1 r13 0x3
2014-01-23T16:13:24.464-06:00| vthread-22| W110: r14 0 r15 0x8
2014-01-23T16:13:24.464-06:00| vthread-22| W110: rip 0x7feddb74daf rsp 0x456f0d0 rbp 0x456f230
2014-01-23T16:13:24.464-06:00| vthread-22| W110: LastBranchToRip 0 LastBranchFromRip 0
2014-01-23T16:13:24.464-06:00| vthread-22| W110: LastExceptionToRip 0 LastExceptionFromRip 0
2014-01-23T16:13:24.464-06:00| vthread-22| W110: The following data was delivered with the exception:
2014-01-23T16:13:24.464-06:00| vthread-22| W110: -- 0
2014-01-23T16:13:24.464-06:00| vthread-22| W110: -- 0xc0
2014-01-23T16:13:24.464-06:00| vthread-22| W110: CoreDump: Writing minidump to C:\VirtualMachines\TitanXxxx-VM\vmware-vmx-5780.dmp
2014-01-23T16:13:24.501-06:00| vthread-22| I120: CoreDump: including module base 0x0x13f4c0000 size 0x0x014ad000
2014-01-23T16:13:24.501-06:00| vthread-22| I120: checksum 0x012d7405 timestamp 0x52618ae3
2014-01-23T16:13:24.501-06:00| vthread-22| I120: image file C:\Apps\VMware\Workstation\10\x64\vmware-vmx.exe
2014-01-23T16:13:24.501-06:00| vthread-22| I120: file version 10.0.1.41495
2014-01-23T16:13:24.501-06:00| vthread-22| I120: CoreDump: including module base 0x0x77020000 size 0x0x001a9000
2014-01-23T16:13:24.501-06:00| vthread-22| I120: checksum 0x001a875f timestamp 0x521eaf24
2014-01-23T16:13:24.501-06:00| vthread-22| I120: image file C:\Windows\System32\ntdll.dll
2014-01-23T16:13:24.501-06:00| vthread-22| I120: file version 6.1.7601.18247
...
Workstation 10 created DMP files each time in the virtual machine directory. I'd like to identify a specific Windows driver or app that may be causing the problem, but am not sure what tool or procedure I need to read the dmp files.
Is there a utility I can use to read the VMware dmp file? (I'm not sure if it is appropriate to upload a dmp file here, but will do so if requested.)
Any other pointers on how I can diagnose the cause of this persistent failure?
This is really putting a chill in my thrill. :-(
Thanks in advance!
--
Jack