GA-970A-UD3 - Windows 7 - Waking on Lan automatically!

[Strongfort]

Hello. I just built a new computer I used the GA-970A-UD3 motherboard. The system is running Windows 7 Home Premium.

I want to have the system in sleep mode when I'm not using it (rather than shutting it down) and I want to be able to remote in with my iPad/iPhone waking it from sleep when I do so. In otherwords I want the "Allow this device to wake the computer" checked on my network card on the mobo.

I have already gotten the above working fine, the problem I'm having is the system seems to be waking itself up automatically. Checking the "-lastwake" in a command prompt occasionally it would show the Keyboard or the Mouse as waking, but not since I disabled them - most of the time it does not state what woke the comptuer.

I've struggled for days trying to solve this. I've:
Turned off the ability for Mouse/Keyboard to wake the machine
Turned on the options for the USB hubs to turn off to save power
Adjusted Power Settings (Turned off USB selective Suspend setting, turned off Allow Wake Timers, etc.)
Edited the Bios settings to make sure the USB can not wake the computer
And many other things...

The Event Viewer keeps showing the point where it wakes up as "System as resumed from sleep" and says "Wake Source: Unknown". The CMD prompt -lastwake does not specify what device cause the wake.

Has anyone else had this issue with this motherboard? I can not for the life of me figure out what is causing the wake ups.

If someone has more knowlege on this and can help me pinpoint what is actually waking the computer please post here, I appreciate any help I can get.

[Dark Mantis]

Hi and welcome.

Obviously it is getting an input from somewhere even if it is erroneous. Try actually unplugging the keyboard and mouse.

What PSU are you using ?

Have you updated the LAN drivers and the BIOS to the most recent versions ?

[Strongfort]

Currently running the AMD FX-6100 (6-Core AM3+)

I did update the Lan to the latest drivers. I updated the Bios using the bios updating tool on Gigabyte's site - it updated to "F3" saying that was the newest. I did notice there's an F4 listed on the website - I trusted that the software had a good reason for not installing that version... 

I'm currently testing today it sleeping with the 2 usb-related items unplugged. I'll monitor it from work and see if it comes on unexpectedly and report back.

[teknology9]

Hi,

Did you use QFlash to update your BIOS?

There is an item here which explains the procedure of updating the BIOS on Gigabyte MB's:

http://forum.giga-byte.co.uk/index.php/topic,2441.0.html

Hope this helps

Teknology9

[Strongfort]

I used the @BIOS tool that was listed on this specific motherboard's download section on Gigabyte's support page. http://www.gigabyte.com/MicroSite/121/tech_a_bios.htm

It updated it to a newer firmware correctly. http://www.gigabyte.com/products/product-page.aspx?pid=3907#bios -I believe it updated it to F3.

[Dark Mantis]

If it worked ok you are lucky. We always try and steer people away from that (@BIOS) as it runs on top of the OS and recommend QFlash instead. It is much safer  and less likely to end up with a corrupt BIOS.

[teknology9]

Use the following:

Pendrive - say up to 4Gb and formatted to FAT 32

Ensure the correct file is saved on the drive

Plug into the USB headers at the rear of your MB and not the front

DMI Data - Keep this enabled as it is the default setting
 
 As I have said just read through the post I brought to your attention carefully.

[Dark Mantis]

If you have an even smaller drive like 2GB or less try that.

Plug into the USB headers at the rear of your MB and not the front

Very important!!

[Strongfort]

Well I figured I should post for closure, but I really have no idea what happened.

The issue appears to be fixed. After a ton of tinkering and reinstalling drivers/softwares it appears that a restart after some changes fixed the issue. I have no good explanation of what it was though. It's been 5 days and It has not once woken up unexpectedly, and I even have the mouse/keyboard set to be able to wake the machine (which early, was my best suspect).

Thanks in any case for the suggestions everyone.

[Dark Mantis]

That's the way it happens sometimes and it is a apin because you are never quite sure what did the trick and so can't note it in case it happens again. Never mind, at least your system is working properly again now.