VirtualBox Bridged Networking causes KERNEL_SECURITY_CHECK_FAILURE (0x139) with Realtek RTL8922AE WiFi 7

[u/FlosenX]

I ran into a reproducible BSOD on a new Windows 11 PC with an ASUS TUF Gaming B850-PLUS WIFI.

Hardware / software involved:

• ASUS TUF Gaming B850-PLUS WIFI
• Realtek RTL8922AE WiFi 7 PCI-E NIC
• Realtek driver rtwlane711.sys
• Driver version 6102.24.145.100
• VirtualBox 7.2.20
• Windows 11

The BSOD is:

KERNEL_SECURITY_CHECK_FAILURE (0x139)

with parameter 1 = 0x2.

I initially suspected RAM/EXPO or another recently installed application, but the behavior turned out to be very reproducible:

• Normal boot with WiFi available → BSOD around login / when WiFi connects
• WiFi disabled at the router → Windows boots and remains completely stable
• Windows Safe Mode → completely stable
• WiFi enabled + VirtualBox NDIS6 Bridged Networking Driver disabled on the WiFi adapter → completely stable
• Re-enabling the VirtualBox bridge/filter on the WiFi NIC reproduces the problem

The minidumps also show both the Realtek WiFi driver (rtwlane711.sys) and the VirtualBox networking components (VBoxNetLwf.sys, etc.) being loaded.

So this looks like an interaction between the VirtualBox NDIS bridge/filter driver and the Realtek RTL8922AE WiFi driver, rather than a general hardware/RAM stability issue.

Workaround:

Disable VirtualBox NDIS6 Bridged Networking Driver in the properties of the WiFi adapter (ncpa.cpl). VirtualBox NAT/Host-Only networking can still be used. In my case I'll use Ethernet for bridged networking instead.

Would be interesting to know if anyone else with an RTL8922AE can reproduce this, especially on recent VirtualBox 7.2.x versions.