VMware Communities
phil_mc
Contributor
Contributor
Jump to solution

Workstation 15 Pro - Exception 0xc0000005 (access violation) has occurred

I've been running Workstation 15.5.7 for a little while now on Win 10 Pro 64, however I've found one of my XP VMs won't startup and displays the error "Exception 0xc0000005 (access violation) has occurred".

I've tried disabling the "Accelerate 3D Graphics" from VM Display settings

I've also tried copying the VM to another disk drive and running it from there, but still the same error.

Log file attached.

My other XP VMs work ok, just this one is giving problems. 

thanks in advance to anyone who can offer any suggestions...

0 Kudos
1 Solution

Accepted Solutions
phil_mc
Contributor
Contributor
Jump to solution

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

monitor_control.disable_apichv = "TRUE"

This resolves the crashing issue.

https://communities.vmware.com/t5/VMware-Workstation-Pro/Upgraded-to-16-and-now-WinXP-won-t-boot/m-p...

 

View solution in original post

4 Replies
umarzuki
Enthusiast
Enthusiast
Jump to solution

How's your RAM usage during that error?

Tags (1)
phil_mc
Contributor
Contributor
Jump to solution

Hi Umarzuki, I've just tried after a re-boot and with no other apps running.

Task manager showed memory of: "6 / 31.8 GB (19%)"

still same error when trying to start this VM

0 Kudos
phil_mc
Contributor
Contributor
Jump to solution

extract from vmware.log

2021-06-01T12:27:09.245+10:00| vcpu-0| I005: BUSLOGIC: Store HAL[16] = 0xffff
2021-06-01T12:27:09.245+10:00| vcpu-0| I005: BUSLOGIC: Store HAL[18] = 0xfe01
2021-06-01T12:27:09.245+10:00| vcpu-0| I005: BUSLOGIC: Store HAL[16] = 0xffff
2021-06-01T12:27:09.245+10:00| vcpu-0| I005: BUSLOGIC: Store HAL[18] = 0xfe01
2021-06-01T12:27:09.394+10:00| vcpu-0| I005: DDB: "longContentID" = "7265abad1f99f7cb29894ae6118ee1b6" (was "9fadf123000e7dfa1cbdc24bd7b9c4ed")
2021-06-01T12:27:11.194+10:00| vcpu-0| W003: ----Win32 exception detected, exceptionCode 0xc0000005 (access violation)----
2021-06-01T12:27:11.194+10:00| vcpu-0| W003: ExceptionAddress 0x7ff627ac3434 eflags 0x00010216
2021-06-01T12:27:11.194+10:00| vcpu-0| W003: rwFlags 0x1 badAddr 0xf0
2021-06-01T12:27:11.194+10:00| vcpu-0| W003: rax 0 rbx 0x1e9ff543ef0 rcx 0xf
2021-06-01T12:27:11.194+10:00| vcpu-0| W003: rdx 0 rsi 0x80 rdi 0x1e9ff543f70
2021-06-01T12:27:11.194+10:00| vcpu-0| W003: r8 0x1e r9 0x16288 r10 0
2021-06-01T12:27:11.194+10:00| vcpu-0| W003: r11 0 r12 0 r13 0

0 Kudos
phil_mc
Contributor
Contributor
Jump to solution

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

monitor_control.disable_apichv = "TRUE"

This resolves the crashing issue.

https://communities.vmware.com/t5/VMware-Workstation-Pro/Upgraded-to-16-and-now-WinXP-won-t-boot/m-p...