[DRIVERS] Intel Ethernet/WiFi/Bluetooth

Quote:

---

Originally Posted by MoKiChU

Therefore, some third party apps that use NDIS drivers/devices (like Avast and its Avast! Firewall NDIS Filter Miniport) and/or that use WFP (Windows Filtering Platform) can cause your NetAdapter miniport driver kernel to crash/BSoD.

---

Thank you for this information! This helped me track down the cause on my system. I am still testing, but virtualization appears to break these drivers. This includes Windows Sandbox and Windows Subsystem for Linux. Removing these allows the drivers to install. Reinstalling either will cause a BSOD after the 2nd reboot (the 1st reboot completes the feature installation, and the system appears to be stable until the 2nd reboot).

Anyone else who experienced BSOD's, can you respond if you're using Windows Sandbox, WSL, Hyper-V, or any other type of virtualization such as Bluestacks, VirtualBox, etc? If someone with a stable system wants to test by installing one of these features, just be aware you'll need to enter Safe Mode and remove the ethernet driver if you end up in a boot loop.

Quote:

---

Originally Posted by funkyd

If you think a BSOD on a clean install of Windows that happens with one set of drivers

---

Quote:

---

Originally Posted by funkyd

I am still testing, but virtualization appears to break these drivers. This includes Windows Sandbox and Windows Subsystem for Linux.

---

Clearly, your definition of a "clean install on Windows" is quite different than what the actual wording would suggest, as I am yet to find any version of Windows that comes by default with WS and WSL installed.

@ MoKiChU, thank you for your update. Appreciated.

Thank you, Mokichu.

Quote:

---

Originally Posted by MoKiChU

Hi everyone,

- Intel WiFi Drivers (Drivers Only) :

Drivers - 9xxx/AXxxx : 22.140.0.2 WHQL [18/04/2022]
Download - 9xxx/AXxxx : Link

Thread updated.

---

Cheers mate as usual.

I was struggling with this like crazy. Both the 2.0.1.3 offered directly by Asus and 2.0.1.7 offered directly by Intel was causing non-stop kernel security check BSOD. Had to disable all kinds of virtualization software in Windows 11 such as Hyper-V, Guarded Host, and Microsoft Defender Application Guard.

Does seem like a massive oversight? I can understand that generic Intel drivers might cause issues, but the fact that Asus themselves list 2.0.1.3 as the only Windows 11 driver for my Asus Z690 Maximus Hero and it doesn't work with common Windows 11 features without causing non-stop BSOD is bad.

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

Attachment 92858

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.

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.

Quote:

---

Originally Posted by 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

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

Attachment 92858

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.

Quote:

---

Originally Posted by bigjohns97

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:

Attachment 92905

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.

Quote:

---

Originally Posted by funkyd

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:

Attachment 92905

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.

Thank you very much, Mokichu.

Thank you ,Mokichu :)

Hi everyone,

- Intel Ethernet Drivers (Drivers Only) :

Drivers - I225/I226 - Windows 10 : 1.1.3.28 WHQL [05/03/2022]
Download - I225/I226 - Windows 10 : Link

Thread updated.

Thank you, Mokichu.

There is no RSS support in the NDIS drivers.

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

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]

Hey MoKiChU, first off thank you for everything you do. Your drivers thread has been very valuable for years.
I had a quick question with regard to the drivers I225 - Windows 10 : 1.0.2.22 WHQL [28/07/2021]. I have a z690 hero on windows 10, would there be any negative outcome to using the 1.1.3.28 driver listed for windows 11 over the 10.2.22 driver for windows 10? Every driver updater (snappy/etc) is telling me to use the 1.1.3.28. I just didn't know since it looks like receive side scaling & jumbo packet has changed.
Thanks.

Hello! MoKiChU, does it make sense to update the Internet drivers on Asus ROG Strix B550-E Gaming Wi-Fi on bios AMD AM4 AGESA V2 PI 1.2.0.3 Patch C 2423 ?
(I have not even installed new BIOS updates on my motherboard yet and I don’t know if they are worth it, but I often update drivers and saw a new version of Internet drivers.)
P.S: Thanks in advance for your reply =)

Quote:

---

Originally Posted by MoKiChU

Hi everyone,

@ I225 controller users : As you can see, there are now 2 types of drivers for Windows 11 in the thread, so I anticipate questions by letting you know the difference between the two :

