VMware Communities
briangideon
Enthusiast
Enthusiast
Jump to solution

Upgraded to 16 and now WinXP won't boot

I upgraded from 15 to 16 today and now my WinXP virtual machine will not boot. It looks like the vmware-vmx.exe process is crashing. A screenshot of the error and full log file are attached in a zip file. I tried booting WinXP into safe mode and get the same result. It looks like the crash occurs just after I see the message in WinXP that it is loading agp440.sys. If anybody has any ideas let me know. 

I get a dialog box that pops that says VMWare Workstation unrecoverable error: (vcpu-0), Exception 0xc0000005 (access violation) has occurred.

Here are some log entries that I feel are pertinent.

2021-01-13T08:56:35.894-06:00| vcpu-0| I005: Unknown int 10h func 0x2000
2021-01-13T08:56:39.486-06:00| vcpu-0| I005: DDB: "longContentID" = "45996b866d42635a00452d3ebb892143" (was "342464ba1de4b5987910cfd07387e093")
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: ----Win32 exception detected, exceptionCode 0xc0000005 (access violation)----
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: ExceptionAddress 0x7ff67c2efae4 eflags 0x00010216
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: rwFlags 0x1 badAddr 0xf0
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: rax 0 rbx 0x213baba8050 rcx 0xf
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: rdx 0 rsi 0x80 rdi 0x213baba80d0
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: r8 0x1e r9 0x16298 r10 0
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: r11 0 r12 0 r13 0
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: r14 0x10 r15 0x1000
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: rip 0x7ff67c2efae4 rsp 0x72959ff708 rbp 0
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: LastBranchToRip 0 LastBranchFromRip 0
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: LastExceptionToRip 0 LastExceptionFromRip 0
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: The following data was delivered with the exception:
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: -- 0x1
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: -- 0xf0
2021-01-13T08:56:42.010-06:00| vcpu-0| W003: CoreDump: Writing minidump to C:\Virtual Machines\REDACTED\vmware-vmx.dmp

and further down...

