Trouble with gigabyte ep35-ds3r- suspend / standby problems

[evident]

i replaced the stock thermal paste on the northbridge and southbridge w/ some arctic silver ceramique, it couldnt hurt, eh?

i was going to start overclocking soon, but i wanted to play around with the dynamic energy saver function first. has anyone else used this? every time i try to enable it, my computer just powers off completely.

on other unrelated notes, im starting to really hate my thermaltake armor. the push in clips to hold additional cards require too much force and i usually cut or hurt my fingers really bad. its alot less convenient than conventional screws at this point! i also had to remove the rear case fan from my armor because of the width of my thermalright xp-120 heatsink, double ugh.



UPDATE: i just wiped the hard drive, and did a clean reinstall of windows. before i could even install any of the dynamic energy saver, my computer powers off completely now for no reason about 3 minutes after i get into windows. this happened right after i put my computer in standby for the first time. I can no longer bring it up.... wtf?

UPDATE2: I went to bios and under power management i disabled HPET since i am not running vista. don't know if this will do anything. I am starting to get frustrated with this board. I just want this thing to be stable, be able to suspend and resume w/ no issues, while having my power management capabilities... is this too much to ask?

UPDATE3: i just did a mild overclock 400x9 =3.6ghz and it's stable so far w/ prime95 on for a day
but i still can't get suspend to work right. if i resume from suspend within an hour or a short period of time it seems to do fine. if i suspend overnight and resume in the morning, the entire system just shuts off.

does anyone have any suggestions? are there any standby/suspend experts here? If anyone has close to my config, can they test out their suspend and see if it works?

using win xp
e8400
gskill 2x2gb pc1000
seasonic s12 550W
8800gt
raptor 160gb

Update 4 and 5:

sent them an email a few days ago saying the following

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

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?

just replied to them again asking if they could test for themselves an e8400 and this board.

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?

found a similar thread but different gigabyte motherboardhttp://www.avsforum.com/avs-vb/showthread.php?t=734031

 

[evident]

bump, anyone else experiencing this?

 

[Doclife]

I experienced a similar problem with the P35-DS3R rev 2.0 motherboard when I tried to upgrade my system from the E4500 to E8400. Windows would load normally and I can see my desktop, but within a few seconds the computer would shut down abrubtly and the screen went blank.

To solve this problem, I have to go into the BIOS menu change the settings on "CPU C1E" and "CPU EIST" to "DISABLE". The system would run great and no more crashes with those 2 settings disabled.

I emailed Gigabyte and they think that the motherboard could not have contributed to the problem because all the motherboard does is to enable or disable the Intel power savings features that are built in to the CPU. I ended up returning the E8400 because I want to be able to use those power saving features.

 

[evident]

Originally posted by: Doclife
I experienced a similar problem with the P35-DS3R rev 2.0 motherboard when I tried to upgrade my system from the E4500 to E8400. Windows would load normally and I can see my desktop, but within a few seconds the computer would shut down abrubtly and the screen went blank.

To solve this problem, I have to go into the BIOS menu change the settings on "CPU C1E" and "CPU EIST" to "DISABLE". The system would run great and no more crashes with those 2 settings disabled.

I emailed Gigabyte and they think that the motherboard could not have contributed to the problem because all the motherboard does is to enable or disable the Intel power savings features that are built in to the CPU. I ended up returning the E8400 because I want to be able to use those power saving features.

man, i want to use those power saving feature too... which is why i bought the e8400 in the first place because it uses less power >_< i don't want to end up returning the cpu that will just create an even bigger hassle. i don't know what bios this board ships with on default, but i checked the gigabyte bios website and they have a F2 revision that says improved dynamic power savings or something... hopefully it will be a little more stable...

 

[evident]

updated:I went to bios and under power management i disabled HPET since i am not running vista. don't know if this will do anything. I am starting to get frustrated with this board. I just want this thing to be stable, be able to suspend and resume w/ no issues, while having my power management capabilities... is this too much to ask?

