X58A-UD3R takes 30sec to wake from S3

[Gary123]

X58A-UD3R rev 2.0 BIOS FB, i7-950, 6 GB OCZ Gold DDR3-1600, OCZ Onyx SSD 64GB, 2TB WD GreenPower SATA. GTX 260, Windows 7 Pro x64.
No overclocking, ACHI disabled in BIOS.

When the PC resumes from sleep (S3), there's a period of about 30 seconds before the monitor turns on. (During this time, there's a loud fan sound--probably from the GPU--which then subsides.) Then the monitor turns on, and Windows is ready to log back in.

I've seen older Windows 7 PCs that resume from sleep in less than 5 seconds. Do all X58A-UD3Rs take this long, or is this a quirk of my setup? (There are no other problems that I've noticed.)

[Wonderwrench]

I normally never use sleep of any kind. I do have hibernate enabled in case of a PF. I did some testing since I have the same board (see sig). It takes about 18 seconds to enter S3 and about 10 seconds to resume. All my drives are on the Intel SATA 2 controller and the controller is in AHCI mode. My Intel SSD boot drive is on port 0. Port 0-3 native mode is set to native mode (enabled). My WD data drive is on port 1 and the optical drives are on ports 4 and 5. I'm using Intel's RST 9.6 driver. The eSATA controller is in AHCI mode. USB 3 is enabled. The Marvell SATA 3 and Gigabyte SATA 2/IDE controllers are disabled. 1394 is also disabled. I'm using a PS2 mouse and keyboard BTW. None of this may mean anything but it might lead you somewhere?

I would think the time taken to enter and resume from S3 would depend on the amount and size of the programs you have running when you enter S3. The amount of Physical memory may also have an affect. The only programs running during my testing was Firefox 3.6.10, Speedfan 4.42 b4, DiskCheckup 3.0 b1003 and Avast 5 IS 5.0.667. USB devices connected, APC BX1000G UPS, HP C6380 printer and a MS FFB wheel. The Realtek onboard NIC connects to a D-link 655 router.

edit: forgot about USB 3 (enabled)  

[Gary123]

Thanks, Wonderwrench, for the thorough report! So there is indeed something that's causing my setup to take longer to wake. Some of your components are faster than mine, but not by enough to account for the difference between 10 seconds and 30. I'll try disabling my unused SATA controllers (I'm only using the ICH ones) and see if that helps.

I would think the time taken to enter and resume from S3 would depend on the amount and size of the programs you have running when you enter S3. The amount of Physical memory may also have an affect.

Amount of memory in use (or installed) could affect the time required to resume from hibernation, or the time to enter hybrid sleep (which copies RAM to disk in case of power loss, and then enters normal S3 sleep). But if I understand correctly, neither factor should matter for resuming from S3, since everything is still in RAM and doesn't need to be restored from the disk.

[Wonderwrench]

You got me thinking so I had a look at my power settings and hybrid sleep was enabled so I disabled it and retested. It now takes 4-5 seconds to sleep and 4-5 seconds to resume. That's freakin fast! My last build must not of supported hybrid sleep as it was disabled by default so I never payed close attention on this build. Ah I know what the difference was my old board defaulted to S1 in the bios not S3, so no hybrid sleep.

Bill 

[Dark Mantis]

I normally never use sleep of any kind.

Yes I notice that mate from the time of your post  

Posted on: Today at 04:50:19 am




(I do know that you are in the USA  )

[Gary123]

I tried disabling my 1384 and my unused SATA controllers, but it made no difference to the resume-from-S3 time. (Booting is a few seconds faster now, though.)

I wonder if the delay has to do with my GTX 260 card. I think it's the GPU fan that's running loudly during the resume-from-S3 process, and the monitor stays off until the very end of the process; when it turns on, the Windows login screen is already displaying.

[Dark Mantis]

It does sound quite possible. Can you use newer drivers? Failing that try using some much older drivers as there have been quite a few issues with the later drivers.

[Gary123]

I have the 258.96 WHQL release, which was installed by Windows. It's the latest Nvidia release (from Aug. 19).

I'm reluctant to revert to older drivers to investigate this problem, but I appreciate the suggestion.

[Dark Mantis]

Have you got a friend with a similar card (nVidia) that you could try in place of the 260?

[Wonderwrench]

I have the 258.96 WHQL release, which was installed by Windows. It's the latest Nvidia release (from Aug. 19).

I'm reluctant to revert to older drivers to investigate this problem, but I appreciate the suggestion.

I'm running the 258.96 WHQL drivers also installed by windows update. It could be the card difference though. BTW what brand and model GTX 260 are you running?

[Gary123]

Have you got a friend with a similar card (nVidia) that you could try in place of the 260?

No, but I just found a recent post from someone else with this problem. They have the same Gigabyte board, but a completely different graphics card (Radeon HD5870).
http://windows7forums.com/windows-7-support/48375-x64-slow-resume-sleep.html

I've used "View performance details in Event Log". It does show a Critical diagnostic for Standby Performance (Resume Duration is 27131ms), but there are no items providing information as to the cause.

Resume time was normal until I upgraded my motherboard, processor, RAM, and installed an SSD as my boot device. All other system components/devices are unchanged. I clean-installed Windows 7. All software/drivers are up-to-date. This looks like a Gigabyte BIOS problem that manifests with some configurations.

[Dark Mantis]

Resume time was normal until I upgraded my motherboard, processor, RAM, and installed an SSD as my boot device. All other system components/devices are unchanged.

To be fair that is most of your  system!

[Gary123]

I'm running the 258.96 WHQL drivers also installed by windows update. It could be the card difference though. BTW what brand and model GTX 260 are you running?

eVGA GeForce GTX 260. But I was getting normal resume-from-S3 times (~5 sec) until I upgraded the motherboard. And I came across another recent post (referenced above) from someone with a Radeon card, but the same motherboard, having the same slow-resume problem.

[Dark Mantis]

Have you tried flashing back to an older BIOS version?

[Gary123]

Resume time was normal until I upgraded my motherboard, processor, RAM, and installed an SSD as my boot device. All other system components/devices are unchanged.

To be fair that is most of your  system!

True. But since the PC's performance is great once it resumes from sleep, the motherboard/BIOS seems like a plausible culprit.

Actually entering sleep (whether manually or by idle timeout), and resuming from sleep, work flawlessly, except for the consistently long time to resume.