I'm getting BSOD IRQL_NOT_LESS_OR_EQUAL on my Windows 10 VM. I don't get it on my Server2016 VM so it's odd.
I searched for similar issues but haven't found a solution to it.
I attached my log. I deleted a portion of the log so it was under 128kib
Thanks.
Windows 10 VM BSOD IRQL_NOT_LESS_OR_EQUAL
Windows 10 VM BSOD IRQL_NOT_LESS_OR_EQUAL
- Attachments
-
- Windows 10 v2 no crash hopefully-2022-06-13-16-27-14.log
- (122.23 KiB) Downloaded 3 times
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: Windows 10 VM BSOD IRQL_NOT_LESS_OR_EQUAL
Such is not necessary. Zipped logs fit.Nickhey wrote:I deleted a portion of the log so it was under 128kib
Fortunately, the part you deleted didn't take the parts needed to diagnose the problem.
First, try setting the VM to two processors.
If that doesn't help, try upgrading to the 6.1.35 test build. Save the test build installer until you update again later. You'll need it if your host's MSI installation database goes south (they do) and the installer will not be available for download after the next even-number version gets released.
If that doesn't help, Hyper-V is enabled. See HMR3Init: Attempting fall back to NEM (Hyper-V is active)
Re: Windows 10 VM BSOD IRQL_NOT_LESS_OR_EQUAL
Switching to two processors made it very slow.
What worked, at least so far, is using the test build.
Thank you scottgus1
What worked, at least so far, is using the test build.
Thank you scottgus1
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Windows 10 VM BSOD IRQL_NOT_LESS_OR_EQUAL
What would work even better is disabling Hyper-v, per Scott's second link.