virtualbox.org

Hi everyone,

First time poster here so I apologize if this is not the right place to be.

I am currently running Windows 11 Version 22H2 (OS Build 22621.1) and running VirtualBox Version 6.1.34r150636 (Qt5.6.2). The hardware on the system is running a AMD Ryzen 3900X 12-core CPU and 32GB of RAM, which I feel should be plenty for just two VMs.

Within VirtualBox, I am running two VMs -- one Windows Server 2019 (21H2 [OS Build 20348.169]) and Windows 10 Enterprise (Version 21H2 OS Build 19044.1288). I have been running into several problems with both of them, but I seem to have gotten the Server VM stable for time being.

Windows 10 Enterprise:
This VM is also running poorly - significant input delay. I have only been able to actually sign in and get into the desktop once since creating this VM. I was also getting the IRQL_NOT_LESS_OR_EQUAL error. So, I tried deleting the VM and starting from scratch. I have also included 4GB of RAM, 1 cpu core. The VM will reboot and I can get to the sign in screen. Once I enter my password and it starts signing in, that is when I get the above error IRQL_NOT_LESS_OR_EQUAL. Sometimes I get into the desktop for a few minutes and navigate around but it will eventually go back to the same BSOD error. I tried adding an additional cpu core and it will not boot up to the login screen. I reverted back to allocating a single core and now I am back at the login screen and sometimes getting into the desktop. Any help would be greatly appreciated. I have attached a ZIP file for the IRQL error

You have a common problem - so common there are lots of posts about it.

Here are the telltale lines in your log.
See this one. viewtopic.php?f=25&t=99390

If you need Hyper-V to be on, try putting two processors in the VM.

Thanks you two!

I searched up the NEM: AMD-V is not available and quickly led me to another post on this forum.

I followed the steps in this post: HMR3Init: Attempting fall back to NEM (Hyper-V is active)
[Text copied from FAQ post deleted]

After doing the above steps, the performance has significantly improved. I can actually use both of my VMs and are responding as expected. So far, no IRQL error have populated by will continue to monitor in case there is something else going on in the background but so far it's promising.

It's been a few days and no more errors. Both VMs have been running beautifully.

Thanks again.