BSOD on Win 10 Home Host

[Nihilistic_Saint]

I have started a course in Windows servers and I have to setup a Windows 2019 server and Windows 10 VM.

My problem is after setting up the VMs and giving the correct .ISO file, they give a blue screen or restart my PC when I try to start them for the first time and Install them.
BSOD Error: Machine Check Exception.

I feel like I've tried everything. Virtualization is on, my other VMs for a Linux course works fine. I have disabled fast startup, disabled EFI Secure boot, cleared all secure boot keys and ran a System File Check.

Since I have Windows 10 Home I don't meet the requirements for Hyper-V. My classmates also have Windows 10 Home but have had no problem with their virtual machines.

Any advice in the topic would be appreciated.
Thank you in advance!

[scottgus1]

Please right-click the guest in the main Virtualbox window's guest list, choose Show Log.

Search the far left tab's log for this text:

Attempting fall back to NEM

If you find it, Hyper-V is enabled. If you are still running 6.1.14 or earlier, update to 6.1.16, and try again.

If the 6.1.16 log still shows these words, Hyper-V needs to be disabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active).

If you don't find that text, save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.

[Nihilistic_Saint]

Thank you for the reply Scottgus1. I am running VirtualBox 6.1.18 and there was no "Attempting fallback to NEM" line of text in the log file. I'll upload the log file.

Server-2019-template.zip

Log file

(16.52 KiB) Downloaded 5 times

[scottgus1]

Virtualbox was installed in a non-default folder D:\VirtualBox. Many folks change the install folder in the incorrect idea that doing so makes the VMs also go on the other drive, which it doesn't. Other problems can happen too from the non-default install. Better to uninstall Virtualbox, reboot, then restart the installer with right-click-Run-As-Administrator, even if your account already has admin privileges, and install in the default C:\Program Files\Oracle\Virtualbox folder.

The Windows 2019 VM template may have a bug in it. Make a new VM, set the template to 2016 64-bit. In the new VM's System settings, Acceleration tab, set Paravirtualization Interface to Hyper-V (note this is not turning on Hyper-V in the Windows host). Give the VM 2 processors.

If this new VM has trouble, post a new log.

[Nihilistic_Saint]

I tried this and made a new template and attempted with the 2016 and 2019 server machines but both gave the same blue screen error (machine check exception)
I added a new log file.

[scottgus1]

It appears that all the recommended changes were made, good. The log stops cold at 24 seconds with no indication of a problem in the Virtualbox environment that I can see.

BSODs for machine check exception happen on real PCs too, and it's usually hardware trouble, according to my web-searching. Of course, all the 'hardware' is simulated in a VM... (except for the CPU itself).

A VM does stress parts of memory not commonly touched in a host PC. Try a host memory test. Try a different OS, like W10 or Ubuntu, to see if Virtualbox itself is having trouble. Try making new install media. Just guessing now, there's nothing I see to indicate the problem. We'll have to wait to see if a guru can pick out the problem in the posted logs.