Question Periodic disconnects - Netwtw14 - Intel Wi-Fi 6E AX210 ?

[Maverick_Zer0]

Recently, i rebuilt my PC as i was downsizing case and ever since, i've been having a constant issue with my Wi-Fi straight up disconnecting. These disconnects happen usually intermittently every 2-15 minutes, though sometimes occur multiple times in a minute. The disconnects are brief in nature, lasting literally only a couple of seconds but usually it's enough to boot me from whatever game i am playing or cut out voip for a moment or two before returning to normal.

I never used to get these issues, it's only started happening since i've rebuilt my PC, all the exact same components just a new case, which makes the issue perplexing.

I tracked the issue to event viewer where i get multiple error codes popping up under the source 'Netwtw14', these error codes are usually 6062, 7021 or 7002 but recently there have been more. These events occur in time with the disconnects and state the following.

The description for Event ID 6062 from source Netwtw14 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.


If the event originated on another computer, the display information had to be saved with the event.


The following information was included with the event:


\Device\NDMP17
Intel(R) Wi-Fi 6E AX210 160MHz


The message resource is present but the message was not found in the message table

This message is identical between the different error codes.

So I updated the drivers for the Intel Wi-FI 6E AX210 device (which were out of date) from my motherboard's manafacturere's website (Asus) and the issue still occured. I tried a couple of drivers after that from Intel's own website. Next I went into the device's properties and tried changing some of the settings in there including changing the 802.11 between A and AX mode, forcing it to only connect to 5GHz or 2.4 GHz channels from my router, changing roaming aggressiveness and changing the power management settings, none of which seemed to make much of a difference at all.

Interestingly enough this issue does not occur if I connect to my phone's 4g Wi-FI hotspot, it's perfectly fine which makes me think it's an interaction with the router that's causing it. I have no idea what that would be however, no other devices on the network drop when the PC does, only the PC.

I am going to reset and update my BIOS at the weekend and failing that, a full re-install of windows but i'd like a couple of other options before I do.

Before anyone suggests a wired connection, yes I have considered it but my living situation makes that difficult at best.

System Specs as follows

Windows 10 Home Edition - Version 19045.5011


Intel i9-11900K
ROX STRIX Z590-E Wi-Fi
Samsung SSD 850 EVO 250gb (OS Drive - 36gb Free)
Samsung SSD 850 EVO 500gb (150gb Free)
Samsung 870 QVO 1TB (71gb Free)
Samsung 870 QVO 4TB (1.3TB Free)
WDC WD60EZRZ 6tb (1.8TB Free)

Corsair CP-9020094-UK RM1000x 100w 80 Plus Gold Modular Power Supply - 2 Years old - Good condition - Purchased new.

Router was provided by my ISP (Sky) - Model Sky Hub Q SR203.

 

[Ralston18]

Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

Make and model: modem, router, or modem/router if combined?

On your computer run "ipconfig /all" (without quotes) via the Command Prompt.

Copy and paste the full results herein.

 

[bill001g]

I saw this on another forum and only read it because they were talking about intel "killer" chips. Before intel purchased the killer network company I used to hate on that company constantly. Problem is intel hired a bunch a the engineers from killer and sell product lines with that name. They still think they can reduce latency in gaming inside someone computer.

So back on topic. After searching around it appears this is a problem with anything based on intel ax210 or ax211 chipset not just killer versions. It does not appear to happen the newer ax411. Since the ax210 has been around for many years and has been the most stable wifi6e chipset it would be strange for it to have a new hardware issue. It is not clear if there is any correlation based on when the ax210 chip was manufactured.

The stupid thing I saw on intel site was their recommendation to just not use the 5g radio band. Maybe they mean to use the 6ghz band but it is unclear if this problem occurs.

In any case this seems to be some bug intel knows about and has known about for getting close to a year now. What I would try is see if you can get a driver from say a year ago or even more than a year ago. Mostly the older driver just do not support the newer chipset since intel uses the same driver for all their chips and load the proper one from the file. Be sure to dig around and find the option in windows to not allow it to update your drivers since I suspect that is how you got a "new" driver in the first place.

 

