Virtualbox causes SYSTEM_SERVICE_EXCEPTION on Win10

[Nayz]

How to Reproduce

While trying to restart a VM with a saved state computer turns off and a blue screen shows the SYSTEM_SERVICE_EXCEPTION message then it restarts.

System Information

I am running: VirtualBox VM 5.0.17 r106155 win.amd64 Windows 10 DMI Product Name: Dell Precision M3800 Host RAM: 16286MB total, 12942MB available Package type: WINDOWS_64BITS_GENERIC

Enabled Plugins

No plugins installed

[Nayz]

Log

[Frank Mehnert]

For reporting BSOD, please provide a kernel dump (scroll down to the Windows part). Otherwise there is nothing we can do.

[Well]

mini dump for 106471 on win10

[Well]

Replying to frank:

For reporting BSOD, please provide a kernel dump (scroll down to the Windows part). Otherwise there is nothing we can do.

I've attached the kernel dump file(using the least test build 106471), pls help to analyze this blue screen problem, thanks!

[Frank Mehnert]

Still relevant with the most recent VBox 5.0.17 Windows test build?

[Well]

Replying to frank:

Still relevant with the most recent VBox 5.0.17 Windows test build?

Yes, I've tried the today's latest test version, blue screen still occurred.

[Frank Mehnert]

Is there a VBox.log file generated? If so, please attach it. Thank you!

[amedvedev]

Thank you for published kernel dump. We got some useful information from it. For further analyze we need additional info, so could you reproduce the issue and collect a pair of kernel dumps again? Thank you!

[Frank Mehnert]

And again, please don't forget the corrsponding VBox.log file!

According to the initial description, this BSOD does only happen if you start a VM from a saved state (ie not if you start a VM normally). Could you confirm that?

[Well]

blue screen win10 14316 within VB 106583

[Well]

Replying to frank:

And again, please don't forget the corrsponding VBox.log file!

According to the initial description, this BSOD does only happen if you start a VM from a saved state (ie not if you start a VM normally). Could you confirm that?

No, my VM was closed before, not a saved status.

[Frank Mehnert]

Could you try again and re-upload the new VBox.log file? The current VBox.log file is scrambled. It contains only a few useful lines. Maybe it was not correctly written due to the BSOD. Thanks!

[Frank Mehnert]

Thanks. VBoxHardening.log looks much better, VBox.log still cut ... :-(

[Frank Mehnert]

Another question: Do you have Hyper-V installed and active? Try to disable it: See for instance ​here.

[Well]

Replying to frank:

Another question: Do you have Hyper-V installed and active? Try to disable it: See for instance ​here.

Yes, after Hvper-V is disabled, the Virtual Box is well now...

[Frank Mehnert]

Could you provide a VBox.log file for your working VM session? Also, could you do another experiment? Please disable VT-x/AMD-V for your VM (VM settings / System / Acceleration) and try to start the VM. The resulting VBox.log file would be interesting for us as well. Thank you!

[Well]

Lates logs

[Well]

Latest logs attached, please analyse, thanks. After disable VT-X, the guest system reboot loop, seems that it has processor driver problem, but it wouldn't cause my win 10 blue screen.

[iguana007]

I am facing same issue, BUT disabling of Hyper-V did not resolve it. I always get BSOD, when starting virtual box and VM settings / System / Acceleration is disabled, so I cannot change anything there. I am running version: Version 5.1.18 r114002 (Qt5.6.2)

[Bwavo Bunny]

* This is STILL an issue in the latest builds. Worse yet, turning off Hyper V seems to do nothing at all.

Docker managed to ruin my work machine's Windows 10 install. :C

[Pesoen]

i have this problem as well.. always does bluescreen, no matter what i try to do, and how i set the settings. going to try turning off Hyper-V, if this still fails, i am gonna try another virtual machine software.

[Bobk000001]

I also have this problem. Have not had to run my VM's in a few weeks, go to run today and BSOD in latest Win 10. Removed Hyper V. Still happening. !?!??!??

[yena]

i can confirm that this is still an issue its mind-blowing that you didnt fix that already for more then a year just mind-blowing.

[Klaus Espenlaub]

What's mind-blowing about this? None of our Windows 10 install ever showed such problems. Also there are rather few reporters of this issue, so it's likely a rare, config specific problem. This makes it next to impossible for us to debug the root cause and fix it.

It's still likely to have something to do with an incompletely disabled Hyper-V (which is extremely difficult to detect, as Microsoft apparently decided not to remove the hardware virtualization support from the CPUID report in the root partition).

[DeKi]

Would be great to have a warning message in VirtualBox with a hint how to deactivate Hyper-V.

[DeKi]

Ok this was already requested in #16801

[MrMubi]

i had the same issue on windows 10 x64 surfacebook pro 2. My Virtual Box was working fine but then i started getting this blue screen error after windows update. i noticed x64 bit option was gone from virtual box while creating new vm. i simply followed steps here and my problem was solved ​https://kb.vmware.com/s/article/2146361

[terriblefire]

I found that AVAST antivirus has a virtualization mode that causes this issue with Ryzen CPUs.

​https://community.amd.com/thread/233420

"In some antivirus softwares, there is virtualisation fonctionnality. disable it and it should work. I searched for hours searching to fix it, I had SYSTEM_SERVICE_EXCEPTION and KMODE_EXCEPTION_NOT_HANDLED bsod, checked everything in bios, did a lot of tricks. I uninstalled Avast and it worked, but you can also disable virtualisation in avast. Also disable completely HYPER-V fonctionnality by going to Add Remove Programs the Add Remove Windows Functionnalities."

Disabling the option has stopped the BSODs so far.

[Rudion]

Yap, I also have this BSOD issue because of avast. But because I still need it, I just temporarily disable protection, 10 minute, or until restart. Then virtual box run just fine :)