VMware Communities
antslarson
Contributor
Contributor
‎10-15-2007 08:11 AM

VMware Workstation unrecoverable error (vmui) Exception 0xc0000005 (access violation) has occurred

VMware Workstation unrecoverable error (vmui)

Exception 0xc0000005 (access violation) has occurred.

This occurred after I had created a snapshot in VMWare Workstation 6.0.1 build-55017 and restarted the vmware session. The vmware session is Windows XP Pro.

Now anytime I attempt to start this VMWare session the above exception error occurs and the session crashes.

I have attached the log file, core file & the "Collect Support Data" file.

vmware-Anthony Larson-2720.log
vmware-2720.dmp
vmsupport-10-15-2007-11-10.zip
Reply
0 Kudos
8 Replies
continuum
Immortal
Immortal
‎10-15-2007 09:06 AM

Yes - i get this often too. Don't know why.

Anyway - do you have snapshots ?

Remove any *.vmem files and *nvram files and try again


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
antslarson
Contributor
Contributor
‎10-15-2007 09:32 AM

Yes, I have one snapshot, which I created right before this issue occurred.

Reply
0 Kudos
antslarson
Contributor
Contributor
‎10-15-2007 09:40 AM

I have moved the *.vmem and nvram files to a temporary folder, just in case I need them later, however vmware workstation is still giving the same "exception 0xc0000005 access violation" error.

Reply
0 Kudos
continuum
Immortal
Immortal
‎10-15-2007 10:00 AM

Have you rebooted ?

That error usually disappears after some fiddling


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
antslarson
Contributor
Contributor
‎10-15-2007 10:28 AM

Unfortunately rebooting my pc hasn't resolved this issue.

One thing I have noticed is that the OldWorkPCConvert-0.vmdk non-working vmware session file is 0 KB and that in my other working VM's it's 2 KB in size.

Reply
0 Kudos
antslarson
Contributor
Contributor
‎11-10-2007 05:09 PM

I called VMWare Support and they were able to resolve this issue with an "unofficial hack/fix".

It took many hours, but they got it to work.

Cudo's to VMWare Support!

Reply
0 Kudos
columbiasts1
Contributor
Contributor
‎11-16-2007 06:58 AM

Could you possibly post the fix that VMware implemented for you.

Reply
0 Kudos
antslarson
Contributor
Contributor
‎05-14-2008 08:15 PM

From VMWare Support:

Parent virtual disk had been modified and couldn't access snapshot.

Used dsfok to write out the baseb vmdk and snapshot vmdk to txt file.

Modified the Parent CID of the snapshot vmdk txt file to point to the CID of the base vmdk.

Wrote in the txt file to the snapshot vmdk. Powered on the VM and we are able to access the snapshot vmdk with the most recent data.

Recommend using Converter for cleanup to remove all the snapshot files since snapshot manager does not recognize the snapshot.

Reply
0 Kudos