can someone who has this board or the p35-ds3r give me some feedback on their suspend/standby experiences? maybe see what bios settings you guys have too?

 

[Doclife]

Did you solve the crash problem yet ? I assume that you did and now you cannot resume from S3 standby ?

 

[evident]

Originally posted by: Doclife
Did you solve the crash problem yet ? I assume that you did and now you cannot resume from S3 standby ?

no, the problem still stands. it's weird. when i do a format and reinstall everything works fine. then when after the first time i put the system in standby and resume, the computer shuts down within 20 seconds of resuming from suspend, and from that point on after cold booting, the system just turns off completely after 20 seconds.

this board is ridiculous. it's my first gigabyte experience and it's making me wonder why i ever went away from asus abit and dfi!

 

[evident]

UPDATE3: I'm starting to think it's the on-board LAN causing the issues. started to think what i did right before the computer died, and every time i was surfing the web, or doing some lan type activity. i had prime 95 on for a while now, installed some games and did other things not requiring network card and it seems to be ok... is this a design issue or is it just adefective board?

 

[Doclife]

Although my system is running completely stable at 3.2GHz (291MHz x 11, see my signature) and I'm able to resume from S3 standby without any problems, I will experience the S3 standby resume issue like you do now if I change my settings from 291MHz x 11 to 320MHz x 10; however. My system still run at the same 3.2GHz clock speed with those 2 settings, but I cannot resume from S3 standby if my settings are at 320MHz x 10. Thus, I think that the motherboard is having problems waking up from S3 if the bus speed is greater than 300MHz

I suggest that you try to downclock your E8400 to something like 2.6GHz (290MHz x 9) and see if you can resume from S3 standby.

I have sent an email to Gigabyte and asked them to look into this issue because if the problem persist, it means that I cannot upgrade to E8400 (stock speed of the E8400 is 333MHz x 9 = 3GHz).

 

[evident]

I disabled the XD bit in the bios now , and i havent gotten this issue..... but i will give it some more time before this is the conclusive solution.... my next step is to GHOST THIS IMAGE so i dont have to suffer through another reinstall! lol

 

[Doclife]

Originally posted by: evident
I disabled the XD bit in the bios now , and i havent gotten this issue..... but i will give it some more time before this is the conclusive solution.... my next step is to GHOST THIS IMAGE so i dont have to suffer through another reinstall! lol

What XD bit are you talking about and where in the BIOS menu does it show ?

 

[evident]

advanced bios - no execute memory protect

 

[evident]

i just did a mild overclock 400x9 =3.6ghz and it's stable so far w/ prime95 on for a day

but i still can't get suspend to work right. if i resume from suspend within an hour or a short period of time it seems to do fine. if i suspend overnight and resume in the morning, the entire system just shuts off.

does anyone have any suggestions? are there any standby/suspend experts here?

 

[evident]

can anyone w/ the same mobo suspend? im thinking about rmaing / getting something else now ... =\

 

[nylife]

Originally posted by: Doclife
Although my system is running completely stable at 3.2GHz (291MHz x 11, see my signature) and I'm able to resume from S3 standby without any problems, I will experience the S3 standby resume issue like you do now if I change my settings from 291MHz x 11 to 320MHz x 10; however. My system still run at the same 3.2GHz clock speed with those 2 settings, but I cannot resume from S3 standby if my settings are at 320MHz x 10. Thus, I think that the motherboard is having problems waking up from S3 if the bus speed is greater than 300MHz

I suggest that you try to downclock your E8400 to something like 2.6GHz (290MHz x 9) and see if you can resume from S3 standby.

I have sent an email to Gigabyte and asked them to look into this issue because if the problem persist, it means that I cannot upgrade to E8400 (stock speed of the E8400 is 333MHz x 9 = 3GHz).

I have the same problem, except i do have Xeon E3110 which is pretty much E8400 and when i put computer to sleep in S3 mode, and then try to wake it up it will start initializing and will shut off again and then it will be never ending loop until i pull the plug and boot from scratch.

