Virtualbox 7.0.16 crashes Windows 11 host

[kabu]

Just upgraded to 7.0.16 and my Windows 11 host is crashing in blue screen.
Linux VM start works, I can login using ssh and basic commands like 'ls -l', 'df' works.
But immediately after running 'cat /proc/meminfo" or "top" in virtual machine, whole Windows 11 host system crash.
VM is Oracle Linux 8, tested 5.15.0-202.135.2.el8uek and 5.4.17 UEK kernels, both fails.
Tested it on two laptops, one with i7-1270P CPU, second three generations older, on both it fails.
I'm usually running in green turtle mode, but tested also with VT-X (after disabled core isolation), it fails on both modes.
I have no extension pack and guest additions installed.
Downgraded Virtualbox to 7.0.14 on newer laptop and all works fine there again.
Does anybody else has same issue after 7.0.16 upgrade?

EDIT: BUG report for this issue:
https://www.virtualbox.org/ticket/22045

EDIT2: Development is aware of the problem and working on fix.
This info is published on main virtualbox page and download page:

"ATTENTION: PLEASE REFRAIN FROM UPGRADING TO 7.0.16 FOR NOW. THIS RELEASE HAS AN ISSUE WHICH MIGHT CAUSE HOST OS CRASH WHEN VM IS CONFIGURED TO USE BRIDGED OR HOST-ONLY NETWORKING. WE WILL SEND AN ANNOUNCEMENT TO MAILING LISTS WHEN FIX WILL BE AVAILABLE FOR DOWNLOAD."

[kabu]

In Windows logs I found this related error
"The driver detected an internal driver error on \Device\VBoxNetLwf."
Similar like reported for 7.0.16 here viewtopic.php?t=111370

[SkyBeam]

I cannot add much detail other than confirming the issue.

Running VirtualBox 7.0.16 crashing host OS (Windows 11 23H2 build 22631.3447) immediately with a BSOD by VBoxNetLwf.sys. Downgrading to VirtualBox 7.0.14 entirely resolving the problem.

Bug Chekc String: PAGE_FAULT_IN_NONPAGED_AREA
Bug Check Code: 0x00000050

[linuxnerd]

Experiencing same issue!
Don't you guys test your stuff before release?

[reine667]

Hello, i have the same error. My Windows 11 host (Windows 10 Guest) crashes shortly after the guest's desktop appears (when establishing network connections?) with an error related to VBoxNetLwf.sys. The blue screen on the host also destroyed my virtual environment (.vmdk). Since I have backups, that's not a big deal. VirtualBox version 7.0.14 has been running without any problems since it was released (January).

[Obsession]

Here same, 7.0.16 crashes host. My VB has an connection to my Wifi. If I disable Wifi and start the VB, there is no problem. As soon as I start the Wifi-connection (on the host) and VB will get the network connection (you can see it in the taskbar), the host crashes. Without connection the VB runs without problems. Once established the connection - blue screen.

[kabu]

I have created new bug report

https://www.virtualbox.org/ticket/22045

[kabu]

Same issue reported here
viewtopic.php?t=111418
viewtopic.php?t=111370

[awakened]

I also confirm these reproducable BSOD's in 7.0.16 on Windows 10 host immediately when connecting via RDP to a Fedora 39 guest.
Attached a Windbg report in case that may help.

[SirJohn2024]

Yep!

PAGE_FAULT_IN_NONPAGED_AREA apparently caused by VBoxDDR0.r0

[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 Guest. I usually have 1 NAT adapter and 1 Bridged Adapter per VM.

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 guests. 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. Also, the problem disappears when the Bridged Adapter is changed to other type, like NAT or Host-only etc.

Reinstalling Windows 11 build 26100 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 can reproduce it also with WiFi disabled and with no internet connectivity from host and VM. In VM I have one NAT network and one host network adapter. When I run "top" from Virtualbox console, it works. But once logged from host to VM using ssh through host-only networking and starting "top", it crash.

[Simple07]

Did you try installing VirtualBox 7.0.15-162549 instead of 7.0.14? I hope it works for you.
It may be someone made a mistake when packaging this version, I hope the developers fix the issue quicky and release it with updated build number (7.0.16-162xxx) and not leave the buggy one in GA status.

[RonaldOldDonald]

Hopefully the VBox team will resolve this critical bug asap and release a more stable 7.0.16 RC

[Pharao507]

Same happened to me. Just upgraded from 7.0.14 to 7.0.16 on Windows 10 host.
Got the BSOD running a Windows 10 guest AND a Linux gust.
Unfortunately this also rendered the Windows 10 guest unusable - does not boot anymore; boot repair not working.

Is there a way to work around the problem other than going back to 7.0.14?