Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Extremely aggravating S3 problem
New Posts  All Forums:Forum Nav:

Extremely aggravating S3 problem

post #1 of 5
Thread Starter 
This problem showed up last Wednesday, and reared its ugly head three days ago. Windows 7 will not resume from sleep. I put the machine to sleep when I go to bed, with an alarm set in foobar2000 to wake the computer and play music. (it also does it when I manually resume with the power button)

When the alarm goes off (set to 9:30) the system comes on, but crashes immediately. Blank screen, no music from foobar, keyboard lights will not turn on when lock keys are pressed. I hit the reset switch, it reboots, says "Resuming Windows" instead of "Starting Windows," THEN works again.

Only recent hardware change is a GTX 260 to a 285, with a fresh reinstall of Windows and update to latest drivers. It worked for a week after that, then started doing this.

This is a problem because I need this alarm to wake me up for work, My fans have woken me the times it has done this, but they are not that loud and if I am sleeping deeply, they won't wake me, the call from my boss saying I'm fired will.

I have read about this being a problem with Windows 7, but I have been using Windows 7, Foobar scheduler with the exact same setup for two years now without a single problem. GPU is stock clocked, rest of system is totally stable, has been for 8 months.
Edited by mrfajita - 1/29/11 at 1:45am
Takatalvi
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7 860 4.0GHz Gigabyte p55a-ud3p EVGA GTX 580 4GB Ripjaws 
Hard DriveHard DriveOptical DriveCooling
Intel 530 Series 180GB Seagates HP SATA DVD-RW Cooler Master V6-GT 
OSMonitorKeyboardPower
Windows 7 Ultimate x64 HP LP2465 SIIG USB Multimedia (quite nice for $15) Corsair TX750W 
CaseMouse
Cooler Master 690 (modded) Logitech LX3 
  hide details  
Reply
Takatalvi
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7 860 4.0GHz Gigabyte p55a-ud3p EVGA GTX 580 4GB Ripjaws 
Hard DriveHard DriveOptical DriveCooling
Intel 530 Series 180GB Seagates HP SATA DVD-RW Cooler Master V6-GT 
OSMonitorKeyboardPower
Windows 7 Ultimate x64 HP LP2465 SIIG USB Multimedia (quite nice for $15) Corsair TX750W 
CaseMouse
Cooler Master 690 (modded) Logitech LX3 
  hide details  
Reply
post #2 of 5
I had this problem for a long time, I updated my bios and my problem went away.
post #3 of 5
I am also having this problem. Except my problems started AFTER I updated my BIOS. :/ I have yet to find a fix. I was recommended this link on another forum, you might want to read through it (it didn't help me however): http://www.vistax64.com/tutorials/63...-problems.html

I've pretty much given up on S3 sleep, and now I use S4 hibernate instead. Slower to resume, but I can live with it because it actually works.
post #4 of 5
Did you disable the bios setting: Resume from sleep? (or Wake From Sleep)
The Rock
(15 items)
 
  
Reply
The Rock
(15 items)
 
  
Reply
post #5 of 5
Thread Starter 
No but I seem to have fixed it by changing a BIOS setting for video BIOS POST on resume from S3.
Takatalvi
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7 860 4.0GHz Gigabyte p55a-ud3p EVGA GTX 580 4GB Ripjaws 
Hard DriveHard DriveOptical DriveCooling
Intel 530 Series 180GB Seagates HP SATA DVD-RW Cooler Master V6-GT 
OSMonitorKeyboardPower
Windows 7 Ultimate x64 HP LP2465 SIIG USB Multimedia (quite nice for $15) Corsair TX750W 
CaseMouse
Cooler Master 690 (modded) Logitech LX3 
  hide details  
Reply
Takatalvi
(15 items)
 
  
CPUMotherboardGraphicsRAM
i7 860 4.0GHz Gigabyte p55a-ud3p EVGA GTX 580 4GB Ripjaws 
Hard DriveHard DriveOptical DriveCooling
Intel 530 Series 180GB Seagates HP SATA DVD-RW Cooler Master V6-GT 
OSMonitorKeyboardPower
Windows 7 Ultimate x64 HP LP2465 SIIG USB Multimedia (quite nice for $15) Corsair TX750W 
CaseMouse
Cooler Master 690 (modded) Logitech LX3 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Windows
Overclock.net › Forums › Software, Programming and Coding › Operating Systems › Windows › Extremely aggravating S3 problem