What exactly is S1/S3 sleep? C1E? huh?

[LOUISSSSS]

without linking me to some tech jargon, can someone simply tell me what all these forms of sleep is?

the OS i'll be using is XP 32 and the MB is a gigabyte GA-P35-DS3P with the latest bios.

i'm receiving this mb back from Gigabyte as an RMA after i sent it in with freezing problems mostly under idle, although i did freeze once or twice while browsing the net and once during CS.

IF it IS a sleep problem, can someone tell me what i need to disable or how to fix it?

i dont care much about power saving or heat... and i'd prefer to leave my PC on 24/7 or simply shut it down.

 

[evident]

s1 does not really put your system in low power
s3 is a deep sleep that powers off everything except for RAM - when you power on the PC again, it turns on instantly where you left off.

c1e - http://techreport.com/articles.x/7998/2
FTA: C1E enhanced halt state ? Introduced in the Pentium 4 500J-series processors, the C1E halt state replaces the old C1 halt state used on the Pentium 4 and most other x86 CPUs. The C1 halt state is invoked when the operating system's idle process issues a HLT command. (Windows does this constantly when not under a full load.) Entering halt state, which is a lower-power state, will cut a CPU's power consumption and heat production. Intel's new C1E halt state is also invoked by the HLT command, but it turns down the entire CPU's clock frequency (via multiplier control) and voltage in order to work its mojo. This more robust halt state requires significantly less power than the old C1 implementation.
C1E halt cranks the CPU bus multiplier down to its lowest possible level on the 600-series processors, which is 14X, so a P4 660 processor with the C1E halt state active actually runs at 2.8GHz. I believe that C1E halt is also a binary condition invoked by the HLT command; it's either on or it's off.

basically, EIST and C1E throttle your CPU down when it's not being used (more power savings and lower heat)

from my experience, i had a gigabyte ep35-ds3r that was a POS when it came to sleep functions. it was a total deal breaker for me since i utilize the power saving features of my rig. whats the point of leaving it on 24/7 at night esp when i dont have anything downloading or doing any maint, i walk away from the computer when im done, it does some updates and maint, then puts itself to sleep.

i want the gigabyte to sleep and come back from sleep seemlessly and all it would do was crash and reboot on me after i resumed from sleep mode. i'd' never get a gigabyte again based on my experience w/ that board. i had a P5WDH and now an IP35Pro that handles sleep without a problem.

hopefully gigabyte got their act together now with their latest bios releases, because sleep is truly a great feature when implemented correctly!

 

[mchammer]

^he's throwin' it down. I would add, get a ups, it's a good investment. You could also use s4, suspend to disk (which has been replaced by hybrid sleep s3+s4 in vista and up for the speed of s3 plus the safety of s4).

 

[LOUISSSSS]

what does having a UPS have to do with these sleep states?

i have one btw...

 

[evident]

Originally posted by: LOUISSSSS
what does having a UPS have to do with these sleep states?

i have one btw...

i dont think it has anything to do w/ it directly other that you can sleep for a much longer amt of time if you have a ups connected and the power runs out...

 

[BonzaiDuck]

Just a wee bit off topic here, but I think my query is related.

For years, I've kept a file-server on our home network. I'm getting ready to upgrade it substantially, excluding the old full-tower case and the fairly new Antec PSU.

For all that time, being left running 24/7/365 -- the server nominally consumed between 90W and 150W.

Ideally, I'd like to set up the system to power down after so much time, and power up when a workstation on the LAN attempts to access it.

Anyone have any experience in this matter? Motherboards previously used with this server either didn't have gigabit-LAN built-in, or just didn't do it.

 

[mchammer]

Originally posted by: evident

Originally posted by: LOUISSSSS
what does having a UPS have to do with these sleep states?

i have one btw...

i dont think it has anything to do w/ it directly other that you can sleep for a much longer amt of time if you have a ups connected and the power runs out...

