Wireless network adapter missing after resuming from S3 sleep.

I have had this same thread in Networking forums with no response and am now trying it here.

My adapter is always gone from resuming from sleep. I know it was working before. Just changed my ram and bios settings from a fresh build. Went from Corsair xms3 to G.Skill Ripjaws.

I am having this same issue with my newly built pc. The drive running Windows 7 is from a laptop where the mobo died. I am using it in AHCI mode because my case has a front hot swap caddy.

I have a Gigabyte Z68X-UD3H-B3 mobo and after installing and uninstalling drivers, software, changing settings, removing ram, changing power options to maximum power for pci card and wifi, turning off hibernate, restarted, rebooted, updated all drivers from Gigabyte, chipset drivers, etc. I have unchecked "allow Windows to turn off this device". Restarted and tested and I get the same issue. I have unchecked this box in all of my networking devices too including, 802.11n Wireless Lan Card #2 and Microsoft Virtual Wifi Miniport Adapter. Also, uninstalled and reinstalled these and updated drivers from my disc that came from Gigabyte as well as driver update from the Gigabyte website.

Nothing I do will turn on my wifi card after sleep. Windows will not see a network adapter. In device manager, there is no wireless card, even after showing hidden devices. Adding a device does not discover it. Installing the network card driver and software does nothing to detect it. Windows thinks there is no device connected. Everything works fine after restarting though. I have S3 enabled in bios as that is what I want. I have cpu fan that I don't want to hear with no option to turn them off. Otherwise, i'd be fine with S1.

Is this just not a working feature? I've read that sleep is an ongoing issue with Windows, but my pc sleeps fine. I just want to be able to put my pc to S3 sleep and resume with a working wifi card. There must be a key setting i'm missing because i'm sure it was working with my last set of ram.

jumanji said:

Could you try the wireless adapter on another PC - preferably not yours where you seem to have done a lot of things :) - and check whether the same problem is there?

Don't have one. I am going to pick up another adapter to rule it out.

Anything else I can try in the meantime?

1. Go through your motherboard manual and check whether you need to move the jumpers on the USB headers to a different position to enable USB wake-up. ( On some older motherboards this had to be done.)

2. Also check from the manual whether all the USB ports are wake-enabled or only some. ( On my current Zotac Mini-PC only some ports are wake-enabled as mentioned in the manual)

3. Go to your device (wireless adapter) manufacturer's website, download the latest driver for it and install. For some updated drivers resolved the problem.

4. I myself wanted to suggest that you change the wireless adapter to a different brand. Many got fed up trying to fix the problem, changed to a different brand and lived happily thereafter :). (If that does not work, you may always return it. I presume you are in USA where it is not a problem.)

The adapter is pcie so I don't understand messing with the usb header.

Got a new adapter to use. This one was usb so not the pcie I was having problems with. The usb adapter works and resumes from sleep fine.

In the process of this I have found a solution to my woes via ethernet and there are also no issues from waking out of sleep. I am going to continue using ethernet as it is much faster and reliable so the hunt for the pcie solution is still UNSOLVED. I will no longer be exploring this further, however if anyone can think of anything else, please add any ideas for those seeking the same as I was.

EMINENT 1 said:

The adapter is pcie so I don't understand messing with the usb header.

OK, I had assumed that you were talking of an USB wireless adapter.:) Not many use a PCIe adapter.

Good you cahanged over to an USB adapter. The advantage is that you can always use it in some other PC - portability.