Can't POST over 270-280Mhz HTT with Gigabyte M55Plus-S3G (AM2) - Suggestions ?

**Vuco** · 06-14-2007, 03:27 PM

Hello everyone,

I'm having a small problem while OC-ing my PC.

The parts are:
AM2 x2 3600+ Windsor (200x10, 1.25V)
Gigabyte M55Plus-S3G (Rev1.0 with Nv 6100 IGP and 430 SB)
Using the IGP, no external GPU

Fortron 400W PNF model
Hitachi SATA2 HDD

The "problem" is that I can't boot while having the HTT set in BIOS over 280Mhz. Firstly, let me ask if someone has the board ? Can that someone boot over 280Mhz without problems ?

Next thing, I din't write what memory I have, cause I tried many of them, 2x512MB Crucial Ballistix (which went to 1150Mhz CAS4)
2x512 GoodRAM 667 Value (go to ~830Mhz CAS 5)
2x1GB Crucial Value 667 (go to 860Mhz CAS 5)
2x1GB Apacer 800 (~880 CAS5)
1x512MB Corsair (~900 CAS5)
2x1GB SuperTalent (~1050 CAS5)

And the board works great with the Crucial's, GoodRAM and SuperTalent with which it went to 270Mhz HTT without any problem, rock stable. Apacer and Corsair didn't go so good, bootable at 260Mhz, and not 270Mhz.

I tried all the memory dividers with all the memories (of course, some of them push the HTT on 1:2 divider cause of their limits), tried lowering the HT multy, tried putting in a PCI graphics card, raising the PCI-E frequnency (you never know

) raising Vcore and chipset voltage, lowering CPU multy...I'm not a n00b

but this is killing me (softly :p)....

Tried with clockgen in windows and it showed that the board could easily go over 300Mhz in Windows, stable of course (think I got to ~330Mhz without any problems) - so the conclusion is that something is stopping me.

What could it be, has anyone got an idea or a solution ? The BIOS, memory compatibility (

), memory dividers not working so good, what ?

The PSU is not a problem, it's one of Fortron's finest

, and it pushed a stronger PC without a problem (OC-ed E6600, 2GB, X1900XT and much more).

I, like don't have any more ideas. Does anyone have a solution ? A BIOS option that I didn't try to change ? Or is it simply the board and/or the BIOS ? Maybe the CPU that doesn't like some dividers ? It is a budget motherboard (chipset), but as I can see on the net, many Gigabyte boards are having a hard time booting over particulary frequency's...

Thanks in advance and sorry for a long post

Regards,
Sven

**freakBYnature** · 06-16-2007, 06:27 PM

See you have tried the chipset overvolt. Try the overvolt on hyperthreading as well if available. Seems to do the trick on A8N32-SLI DELUXE when going for high HTT, still when I'm not overclocking it, strangely enough. Understand you aren't a newbie, but the hyperthreading overvolt really surprised me on my mobo. Don't know if it will work on yours.

**Neon Biker** · 06-17-2007, 12:12 AM

Originally Posted by freakBYnature

Try the overvolt on hyperthreading as well if available.

You mean "hypertransport", right?

**freakBYnature** · 06-17-2007, 06:29 AM

Originally Posted by Neon Biker

You mean "hypertransport", right?

Yes that was what I meant... sorry... was up so late I almost saw the "transport" myself

**Vuco** · 06-17-2007, 02:30 PM

Originally Posted by freakBYnature

See you have tried the chipset overvolt. Try the overvolt on hyperthreading as well if available. Seems to do the trick on A8N32-SLI DELUXE when going for high HTT, still when I'm not overclocking it, strangely enough. Understand you aren't a newbie, but the hyperthreading overvolt really surprised me on my mobo. Don't know if it will work on yours.

Hey, thanks for answering

I tried to raise voltages on everything that has an option to raise

. Even tried to raise one by one. I think that voltage doesn't help. Had a feelin' that it does the opposite

Hell, will try it again, since the last try, I changed the BIOS to a newer version.

Thanks again

Regards,
Sven

**freakBYnature** · 06-17-2007, 03:54 PM

Originally Posted by Vuco

Hey, thanks for answering

I tried to raise voltages on everything that has an option to raise

. Even tried to raise one by one. I think that voltage doesn't help. Had a feelin' that it does the opposite

Hell, will try it again, since the last try, I changed the BIOS to a newer version.

Thanks again

Regards,
Sven

No problem with answering, that's what the forums all about

Like I said, don't know if it will work on your mobo, but it did to some extent on mine. I have a PSU problem, so I may be able to turn it off when I recieve my new PSU. But anyway, have you tried slacking up the TREF to 7.8 or 15.6? If running the tightest you also may be getting problems with your RAM when running high FSB's.

**Vuco** · 06-17-2007, 04:25 PM

I shouldn't have problems with my RAM, since I'm using lower memory dividers, so mem. frequency is under defoult settings. Also, the RAM is very loose, 5-5-5-15 2T, overvolted to 2.1V.

I don't remember if I have TREF option in my BIOS, I thought I saw it in the newest BIOS, but I'm not sure. Will look into it. If there isn't, than it's no help

EDIT:
Nope, no TREF in my current BIOS, or in the newest one

Tried again with the voltage bumps - no go, again. It came to 280mhz without a problem, and then cannot bump to 282Mhz. Even tried to 300 and 310 to rule out, FSB hole that some C2D mobos had

Oh well, once I get my phase going, will break records with clockgen

**freakBYnature** · 06-17-2007, 05:31 PM

Originally Posted by Vuco

I shouldn't have problems with my RAM, since I'm using lower memory dividers, so mem. frequency is under defoult settings. Also, the RAM is very loose, 5-5-5-15 2T, overvolted to 2.1V.

I don't remember if I have TREF option in my BIOS, I thought I saw it in the newest BIOS, but I'm not sure. Will look into it. If there isn't, than it's no help

EDIT:
Nope, no TREF in my current BIOS, or in the newest one

Tried again with the voltage bumps - no go, again. It came to 280mhz without a problem, and then cannot bump to 282Mhz. Even tried to 300 and 310 to rule out, FSB hole that some C2D mobos had

Oh well, once I get my phase going, will break records with clockgen

RAM problems always come from RAM itself, but sometimes from memory controller on CPU, and that's where slackening up some timings might give some effect - sometimes, not every

Async Latency and that other option I can't remember right might also be worth slacking up... those involving ns, like this; 11ns and 8ns... atleast on s939 that might be what it looks like, or 8ns and 6ns... the tighter the better, but it is likely to have an effect on your level of OC if they are set wrong from default

Test out one at a time!

**Vuco** · 06-18-2007, 07:57 AM

Tried today with another mobo and the same memory. It went to 310HTT without a problem, DDR2 533 divider, same memory.

So it's definitely a MBO problem. I give up, thanks for all the help, freakbynature, but I'll leave it like this. I tried almost every option to change to affect the OC, but no success. All in all, not a bad board, still can go to 2700-2800 witch is the max. of this Windsor on air and 1.55V.