Opened 7 years ago
Last modified 7 years ago
#17433 new defect
VMMR0.r0 Bluescreen on HP Laptop Win10 v1709
| Reported by: | Patrick_BNC | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.2.4 |
| Keywords: | VMMR0, Bluescreen | Cc: | |
| Guest type: | other | Host type: | Windows |
Description
VMMR0.r0 ( VMMR0!VMMR0EntryFast+13de ) Virtual Box 5.2.4 (fresh install) Windows 10 v1709 10.0.16299.125 (Enterprise) (fresh install) HP EliteBook 840 G3 W4S08UC#ABL (bios and drivers updated 2018-01-08)
Starting a fresh VM on this configuration triggers a bluescreen. May also occur on HP Elite X2. Not on HP Z230. Computer available for remoting
Attachments (8)
Change History (14)
by , 7 years ago
| Attachment: | VM7-2018-01-08-13-48-19.log added |
|---|
comment:1 by , 7 years ago
Tested additional models:
No Issue on:
- HP Elitebook 820 G1
- HP Elitebook 840 G1
- HP Elitebook 840 G2 (Broadwell, i5-5300U)
- HP EliteBook Revolve 810 G2
- HP EliteBook Revolve 810 G3
- HP EliteDesk 800 G1
- HP EliteDesk 800 G2
- HP Compaq Elite 8300
- HP z230 Tower Workstation
Fails on
- HP Elite x2 1012 G1 (Skylake, Intel Core m5-6Y57)
- HP Elitebook 840 G3 (Skylake, Intel Core i5-6300U)
- HP z240 Tower Workstation (Skylake, Intel Core i7-6700U)
These newer models have Skylake processors. This seems to be a pattern.
comment:2 by , 7 years ago
After making 110% sure that Hyper-V is disabled in the Windows Features, 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...
comment:3 by , 7 years ago
Another interesting effect is that the dialog box on all failing computers only offer creating 32-bit Windows VMs. (see attachment)
Also, on the primary HP Elitebook 840 G3, this is a vanilla installation of Windows 10 v1709 Enterprise Edition. I'll test the Fast Boot shortly.
comment:4 by , 7 years ago
Please go thoroughly through the FAQ: I have a 64bit host, but can't install 64bit guests. This is becoming more and more a "Hyper-V" issue...
comment:5 by , 7 years ago
I've reviewed the FAQ.
The i5-6300U is 64-bit and supports VT-x https://ark.intel.com/products/88190/Intel-Core-i5-6300U-Processor-3M-Cache-up-to-3_00-GHz
The VT-x is enabled in the BIOS
Get-WmiObject -Namespace root\hp\instrumentedBIOS -Class HP_BIOSEnumeration -Recurse | Where {$PsItem.Name -like '*VTx*'} | Select Name,CurrentValue
Name CurrentValue
---- ------------
Virtualization Technology (VTx) Enable
Hyper-V is not checked in OptionalFeatures.exe. There is also no "Isolated User Mode Feature". Tested with "Get-WindowsOptionalFeature -Online | Where {$PsItem.FeatureName -like "*Hyper*"}" and all features are disabled.
Check gpedit.msc and "Turn on Virtualization Based Security" is not configured. Device Guard and Credential Guard should not be enabled. Since this is not joined to a domain I did not check rsop.msc
Windows Defender is the only antivirus.
comment:6 by , 7 years ago
The "Hyper-V manager" may not be installed, but Hyper-V may be in use. Start uninstalling things that you do not need. Start with all the HP assistants, they're useless crapware. Next the B&O thing, DTSConfig, and pretty much all the "helpers". One of them is the culprit.
The articles I gave you are supposed to give you ideas to try, not to pinpoint the solution for you. Only you can do that...
VBoxHardening.log