NetAdapter : More efficient than NDIS drivers type because of more low level access to the controller than NDIS drivers type, but can generate side effects due to the non-support of NetAdapter by other apps or system addons features. If you encounter any issue with NetAdapter drivers type, switch to the NDIS drivers type.

NDIS : NDIS drivers type is the legacy drivers type used for all other I21x controllers drivers whether for Windows 10 drivers or Windows 11 drivers, this drivers type will give you better stability/compatibility.

---

The NDIS driver (I225 - Windows 10/11 (NDIS) : 1.1.3.28 WHQL [05/03/2022]) does not work on my system, no internet connection.
I have a Strix z490-E Gaming with WIN 11. Any advice?
Thanks

Quote:

---

Originally Posted by Shad8

The NDIS driver (I225 - Windows 10/11 (NDIS) : 1.1.3.28 WHQL [05/03/2022]) does not work on my system, no internet connection.
I have a Strix z490-E Gaming with WIN 11. Any advice?
Thanks

---

Drivers NetAdapter 2.1.1.7 WHQL [02/02/2022]
I'm also using Z490 - E, windows 11 and it works fine.

Attachment 93157

The Win10 1.1.3.28 drivers also has no RSS support.
The Inf has the proper entries to set it up but it isn't added into the registry because the rss reg part isn't added into device section.

// edit
This driver version was available through snappy driver installer for some time now.
But reverted back to 1.0.2.2 because RSS support was missing. (or at least not configurable?)

It seems like the newest Intel driver package also contains this driver version without (configurable?) RSS support.
The question is now, did they forget to add this? Or did they to it purpose?

Drivers works for me on Win10 with I225 though.

//edit2
Get-NetAdapterRss doesn't show any RSS support.
However, after manually adding the RSS entries to the registry, RSS shows up again but only with 1 queue.
So basically not working. But I'm also using WSL/Hyper and I'm not sure if WSL/Hyper forces the NIC to use 1 queue.
Maybe someone else can test?

Also, the changelog doesn't mention anything about the removal of RSS.

//edit3
the lack of RSS is maybe related to:
https://community.intel.com/t5/Ether...1/td-p/1377927

Quote:

---

Originally Posted by Minh Le

Drivers NetAdapter 2.1.1.7 WHQL [02/02/2022]
I'm also using Z490 - E, windows 11 and it works fine.

Attachment 93157

---

The v2.1.1.7 works fine for me to. I was talking about the 1.1.3.28 version which was listed as Win 11 compatible. Anyway, i reset the network settings and now is working just fine.

Hi everyone,

- Intel WiFi Drivers (Drivers Only) :

Drivers - 9xxx/AXxxx : 22.150.0.3 WHQL [24/05/2022]
Download - 9xxx/AXxxx : Link

Thread updated.

Quote:

---

Originally Posted by MoKiChU

Hi everyone,

- Intel WiFi Drivers (Drivers Only) :

Drivers - 9xxx/AXxxx : 22.150.0.3 WHQL [24/05/2022]
Download - 9xxx/AXxxx : Link

Thread updated.

---

Thx mate, works great here :o

Quote:

---

Originally Posted by schm0

Get-NetAdapterRss doesn't show any RSS support.
However, after manually adding the RSS entries to the registry, RSS shows up again but only with 1 queue.
So basically not working. But I'm also using WSL/Hyper and I'm not sure if WSL/Hyper forces the NIC to use 1 queue.
Maybe someone else can test?

---

This is interesting, as upgrading the built-in 1.0.2.14 driver (included with the motherboard) to the latest v2 driver does not disable RSS support, at least on my system. I am guessing there is an issue with the current v2 drivers and they do not disabled RSS support as the 1.1.3.28 appear to do (I have never tested these drivers). I created the Intel thread that you linked, because RSS causes a BSOD when WSL/WSB/HyperV is enabled.

That said, search for my earlier post in this thread... it seems to be possible to enable RSS via PowerShell if you limit it to only the P-Cores. RSS doesn't support hyperthreading so it likely doesn't support E-Cores either. However, RSS is smart enough to not use the hyperthreaded cores... it doesn't appear to be smart enough to not use the E-Cores, hence the BSOD's.

Quote:

---

Originally Posted by funkyd

This is interesting, as upgrading the built-in 1.0.2.14 driver (included with the motherboard) to the latest v2 driver does not disable RSS support, at least on my system. I am guessing there is an issue with the current v2 drivers and they do not disabled RSS support as the 1.1.3.28 appear to do (I have never tested these drivers). I created the Intel thread that you linked, because RSS causes a BSOD when WSL/WSB/HyperV is enabled.

