Trouble with gigabyte ep35-ds3r- suspend / standby problems

[evident]

gigabyte still didnt respond to me yet. how long does it normally take for them to respond to people?

 

[nylife]

once i asked them a question it took them 3 days to respond

 

[nullpointerus]

I found an interesting workaround for this problem.

This method will let you run the PC at a slightly lower FSB during normal use (and during suspend/resume), yet your FSB will automatically (and predictably) increase under load. So you can effectively overclock past 266 mhz FSB (or wherever your S3 suspend/resume wall is) and then get S3 working again.

Here's what you do:

1. Disable C1E/EIST.
2. Find a target o/c.
3. Find voltage, timings, etc. that are stable at this speed.
4. Lower FSB by a certain amount (i.e. 64 mhz?).
5. Enable C.I.A. 2 auto-overclock, which will bump the FSB up under load.

For example, here are the C.I.A. 2 levels on my board:

-- 266 FSB --( +20 )--> 286 FSB @ load w/ (1) Cruise
-- 266 FSB --( +32 )--> 298 FSB @ load w/ (2) Sports
-- 266 FSB --( +44 )--> 310 FSB @ load w/ (3) Racing
-- 266 FSB --( +52 )--> 318 FSB @ load w/ (4) Turbo
-- 266 FSB --( +64 )--> 330 FSB @ load w/ (5) Full-thrust

So here are my settings:

CPU ......... 8x
FSB ......... 266 MHz
C.I.A.2 .... Full-thrust
RAM ........ 2x multi, 5-5-5-15 (subtimings are auto.)
VPCIE ..... +0.1v
VFSB ....... +0.1v
VMCH ...... +0.1v
VDIMM .... +0.1v
VCORE .... 1.35v

This gives me:

266 x 8 = 2128
330 x 8 = 2660 (<-- when C.I.A. 2 kicks in, under full load)

So I can run my 330 FSB in games, yet have a stable S3 suspend/resume @ 266 FSB.

Of course, this probably does little for people who must run FSB above 333 mhz load to get a decent overclock, since the C.I.A. 2 boost seems to max out at 64 mhz.

Gigabyte really needs to fix this problem... :|


One other thing I found today...

Raising PCI-E voltage by 0.1v was the only thing that helped me hit higher FSBs (333 --> 345 mhz). All the traditional changes -- RAM timings, chipset voltage, etc. -- do not make my PC stable above 333 mhz. This was a reproducible result. In fact, none of my memory subtiming adjustments did anything for this little FSB wall.

I'm not recommending PCI-E voltage increases. I'm just mentioning them because it seems wierd. Does the board have some sort of problem supplying power to the PCI-E bus at high FSBs?

Raising PCI-E voltage had no effect on my S3 suspend/resume problems, unfortunately.

 

[evident]

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?

I have no overheating issues, my heatsink is cool to the touch and i'm reporting 27-3x at any particular time.
i noticed that s3 resume patch was on the disc and i installed it, but it didnt do anything... also, there are other folders on the disc as well to things i have no idea what they are
going to report back to them what i just said here...

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

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

 

[evident]

updated

 

[evident]

they just replied to me:

How 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.

i replied back Quote:

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/me...id=2157117&STARTPAGE=1

http://www.silentpcreview.com/.../viewtopic.php?t=46009

 

[nullpointerus]

Yep, I have smilingcrow's problem:

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.

I can confirm that this happens to me after clean installation (w/ drivers) after BIOS flash + clear CMOS. No standby at 6x333, but it works fine at 10x266 or even 6x300.

Boosting everything by 0.2v still doesn't make S3 work at a high FSB.

Nothing I've tried enables my PC resume from S3 at 333 FSB.

I've tried loosening memory timings, increasing vcore, increasing various board voltages, reflashing BIOS, clearing CMOS, reformatting and reinstalling Vista, etc. Nothing fixes this problem, except changing the FSB.

 

[nylife]

What version of bios is everyone on?
i am on F3b, not sure it makes a difference

 

[Xpoc]

lots of Gigabyte info here: http://forums.tweaktown.com/forumdisplay.php?f=69

