[DRIVERS] Intel Ethernet/WiFi/Bluetooth

[funkyd]

After more troubleshooting, I've determined the BSOD with virtualization enabled is likely caused by Receive Side Scaling (RSS). I turned this off on my NIC and was able to install the new 2.1.1.7 drivers. Still testing, but the system appears to be stable.

To turn off, open PowerShell as administrator. Run the following to get the name of your NIC (mine was simply named Ethernet):
get-netadapter

Then, run the following to turn off RSS:
disable-netadapterrss -Name name from previous command

More Info on RSS:
https://docs.microsoft.com/en-us/win...e-side-scaling
https://www.broadcom.com/support/kno...indows-servers

Edit:

On a hunch I did some more testing, and this appears to be related to the E-cores on Alder Lake. I am guessing this will end up being a Windows issue. The following is what causes the BSOD in my case:

• Alder Lake chip with E-Cores enabled
• Ethernet driver that utilizes the NetAdapterCx miniport driver
• Ethernet RSS settings at default values
• Windows virtualization features enabled, such as Windows Sandbox, Subsystem for Linux, and possibly Hyper-V

I've been testing the following workaround, which will keep RSS from utilizing the E-Cores and causing the BSOD. Before updating to v2 of the ethernet drivers:

• Open PowerShell as administrator
• Run the following to get the name of your I225-V NIC (mine was simply named ethernet, and I'll use that for the examples below):
  
• get-netadapter
• Run the following to tell RSS to only use the first 8 cores (which will be your P-Cores):
  
• set-netadapterrss -name ethernet -MaxProcessorNumber 14
• By default, MaxProcessors is set to half the total number of processors:
  
• set-netadapterrss -name ethernet -MaxProcessors 4
• If you run get-netadapterrss -name ethernet, it should look like the below

After the above, you should be able to install the latest 2.1.1.7 drivers with no issue. I've reported this to both Intel and Asus, but no idea who to report to at MS. Hope this is helpful to others with the same issue.

[brantgurga]

Nice to see I'm not the only one with major issues with all 2.* drivers available so far whether through Asus or Intel. My experience has been that USB hotplug functionality quits working and the driver would quit working at times.
The current Windows Insider build (22598) will install with virtualization features enabled out the gate if that is an exacerbating feature. Namely, Memory integrity will be on by default from the get-go if installed via Setup. However a Reset will reinstall with Memory Integrity off and require manually turning it on. I'll wait till newer versions to try this new driver model again.

[bigjohns97]

After more troubleshooting, I've determined the BSOD with virtualization enabled is likely caused by Receive Side Scaling (RSS). I turned this off on my NIC and was able to install the new 2.1.1.7 drivers. Still testing, but the system appears to be stable.

To turn off, open PowerShell as administrator. Run the following to get the name of your NIC (mine was simply named Ethernet):
get-netadapter

Then, run the following to turn off RSS:
disable-netadapterrss -Name name from previous command

More Info on RSS:
https://docs.microsoft.com/en-us/win...e-side-scaling
https://www.broadcom.com/support/kno...indows-servers

Edit:

On a hunch I did some more testing, and this appears to be related to the E-cores on Alder Lake. I am guessing this will end up being a Windows issue. The following is what causes the BSOD in my case:

• Alder Lake chip with E-Cores enabled
• Ethernet driver that utilizes the NetAdapterCx miniport driver
• Ethernet RSS settings at default values
• Windows virtualization features enabled

I've been testing the following workaround, which will keep RSS from utilizing the E-Cores and causing the BSOD. Before updating to v2 of the ethernet drivers:

• Open PowerShell as administrator
• Run the following to get the name of your I225-V NIC (mine was simply named ethernet, and I'll use that for the examples below):
  
• get-netadapter
• Run the following to tell RSS to only use the first 8 cores (which will be your P-Cores):
  
• set-netadapterrss -name ethernet -MaxProcessorNumber 14
• By default, MaxProcessors is set to half the total number of processors:
  
• set-netadapterrss -name ethernet -MaxProcessors 4
• If you run get-netadapterrss -name ethernet, it should look like the below

After the above, you should be able to install the latest 2.1.1.7 drivers with no issue. I've reported this to both Intel and Asus, but no idea who to report to at MS. Hope this is helpful to others with the same issue.

I never touched anything but the Asus BIOS does have vt-d enabled by default and I never turned it off.

I don't use any of the newer virtualization based security such as memory integrity (but have before without issue) but do have the older hyper-v based stuff enabled in system information.

I do not have the hyper-v feature installed to be able to run VM's on this machine.

I have never had any issues with these drivers running a 12700k on the latest (non-insider) version of Windows 11

Just wondering what differences between mine and your system that really caused the BSOD.

[funkyd]

Just wondering what differences between mine and your system that really caused the BSOD.

The BSOD isn't caused by the VT-D BIOS settings and doesn't seem to be related to memory integrity/core isolation. Your post was a bit unclear to me, do you have Hyper-V enabled on your system?

Below are the features I have enabled:



I have confirmed both Windows Subsystem for Linux and Windows Sandbox cause the BSOD independently of each other, but have not tested with only Virtual Machine Platform enabled (which is required for both WSL or WSB to function). I also haven't tested with Hyper-V, but I believe both WSL and WSB use virtual Hyper-V switches, which I believe is the cause of the issue in combination with RSS and Alder Lake E-cores, as I mentioned above.

Asus support was also able to reproduce the BSOD on their end and recommended reverting to the previous driver version on their site, 1.0.2.14. I requested they escalate to Intel/MS, but obviously have no control over what they do with the info I provided. Intel is still investigating, which is promising.

Edit: I will also clarify my previous post, by "virtualization features enabled" I am specifically referring to features such as WSL, WSB, and possibly Hyper-V, NOT VT-D or core isolation.

[bigjohns97]

The BSOD isn't caused by the VT-D BIOS settings and doesn't seem to be related to memory integrity/core isolation. Your post was a bit unclear to me, do you have Hyper-V enabled on your system?

Below are the features I have enabled:



I have confirmed both Windows Subsystem for Linux and Windows Sandbox cause the BSOD independently of each other, but have not tested with only Virtual Machine Platform enabled (which is required for both WSL or WSB to function). I also haven't tested with Hyper-V, but I believe both WSL and WSB use virtual Hyper-V switches, which I believe is the cause of the issue in combination with RSS and Alder Lake E-cores, as I mentioned above.

Asus support was also able to reproduce the BSOD on their end and recommended reverting to the previous driver version on their site, 1.0.2.14. I requested they escalate to Intel/MS, but obviously have no control over what they do with the info I provided. Intel is still investigating, which is promising.

Edit: I will also clarify my previous post, by "virtualization features enabled" I am specifically referring to features such as WSL, WSB, and possibly Hyper-V, NOT VT-D or core isolation.

Yeah I don't have any of those Hyper-V features enabled.

I agree this is probably related to the Hyper-V features you are using to either run VM's or WSL/WSB.

Under More Windows Features

Hyper-V
Virtual Machine Platform
Windows Hypervisor Platform
Windows Sandbox
Windows Subsystem for Linux

Are all unchecked on my machine.

I believe this is why you are seeing issues while others are not, good to know.

Maybe someone should report to Intel since this isn't default Windows options it is possible they aren't aware of the issue.

[Ataemonus]

Thank you very much, Mokichu.

[ahfoo]

Thank you ,Mokichu

[Ataemonus]

Thank you, Mokichu.

[schm0]

There is no RSS support in the NDIS drivers.

//edit
Well, seems like both Win11 drivers have no RSS support?

[xProlific]

I'm on a Dark Hero Motherboard. The Wifi Device name is AX200 but the Hardware ID is 8086?
https://imgur.com/a/HsYfyAe

Which driver is correct?
Drivers - 9xxx/AXxxx : 22.140.0.3 WHQL [26/04/2022]
Drivers - 3165/3168/7265D/8xxx : 22.130.0.5 WHQL [15/03/2022]