2021-01-13T08:56:42.200-06:00| vcpu-0| I005: Backtrace:
2021-01-13T08:56:42.204-06:00| vcpu-0| I005: backtrace[00] frame 0x72959ff7a0 IP 0x7ff67c2a9f11 params 0x213baba80b0 0x213baba80b0 0x213baba8060 0x213baba80d0 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff67c290000 0x0001:0x0000000000018f11] <C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x19f11
2021-01-13T08:56:42.204-06:00| vcpu-0| I005: backtrace[01] frame 0x72959ff7e0 IP 0x7ff67c2b0635 params 0 0x213baba8050 0 0 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff67c290000 0x0001:0x000000000001f635] <C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x20635
2021-01-13T08:56:42.204-06:00| vcpu-0| I005: backtrace[02] frame 0x72959ff810 IP 0x7ff67c2ccf5d params 0x213baba8050 0 0x213baba9918 0 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff67c290000 0x0001:0x000000000003bf5d] <C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x3cf5d
2021-01-13T08:56:42.204-06:00| vcpu-0| I005: backtrace[03] frame 0x72959ff840 IP 0x7ff67c2a8652 params 0x213b7f7a000 0 0x213badedbe0 0x279c9ee853f6 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff67c290000 0x0001:0x0000000000017652] <C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x18652
2021-01-13T08:56:42.204-06:00| vcpu-0| I005: backtrace[04] frame 0x72959ff870 IP 0x7ff67c7a0489 params 0 0 0 0 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff67c290000 0x0001:0x000000000050f489] <C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x510489
2021-01-13T08:56:42.204-06:00| vcpu-0| I005: backtrace[05] frame 0x72959ff900 IP 0x7ff67c92d204 params 0 0 0 0 [C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe base 0x00007ff67c290000 0x0001:0x000000000069c204] <C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx.exe>+0x69d204
2021-01-13T08:56:42.204-06:00| vcpu-0| I005: backtrace[06] frame 0x72959ff908 IP 0x7ff8616a7034 params 0 0 0 0 [C:\WINDOWS\System32\KERNEL32.DLL base 0x00007ff861690000 0x0001:0x0000000000016034] BaseThreadInitThunk
2021-01-13T08:56:42.208-06:00| vcpu-0| I005: backtrace[07] frame 0x72959ff938 IP 0x7ff861efd0d1 params 0 0 0 0 [C:\WINDOWS\SYSTEM32\ntdll.dll base 0x00007ff861eb0000 0x0001:0x000000000004c0d1] RtlUserThreadStart
2021-01-13T08:56:42.208-06:00| vcpu-0| I005: Msg_Post: Error
2021-01-13T08:56:42.208-06:00| vcpu-0| I005: [msg.log.error.unrecoverable] VMware Workstation unrecoverable error: (vcpu-0)
2021-01-13T08:56:42.208-06:00| vcpu-0| I005+ Exception 0xc0000005 (access violation) has occurred.
2021-01-13T08:56:42.208-06:00| vcpu-0| I005: [msg.panic.haveLog] A log file is available in "C:\Virtual Machines\REDACTED\vmware.log".
2021-01-13T08:56:42.208-06:00| vcpu-0| I005: [msg.panic.requestSupport.withoutLog] You can request support.
2021-01-13T08:56:42.208-06:00| vcpu-0| I005: [msg.panic.requestSupport.vmSupport.windowsOrLinux]
2021-01-13T08:56:42.208-06:00| vcpu-0| I005+ To collect data to submit to VMware support, choose "Collect Support Data" from the Help menu.
2021-01-13T08:56:42.208-06:00| vcpu-0| I005+ You can also run the "vm-support" script in the Workstation folder directly.
2021-01-13T08:56:42.208-06:00| vcpu-0| I005: [msg.panic.response] We will respond on the basis of your support entitlement.
2021-01-13T08:56:42.208-06:00| vcpu-0| I005: ----------------------------------------
2021-01-13T08:56:42.983-06:00| mks| W003: Panic in progress... ungrabbing
2021-01-13T08:56:42.983-06:00| mks| I005: MKS: Release starting (Panic)
2021-01-13T08:56:42.983-06:00| mks| I005: MKS: Release finished (Panic)
2021-01-13T08:57:33.573-06:00| vmx| I005: GuestRpcSendTimedOut: message to toolbox-dnd timed out.
2021-01-13T08:59:33.678-06:00| vmx| I005: GuestRpcSendTimedOut: message to toolbox timed out.
2021-01-13T08:59:33.678-06:00| vmx| I005: Vix: [guestCommands.c:1942]: Error VIX_E_TOOLS_NOT_RUNNING in VMAutomationTranslateGuestRpcError(): VMware Tools are not running in the guest
2021-01-13T09:06:33.571-06:00| vmx| I005: Tools: No activity for 10 minutes, resetting Tools version.
2021-01-13T09:06:33.571-06:00| vmx| I005: TOOLS setting legacy tools version to '0' type 0, manifest status is 9
2021-01-13T09:06:33.571-06:00| vmx| I005: Tools_SetVersionAndType: Updating the Tools Version in the disk
2021-01-13T09:06:33.571-06:00| vmx| I005: DDB: "toolsVersion" = "0" (was "10252")
2021-01-13T09:06:33.578-06:00| vmx| I005: DDB: "toolsInstallType" = "0" (was "1")
2021-01-13T09:06:33.582-06:00| vmx| I005: Tools_SetVersionAndType: Done updating the Tools Version in the disk
2021-01-13T09:06:33.582-06:00| vmx| I005: ToolsISO: Refreshing imageName for 'winxppro' (refreshCount=1, lastCount=1).
2021-01-13T09:06:33.586-06:00| vmx| I005: ToolsISO: open of C:\Program Files (x86)\VMware\VMware Workstation\isoimages_manifest.txt.sig failed: Could not find the file
2021-01-13T09:06:33.586-06:00| vmx| I005: ToolsISO: Unable to read signature file 'C:\Program Files (x86)\VMware\VMware Workstation\isoimages_manifest.txt.sig', ignoring.
2021-01-13T09:06:33.590-06:00| vmx| I005: ToolsISO: Updated cached value for imageName to 'winPreVista.iso'.
2021-01-13T09:06:33.590-06:00| vmx| I005: ToolsISO: Selected Tools ISO 'winPreVista.iso' for 'winxppro' guest.
2021-01-13T09:06:33.590-06:00| vmx| I005: TOOLS updated cached value for isoImageExists to 1.
2021-01-13T09:06:33.590-06:00| vmx| I005: VMXVmdb_SetToolsVersionStatus: status value set to 'noTools', 'noTools', install possible
2021-01-13T09:06:33.590-06:00| vmx| A000: ConfigDB: Setting toolsInstallManager.updateCounter = "5"
2021-01-13T09:06:33.606-06:00| vmx| A000: ConfigDB: Setting extendedConfigFile = "REDACTED.vmxf"
2021-01-13T09:06:33.617-06:00| vmx| A000: ConfigDB: Setting ide0:1.fileName = "auto detect"
2021-01-13T09:07:33.623-06:00| vmx| I005: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

Tags (2)
0 Kudos
1 Solution

Accepted Solutions
briangideon
Enthusiast
Enthusiast
Jump to solution

In case anyone runs across this problem I added the following line to the vmx file per support advice.

monitor_control.disable_apichv = "TRUE"

This resolves the crashing issue.

View solution in original post

0 Kudos
4 Replies
briangideon
Enthusiast
Enthusiast
Jump to solution

In case anyone runs across this problem I added the following line to the vmx file per support advice.

monitor_control.disable_apichv = "TRUE"

This resolves the crashing issue.

0 Kudos
jongwon
Contributor
Contributor
Jump to solution

Can I ask where is "monitor_control.disable_apichv = "TRUE" ?

I can`t find it in any files.

0 Kudos
jongwon
Contributor
Contributor
Jump to solution

Is the vmx file you methioned a vmware-vmx file?

But my vmware-vmx file is hex file..

How can I fix that file?

0 Kudos
scott28tt
VMware Employee
VMware Employee
Jump to solution

Look in the folder for the VM, there will be a file name_of_VM.vmx

It is a text file.

Make a copy of it before you amend it.

 


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

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