- Jun 30, 2004
- 16,867
- 2,184
- 126
I had given up or dropped the idea of using sleep-states when I started OC'ing, and I also remember having trouble configuring it. That must have been several years ago.
Now I'm on a campaign to trim household power usage. There are three very active computer users here under the same roof, each with their own machine, and there is a WHS server.
It seemed that yesterday was a point of watershed progress after I read some few web-guides about the sleep feature. I was trying to enable all machines for S3 or S1&S3 "hybrid" sleep.
I've now enabled "WOL" on all the machines, and with some simple shareware software [WakeMeOnLAN], I can wake the machines throughout the house from my single workstation here. Which . . . enables me to do maintenance via Remote Desktop on the machines when they're not being used.
One of the machines set to sleep after an hour is an E8600 with an EVGA 132-CK-NF78 780i motherboard, and is rock-solid. It goes in and out of hybrid sleep and remains totally stable.
The other uses a much cheaper Gigabyte mATX motherboard [LGA775/C2Q-capable]. It only has S1 or S3 -- not S1&S3. Had it set up yesterday for S3 sleep, and it would reliably wake properly throughout the day. But after sleeping overnight -- about 12 hours -- I couldn't wake it remotely and went upstairs to investigate. When I hit the power-button (quickly) to wake it, it cold booted! So it didn't maintain itself in S3 "save to RAM" mode.
Couple web-searches suggest that people began having trouble with this feature as their computers got a bit older. Right now, I'm testing the S1 state on the latter computer to see if it remains stable.
Any ideas? Comments?
Now I'm on a campaign to trim household power usage. There are three very active computer users here under the same roof, each with their own machine, and there is a WHS server.
It seemed that yesterday was a point of watershed progress after I read some few web-guides about the sleep feature. I was trying to enable all machines for S3 or S1&S3 "hybrid" sleep.
I've now enabled "WOL" on all the machines, and with some simple shareware software [WakeMeOnLAN], I can wake the machines throughout the house from my single workstation here. Which . . . enables me to do maintenance via Remote Desktop on the machines when they're not being used.
One of the machines set to sleep after an hour is an E8600 with an EVGA 132-CK-NF78 780i motherboard, and is rock-solid. It goes in and out of hybrid sleep and remains totally stable.
The other uses a much cheaper Gigabyte mATX motherboard [LGA775/C2Q-capable]. It only has S1 or S3 -- not S1&S3. Had it set up yesterday for S3 sleep, and it would reliably wake properly throughout the day. But after sleeping overnight -- about 12 hours -- I couldn't wake it remotely and went upstairs to investigate. When I hit the power-button (quickly) to wake it, it cold booted! So it didn't maintain itself in S3 "save to RAM" mode.
Couple web-searches suggest that people began having trouble with this feature as their computers got a bit older. Right now, I'm testing the S1 state on the latter computer to see if it remains stable.
Any ideas? Comments?
Facebook
Twitter