Hi,
I am trying to boot up a VM on my Windows PC, but I keep getting a "Blue Screen of Death". Typically, my PC blue screens right before I am even able to log into the VM, but sometimes I am able to login and then it blue screens briefly after that.
I have tried lowering the base memory down to 4 GB and the number of CPUs down to 2 in the system settings, but I am still getting the same issue. For reference, I've attached the VBox.log and VBox.png files in a zipped folder (the original 451KB exceeded the size limit).
Thanks in advance for any help provided!
- asr
Blue Screen on Windows Host when booting up VM
Blue Screen on Windows Host when booting up VM
- Attachments
-
- Compressed_Logs.zip
- (74.69 KiB) Downloaded 2 times
-
multiOS
- Volunteer
- Posts: 1227
- Joined: 14. Sep 2019, 16:51
- Primary OS: Mac OS X other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows, Linux, BSD
- Location: United Kingdom
Re: Blue Screen on Windows Host when booting up VM
This from the Log shows that Hyper-V is enabled:
For now, you need to completely disable Hyper-V if you want to run VirtualBox successfully. See: viewtopic.php?f=25&t=99390 for further help. If you really need to use Hyper-V and VirtualBox, then then the only current 'workaround' is to "Toggle" between having Hyper-V active when VirtualBox is not needed and inactive when you want to run VirtualBox, but that requires a reboot after each change.
Not good, as VirtualBox really needs access to VT-x to perform effectively.00:00:03.992465 ********************* End of CFGM dump **********************
00:00:03.992761 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:04.060137 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
For now, you need to completely disable Hyper-V if you want to run VirtualBox successfully. See: viewtopic.php?f=25&t=99390 for further help. If you really need to use Hyper-V and VirtualBox, then then the only current 'workaround' is to "Toggle" between having Hyper-V active when VirtualBox is not needed and inactive when you want to run VirtualBox, but that requires a reboot after each change.