BSOD "Driver IRQL Not Less or Equal" Win10 Home Insider

[chross]

Hi,
I'm trying to load up an older VM after Windows Insider did update (running Windows 10 Home Insider Preview 17074.rs_prerelease.180106-2256 on a DELL XPS 15 9560). Also, I went to VirtualBox 5.2.4 r119785 (Qt5.6.2).
Everytime I try to load my VM, I will get a BSOD with the message "Driver IRQL Not Less or Equal". I am attaching the VBox.log and a MiniDump file. Hope someone can help. I tried disabling the VM support for USB and Networking as I believed them to be the culprit. However, nothing changed and VirtualBox became unusable for me now.

[socratis]

If you want to use the latest version for your host/guests, you should also consider doing the same for VirtualBox. You should try the latest test builds, especially with all the Spectre/Meltdown patches coming in from all sides. Not sure if it's going to work or not, but you should at least try it out...

[chross]

Hi,
I have tried the latest builds and I am receiving the same error again.
Must be some kind of mismatch between the kernel an some vbox drivers, I guess.

[Jack Yan]

Chross, can I ask if you have tried to run driver verifier on your Windows machine?

I began getting the same error since Windows 10 Creators fall update but usually when Explorer was accessed (not always, but I would average three to six BSODs daily since mid-December). While I had some other outdated drivers that driver verifier identified, which I since deleted, verifier eventually identified vboxdrv.sys as being the culprit. I’d be interested to know if your PC comes up with the same, as it would then suggest there is some incompatibility.

Previous Windows 10 updates were fine: this is the only one that BSODs so frequently.

[socratis]

You should be checking the "VirtualBox success reports on Windows 10 Insider builds" thread, all the pages. According to the (really dedicated) user 'Jacob Klein' who's been testing each and every Win10 insider build, Windows 10 Build 17074 (and even higher) has no problem with VirtualBox v5.1.32 Build 120294. I would imagine that the latest 5.2.x would behave the same.

[Jack Yan]

Jacob defines ‘works’ as, in his words:

- Can launch VirtualBox VM Manager
- Can start any VM (new or old)

I haven’t any disagreement with him on this. I can launch the manager and I can start any VM.

I’m simply trying to find out if Chross and I have anything in common with our PCs that is causing this exact BSOD error message.

[chross]

I have other issues with my DELL 9560 as well (micro stuttering of my MX2 Anywhere mouse as well as recovery problems from sleep mode). I've read on a Dell forum that it all is due to the Killer wifi card installed and I am now looking to getting an exchange. I will report back when I receive the Intel wifi card.