5.2 causes blue screen of death on windows 10

[silvermangb]

I upgraded from 5.1.30 to 5.2 to use my ubuntu 17.04 and 17.10 machines. I had multiple BSOD per hour until I reverted to 5.1.30. No BSOD since then.

I have a Surface Pro 4 with the latest Windows 10 updates.

Sorry, I could not capture the error code or QR on the blue screen before the PC rebooted.

[silvermangb]

Blue Screen of Death

[silvermangb]

I was able to capture one BSOD. However, I saw other stop codes, as well.

[YaakoVB]

I also get a BSOD with 5.2.0, and Windows 10 message "System Service Exception". My computer is a desktop Intel Core i5-4590 CPU @ 3.30GHz with 8 GB RAM. The OS is Windows 10 Pro, Version 1703, OS Build 15063.674, 64-bit.

[Socratis]

Besides making 110% sure that Hyper-V is disabled in the settings, you might want to ​make sure that Fast Boot is disabled and do a cold boot (i.e. shut down the host for a minute or two). You also must make sure that nothing else is using Hyper-V, things like antivirus, debuggers, emulators, etc. Check out the article ​Diagnosing VirtualBox Hardening Issues to get some ideas.

See if that helps...

[mtpultz]

I found the only way to solve this was to step back to 5.1.30. Disabling Hyper-V with v5.2.x wasn't working I still got BSOD. Also, side note having to turn Hyper-V on/off when switching between Vagrant and Docker is really annoying since it requires a restart.