VBox 7.0.16 Page fault in nonpaged area

[Simple07]

After upgrading from VirtualBox 7.0.15-162549 to VirtualBox 7.0.16-162802, I am getting a BSoD in Windows 10 Host when trying to run Windows 11 Build 26100.1

The Error message: Page fault in nonpaged area
The file: VBoxNetLwf.sys

This problem does not happen when running Win XP or Win 7 or Linux. It only happens when running Windows 11 host only. When reverting to VirtualBox 7.0.15-162549 all is fine, but when updating back to 7.0.16-162802 Win10 host crashes again.

Update: Reinstalling Windows 11 b26100 afresh, with the very same settings, did not sort it. It still crashes when a Bridged Adapter is attached to my Intel WiFi 6E AX210 Adapter.

[kabu]

I have created new bug report
https://www.virtualbox.org/ticket/22045

There are more topics for same problem, I suggest to add reports to one:
viewtopic.php?t=111417

[lxt123]

same here, I'm running ubuntu23.10 on windows 10 22H2. I got blue screen with Page fault in nonpaged area mostly when I vim some thing.

[RVT]

Same issue, running Windows 10 with Fedora 39 as guest. Network is in bridged mode.
What failed: VBoxNetLwf.sys

[multiOS]

@RVT

If, like the OP, you've installed the original VirtualBox 7.0.16 update, then I hope you've seen the warning on the Downloads page https://www.virtualbox.org/wiki/Downloads

As of 29 April 2024, the warning against installation is still current.

[Simple07]

I still don't understand, why is a seriously unstable and faulty software (7.0.16-162802) kept in General Availability (GA).

There are already 7.0.17-162950 and 7.0.17-162969 test builds released since, both don't exhibit the bug. 7.0.16-162802 should have been pulled out, fixed, and repackaged with a new build number (7.0.16-162xxx) and not wait until 7.0.18 is released.

Now we have 7.0.12 and 7.0.16 GA releases with problems. How can they stay in the stable stack and be called stable releases!!??

[AndyCot]

The simple answer is that Oracle treats us end users as free testers and as such the more testing that gets done the better the quality for the paying customers.

Open source software updates are tested, but bugs and major issues can still get through. At least Oracle have posted on the download page the warning, but there has been very little posted in the forums about reverting if you are using the "features" that cause the crash, which I think is very bad.