[SOLVED] WiFi Adapter keeps needing to be reset

[Lazonda]

My WiFi adapter keeps needing to be reset. It appears to be at random intervals and has started happening out of nowhere.

Troubleshooting steps:

1. Both rolled back and updated drivers
2. Updated BIOS
3. Run intel hardware tests
4. Various Windows troubleshooting and changing settings as suggested.

I looked at the error logs and I can't see anything that is immediately preceeding it. The report reads;

Log Name: System
Source: Netwtw08
Date: 28/09/2019 13:59:52
Event ID: 5005
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-Q9BNR95
Description:
Intel(R) Wireless-AC 9260 160MHz : Has encountered an internal error and has failed.

Specs:

OS Name Microsoft Windows 10 Pro
Version 10.0.17763 Build 17763
Processor AMD Ryzen 5 2600 Six-Core Processor, 3400 Mhz, 6 Core(s), 12 Logical Processor(s)
BIOS Mode UEFI
BaseBoard Product B450 GAMING PRO CARBON AC (MS-7B85)
Wireless adapter Intel(R) Wireless-AC 9260 160MHz

 

[Ralston18]

Corrupted system file perhaps?

I googled "Event 5005" and found quite a number of links.

I would start with running "sfc /scannow" (without quotes) via the command prompt.

Then, if the problem continues try "dism" per the following link:

https://answers.microsoft.com/en-us...rt-after/e0164f10-47df-4c53-99ea-01ba9b6e47fb

For more information regarding sfc /scannow -

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Overall, read through the above links first, do some additional googling to learn more as necessary, then try sfc /scannow and dism.

Be aware that your searches are likely to turn up many links claiming to have fixes. Some of those links will appear no matter what problem you are researching. Avoid any third party downloads for tools or fixes. Likewise do not do any Registry editing - that should only be a very last resort. And only if your system is fully and verifiably backed up.

 

[Lazonda]

Corrupted system file perhaps?

I googled "Event 5005" and found quite a number of links.

I would start with running "sfc /scannow" (without quotes) via the command prompt.

Then, if the problem continues try "dism" per the following link:

https://answers.microsoft.com/en-us...rt-after/e0164f10-47df-4c53-99ea-01ba9b6e47fb

For more information regarding sfc /scannow -

https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161

Overall, read through the above links first, do some additional googling to learn more as necessary, then try sfc /scannow and dism.

Be aware that your searches are likely to turn up many links claiming to have fixes. Some of those links will appear no matter what problem you are researching. Avoid any third party downloads for tools or fixes. Likewise do not do any Registry editing - that should only be a very last resort. And only if your system is fully and verifiably backed up.

Thank you. I've carried out both. Won't post the log files unless neccessary but the cmd output was as follows below. Since it's a random problem I'll just have to wait for now.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\system32>Dism /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.737

The component store is repairable.
The operation completed successfully.

C:\Windows\system32>Dism /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.737

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\Windows\system32>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.1

Image Version: 10.0.17763.737

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

 

[gggplaya]

Make sure you download the proper driver for your wireless adapter, try not to rely on windows automatic driver downloads. I've seen similar behavior in the past with wifi adapters and microsoft drive detection and auto download.

 

[Ralston18]

Next step would be to open up the case and look for a loose connection with respect to the installed wireless adapter.

Check the motherboard's User Guide/Manual and the wireless adapter's User Guide manual to ensure that the wireless adapter is fully and firmly connected. If there are antennas check that they are properly installed.

Antenna extensions may be helpful.