[Maverick_Zer0]

Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

Make and model: modem, router, or modem/router if combined?

On your computer run "ipconfig /all" (without quotes) via the Command Prompt.

Copy and paste the full results herein.

Updated the OP with system information.

Spoiler: Ipconfig

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-RDKF3P6
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Home

Ethernet adapter Ethernet 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Controller (3) I225-V
Physical Address. . . . . . . . . : 50-EB-F6-B3-64-D0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Ethernet Controller (3) I225-V #2
Physical Address. . . . . . . . . : 50-EB-F6-B3-64-CF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #3
Physical Address. . . . . . . . . : 44-E5-17-04-F4-94
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 12:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #4
Physical Address. . . . . . . . . : 46-E5-17-04-F4-93
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter WiFi 2:

Connection-specific DNS Suffix . : Home
Description . . . . . . . . . . . : Intel(R) Wi-Fi 6E AX210 160MHz
Physical Address. . . . . . . . . : 44-E5-17-04-F4-93
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2a02:c7c:d482:eb00:24b1:35de:2edd:6233(Preferred)
IPv6 Address. . . . . . . . . . . : fd35:412e:1f22:0:5171:60dd:581b:98b5(Preferred)
Temporary IPv6 Address. . . . . . : 2a02:c7c:d482:eb00:144d:ea11:ed64:458(Preferred)
Temporary IPv6 Address. . . . . . : fd35:412e:1f22:0:144d:ea11:ed64:458(Preferred)
Link-local IPv6 Address . . . . . : fe80::92f:342c:3d9f:22aa%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.18(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 10 November 2024 18:02:05
Lease Expires . . . . . . . . . . : 11 November 2024 18:02:04
Default Gateway . . . . . . . . . : fe80::3e45:7aff:fe62:8039%13
192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 222618903
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-29-F1-50-B9-38-D5-47-29-48-59
DNS Servers . . . . . . . . . . . : fd35:412e:1f22:0:3e45:7aff:fe62:8038
192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Bluetooth Network Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) #2
Physical Address. . . . . . . . . : 10-7C-61-2B-63-0E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

 

[Maverick_Zer0]

I saw this on another forum and only read it because they were talking about intel "killer" chips. Before intel purchased the killer network company I used to hate on that company constantly. Problem is intel hired a bunch a the engineers from killer and sell product lines with that name. They still think they can reduce latency in gaming inside someone computer.

So back on topic. After searching around it appears this is a problem with anything based on intel ax210 or ax211 chipset not just killer versions. It does not appear to happen the newer ax411. Since the ax210 has been around for many years and has been the most stable wifi6e chipset it would be strange for it to have a new hardware issue. It is not clear if there is any correlation based on when the ax210 chip was manufactured.

The stupid thing I saw on intel site was their recommendation to just not use the 5g radio band. Maybe they mean to use the 6ghz band but it is unclear if this problem occurs.

In any case this seems to be some bug intel knows about and has known about for getting close to a year now. What I would try is see if you can get a driver from say a year ago or even more than a year ago. Mostly the older driver just do not support the newer chipset since intel uses the same driver for all their chips and load the proper one from the file. Be sure to dig around and find the option in windows to not allow it to update your drivers since I suspect that is how you got a "new" driver in the first place.

From what I could find, this issue does stem back to even 2016 with no concrete fix found. I'll try backdating drivers and see if that makes any difference.

 

[bill001g]

Not sure where you fond 2016 unless this happens with older chips. The ax210 came out end of 2020 according to intels site.

 

[Maverick_Zer0]

Not sure where you fond 2016 unless this happens with older chips. The ax210 came out end of 2020 according to intels site.

Not for that particular chip no, but just the nature of the issue in general. Anyway, after jumping through some hoops to install some older drivers (thanks intel), there has not been an issue thus far. I'll report back after a day or two to see if the issue has completely gone.