The instruction at 0x12465ad0 referenced memory at 0x12465ad0. The memory could not be written.

[Josef Murcek]

I'm using VirtualBox 5.0.16 and getting this strange error all the time. VirtualBox let me create a new virtual machine, but when I tried to mount an ISO file, it will immediately crash with read memory access (see Error.jpg). After clickin' on OK button, I'll get another one (Error2.jpg). My colleague have the same problem, we both are using Dell Precision laptops with integrated NVIDIA Quadro graphic card, for example, I have a K3100M type. But my drivers are up-to-date (according to Dell update software) and 3D acceleration is turned off. Can you please look on this issue and tell me what should I do for fixing it?

P.S: This ticket has been created as a new, original form is [here (https://www.virtualbox.org/ticket/13580#comment:30)].

[Bernie]

I just started getting this error last week after not using Virtual Box for a few weeks. I dropped my VMs and tried to recreate them getting this same error with different memory locations. I then upgraded to 5.0.16 and continue to get the error. Has anyone found a work around.

[Frank Mehnert]

Same problem as #14907. Still investigating.

[Josef Murcek]

Replying to frank:

Same problem as #14907. Still investigating.

Strange thing is that we have also McAfee OAS installed, but I tried to run VMs with McAfee disabled and still have the same problem.

[Mihai Hanor]

Disabling it using its GUI might not be enough. Try to uninstall it. After uninstalling it, also check for remnants, like drivers and services. To identify them, you can use ​Autoruns

[Josef Murcek]

Replying to mhanor:

Disabling it using its GUI might not be enough. Try to uninstall it. After uninstalling it, also check for remnants, like drivers and services. To identify them, you can use ​Autoruns

Uninstalling McAfee OAS is forbidden by company rules, so I can't do that :/

[Frank Mehnert]

Which version of McAfee OAS is this (exact version number please)?

[BenjaHex]

Wrote a comment at #14363 that could eventually also relate to your problem.

[Josef Murcek]

I've just downloaded the latest version of VirtualBox (v5.1.2) and it seems that this problem is fixed, because everything works fine now!