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

2.8c overclocking

F

FalconSS

[H]ard|Gawd
Joined
Jul 2, 2004
Messages
1,297
Im having trouble overclocking my 2.8c... here's my specs:

thermaltake xaser 3 (7 fans)
Abit IC7-G max2
p4 2.8c
1gig cosair xms 2.2.2.5 (2x512)dual channel
radeon 9800pro 128

I have my ram on f1 setting in bios and it is 1:1

I locked my AGP:pCI ratio

if I bumped it up to 3.08 ... it won't boot unless I put the ratio to 5:4

when I had my 2 sticks of samsung pc2700 (2x256) not overclocked... I could get it up to 3.2 but i would be scared because I had stock cooling.

Im using a thermaltake volcano all copper heatsink, stock intel fan, and as5

My stock temps are 35-idle 50-load (doom 3 for 3 hours) temps go down VERY quickly after exiting doom 3... usually it is at 45* by the time I exit the game. the only reason Im saying 50 is because ive seen it up there once or twice.

can someone help me overclock? tips? hints? other people who have used this board??
thanks!
 
no...I don't know if abits accelarator does that itself though... I'll check but right now im at work.

does anyone else have close to my setup? any tips?

I really want to run at 3.2 for fear... If I can get it to work I will buy a better heatsink/fan combo... I am also planning on buying another gig of the same ram and a 6800gt/gs
 
bump

Im new to overclocking, Ive gotten it to 3.2 without raising the vcore on the older less powerful memory... maybe Im going to lower my accelerator down to auto and try it again. what do you think?
 
so you're overclocking from Windows or through the bios ?

You need to change the voltage on your ram and CPU at times ..

You bump up the voltage on the ram if you get blue screen with a 0x0000000 error and you bump up the voltage on the cpu when you get sudden restarts ...
 
overclocking through bios... what will happen is when I restart after the overclock, (even to 3.08) (220) it wom't post and will lock up before it detects my drives or ram... thats why I think I need to lower the ram down... its at 1:1 so maybe im just pushing it to hard. which would give my more performace? faster ram or higher cpu clock?
 
what's your pci:agp ratio .. is it definitely fixed ?

add more voltage to your ram and your cpu ... just a little bit

overclock it again and if it boots, drop the voltage on one of them and check which one locks.
 
im sure the ratio is fixed. I found that out a year ago when I was overclocking with my old ram. i'll tackle the voltage next. im leaving work now so I should be home in about 30 min... i'll tell how it goes. (though there I have dial-up instead of t1...BAH!)
 
I just lowered my ram settings to the auto on game accelerator. I bumped up my cpu to 3.220. bumped up voltage to 1.6. when I restarted all I got was a very long post beep and nothing happened. it beeped twice before I shut it down. any ideas? what should I raise the latencies to?
 
FalconSS said:
I just lowered my ram settings to the auto on game accelerator. I bumped up my cpu to 3.220. bumped up voltage to 1.6. when I restarted all I got was a very long post beep and nothing happened. it beeped twice before I shut it down. any ideas? what should I raise the latencies to?
Click to expand...

For starters, max your latencies out. Also turn off GAT, I find its very unstable when overclocking. I think the settings are Auto-Normal-Auto-Disable-Disable. Try raising your vdimm to 2.7v.

What BIOS version are you running, I have had drastically different overclocking results on different bios versions, old ones(>20) in particular
 
okay..update..

I am currently running a at 3.08 stable with no problems...here are my specs

agp : pci - fixed
5:4 ratio (220:178)
temps..idle : 37 (right now) (no oc was 35)
vcore - 1.575

If I bump it up to 3.220 (230) 14x ... my comp will post fine... first screen says 2.8 running at 3.22, memory ratio, agp : pci ratio, next screen, detects my raid fine... next screen shows irq stuff. when it goes to verify updat it never says update success like it normally would after a bios change, then when its supposed to be loading the windows xp load screen it just turns black. not black like the load screen but dark. then won't accept any commands... any ideas?


EDIT: I just bumped it up to 3.15 (225) ... its running fine (obviously) the temp right now is 39. why wouldn't it work at 230? 3.220?

Another EDIT: I bumped it up to (228) and it loaded windows, allowed me to put in my password, loaded everything then restarted. at (229) it loaded two bars of the windows loading screen then restarted at (230) it would load up to the loading screen but not it.

temp is 37 idle
 
when it restarts like that then you're having problems with stabilizing your cpu .. try bumping up the voltage on the cpu and check if it will post
 
Go download Memtest and burn it to a CD. Boot to the CD and see if you're getting any memory errors. If you are, than you can isolate the instability to your ram, then try messing around with latencies and voltages more.

