VoodooNinja Posted December 24, 2004 Posted December 24, 2004 Something really strange occurs with the voltages and CPU temps when I resume my computer from the S3 power management suspend to ram state. All the voltages and temps appear normal, I then suspend my system. Upon waking it up, the CPU temp is approx 10C higher, and the voltages have taken a nose dive. (Example - 12.03V becomes 11.66V) If I suspend the computer again, and wake it up, the voltages and temps are back to normal. Every other suspend leads to the odd reportings. Extremely unusual! Could someone set their suspend state to S3 in the BIOS and monitor Smart Guardian while doing a few suspends? I'm curious if this occurs with other users. I have tried all the available BIOS versions. Do I have a flaky board or is this a strange problem that most people aren't aware of. Thanks for any help in advance for trying to replicate this issue. Share this post Link to post Share on other sites More sharing options...
VoodooNinja Posted December 25, 2004 Posted December 25, 2004 Did I post this in the wrong forum? It's hard to believe that not one person who viewed this thread has a DFI 250GB mobo. It would only take a few minutes of your time to monitor your Smart Guardian readings and suspend your system a few times. (S3 mode) Share this post Link to post Share on other sites More sharing options...
Angry_Games Posted December 25, 2004 Posted December 25, 2004 no one uses S3 that I know of because of it's inherent flaws (ie: it hasnt worked correctly but for a few very minority users) ive never been able to get S3 to function properly and gave up a long time ago (yet i still try on each new board). i prefer to let the system shut down or just run with the monitor powered down. S3 states are NOT recommended for overclocking at all, same for AMD's Cool & Quiet. Share this post Link to post Share on other sites More sharing options...
VoodooNinja Posted December 25, 2004 Posted December 25, 2004 Thanks for your reply. I notice this issue with no overclocking. I have used S3 on my Asus A7N8X Deluxe mobo for the last two years with no issues.(overclocked XP2700+ @ 2436) So when I got this mobo, I just set it up the same. I really prefer S3 as it shuts the system down quickly and allows me to resume my work quickly. I have alot of fans, lights, and a water pump and I prefer to have them off when I take a break. Every user has their own preference. If the rare S3 user reads this, let me know your experience. Share this post Link to post Share on other sites More sharing options...
Nanosu Posted March 23, 2005 Posted March 23, 2005 I've been having this EXACT same problem. I started messing with suspend modes a couple of days ago and I was having problems with S3 resuming, and then just shutting down after a few seconds. After trying a few different things, I reloaded the optimum BIOS settings, turned it back on, and restarted. Suspend worked fine, so I went back into BIOS and started moving some settings back, setting my overclock back up etc. Just a a couple of things at a time. I turned it back on, hit suspend, and now it shut down again, but gave me a few seconds to see ITE Guardian which was up and showing about 65C. I verified that my fan was spinning, so I doubt it's actually that high. So, I guess what was causing it to shutdown was my having turned on the autoshutdown at 60c in bios. My voltages are also all over the place after resuming (my CPU voltage showed around 1.29 from 1.4 I had it set on), my 12v line went from 11.79 (as reported by ite guardian) to 11.21). I'll try putting it in and out of suspend a few times later on and see what happens. Share this post Link to post Share on other sites More sharing options...
Paulh Posted March 23, 2005 Posted March 23, 2005 no one uses S3 that I know of because of it's inherent flaws (ie: it hasnt worked correctly but for a few very minority users) ive never been able to get S3 to function properly and gave up a long time ago (yet i still try on each new board). i prefer to let the system shut down or just run with the monitor powered down. S3 states are NOT recommended for overclocking at all, same for AMD's Cool & Quiet. Hello, This is strange, never got it to work??? this works on any other computer?? (not overclocked). I think that you have a basic bios bug that you need to fix. By the way is there an official way to report bios bugs? Another thing that would not be so bad is to have more detailed release notes for each new bios release. Paulh Share this post Link to post Share on other sites More sharing options...
Nanosu Posted March 24, 2005 Posted March 24, 2005 I just tried setting my computer in standby and bringing it back several times. Each time I brought it back from suspend my temperature reading was different. The core of my system is: Athlon 64 3000+ Winchester Lanparty UT NF4 Ultra-D Corsair Value Ram 1GB Geforce 6600 FOrtron Blue Storm 500w Has anyone else had this problem or has anyone found a solution? Would the only solution be a bios update? Share this post Link to post Share on other sites More sharing options...
wadja Posted March 31, 2005 Posted March 31, 2005 Attached are screenshots before and after suspend(S3)/resume. If system is suspended during full CPU load - it shutdowns immediately after resume. After second suspend/resume cycle - voltage and temp readings are back to normal values. I tried to upgrade BIOS (really it was the only reason for me to upgrade BIOS to beta 1/28), but the problem is still here. Share this post Link to post Share on other sites More sharing options...
vv132 Posted April 1, 2005 Posted April 1, 2005 yep i get the same thing Share this post Link to post Share on other sites More sharing options...
VoodooNinja Posted April 1, 2005 Posted April 1, 2005 I see that I finally got some users with the same issue that generated this thread of mine. Share this post Link to post Share on other sites More sharing options...
Maarek_Stele Posted April 3, 2005 Posted April 3, 2005 Under stock bios it happens the same. I'm getting higher readings after s3, and after another standby readings go normal. Stopping ITE before s3 doesn't alter this situation, so it might have to do with onboard sensors/bios. On the same way flashing bios can alter my readings (overvolting as it done with this s3), but values will go normal after the next cold boot. Anyway, I can get it on s3, the first time it will resume instantly after I put it into standby. The next it will turn on after a few minutes, and no lan resume is enabled. EDIT: Going to hardware manager and disabling "allow the computer to turn off..." in the power properties for the onboard NIC got rid of those spontaneous wake ups altough now the NIC leds stay on. EDIT2: I just confirmed that if I leave "allow computer to turn off" enabled and try to access the computer with another computer from my lan I'll wake him up (NIC lights off before). But with that disabled, the NIC light remain on and the computer simply doesn't respond to lan calls. On both cases the "enable this device to bring computer out of standby" option is disabled. So this is either a prob with windows, the nvidia driver, or "WOL (PME#) From Soft-Off" in bios that is malfunctioning, because it's disabled on my bios. Sorry for going so OT, but if this info is usefull for someone it might be worth it Share this post Link to post Share on other sites More sharing options...
racinjimy Posted April 10, 2005 Posted April 10, 2005 reviving this old thread...... anyone with a newer bios seen this problem resolved? I am still running 1/25 as I have no issues with it. Smartguardian reads my voltages all over the place once I resume from standby mode Share this post Link to post Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now