virtualbox.org

Hello,

I update my old VirtualBox 4.3.12 to the last version 5.0.12 with the Extension Pack 5.0.12-104815.

At the install all my virtual OS was working well.

After a reboot of my PC everything change.
Impossible to start any virtual OS.
Sometimes I have a 0x80BB0005 error and sometimes nothing.

I looked the virtualbox 0x80BB0005 error on google but it seems to be very common error number for a lot of different problems.

I re-install the 4.3.12 version and all my virtual OS work's well.

I can start 8 virtual OS at the same times (I have 32giga of ram) without any crash.

In fact all version up to the 4.3.12 generate the same problems.

So why everything (except the shared folder on win10) work fine on 4.3.12 and nothing on 5.0.12 ??

Someone have an idea ?

Thanks

Best regard
Nexus

You report your host as Windows 7. Version 4.3.12 was the last version before a security hole on Windows hosts was plugged. You may be having issues with the security hardening. See the "Hardened Security" sticky at the top of the Windows Hosts forum.

Does your error mention a VboxStartup.log or VboxHardening.log? If so, post whichever is mentioned and we can see if you are hitting the hardening wall.

I re-install the version 5.0.12 to grab the error but I can't recreate it

Now it's different.

I need to start and crash 5 or 6 times a virtual OS to have this error :

The instruction at "0x063aa640" referenced memory at "0x063aa640", The memory could not be "written"

The number is each times different.
Wait the complete boot of the virtual OS and then click Ok on the error message.

After that, I can start any virtual OS and use it without any problem ??

Minimal information needed to be able to help

Give us the things mentioned above, please.

So here is the logs for the first 3 crashs then the boot with the error message 0x80BB00XXX and finally the normal boot

Any one have a idea about this ?


Thx

Nothing jumps out to me as suspect in the hardening logs posted. Maybe others can see something?
Meanwhile, try posting on the Bugtracker. When we get into "memory could not be written" stuff (a common Windows error box for any application that tries to access memory it is no longer allowed to access) the developers would probably have to get involved.

Nothing wrong in the hardening logs, but these are not the logs requested and not the one explained in the link. Please attach the VBox.log, not the hardening or startup one.