so for now i just switched to S1 mode
I am also running Vista 64 with Sp1 which i think made it worth then just regular Vista

 

[evident]

Originally posted by: nylife

Originally posted by: Doclife
Although my system is running completely stable at 3.2GHz (291MHz x 11, see my signature) and I'm able to resume from S3 standby without any problems, I will experience the S3 standby resume issue like you do now if I change my settings from 291MHz x 11 to 320MHz x 10; however. My system still run at the same 3.2GHz clock speed with those 2 settings, but I cannot resume from S3 standby if my settings are at 320MHz x 10. Thus, I think that the motherboard is having problems waking up from S3 if the bus speed is greater than 300MHz

I suggest that you try to downclock your E8400 to something like 2.6GHz (290MHz x 9) and see if you can resume from S3 standby.

I have sent an email to Gigabyte and asked them to look into this issue because if the problem persist, it means that I cannot upgrade to E8400 (stock speed of the E8400 is 333MHz x 9 = 3GHz).

I have the same problem, except i do have Xeon E3110 which is pretty much E8400 and when i put computer to sleep in S3 mode, and then try to wake it up it will start initializing and will shut off again and then it will be never ending loop until i pull the plug and boot from scratch.

so for now i just switched to S1 mode
I am also running Vista 64 with Sp1 which i think made it worth then just regular Vista

can you see if you have the same problems if you install Dynamic Energy Saver and try to activate it? I get the same symptom if i install the software and try to run that. i think they may be related, but i uninstalled it and am not using it for now.

 

[braddy752]

I would have a assumption for your problems
1) Your CPU cooler is not properly installed, resulting the CPU got overheated and shuts down automatically.. Maybe you would have to reinstall the CPU cooler again

Dynamic Energy Saver won't work if you overclocked your board..

 

[nylife]

Originally posted by: evident

Originally posted by: nylife

Originally posted by: Doclife
Although my system is running completely stable at 3.2GHz (291MHz x 11, see my signature) and I'm able to resume from S3 standby without any problems, I will experience the S3 standby resume issue like you do now if I change my settings from 291MHz x 11 to 320MHz x 10; however. My system still run at the same 3.2GHz clock speed with those 2 settings, but I cannot resume from S3 standby if my settings are at 320MHz x 10. Thus, I think that the motherboard is having problems waking up from S3 if the bus speed is greater than 300MHz

I suggest that you try to downclock your E8400 to something like 2.6GHz (290MHz x 9) and see if you can resume from S3 standby.

I have sent an email to Gigabyte and asked them to look into this issue because if the problem persist, it means that I cannot upgrade to E8400 (stock speed of the E8400 is 333MHz x 9 = 3GHz).

I have the same problem, except i do have Xeon E3110 which is pretty much E8400 and when i put computer to sleep in S3 mode, and then try to wake it up it will start initializing and will shut off again and then it will be never ending loop until i pull the plug and boot from scratch.

so for now i just switched to S1 mode
I am also running Vista 64 with Sp1 which i think made it worth then just regular Vista

can you see if you have the same problems if you install Dynamic Energy Saver and try to activate it? I get the same symptom if i install the software and try to run that. i think they may be related, but i uninstalled it and am not using it for now.

I never even installed the software in the first place, everything else works fine on the pc just the s3 sleep mode

 

[nylife]

Originally posted by: braddy752
I would have a assumption for your problems
1) Your CPU cooler is not properly installed, resulting the CPU got overheated and shuts down automatically.. Maybe you would have to reinstall the CPU cooler again

Dynamic Energy Saver won't work if you overclocked your board..

the board is overclocked but very very mildly only to 3.4(375x9) from the stock 3.0
I never installed Dynamic Energy, and i can see the point about CPU cooler as i did just install my Tuniq 120, but if it overheats how come i am not having any problems running windows or doing anything else for that matter its just the damn S3 sleep mode

 

[nullpointerus]

