• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

P4 Overclocking problem

Fanerim

n00b
Joined
Mar 17, 2004
Messages
20
Hy, I´m having trouble getting a P4 2.8C beyond 3.01 GHz, I use the Zalman 7000 AlCu and some passive RAM coolers.
If I set the divider to 5:4 I can get to 225 FSB but my memory runs at 182Mhz.
If I set it to 1:1 I can get to 215 FSB.
Had experience overclocking Athlons but now that i made the switch I´m a little confused.
The weird thing is that upping the voltages (nothing extreme, 1.575 CPU, 2,65 RAM) didn´t gave me more stability.
Is my memory holding me back?
With the divider set to 5:4 shouldn´t I be able to get higher FSB´s? The memory is rated to 200 and if it stills works at 182 there´s room for more O´cing, right?

Thanks!
 
Is it just not stable past 3.01, or it won't post or anything?

If it won't post, check to see if the Bus:AGP:pCI ratio is set to fixed.

Or try loosening your ram timings..
 
It won´t post past 3.01.
The FSB:AGP:pCI ratio is fixed
And the timings are 3-3-3-8.
 
hmm... your setup is very similar to mine, except the ram is a little different...

MAYBE increase the voltage and if it doesn't post even at like 1.65V... I'm not sure what the problem is..
 
Forgot to say that i have a 300W Enermax. All values are in range. Only two 120mm fan´s, VGA, and HD.
 
my suspicion is the ram. IC7 series boards are picky i heard. I have Corsair XMS PC3200 that runs stabe at 3.4, but my friends Kingston HyperX will run my CPU stable at 3.5. It seems like it wouldnt matter, because i've tried my ram at loose timings and a 3:2 divider, but i guess it's something with my mobo/ram compatibility.


Either that, you have a 'bad' CPU, or it's something else I'm not [h]ard enough to figure out! :p
 
DDR 400, so with a 5:4 divider I should be able to raise my FSB beyond 225 upping voltages if necessary, but i´m not.
 
I just posted the exact same question since I'm having the exact same problem!

The guys here advised me to up the RAM and CPU voltages, somewhere to CPU - 1.625 and RAM up to 2.8V. I haven't tried it yet as I'm still at work now, but I'll give it a bash later today:D

Try it - just watch your temps!
 
In the Abit support forums there´s a lot of posts about IC7 undervolting, or MBM5 reporting lower voltages than those set in the BIOS, it´s really anoying that ABIT won´t do anything about this issue, just like the temp´s issue in IC7/IC7-Max.
Bottom line, i don´t know what are my real voltages and temps are, so i´m kind of O´cing in the dark (dubidudida.....)
I´ll post results, if I get them...
 
Have you got the latest BIOS version. I think it's February 2004 version - can be found at Abit's website.

Shit, I know what you mean - overclocking by smell is pretty nerve-wrecking:D

Good luck - I'll be treading the same route tonight.
 
Things just got weird...
I can get to 225 FSB 1:1 RAM ratio with 1,6 Vcore and 2,6 VDDR, even though in BIOS I set it to 1,625 and 2,65.
With 5:4 ratio i can get to 230 FSB with same voltages.
The thing is that my board doesn´t allow to go beyond 2.8 in VDDR and at 2.7 i get visual artifacts in the POST screen.

A BIOS update would do any good?


a link to a similar thread, in case it helps someone else http://www.hardforum.com/showthread.php?s=&threadid=750806
 
You can try changing your mem timings to 3-4-4-8 and 2.8V in BIOS and see what you can get.
 
If your ram reaches 225 in sync, I would rule that out, that ram looks fine to me. Did you set your PSB strap correctly. If you have a C chip set it to 800.
 
i would try different ram, the ic7's are notorious for having issues with certain ram and async modes.
 
Back
Top