VirtualBox causes host BSOD starting VM under Windows 10. Hyper-V is off

▲
8
▼

I have a freshly-installed 64-bit Windows 10 system, with VirtualBox installed and a CentOS 7.0 VM image. Whenever I try to start the VM, Windows BSODs with SYSTEM_SERVICE_EXCEPTION, code 0x0000003b.

After extensive (and frustrating) Googling, I have found many references to this being caused by Windows 10's Hyper-V virtualisation, so I have turned this off via Windows Features; and ensured that no Hyper-V services are running, or set to run on startup. This has not prevented the BSODs.

This exact same setup, including hardware, but with Win 7 32-bit instead of Win 10 64-bit, was working perfectly until IT re-imaged my machine to Windows 10.

Below is the output of VBox.log, although it doesn't look like anything relevant is in it.

VirtualBox VM 5.0.40 r115130 win.amd64 (Apr 28 2017 19:55:07) release log
00:00:00.308913 Log opened 2017-07-10T13:36:10.933562500Z
00:00:00.308914 Build Type: release
00:00:00.308917 OS Product: Windows 10
00:00:00.308918 OS Release: 10.0.14393
00:00:00.308918 OS Service Pack: 
00:00:00.383912 DMI Product Name: B85M-E
00:00:00.386322 DMI Product Version:  
00:00:00.386327 Host RAM: 8063MB total, 3856MB available
00:00:00.386329 Executable: C:\Program Files\Oracle\VirtualBox\VBoxHeadless.exe
00:00:00.386329 Process ID: 9952
00:00:00.386330 Package type: WINDOWS_64BITS_GENERIC
00:00:00.389754 Installed Extension Packs:
00:00:00.389787   None installed!

Can anyone suggest a way forward?

Edit: Minidump available here, for identical failure except on VirtualBox v 5.1.22.

windows-10
virtualbox
bsod
asked on Super User Jul 10, 2017 by Chowlett • edited Jul 10, 2017 by Chowlett

5 Answers

▲
8
▼

As it turns out, disabling Hyper-V is not enough. There is another Windows feature, called Virtualization Based Security, that employs Hyper-V. You need to disable that as well.

All I needed to do was to change one registry key and reboot:

Use regedit to set

HKEY_LOCAL_MACHINE\SYSTEM\Software\CurrentControlSet\Control\DeviceGuard

to 0, and reboot.

There is a nice description of Device Guard / Virtualization Based Security here: Windows 10 Device Guard and Credential Guard Demystified.

answered on Super User Oct 16, 2017 by n0ha
▲
3
▼

Have this issue on the new Windows 10 Fall Creator Update (1709) build 16299 and Virtual Box. Both VirtualBox versions were tested also: - Version 5.1.26 r117224 (Qt5.6.2) - Version 5.2.2 r119230 (Qt5.6.2) HyperV features are NOT deployed but by default, MSINFO32 shows up "Hypervisor enforced Code Integrity" on the new Fall Creator Update build.

Result from MSINFO32.EXE enter image description here

It looks like that this feature will lead VirtualBox to a BSOD.

You lucky guys, there is a fast and dirty way to fix this: DISABLE SECURE BOOT.

(Just to test!!! your security department won't like it) If I get a clean solution I'll post it ;-)

Cheers

answered on Super User Dec 5, 2017 by Laurent Vonau • edited Dec 5, 2017 by Toto
▲
0
▼

we can't fix this because Windbg shows the Virtualbox driver as cause, wich tries to execute a command that is not allowed (Privileged instruction):

EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - Privileged instruction.

00 nt!KeBugCheckEx
01 nt!KiBugCheckDispatch
02 nt!KiSystemServiceHandler
03 nt!RtlpExecuteHandlerForException
04 nt!RtlDispatchException
05 nt!KiDispatchException
06 nt!KiExceptionDispatch
07 nt!KiGeneralProtectionFault
08 0x0
09 0x0
0a 0x0
0b VMMR0

    Image path: \??\C:\Program Files\Oracle\VirtualBox\VMMR0.r0
    Image name: VMMR0.r0
    Browse all global symbols  functions  data
    Timestamp:        Fri Apr 28 17:37:03 2017

try lastest testbuilds and if you still get the issue report it to the developers in their bug tracker .

answered on Super User Jul 10, 2017 by magicandre1981
▲
0
▼

On this Windows 10 Enterprise ("10.0.16299 Build 16299") machine in addition to n0ha's answer I had to disable Device Guard/Credential Guard:

On the host operating system, click Start > Run, type gpedit.msc, and click Ok. The Local group Policy Editor opens.

Go to Local Computer Policy > Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization Based Security.

Select Disabled.

Doing both re-enabled the "Acceleration" tab and stopped the HYPERVISOR_ERROR BSODs on VM start.

answered on Super User Aug 27, 2018 by genpfault
▲
0
▼

It seems a recent update of Avast causes problems with virtualization (you can check by disabling it for 10 mn, then trying to start up a VM).

To fix, go into Avast settings, then in "problems resolution" disable "enable hardware virtualization assistance" (or something like that).

answered on Super User Jul 27, 2019 by Zezombye

User contributions licensed under CC BY-SA 3.0