VMware Communities
joe_y
Contributor
Contributor

VMware Player unrecoverable error: (vcpu-0) -- system starts and then vmware crashes with access violation

This has been a VM I have been using for a long time.  It is Windows XP.  I was using VMWare workstation player 15.0 and upgraded to 15.5.6 and then it started having problems.  I hope someone can see something in the log that I can fix.  Thanks in advance. _Joe_

=======================

vmware.log file attached

=======================

Reply
0 Kudos
17 Replies
Alex_Romeo
Leadership
Leadership

Hi,

the log file put it in .txt file and attach it to the post.

ARomeo

Blog: https://www.aleadmin.it/
Reply
0 Kudos
scott28tt
VMware Employee
VMware Employee

Moderator: Two things for you to consider:

- Please create posts in the correct product area, thread moved to the Workstation Player area.

- Please edit your post and use the Attach function in the bottom-right of the post creator window to add your log file, rather than posting it as a massive text dump


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
Reply
0 Kudos
joe_y
Contributor
Contributor

Sorry about that.  I found that group with a search engine and didn't look for another group.

Reply
0 Kudos
joe_y
Contributor
Contributor

Can I use a working vmx file and point it to my vmdk file?  Is there something I should be looking at for a typical vcpu error?

Thanks

Reply
0 Kudos
dariusd
VMware Employee
VMware Employee

Hi Joe,

Could you please try setting the option to Gather Debugging Information to Full and then try powering on your virtual machine again?  It will most likely fail again, but the resulting vmware.log could prove more useful in troubleshooting.

Thanks in advance,

--

Darius

Reply
0 Kudos
dariusd
VMware Employee
VMware Employee

Actually, I think I have figured out what is going on.  If you are game to try editing your VM's configuration file, try adding:

   monitor_control.disable_apichv = "TRUE"

to the configuration file and see if your VM then functions correctly.  Its performance will probably be degraded (perhaps substantially), but it might be enough to get you going again.

Thanks,

--

Darius

zcui
VMware Employee
VMware Employee

Hi Joe_y,

Would it be possible for you to reproduce the problem by following the instructions below?

1) Add the following line to C:\ProgramData\VMware\VMware Workstation\config.ini:

   

coreDumpFlags = 0x20002

2) Add the following line to the .vmx configuration file of the VM (it is located under the VM directory):

vmx.buildType=debug

3) Power on the VM and when it crashes, could you upload the vmware-vmx*.dmp files from the VM directory?

Let me know if you need clarifications.

Thanks for your cooperation!

Reply
0 Kudos
zcui
VMware Employee
VMware Employee

> 3) Power on the VM and when it crashes, could you upload the vmware-vmx*.dmp files from the VM directory?

I meant to say upload both the "vmware-vmx*.dmp" files and "vmware.log".

Reply
0 Kudos
zcui
VMware Employee
VMware Employee

Hi Joe_y,

Any updates?

Thanks.

Reply
0 Kudos
fipsy
Contributor
Contributor

@dariusd:Thanks for the tip! This solved the same problem on a Windows XP machine for me. By the way, the problem also occurs with Workstation Pro 16.1.0. But only if the Hyper-V hypervisor is enabled! If I disable the hypervisor in Powershell (bcdedit /set hypervisorlaunchtype off), the error does NOT occur and Windows XP starts without problems! So it seems to be an issue interacting with Hyper-V. I think this should be fixed by all means!

For reference, here is an excerpt from the log showing the error:

2021-01-20T13:11:09.756+01:00| vcpu-0| I005: DDB: "longContentID" = "9e2566e4c9e3c474366b2182f6f836d5" (was "4aaa2f8d200610b08b1c8468f4d5273b")
2021-01-20T13:11:13.302+01:00| vcpu-0| W003: ----Win32 exception detected, exceptionCode 0xc0000005 (access violation)----
2021-01-20T13:11:13.302+01:00| vcpu-0| W003: ExceptionAddress 0x7ff65fc8fae4 eflags 0x00010216
2021-01-20T13:11:13.302+01:00| vcpu-0| W003: rwFlags 0x1 badAddr 0xf0
2021-01-20T13:11:13.302+01:00| vcpu-0| W003: rax 0 rbx 0x1965e329b90 rcx 0xf
2021-01-20T13:11:13.302+01:00| vcpu-0| W003: rdx 0 rsi 0x80 rdi 0x1965e329c10
2021-01-20T13:11:13.302+01:00| vcpu-0| W003: r8 0x1e r9 0x16298 r10 0
2021-01-20T13:11:13.302+01:00| vcpu-0| W003: r11 0 r12 0 r13 0
2021-01-20T13:11:13.302+01:00| vcpu-0| W003: r14 0x10 r15 0x1000
2021-01-20T13:11:13.302+01:00| vcpu-0| W003: rip 0x7ff65fc8fae4 rsp 0x3a66dffac8 rbp 0
2021-01-20T13:11:13.302+01:00| vcpu-0| W003: LastBranchToRip 0 LastBranchFromRip 0
2021-01-20T13:11:13.302+01:00| vcpu-0| W003: LastExceptionToRip 0 LastExceptionFromRip 0
2021-01-20T13:11:13.302+01:00| vcpu-0| W003: The following data was delivered with the exception:
2021-01-20T13:11:13.302+01:00| vcpu-0| W003: -- 0x1
2021-01-20T13:11:13.302+01:00| vcpu-0| W003: -- 0xf0
2021-01-20T13:11:13.305+01:00| vcpu-0| W003: CoreDump: Writing minidump to D:\VMs\Windows XP Professional\vmware-vmx.dmp

