Official GIGABYTE Forum
Questions about GIGABYTE products => Motherboards with Intel processors => Topic started by: Gary123 on October 07, 2010, 02:26:38 am
-
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.)
-
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)
-
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.
-
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
-
I normally never use sleep of any kind.
Yes I notice that mate from the time of your post ;D
Posted on: Today at 04:50:19 am
(I do know that you are in the USA ;))
-
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.
-
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.
-
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.
-
Have you got a friend with a similar card (nVidia) that you could try in place of the 260?
-
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?
-
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.
-
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! ::)
-
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.
-
Have you tried flashing back to an older BIOS version?
-
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.
-
Have you tried flashing back to an older BIOS version?
The only other version is the original FA BIOS, which had the same problem.
-
I agree that is the most logical answer (but not everything is logical) ;) That's why I asked about using an older BIOS version. Have you looked on TweakTown forum as they often get newer beta versions than us?
http://forums.tweaktown.com/
-
I agree that is the most logical answer (but not everything is logical) ;) That's why I asked about using an older BIOS version. Have you looked on TweakTown forum as they often get newer beta versions than us?
http://forums.tweaktown.com/
Yup, I appreciate your suggestions. :)
TweakTown lists an FC1, but I'm reluctant to try an unofficial Beta BIOS to investigate this problem when everything else is working so smoothly. FB is the current download on the Gigabyte site.
-
TweakTown is the official site in hte US for Gigabyte and if they are using it I would doubt that there are any real problems with it. Ask Lsdmeasap on there he will know if it is good.
-
TweakTown is hte official site in hte US for Gigabyte
Thanks, I didn't realize that. Still, I think I'll wait until the next BIOS is no longer in beta.
-
OK well keep a look out there because as I say they will probably get it before us. ;)
-
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.
Looking closer, it specifies StandbyResumeS3BiosInitTime=26450ms, which is almost all of the 27131ms total Resume Duration. (There's also StandbyResumeResumeDevices=618ms, less than one second.)
-
I would guesss from those figures that it would be possible to shorten the "wait" duration and make the startup faster.
-
I would guesss from those figures that it would be possible to shorten the "wait" duration and make the startup faster.
Yes, I hope the next BIOS release will do that!
-
Question, why are you running in IDE mode? AHCI mode is needed for Windows 7 SSD TRIM to function. I doubt it is related to your S3 problem but it could be. Info on changing to AHCI mode after windows install. http://www.sevenforums.com/tutorials/61869-ahci-enable-windows-7-vista.html?ltr=A
If you are going to give this a try image your boot drive before hand or at least backup your data. I have enabled AHCI mode after install on two PC's without any problems but it pays to be safe.
Bill
-
No that is not correct. TRIM will work as well in IDE as AHCI mode. The only thing that benfits from running in AHCI apart from a slight speed improvement is the ability to Hot Swap the drives.
-
No that is not correct. TRIM will work as well in IDE as AHCI mode.
Yup. I just verified:
C:\Windows\system32>fsutil behavior query disabledeletenotify
DisableDeleteNotify = 0
-
No that is not correct. TRIM will work as well in IDE as AHCI mode. The only thing that benfits from running in AHCI apart from a slight speed improvement is the ability to Hot Swap the drives.
I revisited this and I may or may not have been wrong. I found no reliable source of info on this subject. I was always under the assumption that it was required because Win7 requires the MSAHCI driver to allow passing of the TRIM commands. Intel's 9.6 driver also allows passing the TRIM command. This can be found everywhere on the net. I may have interpreted this wrong. It may only mean if you are running in AHCI mode trim will not function if your not using the MSAHCI driver not that IDE mode lacks support for TRIM. If trim does work in IDE mode why is there no info on the net saying you must use the IDE driver included in windows 7. IDE drivers from the chipset manufacturer would surely need to support passing the trim command same as AHCI drivers. As far as the C:\Windows\system32>fsutil behavior query disabledeletenotify outputting 0. It does not prove trim is working it just proves it may be working.
Lets say TRIM works in either mode. Why cripple SSD performance by running in IDE mode. AHCI mode makes a big difference in performance in the testing I have done. See screen shots.
(http://i156.photobucket.com/albums/t25/wonderwrench/Misc/SSD01.jpg)
(http://i156.photobucket.com/albums/t25/wonderwrench/Misc/SSD02.jpg)
If anyone can come up with reliable info on this subject please post links! Reliable meaning from MS, Intel, AMD or a SSD manufacturer. BTW I'm talking native Windows 7 TRIM not a manual Trim tool.
Bill
-
Hi Bill, I just knew you were going to make me prove it ;) I almost didn't bother posting but that wouldn't be fair to others who might need the info.
I had this discussion with Lsdmeasap from TweakTown Forums a little while ago and he has now adjusted his posts on the forum to comply.
C:\Windows\system32>fsutil behavior query disabledeletenotify outputting 0
I agree with you on this point all it shows is that TRIM is enabled not necessarily passed on.
TBH I really didn't feel the drive speed was that much more impressive on the whole.
You can read about it here.
http://benchmarkreviews.com/index.php?option=com_content&task=view&id=505&Itemid=38&limit=1&limitstart=12
-
Thanks! I'll try enabling AHCI when I have some time.
-
I just realized I made a dumb mistake. I'd had trouble squeezing my GTX 260 into the top PCIe slot, so I put it in the slot just below, not realizing that's x8 rather than x16. So I need to move the card, and perhaps that'll fix the S3-resume delay. I'll let you know.
-
Yes it could well be to do with that. Please let us know if you have sorted it now. ;)
-
I'd had trouble squeezing my GTX 260 into the top PCIe slot, so I put it in the slot just below, not realizing that's x8 rather than x16. So I need to move the card, and perhaps that'll fix the S3-resume delay.
I moved my GTX 260 to the top slot. While I was at it, I also moved my SSD boot drive from Channel 2 master to Channel 0 master.
It did make a difference: now it takes 40 seconds to resume from S3, instead of 30 seconds! :(
StandbyResumeResumeDevices is still about the same (636ms), but StandbyResumeBiosInitTime has increased to 37382ms.
-
The extra time it takes is probably because you moved the Boot drive and now instead of it being where it was originally it has to locate it first.
-
The extra time it takes is probably because you moved the Boot drive and now instead of it being where it was originally it has to locate it first.
I've rebooted a few times and resume-from-S3 still takes 40 seconds now. Would I need to re-flash the BIOS in order for it to remember the new location of the boot drive? (The boot-drive priority list in the BIOS properly lists the SSD first.)
-
Not re-flash the BIOS but clear the CMOS. Make sure you do a complete clear not just press the button.
-
Not re-flash the BIOS but clear the CMOS. Make sure you do a complete clear not just press the button.
I'll try that, but just out of curiosity, why wouldn't it save the new SSD location to CMOS when I do a save-and-exit in the BIOS setup? (The BIOS does list the SSD in the Channel 0 Master position.)
-
To be perfectly honest I am not 100% sure so I was taking the safe option.
-
To be perfectly honest I am not 100% sure so I was taking the safe option.
Ok, thanks. It turns out I'd have to remove the graphics card again to get to the CMOS battery, so I'm going to avoid that unless there's a strong reason to think it would solve the delay problem.
-
No sure reason just trying to cover all the possible bases. ;)
-
Gigabyte tech support wants me to try it with just one memory module. I don't imagine that'll make a difference, but I guess I'll do the experiment.
-
It's the same as on the forum they will go through a list of things to try and narrow down the possibilities. So you need to do as they ask. ;)
-
Info on changing to AHCI mode after windows install. http://www.sevenforums.com/tutorials/61869-ahci-enable-windows-7-vista.html
I found that the specified registry key is already set to 0, and the Device Manager already showed two Intel ICH10 SATA Controllers. So I enabled ICH SATA AHCI in the BIOS, and the BIOS subsequently detected SATA devices (rather than IDE devices), but then the bootstrap hung after "Verifying DMI Pool Data" and never got to the Windows startup screen.
I switched the BIOS back to ICH IDE, and was able to boot normally again.
-
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
-
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.
-
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.
-
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. ;)
-
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).
-
Excellent outcome and thanks very much for the background information, could very well come in handy in the future. :)
-
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'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.
-
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.
-
Not being funny but why would you want to do that anyway! ???
-
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.
-
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. ;)
-
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.
-
If that't the case maybe you would do well to invest in an UPS to maintain your power should an outage occur.
-
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.
-
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.
-
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.
-
As you say it is a well logged stumbling block. I have had a few little niggles myself recently but I don't use it that much.
-
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.
Yup I did some testing and your right on the money. I hope a driver or bios update will fix this as all claimed functions need to work. BTW after disabling the the USB3 controller in the bios windows resumed using the same hibernate data that previously failed. Just for fun I tried to reproduce a no boot using hibernate but it booted right up even though I had cycled the PSU power switch. Weird as I would have guessed it would have also failed with the USB3 controller enabled in the bios.
Bill
-
Ah, the joys of being early adopters ;D
-
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.
Yup I did some testing and you're right on the money. I hope a driver or bios update will fix this as all claimed functions need to work.
If you have a moment to relay the bug to Gigabyte, they might take it more seriously if they get multiple reports (I've already sent them one).
BTW after disabling the the USB3 controller in the bios windows resumed using the same hibernate data that previously failed. Just for fun I tried to reproduce a no boot using hibernate but it booted right up even though I had cycled the PSU power switch. Weird as I would have guessed it would have also failed with the USB3 controller enabled in the bios.
Good to know. I wondered about that too but wasn't motivated enough to test it. :)
-
By the way, station-drivers has a newer (2.0.20.0 WHQL) driver for the NEC USB3. I installed it this morning following a 0x9 crash during S3 (DRIVER_POWER_STATE_FAILURE, the first crash of any kind I've had since installing the X58A-UD3R nine days ago). No problems so far (I'm not actually using those ports yet), but I haven't tested to see if the new driver fixes the hybrid-power-off problem.
-
If you have a moment to relay the bug to Gigabyte, they might take it more seriously if they get multiple reports (I've already sent them one).
I did just that today. Lets see how long it takes for them to fix it. See copy of my explanation below.
Hybrid sleep aka STR+hibernate fails to resume if the USB 3 ports are enabled in the bios but only after a power interruption while in Hybrid sleep. I've already got the latest NEC USB 3.0 driver (2.0.4.0 2010-07-22) from the Gigabyte website installed. This happens with or without any devices plugged into the USB 3 ports.
To reproduce this problem S3 and USB 3 must be enabled in the bios.
Hybrid sleep must be enabled in windows. USB 3 driver above must be installed. From within Windows 7 64 bit give windows the sleep command (in my case the sleep button on my keyboard). Once the PC is off turn the PSU switch off for 1 minute and then back on. Now attempt to resume from Hybrid sleep. All you will get is a blinking cursor. If you force a power down by holding the power switch in for four seconds then power up and jump into the bios and disable the USB 3 ports. Then save and exit, windows will resume just fine using the same saved hibernate data. I tried to duplicate this problem using regular hibernate but it does not have problems resuming after a power interruption even with the USB 3 ports enabled in the bios. I would guess this is a bios issue of possibly a USB 3 driver issue.
Note normal S3 aka STR works fine on its own (I know it can't recover from a power loss) even with USB 3 enabled in the bios.
Thanks for your time
Bill
-
If you have a moment to relay the bug to Gigabyte, they might take it more seriously if they get multiple reports (I've already sent them one).
I did just that today. Lets see how long it takes for them to fix it. See copy of my explanation below.
Hybrid sleep aka STR+hibernate fails to resume if the USB 3 ports are enabled in the bios but only after a power interruption while in Hybrid sleep. I've already got the latest NEC USB 3.0 driver (2.0.4.0 2010-07-22) from the Gigabyte website installed. This happens with or without any devices plugged into the USB 3 ports.
To reproduce this problem S3 and USB 3 must be enabled in the bios.
Hybrid sleep must be enabled in windows. USB 3 driver above must be installed. From within Windows 7 64 bit give windows the sleep command (in my case the sleep button on my keyboard). Once the PC is off turn the PSU switch off for 1 minute and then back on. Now attempt to resume from Hybrid sleep. All you will get is a blinking cursor. If you force a power down by holding the power switch in for four seconds then power up and jump into the bios and disable the USB 3 ports. Then save and exit, windows will resume just fine using the same saved hibernate data. I tried to duplicate this problem using regular hibernate but it does not have problems resuming after a power interruption even with the USB 3 ports enabled in the bios. I would guess this is a bios issue of possibly a USB 3 driver issue.
Note normal S3 aka STR works fine on its own (I know it can't recover from a power loss) even with USB 3 enabled in the bios.
Thanks for your time
Bill
I received a reply from Gigabyte today and they claim they can't reproduce the problem. Here is their reply.
Dear Customer
Our team had attempted to replicate your issue without any success, we tested with the below configuration:
1. Set USB 3.0 Controller as enable in BIOS and enable Hybrid sleep in Win7
2. Put the PC to sleep mode.
3. Once the pc powers down, we turn off the PSU switch
4. After few second we turn on the PSU switch and power on the system
5. The system will then show the POST screen, continue with “Resuming Windows” and successfully loads into Windows.
Please provide us with procedure to replicating your issue
Do provide your system configuration as well
Hey Gary123 did you get a reply back from Gigabyte yet?
Bill
-
Hey Bill you must be special! They actually read your question and answered in English that makes sense ;D
I expect everyone will be getting that answer now they have copied it to the clipboard ;D
-
Bill, they told me the same thing. I wonder if they're using different BIOS or drivers, but I haven't asked them yet.
-
wow! I can't believe they've known about the USB3-RESUME FROM S3 HIBERNATION issue since October of last year and still no firmware or driver update has been released to address this flaw. My setup is fairly simple. One hard drive, 1 DVD drive, 12gb ram and an ATI HD5700 video card and Windows 7 64-bit. I don't have a problem reproducing the issue. I don't understand why Gigabyte does.
The issue is fairly straight forward and it's happening to more people than myself and not only this board from what I see.
All these threads report what seems to be the same issue:
http://forum.giga-byte.co.uk/index.php/topic,3866.0.html
http://forum.giga-byte.co.uk/index.php/topic,3721.0.html
http://forum.giga-byte.co.uk/index.php/topic,4101.0.html
:o
-
I do find it unusual in the Gigabyte always traded on their fast and excellent driver updating and that is one of the reasons I decided to move over to Gigabyte from Asus. There have been a couple of cases recently which have not been dealt with as well as we could have hoped. :-\
-
Just in case anyone needs this. Resume from hybernate/hybrid sleep was recently fixed with a USB 3 driver update.
You can see it here:
http://forum.giga-byte.co.uk/index.php/topic,3866.msg52045.html#msg52045
-
Thanks for the heads up there Diablito. I am sure there will be other members who find themselves in a similar position. ;)