Weird BlueScreen in Hyper-V with Broadcom 5720 NIC

Hey there,

I have installed a brand new Windows 10 Pro 22H2 Installation on my AMD Platform and I'm running Hyper-V on it.

To ensure great Network Performance with VMQ-Support etc., I bought 2 x Broadcom 5720-2P (Dual Port) PCIe Cards.

One of them got shipped late due to stock problems, so I tried the first Card alone with the Motherboard Port.

The Setup was as followed:

1x BCM5720 Port in External Mode on Virtual Switch as WAN

1x BCM5720 Port in External Mode on Virtual Switch as LAN

1x Realtek 8168 Port for Management and Local Host Access.

This setup went fine, till the other adapter arrived.

I built-in the other 5720 Adapter and my plan was to Migrate the Management Interface to one of the new and free 5720 Ports.

The plan was to connect the new NIC, adjust IP-Config and then disconnect the Realtek Card so there is no loss of connectivity.

When I plugged in the cable to the Port, the Question of Windows arrised "private or public Network".

In the Moment I pressed "private", the System bluescreened with 0x139: KERNEL_SECURITY_CHECK_FAILURE

After reboot, I had the same question again. I pressed "private"- next Bluescreen with 0x139: KERNEL_SECURITY_CHECK_FAILURE

I assumed that the NIC might be defective, but I contiuned with one more test, but clicked on "public" this time.

There was no Bluescreen and System runs fine.

When I go into Network Settings, and try to set the Network to private, I can reproduce the Bluescreen.

This Issue is very strange to me, as I cannot see any loop or somehing, or either the card acting wrong in another System.

The Card-Drivers are the newest available and the cards firmware is also the latest

Driver: 221.0.7.0 / Firmware 226.0.14

I would assume this is a Problem in the Broadcom Windows Driver Implentation, as there is no Problem in the same configuration with the Port on the Realtek card.

Or can this also be a Problem related to Windows/Hyper-V?

Why is it depended on the network zone that Windows uses? Strange.

As the 5720-2P NIC is very common, I would report this issue to Broadcom, but first i eventually want to rule out Hyper-V as issue-source.

I've tested the suspicious card on another Systems, and there were no issues.

Infos of the Bluescreen:

• <System>

<Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{XXXXX-DE45-4366-8631-XXXXXX}" EventSourceName="BugCheck" /><EventID Qualifiers="16384">1001</EventID><Version>0</Version><Level>2</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime="2025-01-03T22:39:08.1732658Z" /><EventRecordID>11498</EventRecordID><Correlation /><Execution ProcessID="0" ThreadID="0" /><Channel>System</Channel><Computer>XXXXX-XXXXX</Computer><Security /></System>

• <EventData> <Data Name="param1">0x00000139 (0x0000000000000004, 0xffff8c8070fe0010, 0xffff8c8070fdff68, 0x0000000000000000)</Data><Data Name="param2">C:\Windows\MEMORY.DMP</Data><Data Name="param3">b56a8bbf-b95f-4958-9760-4e6bcf5669b6</Data></EventData> </Event>

Maybe someone knows something. I would provided any further information/dumps, as needed.

Best regards,

JohnSchnee

Edit:

Some more System Information;

Microsoft Windows 10 Pro

10.0.19045.5247

• Boot Mode: UEFI - CSM disabled
• TPM 2.0 & Bitlocker enabled
• Kernel Isolation enabled
• IMMOU / SVM / SME Support enabled