Opened 7 years ago
#16895 new defect
Host BSOD when starting any VM on Windows 10 host, without Hyper-V
| Reported by: | Chowlett | Owned by: | |
|---|---|---|---|
| Component: | VM control | Version: | VirtualBox 5.1.22 |
| Keywords: | BSOD crash | Cc: | |
| Guest type: | all | Host type: | Windows |
Description
I have a largely-clean Windows 10 system with VirtualBox installed. When I attempt to start any VM (including a Centos 7.0 box, and a basic DOS VM), Windows 10 BSODs with SYSTEM_SERVICE_EXCEPTION, Bug Check Code 0x0000003b.
I found multiple references to this being a conflict with Windows 10's own Hyper-V Virtualisation, so I have disabled the Hyper-V services and removed the feature from Windows; the BSOD still happens. I have also updated host graphics and audio drivers (just in case). I have tested VirtualBox versions 5.1.22 (last stable), preview 5.1.23, and 5.0.40 (which is known-good in my department).
Attached are the VBox.log, VBoxHardening.log for both the DOS and Centos systems, and a representative minidump. Analysis of the minidump on Superuser.com (https://superuser.com/a/1228520/82337) suggests that VMMR0.r0 has attempted to execute a Privileged Instruction.
I'm not sure if any further diagnostics would be helpful here, but please ask and I will attempt to get them for you.
DOS VM VBox log