Originally posted by: Doclife
Although my system is running completely stable at 3.2GHz (291MHz x 11, see my signature) and I'm able to resume from S3 standby without any problems, I will experience the S3 standby resume issue like you do now if I change my settings from 291MHz x 11 to 320MHz x 10; however. My system still run at the same 3.2GHz clock speed with those 2 settings, but I cannot resume from S3 standby if my settings are at 320MHz x 10. Thus, I think that the motherboard is having problems waking up from S3 if the bus speed is greater than 300MHz

I suggest that you try to downclock your E8400 to something like 2.6GHz (290MHz x 9) and see if you can resume from S3 standby.

I have sent an email to Gigabyte and asked them to look into this issue because if the problem persist, it means that I cannot upgrade to E8400 (stock speed of the E8400 is 333MHz x 9 = 3GHz).

Yeah, I get the same problem with my GA-P35-DS3R v1.0 + E4400 when FSB is raised above 266 MHz. IIRC, I would get occasional S3 resume problems at 280 MHz; by 300 MHz, the system will never wake up. Moving to 333 MHz doesn't fix anything. The computer has to be powered off manually and allowed to recover itself via the normal boot process.

What a mess!

It'd be a real shame to lose sleep mode with a stock E8400. I wanted one of those!

 

[evident]

Originally posted by: braddy752
I would have a assumption for your problems
1) Your CPU cooler is not properly installed, resulting the CPU got overheated and shuts down automatically.. Maybe you would have to reinstall the CPU cooler again

Dynamic Energy Saver won't work if you overclocked your board..

nope

i have a thermalright xp-120 and the fan is always on.

I know DES won't work if i OC'ed my cpu. but even at stock, with DES turned on, it completely shuts my computer off within a few minutes of activating the feature.

 

[evident]

Originally posted by: nullpointerus

Originally posted by: Doclife
Although my system is running completely stable at 3.2GHz (291MHz x 11, see my signature) and I'm able to resume from S3 standby without any problems, I will experience the S3 standby resume issue like you do now if I change my settings from 291MHz x 11 to 320MHz x 10; however. My system still run at the same 3.2GHz clock speed with those 2 settings, but I cannot resume from S3 standby if my settings are at 320MHz x 10. Thus, I think that the motherboard is having problems waking up from S3 if the bus speed is greater than 300MHz

I suggest that you try to downclock your E8400 to something like 2.6GHz (290MHz x 9) and see if you can resume from S3 standby.

I have sent an email to Gigabyte and asked them to look into this issue because if the problem persist, it means that I cannot upgrade to E8400 (stock speed of the E8400 is 333MHz x 9 = 3GHz).

Yeah, I get the same problem with my GA-P35-DS3R v1.0 + E4400 when FSB is raised above 266 MHz. IIRC, I would get occasional S3 resume problems at 280 MHz; by 300 MHz, the system will never wake up. Moving to 333 MHz doesn't fix anything. The computer has to be powered off manually and allowed to recover itself via the normal boot process.

What a mess!

It'd be a real shame to lose sleep mode with a stock E8400. I wanted one of those!

so you think this is related directly to the FSB speeds? if so, that's pretty weak, and that implies that this board does not "truly" support 45 nm processors. it seems these new processors are causing probs on current boards, one way or another. the reason why i sold my p5wdh and got a p35 in the first place was to take adv. of the power saving features- eist and c1e were not available on my 975x board for the new 45nm procs. boo.
this also implies that DES feature will be buggy on new 45nm procs. gigabyte made a truly a crappy product then since they pushed this feature AND 45nm support. how do they expect people not to have this problem??

 

[nullpointerus]

Originally posted by: evident

Originally posted by: nullpointerus

Originally posted by: Doclife
Although my system is running completely stable at 3.2GHz (291MHz x 11, see my signature) and I'm able to resume from S3 standby without any problems, I will experience the S3 standby resume issue like you do now if I change my settings from 291MHz x 11 to 320MHz x 10; however. My system still run at the same 3.2GHz clock speed with those 2 settings, but I cannot resume from S3 standby if my settings are at 320MHz x 10. Thus, I think that the motherboard is having problems waking up from S3 if the bus speed is greater than 300MHz

