Hi,
I've been using the UD7 board for a few weeks now after upgrading from an older Asus P5K-E (LGA775) board, and everything seems to work perfectly, except I have yet to get my rig to wake up from S3 sleep. I've been searching countless forums for several days now without result. It may very well not have anything to do with the mobo, but I don't know where else to start.
From what I've gathered so far there seems to be almost as many causes behind this problem as the problems themselves, and for me to have any chance of solving this issue, I'll try to be as specific in describing the symptoms as possible.
My specs are as follows:
MB: GA-X58A-UD7
CPU: i7 920 D0
RAM: Corsair DominatorTR3X6G1600C8D (6gb)
HDD: Intel X25-M 80GB SSD Gen.2
GPU: Sapphire Vapor-X HD5870 1GB
OS: Win7 Home Prem. 64
BIOS: I'm currently on the latest F7h BIOS, and I've also tried both F5 and F6 from gigabytes official UD7 download page.
Exactly what happens:
When entering S3 sleep (both timed and manual activation) the computer saves to ram and powers down everything in what seems like normal S3 sleep behaviour. I'll then press a key on the keyboard and the computer seems to be powering up again and the fans start spinning. But then nothing more happens...
During the attempted wakeup the UD7 POST error code LED seems to cycle three times through C1 as it would during a normal boot, but then halts at CF instead of moving to C3 and furhter towards FF like normal. Now, I'm aware that this may not be abnormal, as S3 to my knowledge won't execute a normal full boot like hibernate (which actually works perfectly on my machine) does, but I suspect the leds are supposed to show FF again after S3 wakeup? Any feedback here as to what the LEDs show for other UD7 users that are able to recover successfully from S3 sleep, when resuming, would be greatly appreciated.
This behaviour had me leaning towards faulty ram modules, but Memtest86+ v.4.10 completes just fine with no errors. Also when manually forcing shutdown after a failed resume, and then booting again, windows resumes correctly from the previous pre-sleep state with the "Resuming Windows" screen, much like hibernate would.
As for BIOS settings I've tried loading both failsafe and optimized defaults, tried forcing most MIT settings on manual insted of auto, and
tried every combination I can think of at the BIOS power management settings (also in combination with different Windows 7 power settings). No OC'ing going on as of yet btw. Ram tested at both stock speed and XMP profile.
I've also read several places that dafault BIOS settings may need some tweaking to operate successfully with S3, but since I'm not that experienced in this field, it's just been guesswork so far. I've tried upping dram and qpi/vtt voltage, but to no avail.
Even tried a complete format/re-install of Win7 with a different Catalyst driver only (official 10.4 version instead of beta version.) in the off chance that it could be GPU related. I'm not so sure about this though, as I'm suspecting the wakeup process doesn't even get to the point of re-posting any video. Also tried all other latest hardware drivers.
A few last thoughts:
Keyboard wakes up the machine, but power seems to disappear again when the UD7 settles on the CF error code, as the keyboard lights go out again. Pressing the mouse buttons won't wakeup the machine in the first place (probably device manager power settings, but that's okay), but when pressing a mouse button while on CF error, the mouse lights up, but nothing more. All other pheripherals like ethernet, audio etc. are disconnected. S1 sleep works fine, but it's not quite what I'm looking for.
Well, that should be about it :) I've probably forgotten to mention something, but I'll leave it up to you helpful experts to ask for other relevant pieces of information. At this point I'm left with no idea whatsoever what the cause(s) of the problem is, and I'd be super grateful to see the problem resolved.
I've been using the UD7 board for a few weeks now after upgrading from an older Asus P5K-E (LGA775) board, and everything seems to work perfectly, except I have yet to get my rig to wake up from S3 sleep. I've been searching countless forums for several days now without result. It may very well not have anything to do with the mobo, but I don't know where else to start.
From what I've gathered so far there seems to be almost as many causes behind this problem as the problems themselves, and for me to have any chance of solving this issue, I'll try to be as specific in describing the symptoms as possible.
My specs are as follows:
MB: GA-X58A-UD7
CPU: i7 920 D0
RAM: Corsair DominatorTR3X6G1600C8D (6gb)
HDD: Intel X25-M 80GB SSD Gen.2
GPU: Sapphire Vapor-X HD5870 1GB
OS: Win7 Home Prem. 64
BIOS: I'm currently on the latest F7h BIOS, and I've also tried both F5 and F6 from gigabytes official UD7 download page.
Exactly what happens:
When entering S3 sleep (both timed and manual activation) the computer saves to ram and powers down everything in what seems like normal S3 sleep behaviour. I'll then press a key on the keyboard and the computer seems to be powering up again and the fans start spinning. But then nothing more happens...
During the attempted wakeup the UD7 POST error code LED seems to cycle three times through C1 as it would during a normal boot, but then halts at CF instead of moving to C3 and furhter towards FF like normal. Now, I'm aware that this may not be abnormal, as S3 to my knowledge won't execute a normal full boot like hibernate (which actually works perfectly on my machine) does, but I suspect the leds are supposed to show FF again after S3 wakeup? Any feedback here as to what the LEDs show for other UD7 users that are able to recover successfully from S3 sleep, when resuming, would be greatly appreciated.
This behaviour had me leaning towards faulty ram modules, but Memtest86+ v.4.10 completes just fine with no errors. Also when manually forcing shutdown after a failed resume, and then booting again, windows resumes correctly from the previous pre-sleep state with the "Resuming Windows" screen, much like hibernate would.
As for BIOS settings I've tried loading both failsafe and optimized defaults, tried forcing most MIT settings on manual insted of auto, and
tried every combination I can think of at the BIOS power management settings (also in combination with different Windows 7 power settings). No OC'ing going on as of yet btw. Ram tested at both stock speed and XMP profile.
I've also read several places that dafault BIOS settings may need some tweaking to operate successfully with S3, but since I'm not that experienced in this field, it's just been guesswork so far. I've tried upping dram and qpi/vtt voltage, but to no avail.
Even tried a complete format/re-install of Win7 with a different Catalyst driver only (official 10.4 version instead of beta version.) in the off chance that it could be GPU related. I'm not so sure about this though, as I'm suspecting the wakeup process doesn't even get to the point of re-posting any video. Also tried all other latest hardware drivers.
A few last thoughts:
Keyboard wakes up the machine, but power seems to disappear again when the UD7 settles on the CF error code, as the keyboard lights go out again. Pressing the mouse buttons won't wakeup the machine in the first place (probably device manager power settings, but that's okay), but when pressing a mouse button while on CF error, the mouse lights up, but nothing more. All other pheripherals like ethernet, audio etc. are disconnected. S1 sleep works fine, but it's not quite what I'm looking for.
Well, that should be about it :) I've probably forgotten to mention something, but I'll leave it up to you helpful experts to ask for other relevant pieces of information. At this point I'm left with no idea whatsoever what the cause(s) of the problem is, and I'd be super grateful to see the problem resolved.
Comment