VirtualBox application error - memory could not be written

[raul1002]

I'm trying to spin up a virtual box machine (ver 5.0.8 ) using vagrant set up.Whenever vagrant is trying to spin up virtualbox machine , the VirtualBox runs into an application error of referenced memory , stating memory could not be overwritten.Post this vagrant goes into aborted state and exits out mentioning the below -

"==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'aborted' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue."

Attached snapshot of the error seen on VirtualBox .

Could you please help giving some pointers to what could be done to fix this ?

[Virtual Dave]

Hi, I'm getting a similar error. The version number reported in help>about is 5.0.10 r104061

The initial error message is shown below:

Capture.PNG (36.33 KiB) Viewed 1058 times

Subsequent error details are:

Failed to open a session for the virtual machine hawkeye.

The VM session was aborted.

Result Code: E_FAIL (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}

The log file for the VM is attached too.

I've tried the following with no luck:
* Uninstalling and reinstalling.
* Uninstalling and reinstalling version 5.0.8
* Uninstalling and removing all references to VirtualBox from the registry
* Removing memory modules
* Checking that virtualisation is enabled in the BIOS

I've found old posting referring to similar problems but with much earlier versions of Virtual Box but nothing referring to this version.

I did have a play around with vagrant which is the only thing I recall doing between this working and being completely broken. I've since removed vagrant from my machine.

The only other possible cause mentioned is that it might be the antivirus software which I have no control over. That said, my colleagues are able to run Virtualbox with no problems so I'm thinking this is unlikely.

The error is the same when starting any of the virtual machines and any new ones created.

Any help with this would be really appreciated.

Merry Christmas!