I suggest that you try to downclock your E8400 to something like 2.6GHz (290MHz x 9) and see if you can resume from S3 standby.

I have sent an email to Gigabyte and asked them to look into this issue because if the problem persist, it means that I cannot upgrade to E8400 (stock speed of the E8400 is 333MHz x 9 = 3GHz).

Yeah, I get the same problem with my GA-P35-DS3R v1.0 + E4400 when FSB is raised above 266 MHz. IIRC, I would get occasional S3 resume problems at 280 MHz; by 300 MHz, the system will never wake up. Moving to 333 MHz doesn't fix anything. The computer has to be powered off manually and allowed to recover itself via the normal boot process.

What a mess!

It'd be a real shame to lose sleep mode with a stock E8400. I wanted one of those!

so you think this is related directly to the FSB speeds? if so, that's pretty weak, and that implies that this board does not "truly" support 45 nm processors. it seems these new processors are causing probs on current boards, one way or another. the reason why i sold my p5wdh and got a p35 in the first place was to take adv. of the power saving features- eist and c1e were not available on my 975x board for the new 45nm procs. boo.
this also implies that DES feature will be buggy on new 45nm procs. gigabyte made a truly a crappy product then since they pushed this feature AND 45nm support. how do they expect people not to have this problem??

I wouldn't generalize it that much yet. Doclife is in contact with Gigabyte, so maybe there'll be a way to isolate this problem and get it fixed with a BIOS update. This series of MB from Gigabyte is supposed to have excellent and stable power delivery -- especially for overclocking -- according to the reviews I've seen.

 

[nylife]

Hopefully new bios, can address all of the issues above

 

[evident]

Originally posted by: nullpointerus

Originally posted by: evident

Originally posted by: nullpointerus

Originally posted by: Doclife
Although my system is running completely stable at 3.2GHz (291MHz x 11, see my signature) and I'm able to resume from S3 standby without any problems, I will experience the S3 standby resume issue like you do now if I change my settings from 291MHz x 11 to 320MHz x 10; however. My system still run at the same 3.2GHz clock speed with those 2 settings, but I cannot resume from S3 standby if my settings are at 320MHz x 10. Thus, I think that the motherboard is having problems waking up from S3 if the bus speed is greater than 300MHz

I suggest that you try to downclock your E8400 to something like 2.6GHz (290MHz x 9) and see if you can resume from S3 standby.

I have sent an email to Gigabyte and asked them to look into this issue because if the problem persist, it means that I cannot upgrade to E8400 (stock speed of the E8400 is 333MHz x 9 = 3GHz).

Yeah, I get the same problem with my GA-P35-DS3R v1.0 + E4400 when FSB is raised above 266 MHz. IIRC, I would get occasional S3 resume problems at 280 MHz; by 300 MHz, the system will never wake up. Moving to 333 MHz doesn't fix anything. The computer has to be powered off manually and allowed to recover itself via the normal boot process.

What a mess!

It'd be a real shame to lose sleep mode with a stock E8400. I wanted one of those!

so you think this is related directly to the FSB speeds? if so, that's pretty weak, and that implies that this board does not "truly" support 45 nm processors. it seems these new processors are causing probs on current boards, one way or another. the reason why i sold my p5wdh and got a p35 in the first place was to take adv. of the power saving features- eist and c1e were not available on my 975x board for the new 45nm procs. boo.
this also implies that DES feature will be buggy on new 45nm procs. gigabyte made a truly a crappy product then since they pushed this feature AND 45nm support. how do they expect people not to have this problem??

I wouldn't generalize it that much yet. Doclife is in contact with Gigabyte, so maybe there'll be a way to isolate this problem and get it fixed with a BIOS update. This series of MB from Gigabyte is supposed to have excellent and stable power delivery -- especially for overclocking -- according to the reviews I've seen.

i'm going to get in contact w/ gigabyte as well. I was hoping this would just be a single problem where i could just RMA, not some type of design issue, as i've heard rave reviews about these boards.

here is what i sent them through their website contact for support

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