Wifi Adapter Disappeared After Sleep

[Zenquiorra]

My wifi was working fine recently, I had no power supply so it was running low on battery. Right around when the battery was around 10-20%, I decided to put it on sleep for a few hours until I get power supply. So after a few hours, I opened the system and the wifi was gone. I cannot find it in the list of available networks.



Now, this has happened earlier and I used to do this: I went to the device manager and in the network adapter section, I will choose Qualcomm Atheros Wireless and I would disable and enable it. This will fix the wireless problem for me.



This time it was a bit different because I was unable to find the wifi adapter in the device manager's network adapter section.

Now I tried various ways to fix it including installing official drivers from the manufacturer's website and updating the BIOS.



The adapter is Qualcomm Atheros QCA61x4A Wireless Network Adapter And it has both WiFi and Bluetooth modules in it. The Bluetooth is working fine, however, the Bluetooth adapter wont show in Device Manager either, instead it will show 'Bluetooth Device(Personal Area Network).

Here is a weird observation: I went into Windows Update and searched for updates, mysteriously it finds an update for: Qualcomm Incorporated - Ports - 3/25/2016 12:00:00 AM - 2.1.2.2 which I went ahead and installed it.



The main result is, I saw the Windows Event Viewer and searched for logs. What I found is after I put the system to sleep, there are a few power logs and right around the time, after I turn it on, I saw this log :


"Miniport Qualcomm Atheros QCA61x4A Wireless Network Adapter, {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, had event Fatal error: The Miniport has failed a power transition to operational power".



Here is an XML View of the log:

Log Name:      System
Source:        Microsoft-Windows-NDIS
Date:          11-06-2020 04:58:22
Event ID:      10317
Task Category: PnP
Level:         Error
Keywords:      (16384),(16),(4),(2)
User:          N/A
Computer:      LAPTOP-QBHK7CFU
Description:
Miniport Qualcomm Atheros QCA61x4A Wireless Network Adapter, {82395df5-aaae-4747-b3b4-c72815243edb}, had event Fatal error: The miniport has failed a power transition to operational power
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-NDIS" Guid="{cdead503-17f5-4a3e-b7ae-df8cc2902eb9}" />
    <EventID>10317</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>2</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000004016</Keywords>
    <TimeCreated SystemTime="2020-06-10T23:28:22.596539200Z" />
    <EventRecordID>61478</EventRecordID>
    <Correlation ActivityID="{82395df5-aaae-4747-b3b4-c72815243edb}" />
    <Execution ProcessID="4" ThreadID="17812" />
    <Channel>System</Channel>
    <Computer>LAPTOP-QBHK7CFU</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="IfGuid">{82395df5-aaae-4747-b3b4-c72815243edb}</Data>
    <Data Name="IfIndex">20</Data>
    <Data Name="IfLuid">19985273102270464</Data>
    <Data Name="AdapterName">Qualcomm Atheros QCA61x4A Wireless Network Adapter</Data>
    <Data Name="MiniportEventEnum">74</Data>
  </EventData>
</Event>

I am using Windows 10 Home on an Acer Swift SF315-41.



I have also seen some other users having a similar problem and some recommended bizarre solutions such as 'Turning off the PC and removing the power cord for 10 seconds' or leave it as it is and Windows will fix it, to updating certain drivers (Since this one was for Intel Adapter, I didn't apply it).

I also tried other suggested solutions such as:'


Reset TCP/IP stack to installation defaults: netsh int ip reset reset.log


Reset WINSOCK entries to installation defaults: netsh winsock reset catalog


Also, checking if the hardware is detected or not using 3rd party applications. The wifi adapter was NOT detected using the method, along with it the Bluetooth adapter was not detected either (but Bluetooth is working fine), even though they are on the same chip.


I assume that it is closely related to power. But it turns out that the possibility of this being a software issue is more likely.


Please suggest how should I fix this?

Continue reading...