That said, search for my earlier post in this thread... it seems to be possible to enable RSS via PowerShell if you limit it to only the P-Cores. RSS doesn't support hyperthreading so it likely doesn't support E-Cores either. However, RSS is smart enough to not use the hyperthreaded cores... it doesn't appear to be smart enough to not use the E-Cores, hence the BSOD's.

---

Im on a 10850k and by default my maxprocessor was 18 for some reason when the chip only has 10 cores. I changed it to 10 and it seems to install fine.

Hi everyone,

- Intel Bluetooth Drivers (Drivers Only) :

Drivers - 8xxx/9xxx/AXxxx : 22.150.0.6 WHQL [30/05/2022]
Download - 8xxx/9xxx/AXxxx : Link

Thread updated.

Hello MoKiChU!
Just updated to Windows 11, and as you told me a few time ago, I went to update only the Intel Ethernet drivers to last Windows 11 version...but trying to update them as usual pointing to the new drivers, it returns me a message that I'm using latest drivers already.
Installed drivers are your latest Windows 10 drivers I installed.

What is the correct way to update them?
Thank you.

EDIT: I tried forcing them with the "Have Disk" button, and it worked. Is that the correct way?

Quote:

---

Originally Posted by piratino

Hello MoKiChU!
Just updated to Windows 11, and as you told me a few time ago, I went to update only the Intel Ethernet drivers to last Windows 11 version...but trying to update them as usual pointing to the new drivers, it returns me a message that I'm using latest drivers already.
Installed drivers are your latest Windows 10 drivers I installed.

What is the correct way to update them?
Thank you.

EDIT: I tried forcing them with the "Have Disk" button, and it worked. Is that the correct way?

---

Hi,

Given that Windows is always based on the date to favor one driver over another, and that Windows 10 drivers are more recent in date than Windows 11 drivers, yes that's the correct way (or other ways such as removing Windows 10 drivers via Driver Store Explorer and then installing Windows 11 drivers).

Quote:

---

Originally Posted by MoKiChU

Hi,

Given that Windows is always based on the date to favor one driver over another, and that Windows 10 drivers are more recent in date than Windows 11 drivers, yes that's the correct way (or other ways such as removing Windows 10 drivers via Driver Store Explorer and then installing Windows 11 drivers).

---

Fantastic! Thank you.

Do you have any personal thoughts regarding which drivers are best (WIn 11 Vs. Win 10) as for the actual state of drivers developing?
As for one of your past posts from a few days ago you were proposing "NetAdapter" v2.1.1.7 Vs. "NDIS" v1.1.3.28 ....

Quote:

---

Originally Posted by MoKiChU

@ I225 controller users : As you can see, there are now 2 types of drivers for Windows 11 in the thread, so I anticipate questions by letting you know the difference between the two :

NetAdapter : More efficient than NDIS drivers type because of more low level access to the controller than NDIS drivers type, but can generate side effects due to the non-support of NetAdapter by other apps or system addons features. If you encounter any issue with NetAdapter drivers type, switch to the NDIS drivers type.

NDIS : NDIS drivers type is the legacy drivers type used for all other I21x controllers drivers whether for Windows 10 drivers or Windows 11 drivers, this drivers type will give you better stability/compatibility.

---

Quote:

---

Originally Posted by piratino

Fantastic! Thank you.

Do you have any personal thoughts regarding which drivers are best (WIn 11 Vs. Win 10) as for the actual state of drivers developing?
As for one of your past posts from a few days ago you were proposing "NetAdapter" v2.1.1.7 Vs. "NDIS" v1.1.3.28 ....

---

Hi,

Unless specifically use, just install the drivers corresponding to your OS.

Quote:

---

Originally Posted by MoKiChU

Hi,

Unless specifically use, just install the drivers corresponding to your OS.

---

Can't think of any particular reasons why I might need a driver for Windows 10 if the one for Windows 11 is working fine.

But as you stated:

NetAdapter : More efficient than NDIS drivers type because of more low level access to the controller than NDIS drivers type, but can generate side effects due to the non-support of NetAdapter by other apps or system addons features. If you encounter any issue with NetAdapter drivers type, switch to the NDIS drivers type.

So I immagine the only reason to use the NDIS drivers is related to some hardware/software incompatibility of some how or anything related to not being able to use NetAdapter drivers without any issues....right?