Intel Wireless-AC 9260 stops scanning after ~30–60 minutes, Event ID 5002/5005/5032/5010 (Netwtw08) – hardware or driver issue?
Question
Hello,
I am experiencing a persistent Wi-Fi issue on a Windows 10 desktop PC. After extensive troubleshooting, I would like to confirm whether this is a known hardware/firmware failure of the Intel Wireless-AC 9260 or if there is still any possible software-side solution.
System information
OS: Windows 10 x64 (fully updated)
Motherboard: MSI B450 Gaming Pro Carbon AC
Wi-Fi module: Intel Wireless-AC 9260NGW (M.2 Key-E)
Ethernet: Intel I211 Gigabit (works perfectly at all times)
Wi-Fi driver: Latest Intel driver (23.60.x, provider: Intel)
Problem description
After a cold boot or system restart:
Wi-Fi works normally
Wireless networks are visible
Internet connection is stable
Mobile hotspot works
After approximately 30–60 minutes of uptime:
All Wi-Fi networks disappear (0 networks visible)
netsh wlan show networks returns 0
Mobile hotspot cannot be enabled
Wi-Fi remains enabled (Radio ON, Software ON)
Ethernet continues to work without any issues
Once this state occurs:
Wi-Fi does not recover automatically
Disabling/enabling the adapter does not help
Restarting WLAN AutoConfig service does not help
Resetting the network stack does not help
Only a full system reboot temporarily restores Wi-Fi
Event Viewer logs
When the failure occurs, Event Viewer consistently reports Intel Wi-Fi driver (Netwtw08) errors in the following sequence:
Event ID 5002 – The network adapter has stopped responding, reset attempted
Event ID 5005 – Miniport reset failed
Event ID 5032 – The network adapter returned an invalid value to the driver (repeated)
Event ID 5010 – The network adapter entered a non-operational state
The final error message is typically:
“Intel(R) Wireless-AC 9260 160MHz: The network adapter has returned an invalid value to the driver.”
Troubleshooting already performed
Clean installation of the latest Intel Wi-Fi drivers (not Microsoft inbox drivers)
WLAN and network stack reset:
netsh winsock reset
`netsh int ip reset`
`netsh wlan delete profile *`
Restarted WLAN AutoConfig service
Disabled all power-saving options for the Wi-Fi adapter
Verified adapter state using `netsh wlan show interfaces`
Confirmed `netsh wlan show networks` returns 0 after failure
Full power drain reset (PSU unplugged, capacitors discharged)
Checked and reseated antennas
Ethernet remains stable during the entire time
Important observation
The issue is clearly time-dependent:
Wi-Fi works after reboot
After some time (likely related to heat or firmware state), Wi-Fi scanning stops completely
Logs indicate firmware/PHY returning invalid values to the driver
Question
Based on:
Consistent Netwtw08 errors (5002 → 5005 → 5032 → 5010)
Complete loss of Wi-Fi scanning (0 networks visible)
Recovery only possible via system reboot
Is this a known hardware or firmware failure mode of the Intel Wireless-AC 9260, and is replacing the M.2 Wi-Fi module (e.g. Intel AX200) the only reliable solution?
Is there any confirmed Windows-side workaround that can recover the adapter without rebooting, or does this behavior conclusively indicate a failing Wi-Fi module?
Thank you for any confirmation or additional insight.
Question
Hello,
I am experiencing a persistent Wi-Fi issue on a Windows 10 desktop PC. After extensive troubleshooting, I would like to confirm whether this is a known hardware/firmware failure of the Intel Wireless-AC 9260 or if there is still any possible software-side solution.
System information
OS: Windows 10 x64 (fully updated)
Motherboard: MSI B450 Gaming Pro Carbon AC
Wi-Fi module: Intel Wireless-AC 9260NGW (M.2 Key-E)
Ethernet: Intel I211 Gigabit (works perfectly at all times)
Wi-Fi driver: Latest Intel driver (23.60.x, provider: Intel)
Problem description
After a cold boot or system restart:
Wi-Fi works normally
Wireless networks are visible
Internet connection is stable
Mobile hotspot works
After approximately 30–60 minutes of uptime:
All Wi-Fi networks disappear (0 networks visible)
netsh wlan show networks returns 0
Mobile hotspot cannot be enabled
Wi-Fi remains enabled (Radio ON, Software ON)
Ethernet continues to work without any issues
Once this state occurs:
Wi-Fi does not recover automatically
Disabling/enabling the adapter does not help
Restarting WLAN AutoConfig service does not help
Resetting the network stack does not help
Only a full system reboot temporarily restores Wi-Fi
Event Viewer logs
When the failure occurs, Event Viewer consistently reports Intel Wi-Fi driver (Netwtw08) errors in the following sequence:
Event ID 5002 – The network adapter has stopped responding, reset attempted
Event ID 5005 – Miniport reset failed
Event ID 5032 – The network adapter returned an invalid value to the driver (repeated)
Event ID 5010 – The network adapter entered a non-operational state
The final error message is typically:
“Intel(R) Wireless-AC 9260 160MHz: The network adapter has returned an invalid value to the driver.”
Troubleshooting already performed
Clean installation of the latest Intel Wi-Fi drivers (not Microsoft inbox drivers)
WLAN and network stack reset:
netsh winsock reset
`netsh int ip reset`
`netsh wlan delete profile *`
Restarted WLAN AutoConfig service
Disabled all power-saving options for the Wi-Fi adapter
Verified adapter state using `netsh wlan show interfaces`
Confirmed `netsh wlan show networks` returns 0 after failure
Full power drain reset (PSU unplugged, capacitors discharged)
Checked and reseated antennas
Ethernet remains stable during the entire time
Important observation
The issue is clearly time-dependent:
Wi-Fi works after reboot
After some time (likely related to heat or firmware state), Wi-Fi scanning stops completely
Logs indicate firmware/PHY returning invalid values to the driver
Question
Based on:
Consistent Netwtw08 errors (5002 → 5005 → 5032 → 5010)
Complete loss of Wi-Fi scanning (0 networks visible)
Recovery only possible via system reboot
Is this a known hardware or firmware failure mode of the Intel Wireless-AC 9260, and is replacing the M.2 Wi-Fi module (e.g. Intel AX200) the only reliable solution?
Is there any confirmed Windows-side workaround that can recover the adapter without rebooting, or does this behavior conclusively indicate a failing Wi-Fi module?
Thank you for any confirmation or additional insight.