virtualbox.org

Have you tried VirtualBox 4.3.28/4.3.30?

Yes, I've run every build of VirtualBox since, 4.2.28 and have had the same problem.

You need to launch Process Explorer as Administrator.

I have no idea if that blog is correct in its description of Hyper-v, but it bears no resemblance to what I know about VirtualBox. Frankly it doesn't seem to be discussing CPU cores at all, but instead the discussion seems more relevant to process scheduling, somewhat similar to the CPU cap feature VBox provides.

You need to launch Process Explorer as Administrator.

D'oh. Of course. Sorry. Please find attached the mini-dump from the lowest level of the VirtualBox service process tree.

You probably need to upgrade the Intel video drivers. Check for a newer version on intel.com

You probably need to upgrade the Intel video drivers. Check for a newer version on intel.com

Well I was about to tell you I already did this, as I updated the video drivers a week ago (as I stated in my original post). However, it turns out new drivers were released over the weekend. Installing them was a bit of a PITA, as the intel installer refused because my current drivers come from Dell (dell hasn't repackaged this release yet), and then even trying manually windows insisted that my drivers were up to date (they weren't, the build was dated March), so I had to force them with the old "Have Disk" method.

Unfortuanately, although the addresses on the error have changed, I still get the same error:

"The instruction at 0xb14da005 referenced memory at 0xcae67468. The memory could not be read. Click OK to terminate the program"

Attached are my logs and dumps, but I presume this means that 3D acceleration just isn't compatible with my Intel graphics chipset? This is a real shame because all the latest linux desktop environments are moving towards requiring acceleration (or requiring in order to not continually hammer the CPU)

An unhandled exception occurs while one VirtualBox process thread executes code in the Intel OpenGL client driver. It's impossible to say who's at fault, VirtualBox or the Intel OpenGL client driver.

Hi all,

I just wanted to add another case where I have this issue as well. I am running 3 monitors and 1 is AMD and the other two are on the Intel HD 4600. I have a slight workaround where I can start the VM on the AMD monitor and let it full boot and login. Then I can move the VM Window to any of the monitors on the Intel graphics adapter. I noticed that if I don't click OK to the error the guest will still boot but missing taskbar so you can't do much. I tested with Mint and Ubuntu.

Here is my version of the error

Update: If I run Firefox then it crashes again. Darn. I will have to try and switch another monitor over to the AMD card.

Hi all,

I had a similar issue showing up. I run a Xubuntu guest virtual machine on a Windows 10 64 bit host. I kept getting the error when launching firefox within the guest:
After noting above that it may have to do with the Intel graphics drivers (some noted above that some AMD drivers have been suspect in the past, but I updated mine and this issue persisted), I realized that I run 1 monitor on my CPU's itegrated graphics, and I run the other 2 on my dedicated AMD graphics card. I also noted that I had been launching/fullscreening the VM guest on the Intel driven monitor. Moving the VM fullscreened to another monitor seems to make the problem go away.

I apologize that I haven't done more work than this to find out which Intel drivers work - I'm just going to not use my intel driven monitor for now.

Good luck!