ga-p35-ds3p trouble recovering from sleep?
Moderators: NeilBlanchard, Ralf Hutter, sthayashi, Lawrence Lee
ga-p35-ds3p trouble recovering from sleep?
Sometimes when I try to wake up my computer after putting into sleep mode, it goes into a strange state where it will continually try to boot, but fail after a few seconds without posting. The only way to recover is to disconnect power for 10 seconds and turn it back on.
Has anyone else seen this kind of behavior before?
Has anyone else seen this kind of behavior before?
I've never experienced multiple booting like that, but my WinXP laptop sometimes needs a lot of time recovering from hibernate. And it gets slower each time it does. I've developed the opinion that WinXP sucks when it comes to hibernate/sleep related stuff, but that may or may not be related to your problem.
Conroy, have you tried other BIOS versions, or other settings? Is it set to S3? If yes, did you change the setting after you installed Windows? XP or Vista?
Edit: Oops, it's in your sig, Vista!
mcv, not true.
My two XP PCs are put to S3 sleep evey night and I only do a restart 2-3 times a month. They do, however have lots of memory, 4GB each. One of them dualboots to Vista, that I don't use much, but is even better sleepwise.
I only shutdown my laptop.
Edit: Oops, it's in your sig, Vista!
mcv, not true.
My two XP PCs are put to S3 sleep evey night and I only do a restart 2-3 times a month. They do, however have lots of memory, 4GB each. One of them dualboots to Vista, that I don't use much, but is even better sleepwise.
I only shutdown my laptop.
thanks for the responses
I'm not sure if I should try an earlier bios, because this bios is the first one produced that officially supports my CPU.
Now that I think about it, I've never had consistently good experiences with sleeping any of my computers, including laptops. I sent a note off to Gigabyte, and I think I'll just ignore sleep mode unless they have some brilliant insight.
I assume that sleep mode also depends on the device drivers for all the other devices (video, hd, audio) all being able to handle it properly, so the problem could be hard to find.
I'm not sure if I should try an earlier bios, because this bios is the first one produced that officially supports my CPU.
Now that I think about it, I've never had consistently good experiences with sleeping any of my computers, including laptops. I sent a note off to Gigabyte, and I think I'll just ignore sleep mode unless they have some brilliant insight.
I assume that sleep mode also depends on the device drivers for all the other devices (video, hd, audio) all being able to handle it properly, so the problem could be hard to find.
Same problem with my GA-EP35-DS3R- can not resume from S3
Hi, first time poster here, did you find a resolution?
I have the exact same problem with my GA-EP35-DS3R, F2 BIOS. my specs are the following:
win xp
e8400
gskill 2x2gb pc1000
seasonic s12 600W
8800gt
raptor 160gb
i sent gigabyte an email through their website stating the following :
S3 sleep is a really important feature for me, and the DES was too, but i'm not too sure if it's worth RMAing the board over. any response from gigabyte saying they are aware of the situation and are addressing it would be great, but i only have another 15 days or so at newegg that i can RMA the board with. hopefully they will respond by then!
I have the exact same problem with my GA-EP35-DS3R, F2 BIOS. my specs are the following:
win xp
e8400
gskill 2x2gb pc1000
seasonic s12 600W
8800gt
raptor 160gb
i sent gigabyte an email through their website stating the following :
I am pretty sure it's an issue with higher clocked processors (such as our E8400's) causing the stability issue w/ these gigabyte boards.Hi,
I would like to point out an issue that many people are having with this motherboard. I just purchased it 5 days ago and would like to have it addressed, as it is a severe issue and I think the motherboard is good otherwise.
After setting up my PC and installing Windows XP SP2 and all the drivers, including gigabyte motherboard drivers on CD, i tried putting my PC into suspend (S3) state. upon resuming, everything seems to be okay, but in a few minutes, my computer powers off completely. If i turn my computer on again, once i get into windows, after a few minutes it will power off again. This loop will continue until i turn off the power supply completely for a few minutes then power on again. I am NOT overclocking any component on my board. I have all the power saving features enabled, such as C1E and EIST. My RAM is also NOT overclocked. everything is stock. I believe this is an issue related to the motherboard or BIOS. Another time this happens is when I try to run Dynamic Energy Saver software (DES). within the first few minutes of activating the software, the computer powers off completely similar to if i am resuming from S3, and the only way i can make the computer functional again is if i power off the power supply for a few minutes.
I am hoping this is an issue that your engineers can troubleshoot and address with a BIOS update, as gigabyte is heavily marketing the DES energy saving feature and 45nm CPU support. I would like to be able to use all of the advertised features of the motherboard, such as S3 suspend, and DES and power saving features of my CPU.
In summary-
When suspending my PC in S3 , upon resuming, computer powers off completely within a few minutes. Powering it on again will just make it shut off within a few minutes in windows.
When installed DES software, upon activating it, computer powers off completely within a few minutes. Powering it on again will just make it shut off within a few minutes in windows.
The only way to get out of this loop is to turn off power supply for a few minutes then turn it back on.
I hope that your engineers can troubleshoot and address this issue, as it is very important to me and many other Gigabyte motherboard users out there, who want to take advantage of suspending their PC and using the DES software.
Thanks,
Dave
S3 sleep is a really important feature for me, and the DES was too, but i'm not too sure if it's worth RMAing the board over. any response from gigabyte saying they are aware of the situation and are addressing it would be great, but i only have another 15 days or so at newegg that i can RMA the board with. hopefully they will respond by then!
Oops, I must have turned off the subscription for this thread by mistake, since I never got notified that it was being responded to.
I did find sort of a resolution for this issue, but it was no good for me:
http://forums.anandtech.com/messageview ... id=2087030
In short, the problem seems to be related to BIOS revisions. Someone using the DS3P rev 1.1 did testing using various BIOS versions and found that versions F7 and earlier were fine, while F8 and later had sleep problems.
I need F9 for E8400 support, so it doesn't really help me directly yet, but it's good to know.
I think cold boots must be a different issue...
I did find sort of a resolution for this issue, but it was no good for me:
http://forums.anandtech.com/messageview ... id=2087030
In short, the problem seems to be related to BIOS revisions. Someone using the DS3P rev 1.1 did testing using various BIOS versions and found that versions F7 and earlier were fine, while F8 and later had sleep problems.
I need F9 for E8400 support, so it doesn't really help me directly yet, but it's good to know.
I think cold boots must be a different issue...
I have a P35-DS3 and have the same problem when resuming from S3 in Windows XP. However, the problem goes away completely under Vista Home Premium 64-bit. Resuming in Vista has worked every single time since I bought the board a few months ago.
I'm using the latest BIOS (F12), an E6600 @ 3.2GHz ( 400*8 ) and 8GB DDR2-800 5-5-5-15.
I'm actually surprised that it works so well [in Vista] even after such an overclock.
I'm using the latest BIOS (F12), an E6600 @ 3.2GHz ( 400*8 ) and 8GB DDR2-800 5-5-5-15.
I'm actually surprised that it works so well [in Vista] even after such an overclock.
-
- *Lifetime Patron*
- Posts: 1809
- Joined: Sat Apr 24, 2004 1:45 am
- Location: At Home
I have a GA-P35-DS3R Rev 2.0 with BIOS F11 and Standby (S3) with XP Pro SP2 is working fine for me as it has on all my Gigabyte boards. The FSB has been raised from a stock 200 to 250.
Any board that fails to manage standby is useless for me and I’d RMA it.
I did have a problem with an M-Audio Audiophile 24/96 PCI card that broke standby support as the drivers don’t support it! Needless to say that has gone the way of the (e)bay. I find it hard to fathom a company that can’t be bothered to support standby on an entry level card that supports DTS/DD pass-through. i.e. it’s aimed not just at musicians.
Any board that fails to manage standby is useless for me and I’d RMA it.
I did have a problem with an M-Audio Audiophile 24/96 PCI card that broke standby support as the drivers don’t support it! Needless to say that has gone the way of the (e)bay. I find it hard to fathom a company that can’t be bothered to support standby on an entry level card that supports DTS/DD pass-through. i.e. it’s aimed not just at musicians.
smiling crow, what cpu are you running on? i am pretty convinced this problem is related somehow to the FSB. e8400 stock fsb is 333. there might be some threshold where the S3 standby becomes unstable.... i am pretty close to RMAing this board, but holding out to see what gigabyte can do, i sent them an email detailing my issues.
-
- *Lifetime Patron*
- Posts: 1809
- Joined: Sat Apr 24, 2004 1:45 am
- Location: At Home
sent them an email a few days ago saying the following
received email from them today
Thanks for your reply!
Hi,
I would like to point out an issue that many people are having with this motherboard. I just purchased it 5 days ago and would like to have it addressed, as it is a severe issue and I think the motherboard is good otherwise.
After setting up my PC and installing Windows XP SP2 and all the drivers, including gigabyte motherboard drivers on CD, i tried putting my PC into suspend (S3) state. upon resuming, everything seems to be okay, but in a few minutes, my computer powers off completely. If i turn my computer on again, once i get into windows, after a few minutes it will power off again. This loop will continue until i turn off the power supply completely for a few minutes then power on again. I am NOT overclocking any component on my board. I have all the power saving features enabled, such as C1E and EIST. My RAM is also NOT overclocked. everything is stock. I believe this is an issue related to the motherboard or BIOS. Another time this happens is when I try to run Dynamic Energy Saver software (DES). within the first few minutes of activating the software, the computer powers off completely similar to if i am resuming from S3, and the only way i can make the computer functional again is if i power off the power supply for a few minutes.
I am hoping this is an issue that your engineers can troubleshoot and address with a BIOS update, as gigabyte is heavily marketing the DES energy saving feature and 45nm CPU support. I would like to be able to use all of the advertised features of the motherboard, such as S3 suspend, and DES and power saving features of my CPU.
In summary-
When suspending my PC in S3 , upon resuming, computer powers off completely within a few minutes. Powering it on again will just make it shut off within a few minutes in windows.
When installed DES software, upon activating it, computer powers off completely within a few minutes. Powering it on again will just make it shut off within a few minutes in windows.
The only way to get out of this loop is to turn off power supply for a few minutes then turn it back on.
I hope that your engineers can troubleshoot and address this issue, as it is very important to me and many other Gigabyte motherboard users out there, who want to take advantage of suspending their PC and using the DES software.
Thanks,
Dave
received email from them today
just replied to them again asking if they could test for themselves an e8400 and this board.Did you checked to make sure there are no overheating issue and cpu temperature does not exceed 60c at any time?
Also the S3 resume patch was installed from the driver disc?
Thanks for your reply!
unfortunately, the s3 resume patch does not solve my problem. my computer still powers off within minutes after i resume from s3 suspend and using the DES software.
my CPU is definitely not overheating, i do not have a fan connected to the motherboard (my fan is connected directly to power supply). i disabled all of the bios fan controls and monitors, and set cpu threshold to 70 degrees. my cpu never goes over 38. also, the rest of my hardware was able to suspend and resume fine on my previous motherboard (intel 975x based P5WDH from Asus) so my logical conclusion is that there is a bug in the EP35-DS3R's bios. is it possible for gigabyte to perform these tests with that motherboard and 45nm E8400 CPU?
your config is very similar to mine too. can you try suspending for a long period of time ( such as overnight or a few days) and see what happens?Hifriday wrote:I just put together a GA-EP35-DS4 (believe it is quite similar). So far no problems resuming from suspend with an 8400 at 333 or 400 FSB.
F2 Bios, 8800GT, 2x2GB 6400, Seasonic, Win XP
what type of RAM do you have? and do you have any special bios settings?
-
- *Lifetime Patron*
- Posts: 1809
- Joined: Sat Apr 24, 2004 1:45 am
- Location: At Home
I just tried running it at 6x333 and it seemed to go into standby okay but it refused to return. I had to switch it off at the power supply and on restarting the BIOS had reset itself to 200 FSB. Not good as I was hoping to upgrade to an E7200 (266 FSB, 3MB cache) when they are released and run it at somewhere between 333 and 400 FSB. I shall contact Gigabyte as the more people that do the more chance they will fix this problem.evident wrote:smiling crow, what cpu are you running on? i am pretty convinced this problem is related somehow to the FSB. e8400 stock fsb is 333. there might be some threshold where the S3 standby becomes unstable....
they just replied to me:
i replied backHow about if the DES software is not launched and has been disable, it will still shut off?
Any settings which you have tweak in the bios please restore it back to factory default.
Thank you again for your quick response.
Yes. this happens if the DES software is not even installed, and all the bios settings are default, AND right after a fresh install of windows xp sp2, with the appropriate drivers installed, of course. In addition to default bios settings, i've also tried disabling C1E and EIST in the bios because i thought that they may be causing issues, but i still have the same problems.
i have been posting on various forums and it seems that many people are having similar issues. I am the user "evident"
http://forums.anandtech.com/messageview ... TARTPAGE=1
viewtopic.php?t=46009
I have suspended it overnight (but not a few days since I use it daily) and it resumes without issue. I have the DES software installed and driver is loaded, but DES is not turned on (makes very little difference in power consumption anyways). I also have the extra molex plugged in to the mb.
I am using OCZ Titanium PC6400 CL4 RAM. RAM settings are in BIOS on auto, it defualts to CL5 by SPD and 5:6 multiplier (ie 800/960). FSB is also set to auto, I'm changing it in XP with EasyTune5Pro supplied on the driver CD. Believe most other BIOS left at default settings.
One odd behavior I did notice, is that after changing/saving the BIOS settings, the system reboots but will power down immediately before powering up again (maybe 1-2 cycles). Maybe this has something to do with writing to the dual bios? At first I thought there was compatibility problems with my Seasonic, but since this only happens when BIOS is changed I am thinking this is normal behavior.
Also when I first installed a SI128SE CPU cooler, suddenly EasyTune's OC functions were disabled and told me the board didn't allow OC!! I thought maybe the backplate was contacting some of the cap feet on the backside or maybe the frame was touching components on the topside, but didn't see this. In anycase reinstalling the heatsink solved this problem. If you have a backplate/frame cooler you might want to insure all components are clear?
I am using OCZ Titanium PC6400 CL4 RAM. RAM settings are in BIOS on auto, it defualts to CL5 by SPD and 5:6 multiplier (ie 800/960). FSB is also set to auto, I'm changing it in XP with EasyTune5Pro supplied on the driver CD. Believe most other BIOS left at default settings.
One odd behavior I did notice, is that after changing/saving the BIOS settings, the system reboots but will power down immediately before powering up again (maybe 1-2 cycles). Maybe this has something to do with writing to the dual bios? At first I thought there was compatibility problems with my Seasonic, but since this only happens when BIOS is changed I am thinking this is normal behavior.
Also when I first installed a SI128SE CPU cooler, suddenly EasyTune's OC functions were disabled and told me the board didn't allow OC!! I thought maybe the backplate was contacting some of the cap feet on the backside or maybe the frame was touching components on the topside, but didn't see this. In anycase reinstalling the heatsink solved this problem. If you have a backplate/frame cooler you might want to insure all components are clear?
That bios thing is normal behavior i think... esp if it isnt' causing you any issuesHifriday wrote:I have suspended it overnight (but not a few days since I use it daily) and it resumes without issue. I have the DES software installed and driver is loaded, but DES is not turned on (makes very little difference in power consumption anyways). I also have the extra molex plugged in to the mb.
I am using OCZ Titanium PC6400 CL4 RAM. RAM settings are in BIOS on auto, it defualts to CL5 by SPD and 5:6 multiplier (ie 800/960). FSB is also set to auto, I'm changing it in XP with EasyTune5Pro supplied on the driver CD. Believe most other BIOS left at default settings.
One odd behavior I did notice, is that after changing/saving the BIOS settings, the system reboots but will power down immediately before powering up again (maybe 1-2 cycles). Maybe this has something to do with writing to the dual bios? At first I thought there was compatibility problems with my Seasonic, but since this only happens when BIOS is changed I am thinking this is normal behavior.
Also when I first installed a SI128SE CPU cooler, suddenly EasyTune's OC functions were disabled and told me the board didn't allow OC!! I thought maybe the backplate was contacting some of the cap feet on the backside or maybe the frame was touching components on the topside, but didn't see this. In anycase reinstalling the heatsink solved this problem. If you have a backplate/frame cooler you might want to insure all components are clear?
-
- Posts: 286
- Joined: Sat Dec 09, 2006 9:45 pm
- Location: Montréal, Canada
My computer is currently refusing to wake from sleep. I tested the ram with memtester86+ and it detected errors, but only when the two sticks of ram are in together. When i test one stick at a time, they test without error but still will note wake from sleep. It worked at one point but then stopped working. You should get your memory tested too.
sighTry the F3 beta bios to see if it'll make any difference
http://www.gigabyte.com.tw/Sup...Type=BIOS&FileID=13367
Other than that only 3 other possibility which can cause it, check the video driver, card and power supply
i gave the f3 bios a shot already and it didnt work. and my vid card, driver and psu all worked fine before i got the gigabyte board. suspended/resumed w/p5wdh intel 975x with no problems. i tried using an 8500GT i have on my sis's PC and am sure that my PSU isnt causing the issue, but ill swap PSU's anyway. i hope they arent just trying to shift blame on some other component and give me the run-around. i am convinced it's an issue with the motherboard!
they wanted me to do a reinstall and just install the nvidia drivers and see what happens. ugh, i have ot go to japan on sat. anyone want to try this and follow up with what happens? maybe try some differnet nvidia drivers? i am almost certain this isn't the issue. this driver worked fine with my g*damn 975x board. maybe it doesn't play nice w/ p35 chipset, but that is highly unlikely..... gigabyte tech support is giving me the runaround and im starting to lose my patience
-
- *Lifetime Patron*
- Posts: 1809
- Joined: Sat Apr 24, 2004 1:45 am
- Location: At Home
From my experience it does sound as if the FSB speed may be the culprit. I’d try setting the FSB to 200 and see if standby works then.evident wrote:they wanted me to do a reinstall and just install the nvidia drivers and see what happens. ugh, i have ot go to japan on sat. anyone want to try this and follow up with what happens? maybe try some differnet nvidia drivers? i am almost certain this isn't the issue. this driver worked fine with my g*damn 975x board. maybe it doesn't play nice w/ p35 chipset, but that is highly unlikely..... gigabyte tech support is giving me the runaround and im starting to lose my patience
If people with CPUs with 1333 FSB that don’t support standby at stock speeds would try to see if they do work at lower FSB speeds it would help to diagnose this problem.
My E4500 works fine at 800 and 1,000 but fails at 1,333; I’ve yet to try 1,066.
so, how's everyone's experience w/ the ABIT IP35 Pro? I heard there are still some issues w/ the E8400 still... im pretty close to just exchanging the board... i don't know whether sleep is that big enough of an issue for me yet, but it's pretty important!!!!
im gonna try some things i shoulda tried earlier... not use IDE, only have one HD and as minimal config possible.... stay tuned... i may not do this till next week as im going to japan tomorrow
im gonna try some things i shoulda tried earlier... not use IDE, only have one HD and as minimal config possible.... stay tuned... i may not do this till next week as im going to japan tomorrow
-
- *Lifetime Patron*
- Posts: 1809
- Joined: Sat Apr 24, 2004 1:45 am
- Location: At Home