• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

I can not go past 220 fsb

H

hlonipha

Junior Member
Can anyone help me out here ? looking at my rig i should be able to overclock higher than 220 fsb
I have tryed lowering the multiplier and increasing the fsb and nothing past 220. I have never oc before , need some help here. if this helps.. when i go past 220 ej 11X222 computer reboots to safe settings.
I've also tryed 10x224 and same thing.

any help would be appreciatted

thanks
 
Lower your HT multiplier (sometimes called "LDT") from 5x to 4x, and then to 3x when you hit the next wall.
 
there is nothing there, when i click onto change that property in cmos machines locks and i have to hit reset to restart machine. also there is nothing there to change, as long as i dont try to get in it reads 5x.



update now i can see all the ht , i hit load fail safe option and it's all back to normal.

can someone help me with some setting to overclock this system ?
like memory settings, fsb, ht, etc...

thanks
 
You won't be able to overclock any higher until you lower your HT multiplier (LDT). There's a bug with teh BIOS you're using that causes it to lock up if you try to hit enter to lower the HT. What you need to do is go into the Cell menu in BIOS. Look for HT (LDT). It is set to 5x at default. You need to lower it to 4. Use the + and - or PgUP and PgDn keys to change the htt speed, DO NOT HIT ENTER.

Also, I found that I had to bump up the CPU voltage a bit to get a stable overclock past 220 FSB. Try setting it to 3.3% over.

I would set a divider on the memory too. Set DRAM to 166 and that will help your overclock until you find out how much your CPU can handle.
 
Originally posted by: icepik
You won't be able to overclock any higher until you lower your HT multiplier (LDT). There's a bug with teh BIOS you're using that causes it to lock up if you try to hit enter to lower the HT. What you need to do is go into the Cell menu in BIOS. Look for HT (LDT). It is set to 5x at default. You need to lower it to 4. Use the + and - or PgUP and PgDn keys to change the htt speed, DO NOT HIT ENTER.

Also, I found that I had to bump up the CPU voltage a bit to get a stable overclock past 220 FSB. Try setting it to 3.3% over.

I would set a divider on the memory too. Set DRAM to 166 and that will help your overclock until you find out how much your CPU can handle.
Click to expand...


will try this now,
i see that you have the same memory that i have , but i do not know what the 2-3-2 stand for in our memory properties, since you have the same MB can you tell me the name of the propeties to set the 2-3-2 values in ? also is it better to decrease the multiplier and increase the fsb as i've seen 9x280 or 10x 250 as to 11x236 ?

thanks
 
Hi hlonipha. Here's my memory settings.
Max Memclock (Mhz) = 166 - I like to run my memory with a divider so that I don't have to increase the voltage to get low timings.
1T/2T Memory Timing = 1T - Make sure you use 1T timing since 2T severely impairs the Athlon 64.
CAS# latency (TCL) = 2
RAS# to CAS# delay (Trcd) = 3
Min RAS# active time (Tras) = 10 - Anand found that the Athlon 64 performs best at this timing setting.
Row Precharge Time (Trp) = 2

Keep in mind that the Winchester 3000+ has a default multiplier of 9 and the 3200+ has a multiplier of 10. That might be why you see varying multipliers in people's signatures. Also, some people are able to push their overclocks slightly by lowering the multiplier and raising the FSB. I tried it but, didn't see any better stability. Your experience might be different. Go ahead and try it and it might give you better results. As many others have said, your mileage may vary when overclocking. Good luck!
 
Originally posted by: icepik
Hi hlonipha. Here's my memory settings.
Max Memclock (Mhz) = 166 - I like to run my memory with a divider so that I don't have to increase the voltage to get low timings.
1T/2T Memory Timing = 1T - Make sure you use 1T timing since 2T severely impairs the Athlon 64.
CAS# latency (TCL) = 2
RAS# to CAS# delay (Trcd) = 3
Min RAS# active time (Tras) = 10 - Anand found that the Athlon 64 performs best at this timing setting.
Row Precharge Time (Trp) = 2

Keep in mind that the Winchester 3000+ has a default multiplier of 9 and the 3200+ has a multiplier of 10. That might be why you see varying multipliers in people's signatures. Also, some people are able to push their overclocks slightly by lowering the multiplier and raising the FSB. I tried it but, didn't see any better stability. Your experience might be different. Go ahead and try it and it might give you better results. As many others have said, your mileage may vary when overclocking. Good luck!
Click to expand...


thanks for helping ... i got one more question, is i run the memory at 166 would not be slower performance than 200 ?

 
If you're running the 166 divider, it basically means your memory is running at a 5:6 ratio of the HTT (I think it's 5:6). Your bandwidth will be lower than if you had the memory set to the 200 divider (1:1 ratio), but the Athlon 64 platform is not very memory dependant, so you will not even notice the minute performance hit. Tighten your timings a little bit, and it will make up for the lower bandwidth as far as real world performance goes.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top