"The GIGABYTE Technical Support forum is now open and ready for posts!

Please welcome Mr. Janus Yeh from GIGABYTE who will be here to answer your tech questions related to all GIGABYTE products."

Since Gigabyte doesn't have their own forum, this is another good one to add I guess.

 

[evident]

nylife: im running F2
xpoc: nice find. i'm going to be creating an account and be bitching over there as well! hopefully this issue gets some more attention

 

[nullpointerus]

I'm running the F11 BIOS, which is the latest for my P35-DS3R rev. 1.0.

 

[nylife]

so the problem seems to exist regardles of Bios version.
evident you can add that to your reply to Gigabyte in case they do ask

 

[evident]

just tried resuming from standby with Ubuntu 7.10. it just hangs at a black screen w/ blinking cursor. doesnt look like suspend/resume works there either, but im sure i dont have all drivers set up right for ubuntu either.

 

[evident]

Try 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

sigh

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. i am convinced it's an issue with the motherboard!

 

[evident]

they wanted me to do a reinstall and just install the nvidia drivers and see what happens. ugh. anyone have time to do this? i have to go to japan on saturday

 

[nylife]

i am hopefully getting my 9600gt today and will do a clean install. i will update the thread

 

[Doclife]

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).

UPDATE: Gigabyte wanted me to do a fresh intallation of Windows XP, all motherboard's drivers including the "enableusbs3xp" driver that was in the motherboard's driver CD and NOT to install ANY other application software on the hard drive.

I did all of that last night including installation of the driver for the video card, but the problem still persist. I still cannot resume from S3 standby mode. Increasing the voltages on the CPU, MCH, northbridge, PCIe bus did not help either. I'm waiting for Gigabyte to response now.

 

[evident]

any updates?

 

[nylife]

problem still exist, i went back to s1 mode
it is most likely something with bios/motherboard, like we all suspect

 

[evident]

hopefully i can still RMA. this is stupid. anyone use an IP35 pro here? how is it with suspend?

 

[nylife]

i am planning on keeping it, first i am to lazy to deal with return/exchange even though it was via egg so it would be easy, plus i do like the board otherwise and i rarely use s3 mode anyways, yes it would be nice for it to be working, but i can just shut it down if i really want to.
when i was picking the board those 2 were my choises the gigabyte and the ip35 pro and i decided to go with gigabyte, due to it being a little cheaper and officially supporthing the 45nm chips, where ip35 supports it and noone has any problems with it, but its not listed as supported yet and they have not released a bios update for it in a while
just my 2cents

 

[nerp]

Originally posted by: evident
hopefully i can still RMA. this is stupid. anyone use an IP35 pro here? how is it with suspend?

IP35-E here going into sleep, hybrid sleep and hibernation and resuming with ease.

 

[PaulProe]

I am experiencing the same problems using a GA-EP35C-DS3R. I disabled the Windows Auto-restart and it appears the error is an IRQL one. 0x00000a

No other drivers installed but the LAN, sound and Video and all the latest ones.

Not sure where to turn, the IRQL error translates to "something's broke somewhere"

Anyone have any suggestions?

Paul
----------------------------
Gigabyte EP35C-DS3R (2.1) F2
E6750 running at 2.66
Vcore - 1.35
Crucial Ballistix 2 Gig (1 Gig x 2 ) in slots 2 & 4
Vdimm +.3 (reports 2.196)
EVGA GeForce 7600GT


Temps running 25-30c

 

[Doclife]

I suggest everyone send an email to Gigabyte requesting them to resolve this issue. Only when more people experiencing this problem and written about it, then Gigabyte will acknowledge that the problem exist and try to resolve it (BIOS update). Below is the link to the Gigabyte support request web page.

http://ggts.gigabyte.com.tw/te...ntry=USA&SourceWeb=B2C

I have done everything that Gigabyte engineer told me to try but nothing work and it looks like that they are running out of ideas. It seems to me that the problem is systemic across the P35 lines of Gigabyte's motherboard and if it is fixable, it has to be a BIOS update.

 

[evident]

they want me to send my board in to have it "checked out", yet i've been telling them just torun a damn e8400 on their motherboards and they will see that its happening .