For s3 this is true, for s4 or the modern s3/s4 hybrid sleep, a ups is not needed. The big benefit is that if that you are working (s0 state) you have time to shut down without losing any work, plus it will protect the pc from under and over voltages which can lead to reboots and be hard on the components over time (especially hard drives imo).

btw, OP: XP does not have hybrid sleep. If you are having problems, take a conservative route.

1. Set your sleep state in the bios to S3, not S1.
2. In Windows enable hibernation.
3. Never use standby in windows (this is S3 which you say has been unreliable)
4. At night either shut down or use hibernate (S4) - (shut down + shift and you'll see it), (or shut down and hit h)
5. Set your ups to go into hibernate after say 10 minutes of power loss. You don't need any software for this, hook it up and windows will recognize it and there will be a new tab in power options. (This so if you are outside and the power goes out, no worries.)

Your problem doesn't sound like a sleep issue, but I would still be conservative as above to eliminate complications. If everything is fine later and you want to play around, fine.

 

[mchammer]

Originally posted by: BonzaiDuck
Just a wee bit off topic here, but I think my query is related.

For years, I've kept a file-server on our home network. I'm getting ready to upgrade it substantially, excluding the old full-tower case and the fairly new Antec PSU.

For all that time, being left running 24/7/365 -- the server nominally consumed between 90W and 150W.

Ideally, I'd like to set up the system to power down after so much time, and power up when a workstation on the LAN attempts to access it.

Anyone have any experience in this matter? Motherboards previously used with this server either didn't have gigabit-LAN built-in, or just didn't do it.

You will to have set the server to sleep or hibernate and then enable wake on lan. Gigabit isn't related as far as I know. Then the clients have to send the the "magic packet" to wake it up.

I haven't done this myself but I get the feeling this is one of those things that sounds like it should work with no big deal but in reality will be a PITA. (Like alot of things with PCs.) The people in home theater would know more.

 

[LOUISSSSS]

Originally posted by: mchammer

Originally posted by: evident

Originally posted by: LOUISSSSS
what does having a UPS have to do with these sleep states?

i have one btw...

i dont think it has anything to do w/ it directly other that you can sleep for a much longer amt of time if you have a ups connected and the power runs out...

For s3 this is true, for s4 or the modern s3/s4 hybrid sleep, a ups is not needed. The big benefit is that if that you are working (s0 state) you have time to shut down without losing any work, plus it will protect the pc from under and over voltages which can lead to reboots and be hard on the components over time (especially hard drives imo).

btw, OP: XP does not have hybrid sleep. If you are having problems, take a conservative route.

1. Set your sleep state in the bios to S3, not S1.
2. In Windows enable hibernation.
3. Never use standby in windows (this is S3 which you say has been unreliable)
4. At night either shut down or use hibernate (S4) - (shut down + shift and you'll see it), (or shut down and hit h)
5. Set your ups to go into hibernate after say 10 minutes of power loss. You don't need any software for this, hook it up and windows will recognize it and there will be a new tab in power options. (This so if you are outside and the power goes out, no worries.)

Your problem doesn't sound like a sleep issue, but I would still be conservative as above to eliminate complications. If everything is fine later and you want to play around, fine.

why would i set sleep state in bios to s3 if i should never use standby (s3) in windows?

 

[mchammer]

Originally posted by: LOUISSSSS


why would i set sleep state in bios to s3 if i should never use standby (s3) in windows?

I think because it's the standard setting that is always used in the bios these days. If you still find problems you could back it down to S1 in the bios.

Ideally, your issue won't be sleep related (perhaps a buggy driver, hardware, etc.) so that if things work for a while you could try s3 if you want to. I think on Windows XP though, s4 is more reliable and it is better to stick with that for only a small amount of extra waiting, which is fine if you do it one or two times a day.

However, as we all know, bios are poorly documented with bad manuals and inconsistent terminology and good tech support does not come with any product. These factors make an exact answer impossible to find at times. So basically what I have suggested is my best feeling for the situation.