[..]

2021-01-20T13:11:13.741+01:00| vcpu-0| I005: Backtrace:
2021-01-20T13:11:13.749+01:00| vcpu-0| I005: backtrace[00] frame 0x3a66dffb60 IP 0x7ff65fc49f11 params 0x1965e329bf0 0x1965e329bf0 0x1965e329ba0 0x1965e329c10 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff65fc30000 0x0001:0x0000000000018f11] <C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x19f11
2021-01-20T13:11:13.749+01:00| vcpu-0| I005: backtrace[01] frame 0x3a66dffba0 IP 0x7ff65fc50635 params 0 0x1965e329b90 0 0 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff65fc30000 0x0001:0x000000000001f635] <C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x20635
2021-01-20T13:11:13.750+01:00| vcpu-0| I005: backtrace[02] frame 0x3a66dffbd0 IP 0x7ff65fc6cf5d params 0x1965e329b90 0 0x1965e32b458 0 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff65fc30000 0x0001:0x000000000003bf5d] <C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x3cf5d
2021-01-20T13:11:13.750+01:00| vcpu-0| I005: backtrace[03] frame 0x3a66dffc00 IP 0x7ff65fc48652 params 0x1965ce8d000 0 0x1965e629150 0x24f68c19af2 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff65fc30000 0x0001:0x0000000000017652] <C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x18652
2021-01-20T13:11:13.750+01:00| vcpu-0| I005: backtrace[04] frame 0x3a66dffc30 IP 0x7ff660140489 params 0 0 0 0 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff65fc30000 0x0001:0x000000000050f489] <C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x510489
2021-01-20T13:11:13.750+01:00| vcpu-0| I005: backtrace[05] frame 0x3a66dffcc0 IP 0x7ff6602cd204 params 0 0 0 0 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff65fc30000 0x0001:0x000000000069c204] <C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x69d204
2021-01-20T13:11:13.755+01:00| vcpu-0| I005: backtrace[06] frame 0x3a66dffcc8 IP 0x7ff8ece77034 params 0 0 0 0 [C:\WINDOWS\System32\KERNEL32.DLL base 0x00007ff8ece60000 0x0001:0x0000000000016034] BaseThreadInitThunk
2021-01-20T13:11:13.760+01:00| vcpu-0| I005: backtrace[07] frame 0x3a66dffcf8 IP 0x7ff8ed9bd0d1 params 0 0 0 0 [C:\WINDOWS\SYSTEM32\ntdll.dll base 0x00007ff8ed970000 0x0001:0x000000000004c0d1] RtlUserThreadStart
2021-01-20T13:11:13.760+01:00| vcpu-0| I005: Msg_Post: Error
2021-01-20T13:11:13.760+01:00| vcpu-0| I005: [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vcpu-0)
2021-01-20T13:11:13.760+01:00| vcpu-0| I005+ Exception 0xc0000005 (access violation) has occurred.
2021-01-20T13:11:13.760+01:00| vcpu-0| I005: [msg.panic.haveLog] A log file is available in "D:\VMs\Windows XP Professional\vmware.log".
2021-01-20T13:11:13.760+01:00| vcpu-0| I005: [msg.panic.requestSupport.withoutLog] You can request support.
2021-01-20T13:11:13.760+01:00| vcpu-0| I005: [msg.panic.requestSupport.vmSupport.windowsOrLinux]
2021-01-20T13:11:13.760+01:00| vcpu-0| I005+ To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.
2021-01-20T13:11:13.760+01:00| vcpu-0| I005+ You can also run the "vm-support" script in the Workstation folder directly.
2021-01-20T13:11:13.760+01:00| vcpu-0| I005: [msg.panic.response] We will respond on the basis of your support entitlement.
2021-01-20T13:11:13.760+01:00| vcpu-0| I005: ----------------------------------------
2021-01-20T13:11:13.797+01:00| mks| W003: Panic in progress... ungrabbing
2021-01-20T13:11:13.797+01:00| mks| I005: MKS: Release starting (Panic)
2021-01-20T13:11:13.797+01:00| mks| I005: MKS: Release finished (Panic)
2021-01-20T13:11:26.180+01:00| mks| I005: MKSGrab: Grab attempt while in Panic. Ignored.
2021-01-20T13:11:30.996+01:00| mks| I005: MKSGrab: Grab attempt while in Panic. Ignored.