1.6v should be enough to get most 2.8C's to 3.2, I think you vcore is enough. Like I said in my previous post, update your bios. My 2.4C wouldn't even break 2.7 with bios version 17(can't remember the exact version, but it was somewhere around there). As soon as I upgraded to the latest, I could go upto 3.4.
 
FalconSS said:
wait! you did a 1ghz overclock!?! whats your cooling?
Click to expand...

Koolance EXOS, I also have a Celeron D 320 2.4@3.8 on air ;)

Do you know the SLCode of you CPU? Download CPUID and check to see if its an D1 or an M0.
 
YAY! Im running at 3.22ghz! its kinda warm though... 39 idle. I bumped the vcore to 1.625 and the vdimm to 2.7. i'm going to go look up my id now.
 
family: F
Model: 2
Stepping: 5
Revision: M0


its an M0 ... what does that mean?
 
FalconSS said:
family: F
Model: 2
Stepping: 5
Revision: M0


its an M0 ... what does that mean?
Click to expand...

M0's use the gallatin core, same as xeons and extreme editions. Presumably, the non EE M0's are extreme editions that either failed the speed or cache test. Being that you need to run 1.625v to get to 3.2, i assume you have one that failed the speed test. M0's have a slightly larger die, allowing them to disipate heat better. My 2.4c is an my, they only came on the 2.4c and the 2.8c.
 
so your saying I have an EE?! is there any way to unlock those features? with the bigger dye I should be able to overclock better. I need a cooler to really see it though. Im going to try 3.4 when I get home from work. is there anything else I should know about overclocking it? you seem to have done an excellent job with yours.

so even though it failed as an extreme edition... does that mean its a worse p4? what was the speed test they put it through?

sorry: I thirst for knowledge
 
FalconSS said:
so your saying I have an EE?! is there any way to unlock those features? with the bigger dye I should be able to overclock better. I need a cooler to really see it though. Im going to try 3.4 when I get home from work. is there anything else I should know about overclocking it? you seem to have done an excellent job with yours.

so even though it failed as an extreme edition... does that mean its a worse p4? what was the speed test they put it through?

sorry: I thirst for knowledge
Click to expand...

There is no way to unlock the cache, sorry. The M0's are said to handle voltage better than a D1 also. I was able to get my 2.3C to 3.3 with stock cooling stock voltage.

When I built this system, I did alot of research into it. One of the things I learned was that with Intel systems low latencies are not as important that on an AMD system. So I tried to keep my ram 1:1. I bought some OCZ PC4200, and although the latencies are 3-4-4-8, they will run 1:1 up to 271mhz. Unfortunatly, it wont run 1:1 at 284fsb to keep my chip at 3.4. Maybe in the future I'll try to get ahold of some DDR1200 ram. I think my overclock is limited by my motherboard. The person who I bought this cpu from had it running at over 3.5, but I cannot run any faster than 284fsb.
 
so you think I should raise my latencies from 2.2.2.5. to something higher then try to go 1:1 instead of 5:4? Im only at 230 right now. I wish I could hit 250... 3.5 ghz! If I was running at 384... I would have a system going 3.9Ghz!
 
FalconSS said:
so you think I should raise my latencies from 2.2.2.5. to something higher then try to go 1:1 instead of 5:4? Im only at 230 right now. I wish I could hit 250... 3.5 ghz! If I was running at 384... I would have a system going 3.9Ghz!
Click to expand...

I'd try it, it can't hurt. But I'm getting a feeling that your processor may be near its limit.
 
im planning on getting a cooler and hopefully that will extend my overclock. what cooler do you prefer? (air cooling). I was thinking the thermaltake big typhoon. It should fit in my XaserIII. will it fit on a northwood 478?
 
FalconSS said:
so you think I should raise my latencies from 2.2.2.5. to something higher then try to go 1:1 instead of 5:4? Im only at 230 right now. I wish I could hit 250... 3.5 ghz! If I was running at 384... I would have a system going 3.9Ghz!
Click to expand...

try 5:4 and check if 250 will work at 1.7 V max .. If it's too hot the computer will shut down

good luck
 
I'm not sure if you have already done this but you need to disable auto restart in Windows so you can find out what your problem is.
 
right click on my computer and click on properties
in there click on the "Advanced" tab then click on "Startup and Recovery"
uncheck "Automatic Restart"

Now you're done!

When you're overclocking, if you ever get a 0x0000000 error then that's a memory based error, your latencies are either too tight or your voltage is too high or too low.
 
You must log in or register to reply here.
Back
Top