Update:
I found a Microsoft hotfix for this problem link
 
Hey guys,
 
My computer has been hanging at the S3 sleep state.  It started last week sometime after I did a BIOS flash.  What I didn't realize was that I didn't need to do this flash since I already had the latest BIOS.  No harm was done except I lost a few settings.  
 
The real issue is that now my computer won't resume from the S3 sleep state.  I've done a little reading on the issue and made some adjustments to BIOS (below is a picture with relevant settings).  I also made adjustments to the windows power profile to allow S3 sleep.
 
Does anyone know what settings are specifically required to ensure S3 works?  
 

Yes, I have installed SP1.  That was also last week about the same time S3 stopped working.  I need to investigate.  Thanks for the tip.  Did anyone else experience problems with S3 after installing sp1 for Windows 7?

Success!
 
After a little research, I fount that this is a Sp1 problem not a hardware problem.  Here is a link to Microsoft's hotfix for the issue.  I must warn that Microsoft has not fully tested this hotfix, so use at your own risk.  The problem exists if your boot drive is connected to your motherboard through a third party controller that shows up as a  SCSIport miniport driver.  This is the case for Marvell controller used for 6Gb SATA III.  
 
Anyone running Windows 7 Sp1 having problems with hibernate or S3 sleep that has their boot drive connected to a Marvell controller should try this hotfix after backing up their data and creating a restore point.

I'm sorry to hear that the hotfix didn't work.  I hope Microsoft has a permanent fix for this problem quickly.  My only thought is to check for chipset driver updates.

lol I literally just started my own thread on this a second ago.  Then I saw this right below.  Ill have to give this a try.

I don't use the Mavell ports but I have the Marvell 91xx driver installed. I have the same problem after installing sp1. I have removed sp1 and wake up from sleep works. I wonder if I uninstall the driver then add sp1, will it wake up from S3 sleep like without sp1? I'll try this when I have time. Thanks

I tried removing the Marvell driver and reinstalled sp1 and it didn't help.  770 board won't resume from sleep (S3).  Is this only happening with the 770 or does anyone with a 760 or 759 have the problem after installing sp1 ?

I am having this problem too. However, hotfix http://support.microsoft.com/kb/2495523 does NOT fix my issue. It doesn't matter if the hotfix is installed or not, if my drives are plugged into the Marvell controller or not, the only thing that makes the issue go away is if uninstall Windows 7 SP1.
 
I opened a thread in the MS forums for this same issue: http://answers.microsoft....e011-9bac-78e7d160ad4e
 
EVGA FTW3 motherboard
Core i7 980x processor
Corsair Dominator DDR3 1600 (3 X 4GB) memory
EVGA GTX 580 Graphics
Crucial C300 SATA 6.0 Gps SSD
Western Digital 1 TB SATA 6.0 Gps data drive
Nvidia 3d Vision Kit
Windows 7 Pro x64

I recently ran into this issue and in my case I think the issue was related to my SSDs being on the Marvell ports (I first had them on the Intel SATA II ports with no problem).  I did not try the hotfix, but I went into the advanced power settings and disabled hybrid sleep.  Now, my computer will sleep and resume properly.  In my case it seems to be a hibernation issue and when hybrid sleep is enabled, it does write to the hibernation file before going to sleep.  You might try that to see if it helps in your scenario.

Please, someone give me a fix.

Please guys, go and post about your problems over at the MS forums. This is the only way this problem will get fixed. I already did so.

I have the same issues with SP1.  When I move the mouse to boot PC from S3 the hard drive light comes on for a second or two, then the fans start, motherboard displays F3 then 01 but that is as far as it gets. Pressing the reset button will make it boot in resume mode.

amatotg

Something to be aware of here is that resume from sleep issues can be caused by Windows and/or hardware.  This isn't just a single issue attributed to Windows 7 SP1 updating in ALL cased.
I own the X58 760 Classified and been having issues with resume from sleep since the BIOS versions started to hit the versions enumerated in the 70's.  Interestingly enough, 77 was kosher, even with SP1.  I just upgraded to 78 last night and now the problem isn't just intermittent like I had experienced back at BIOS 74 (if I remember the version correctly) but it's hard and fast now each and every time.  When the mobo goes through initial POST routines and your Power LED mysteriously comes on and then goes off just seconds after hitting the mouse, keyboard or power button - that's indicative of a BIOS/mobo POST initialization problem and has nothing to do with Windows - be it the base kernel or a SP.

eVGA needs to get this sorted because BIOS 78 with the Intel Rapid Storage firmware update has the problem in it - and like I said - it's hard & fast repeatable.

amatotg, EVGA may not be monitoring this thread. Please post this where they will read it:
EVGA X58 Motherboards - BIOS 78 Released
 

This is a problem with all X58 boards.  There are lots of posts about it on every motherboard site.  The root cause is that the DDR voltage is set to default during S3 sleep mode.  This is why many support people don't find this problem because it won't affect the system unless the RAM is overclocked to some combination of settings that require more than the default voltage and support people use stock settings.  For example, my Corsair XMS1600C7 RAM runs at 1.5v for the stock SPD table frequencies and S3 sleep will work with these settings.  As soon as the RAM is set to 1.65v for the XMP timings or above the S3 sleep fails.
 
You can easily prove this to yourself.  Hang a volt meter on the DDR test point and start your system with a configuration that requires a DDR voltage over 1.5 volts.  Enter S3 sleep and watch your volt meter drop from 1.65v (or whatever) to 1.5v during S3 sleep then move back to 1.65v when you resume.  This lack of voltage causes RAM corruption which is the true root cause of this problem (S3 is also call "suspend to RAM").  Most people report their CAS timing has changed after running this test.
 
Unfortunately, there is no work-around although some people say that some manufacturers have figured out how to fix it in BIOS for some boards.  I cannot verify this.
 
- D