Vmware Workstation 16.1.0 - Support - Online community defect?

[whorsfall]

Hi,

Minor defect. Using: Vmware Workstation 16.1.0 build-17198959

When choosing from the VMware Help Menu - Support - Online community

It takes me to:

http://communities.vmware.com/community/vmtn/desktop/workstation

Which is saying "Page not found"

Thanks,

Ward.

[russtanner]

After much testing here's what I learned.

If any version of Windows VM (2000, XP) is running in the background (or multiple versions of Wins are running),  they will close with the dxgi.dll fault (shown in a previous post above) usually within 20 minutes.

This issue does not affect any of my Linux VMs.

This is interesting: If all the Linux VMs are running in the background, this prevents any Windows VMs from faulting when running in the background.

So this is the repeatable pattern that I've found so far.

[russtanner]

Is there anything I can do to move forward with this, file a bug report, etc? The issue is consistently repeatable  for me.

All my VMs were moved from a previous computer running Workstation 9. They worked perfectly there for years. It was rock solid and we never had any issue. Now, ALL Windows VMs shut down (when running in background) but no Linux VMs do.

How should I proceed?

Your help is very much appreciated as I have to use this software frequently and often need to leave it running in the background to prevent having to reboot and reopen all development apps over and over.

Here is the latest debug log and event viewer entries (logs are attached):

Debug Log

2020-12-15T13:55:25.222-05:00| vcpu-0| I006: GuestInfo: Issuing Vigor notification; additions 0, changes 2
2020-12-15T13:55:31.271-05:00| mks| W003: ----Win32 exception detected, exceptionCode 0xc0000005 (access violation)----
2020-12-15T13:55:31.271-05:00| mks| W003: ExceptionAddress 0x7fffc345cad0 eflags 0x00010247
2020-12-15T13:55:31.271-05:00| mks| W003: rwFlags 0x8 badAddr 0x7fffc345cad0
2020-12-15T13:55:31.271-05:00| mks| W003: rax 0x7fffc345cad0 rbx 0x3fe9e97000 rcx 0
2020-12-15T13:55:31.271-05:00| mks| W003: rdx 0x7fffc345cad0 rsi 0x30000 rdi 0x3feabffc98
2020-12-15T13:55:31.271-05:00| mks| W003: r8 0x3feabffcb8 r9 0x7fffc345cad0 r10 0xffff868b95a
2020-12-15T13:55:31.271-05:00| mks| W003: r11 0x4000000 r12 0 r13 0
2020-12-15T13:55:31.271-05:00| mks| W003: r14 0 r15 0x3feabffcb8
2020-12-15T13:55:31.271-05:00| mks| W003: rip 0x7fffc345cad0 rsp 0x3feabffb08 rbp 0x7fffc345cad0
2020-12-15T13:55:31.271-05:00| mks| W003: LastBranchToRip 0 LastBranchFromRip 0
2020-12-15T13:55:31.271-05:00| mks| W003: LastExceptionToRip 0 LastExceptionFromRip 0
2020-12-15T13:55:31.271-05:00| mks| W003: The following data was delivered with the exception:
2020-12-15T13:55:31.271-05:00| mks| W003: -- 0x8
2020-12-15T13:55:31.271-05:00| mks| W003: -- 0x7fffc345cad0
2020-12-15T13:55:31.272-05:00| mks| I005: CoreDump: Minidump file D:\Virtual Machines\Clone of Windows 2000 Professional\vmware-vmx-debug.dmp exists. Rotating ...

FIRST EVENT

Faulting application name: vmware-vmx-debug.exe, version: 16.1.0.683, time stamp: 0x5fb4b829
Faulting module name: dxgi.dll_unloaded, version: 10.0.19041.546, time stamp: 0x383f2650
Exception code: 0xc0000005
Fault offset: 0x000000000006cad0
Faulting process id: 0x8848
Faulting application start time: 0x01d6d31388f189b9
Faulting application path: C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx-debug.exe
Faulting module path: dxgi.dll
Report Id: a0c8ea47-f6d8-4eee-a3bf-fb183713715e
Faulting package full name:
Faulting package-relative application ID:

SECOND EVENT - Always occurs 2 seconds later

Faulting application name: vmware-vmx-debug.exe, version: 16.1.0.683, time stamp: 0x5fb4b829
Faulting module name: dxgi.dll_unloaded, version: 10.0.19041.546, time stamp: 0x383f2650
Exception code: 0xc000041d
Fault offset: 0x000000000006cad0
Faulting process id: 0x8848
Faulting application start time: 0x01d6d31388f189b9
Faulting application path: C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx-debug.exe
Faulting module path: dxgi.dll
Report Id: c9a41788-b589-49a4-bf70-62e871bd2ec5
Faulting package full name:
Faulting package-relative application ID:

[bonnie201110141]

Sorry for the late response! Will you please enable debug mode from vm > settings > options > advanced > Gather debugging information to "Full", and attach all vmware*.log and mksSandbox*.log, as well as the vmware-vmx-debug.dmp file (all from the VM directory)?

And also, can you give it a try if disabling 3D can workaround the issue? Please disable 3D from vm settings > hardware > display > uncheck Accelerate 3D graphics?

[russtanner]

OK thanks. I'll post all that shortly.

[russtanner]

Disabling 3D is working. The VMs are not shutting down anymore when put them in the background.

I will collect logs with the 3D enabled and post them here as you requested. Thank you again for your help.

[russtanner]

OK, When  re-enabled "Accelerate 3D Graphics", the problem with VMs shutting down returned as before.

Of course, TODAY, the Win 2K VM won't fail  (for some reason) but the XP VM has.

I have attached the logs as you requested. I attached the logs for the XP VM and will send the Win 2K logs as soon as it fails.

Thanks again for your help.

[russtanner]

I rebooted the host computer and opened the Win 2K VM, placed it in the background and it crashed, so I'm including the logs as requested.

Thanks so much.

[bonnie201110141]

Thanks for the logs. I filed an internal bug to involve the related developers.

[russtanner]

Thank you!