Reply
0 Kudos
dcarvalh
Contributor
Contributor

Hi,

I'm having the same issue while trying to run:

- WSL2 so Hyper-V enabled

- Workstation 16.1 and also tried latest TP from 2020

2021-04-24T22:30:08.904+02:00| vcpu-1| I005: Backtrace:
2021-04-24T22:30:08.905+02:00| vcpu-1| I005: backtrace[00] frame 0x8796ffe878 IP 0x00000003 params 0x7ff6feea78e5 0 0x7ff6fee73237 0x7ff700555050 [no module data] ???
2021-04-24T22:30:08.905+02:00| vcpu-1| I005: backtrace[01] frame 0x8796ffe880 IP 0x00000041 params 0 0x7ff6fee73237 0x7ff700555050 0xe [no module data] ???
2021-04-24T22:30:08.905+02:00| vcpu-1| I005: backtrace[02] frame 0x8796ffe888 IP 0x7ff6feea78e5 params 0x7ff6fee73237 0x7ff700555050 0xe 0x1af66f2b628 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx-debug.exe base 0x00007ff6fee40000 0x0001:0x00000000000668e5] <C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx-debug.exe>+0x678e5
2021-04-24T22:30:08.905+02:00| vcpu-1| I005: Msg_Post: Error
2021-04-24T22:30:08.905+02:00| vcpu-1| I005: [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vcpu-1)
2021-04-24T22:30:08.905+02:00| vcpu-1| I005+ Exception 0xc0000005 (access violation) has occurred.


I have the full logs dump how can I share them with VMWare ?

Regards

Reply
0 Kudos
zcui
VMware Employee
VMware Employee

 

Thanks! I have fixed this issue and the root cause is HyperV doesn't support disabled APIC state. You should get the fix on Workstation 16.2 when you do the next upgrade.

dizecrypt
Contributor
Contributor

Wow amazing didn't expect a fix to ever happen...

you can probably close my thread since you fixed it :)) https://communities.vmware.com/t5/VMware-Workstation-Player/VMware-Player-unrecoverable-error-vcpu-0...

edit: I'm the same guy as the guy with the logs above.

Reply
0 Kudos
zcui
VMware Employee
VMware Employee

The issue you mentioned in another link (see below) is for Win10 guest on the fast ring (insider build-21364), and it is different than the WinXP one on the slow ring (build-19041) in this post. Note that MSFT is still making changes at a fast pace to the fast ring and it has quite some bugs, and the code churn won't be stabilized in the near future. The WS beta build is no longer available on our build storage, and I will see if I can restore the build to see what was going on with the Win10 failure.

 

https://communities.vmware.com/t5/VMware-Workstation-Player/VMware-Player-unrecoverable-error-vcpu-0...

Reply
0 Kudos
xsm1997
Contributor
Contributor

Hello,

I am using Workstation 16.2.1 with HyperV enabled, and I still cannot successfully boot Windows 7 guest on Windows 11 host.

Workstation 16.2.1 does not show a vcpu error (but Workstation 16.1 does). Instead, it power off automatically during the windows logo boot stage.

I have added the debug flags. In the vmware.log, it only shows 'vcpu-1 CPU reset: soft (mode Emulation)'. However, in event viewer it shows that vmware-vmx-debug.exe crashed with error 0xc0000005, but I cannot find any dump files.

My colleague can reproduce the issue on almost the same environment (Windows 11 host, Workstation 16.2.1, AMD Zen3 CPU, AMD B550M chipset) but Windows 10 guest. But he is getting a vcpu-0 exception pop-up error and a dump file. By the way, I also tried Windows 10 guest. On my environment, the Windows 10 guest also powered off without any error message.

I am uploading my vmware.log file (vmware-mine.log), his vmware.log file (vmware-colleague.log, but unfortunately without debug settings enabled), and his vmware dump file (vmware-vmx-5900x-win10x64.zip).

I am using Windows 11 insider slow ring, and my colleague is using a regular build of Windows 11 (not insider).

Hope this issue can be resolved soon.

Thanks in advance.

Reply
0 Kudos
xsm1997
Contributor
Contributor

@zcui Can you take a look of my issue mentioned above?

Reply
0 Kudos