VirtualBox has now twice caused a BSOD on my host operating system Windows 7. The first time I was running VirtualPC so thought the two Virtual Systems together might have caused the issue, but this time it was just VirtualBox.

I didn't get the error code.

Has anyone had similar problems?

  • This sounds like a bug with Virtual Box have you reported it to Oracle? – Ramhound Aug 3 '12 at 17:08
  • Can you find the BSOD dump files and check for anything related to this event? – Darius Aug 3 '12 at 17:14
  • There is not enough details to give you an accurate answer: what is the Bug Check Code (i.e.: Stop 0X blah blah blah)? – climenole Aug 4 '12 at 17:38

What is the configuration of your Win-7 machine? VirtualBox is a huge resource drainer. Even with 4GB RAM and a 3.2 ghz dual-core, it lags when I try to run anything on the host and guest at the same time. Also, check your onboard graphics-memory, and read this manual carefully for anything that might apply to your architecture:



I tried all of the above mentioned answers, none of them worked.

So I found out the Hyper-V in windows 7 and higher (in my case it is windows 10) is the culprit!

I disabled the Hyper-V services as below and the issue is fixed!

Follow the following steps:

  1. Find the "Turn windows features on or off" from control panel (or type windows features in windows search box)

  2. Uncheck the "Hyper-V" feature from the list

turn Windows features on or off window screenshot

  • 3
    +1. Works for me on Windows 10 (winver 1607) and VirtualBox 5.1.26 – honzakuzel1989 Sep 7 '17 at 5:50
  • 3
    +1, this saved my life on Windows 10. I am running Docker (that uses Hyper-V) and Oracle VM VirtualBox and they don't fit together well. Is there anywhere we could report this as an issue so that future generations wouldn't have to suffer this pain? – eddyP23 Sep 27 '17 at 9:12
  • 1
    This solution fixed my VirtualBox 5.2 on Windows 10. Thanks – Strabek Dec 11 '17 at 14:23
  • I have the same problem with VBox causing an occasional BSOD, but in my case the Hyper-V is NOT installed (already unchecked in the list of features, like suggested here). So, I don't know what I am supposed to do, in light of the fact that I cannot work without the VBox for the docker machine I need for the current local project run... – TheCuBeMan Sep 5 '18 at 12:01

This happens many times, especially when running more than one virtual machine at a time. I.e. two Linux virtual machines, etc.

I looked at the dumps and it's definitely Virtual Box (at least as recent as 4.3.4). I've see it with single as well as multiple Windows 7 VMS also.

Doesn't occur frequently, and I prefer Vbox over VMWare, so I continue to use. I usually just restart and everything is fine.


In particular, VirtualBox SATA drivers are causing BSOD, so default to IDE.


None of the above has worked for me. However, this simple trick allowed me to run the troubled VM:

  1. Run the machine in headless start mode (Go to start and then choose headless start from the drop-down list)
  2. After the machine cleans the cache and shows the login screen at the little window of VBox page, click on show machine (the green arrow in the main menu).

Make sure to backup your important files :)


Another option is to try Hyper-V itself. Search for Hyper-V Manager. Hyper-V Manager

  • Could you say why it is better? – Toto Nov 5 '17 at 19:48

In my case the other VMs had created a virtual switch on the nic driver.

I went and removed all the non-standard settings on the adapter and let the OS auto-detect it and configure as if it was a new start up. (After disabling Hyper-V and Virtual Box which had been set up natively on the PC.)

Then I was able to fire up vagrant and get things to work. I was using Vagrant 1.9.6 and VBox 5.1.28.

Hope this helps someone else.

Your Answer

By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.