X58A-UD3R takes 30sec to wake from S3

[Wonderwrench]

What you would have to do is clear the DMI memory pool. To do that you have to use QFlash again and then on the main screen disable Keep DMI Data

Instead of re-flashing, I just cleared CMOS (via the button), and then I was able to get AHCI to work. Plus that totally fixed the S3-delay problem. It now resumes from S3 in 3 seconds instead of 40! (I had tried the clear-CMOS button earlier, and it didn't resolve the S3-delay problem, so apparently it was AHCI mode--not just clearing the CMOS--that fixed the S3-delay.)

Of course, there really shouldn't have been such a long S3-resume delay even in the default IDE mode. So that's something that Gigabyte may want to investigate (I'll tell their tech support about the outcome). But I'm all set now.

Many thanks to you and to Bill for your suggestions.

No problem. I had a feeling AHCI mode might fix it because our hardware setup is very similar and S3 was working well for me.

[Dark Mantis]

It was nice to find a solution that makes sense in the end. It was a new one on me so another bit of info to add to my arsenal. Glad we could have helped.

[Gary123]

For future reference, I think I understand how my problem came about.

After I clean-installed Windows 7, I installed drivers from the Gigabyte product web page rather than from the DVD. For the Intel SATA driver, I received an error (computer hardware does not support this driver), but everything seemed to work (except for the S3-resume delay), so I assumed the driver-installation error was because IDE mode was selected in the BIOS. I later noticed two Intel SATA controllers in the Device Manager (one 2-port, one 4-port).

When I enabled AHCI in the BIOS, the Intel SATA controllers were replaced in the Device Manager by a single Microsoft SATA controller. Although that fixed the S3-delay, I soon found that my hard drives would occasionally dismount themselves after resuming from S3. So I installed the Intel SATA driver again, which worked this time and seems to have fixed everything. Now, the Device Manager shows a single Intel ICH10R SATA AHCI Controller.

After I enabled AHCI, my WEI disk score increased from 6.8 to 6.9 (OCZ Onyz 64GB SSD).

[Dark Mantis]

Excellent outcome and thanks very much for the background information, could very well come in handy in the future.

[Gary123]

I've noticed one other problem: with hybrid sleep, if I shut off the power after the PC is in S3 and then power on again, the system properly runs through the POST, displays the Resuming Windows screen for several  seconds, and then the screen goes black. There's a cursor at upper left for a second, and then it's gone and the screen is completely black (although the monitor is awake). The disk light stays off, and the keyboard has no effect (including c-a-d and the sleep button). The case's sleep/power button also has no effect (unless I hold it in for four seconds to force a shutdown). I've waited for up to five minutes before giving up.

Bill, you mentioned your PC has similar components. Do you find the same problem under these circumstances? 

[Wonderwrench]

I've noticed one other problem: with hybrid sleep, if I shut off the power after the PC is in S3 and then power on again, the system properly runs through the POST, displays the Resuming Windows screen for several  seconds, and then the screen goes black. There's a cursor at upper left for a second, and then it's gone and the screen is completely black (although the monitor is awake). The disk light stays off, and the keyboard has no effect (including c-a-d and the sleep button). The case's sleep/power button also has no effect (unless I hold it in for four seconds to force a shutdown). I've waited for up to five minutes before giving up.

Bill, you mentioned your PC has similar components. Do you find the same problem under these circumstances? 

I do not understand exactly what your asking. Shut the power off? how? PSU switch? Are you running S3  STR or S3 hybrid sleep aka STR+ hibernate. I'm not using hybrid sleep just S3 because I do not want gigs of data written to my SSD every time I enter S3. I have an UPS that should hold for hours if I have a power failure so no need to copy to disk. I never really used S3 prior to reading your thread here on the forums. I find I kinda like it. If your running straight S3 killing the power would be a bad idea. Please post more details and I'll attempt to reproduce your problem.

[Gary123]

I've enabled Hybrid Sleep mode in Windows 7. With hybrid mode, when the PC sleeps, it first copies RAM to disk (just as with Hibernate), then enters S3. Subsequently, when the PC wakes, it's normally just a resume from S3 (ignoring the hibernation data on the disk). But if power was interrupted in the meantime, erasing the RAM, the PC does a resume from hibernate instead.

When my PC is in hybrid S3 sleep, I turn off the PSU switch for a few seconds. I turn it back on and restart, which begins a resume-from-hibernate, but then I get the problem mentioned previously.

[Dark Mantis]

Not being funny but why would you want to do that anyway! 

[Gary123]

Not being funny but why would you want to do that anyway! 

Surprisingly, it's a feature that does come in handy from time to time. Not just for power failures (which are infrequent), but also if my PC is already in S3 and I need to disconnect power for some reason. (Just yesterday, for instance, i needed to cut the circuit breaker to the room in order to repair a wall switch.) Also, I like to unplug my whole system if I'm going to be away for a few days (which happens fairly often), and if the PC is already asleep, it's convenient not to have to wake it and hibernate it before pulling the plug.

Anyway, it's not terribly important, but it's an advertised XP/Vista/7 feature that used to work fine for me until the recent upgrade, so it'd be slightly annoying to lose it.

[Dark Mantis]

Fair enough I suppose. I just couldn't understand why someone would want to do it. Personally I would prefer to shut down the PC completely but as I say that is personal choice.

[Gary123]

Fair enough I suppose. I just couldn't understand why someone would want to do it. Personally I would prefer to shut down the PC completely but as I say that is personal choice.

Yeah, I just have a lot of state that's inconvenient to have to re-create if the system shuts down completely. Once everything is stable, I tend to go weeks between booting or logging off.

[Dark Mantis]

If that't the case maybe you would do well to invest in an UPS to maintain your power should an outage occur.

[Gary123]

If that't the case maybe you would do well to invest in an UPS to maintain your power should an outage occur.

I appreciate the suggestion, but I don't like having to buy extra hardware just to work around a software flaw. (A UPS would also help with unexpected power failures while the PC is in use, but that's too rare an occurrence here for me to worry about.)

Anyway, I've now identified the source of the problem. When I disable the USB3 controller in the BIOS, the PC resumes properly from hybrid S3/hibernate even if the power is turned off while the PC is in S3. I've already got the latest NEC USB 3.0 driver (2.0.4.0 2010-07-22) from the Gigabyte product web page, so I'll report it as a driver bug.

[Dark Mantis]

Good news. They probably don't realise it yet so reporting it is good.
I always use an UPS anyway because it conditions the power to the system and in case of supply interuption which like you doesn't happen very often.

[Gary123]

Good news. They probably don't realise it yet so reporting it is good.

Yeah, this is a longstanding peeve I have about Windows. As a matter of truth-in-advertising, I don't think devices/components should be allowed to claim Windows compatibility unless tests show (among other things) that the devices resume properly from sleep and hibernation. (Or at least, any Windows-compatibility claim should be qualified by saying "except for sleep/hibernate".)

Things have improved greatly in this regard, though. This is the first sleep/hibernation incompatibility I've encountered in the past year or two.