topic Re: Exception 0xc0000005 (access violation) has occurred when starting VM in VMware Workstation Player Discussions

Exception 0xc0000005 (access violation) has occurred when starting VM

oscarre — Mon, 16 Oct 2023 12:38:01 GMT

hello. I can't open any virtualization of VWplayer. I get this error in all of them. can anyone help me? I attach the log file. thank you very much.

Re: Exception 0xc0000005 (access violation) has occurred when starting VM

RDPetruska — Mon, 16 Oct 2023 12:19:00 GMT

Host OS and version? Player version? What VM(s) are you trying to run? Have they run in the past?

The pertinent log file is "vmware.log" in the directory of the VM you are trying to run.

Re: Exception 0xc0000005 (access violation) has occurred when starting VM

oscarre — Mon, 16 Oct 2023 12:37:35 GMT

hello. the operating system is windows 10 prof updated. the player is VMware Workstation 17 Player. the virtual machines have worked before. thanks a lot for the help.

Re: Exception 0xc0000005 (access violation) has occurred when starting VM

oscarre — Mon, 23 Oct 2023 18:02:44 GMT

I already answered you.

Can you help me? Thank you

Re: Exception 0xc0000005 (access violation) has occurred when starting VM

RDPetruska — Mon, 23 Oct 2023 18:21:47 GMT

Well, *I* can't personally help, since I am using Workstation 16.1.2 - that was the last version which has features that my work requires working correctly. I asked because in order for anyone to help you, those were pieces of information needed.

Re: Exception 0xc0000005 (access violation) has occurred when starting VM

Kinnison — Tue, 24 Oct 2023 11:10:37 GMT

Hello,

I read your "log" rather quickly but there are various somewhat different errors like:

2023-10-16T09:10:25.835Z In(05)+ pen the disk 'D:\VMPlayer\W7EPL8v2.9_SEG_PROIN\W7EPL8-19.vmdk' or one of the snapshot disks it depends on.
2023-10-16T09:10:25.835Z In(05)+ vmx Module vmx Power on failure messages: The physical disk is already in use
2023-10-16T09:10:25.835Z In(05)+ vmx Cannot o'Disk' power on failed.
2023-10-16T09:10:25.835Z In(05)+ vmx Failed to start the virtual machine.

It's true that one problem doesn't exclude another but from what I read, that is, I fear that you are faced with a series of different problems of which there is no way of knowing which one arose first and as a consequence of what. You could try disabling the option related to the so-called "core isolation memory protection" and/or reduce the vCPU configured to one as a test and see what happens, although it's still just a guesswork.

Regards,
Ferdinando