AMD 64 3000+ OC

  • Thread starter Thread starter rjd
  • Start date Start date

rjd

rjd

Associate
Joined
4 Mar 2006
Posts
168
Location
London
Hi

I have dipped my toe in the OC water by increasing the FSB from 200Mhz to 210Mhz (5% increase).

This has increased the Hyper Transport clock from 1000Mhz to 1050Mhz and the max CPU clock from 1800Mhz to 1890Mhz (9 x 210).

I still have C&Q enabled and the Vcore is unchanged at 1.04v at idle and 1.39v under load and temps are also unchanged.

This change has resulted in a small but noticeable ‘penalty free’ increase in performance and I would appreciate your comments and any help or advice in taking this a little further without increasing Vcore or temps. Is this possible?

I don’t game so I’m not after more speed at the expense of reliability or reduced CPU life expectancy.

Thanks for your help.
 
Last edited:
My 3000+ ran happily at 244x9 with the ram divider at 333 and the HT set at x4 with no adjustment to the Vcore :)
 
rjd said:
Hi

I have dipped my toe in the OC water by increasing the FSB from 200Mhz to 210Mhz (5% increase).

This has increased the Hyper Transport clock from 1000Mhz to 1050Mhz and the max CPU clock from 1800Mhz to 1890Mhz (9 x 210).

I still have C&Q enabled and the Vcore is unchanged at 1.04v at idle and 1.39v under load and temps are also unchanged.

This change has resulted in a small but noticeable ‘penalty free’ increase in performance and I would appreciate your comments and any help or advice in taking this a little further without increasing Vcore or temps. Is this possible?

I don’t game so I’m not after more speed at the expense of reliability or reduced CPU life expectancy.

Thanks for your help.


lower your ram from running at 200 to 166, lower your Hyper Transport clock from 1000 to 800, then overclock the CPU, dont increase the CPU voltage unless the system crashes when overclocked. a good way to test the system is to download and run a program called super Pi. it was designed for testing super computers so it does a good job of stressing your cpu, its only small and very free.

Venice 3000+ CPU`s can ALL do 2.5Ghz at least, on air. i had one for a long time :)
 
Thanks krooton and locutus12.

My mb in an Asus A8V Deluxe.

The RAM Memory Clock is currently set to Auto but can be changed to Limited 1:1 DDR 200, 4:3 DDR 266, 3:2 DDR ?, 5:3 DDR 333 or 2:1 DDR 400.

How do I set it to 166 or would limited 1:1 DDR 200 be ok?

Why is krooton recommending 333?

I'am starting to get confused please help.
 
It is not possible to overclock without raising temps. This does not mean you will fry your stuff if you overclock it - (only if you overclock it too much), and a better cooler can be used to deal with a hotter chip as and when neccessary.
 
rjd said:
Thanks krooton and locutus12.

My mb in an Asus A8V Deluxe.

The RAM Memory Clock is currently set to Auto but can be changed to Limited 1:1 DDR 200, 4:3 DDR 266, 3:2 DDR ?, 5:3 DDR 333 or 2:1 DDR 400.

How do I set it to 166 or would limited 1:1 DDR 200 be ok?

Why is krooton recommending 333?

I'am starting to get confused please help.


setting to 5:3 DDR 333 effectivly sets your rams clock speed at 166, thus when you push up the front side bus to clock your CPU, your also pushing up that 166 frequency, ram usually wont go above 215/220 fsb so downclocking the ram and Hyper transport gives you the headroom you need to push your CPU up and thus effectivly bringing the clock speeds of the ram and HTT to around their normal speeds as you increas the cpu fsb.

:)
 
Last edited:
Thank you for the link SiriusB.

I have had a quick look and it appears to be just what I was looking for so thanks again for pointing me in the right direction.

Reading your concise and clear explanation locutus12, I now feel I understand the basics.

Your help is very much appreciated.
 
You're welcome.

The information in the article I linked to can be a lot to take in. My advice would be to read the whole thing through, then go back and follow it while carrying out the steps it recommends.

Once you actually get your hands dirty and understand the relationships between the different settings it really is quite easy. The hard part is finding the best overclock within the limits of your hardware. Basically you need lots and lots of patience!

SiriusB
 
locutus12 said:
lies! house fires are fun.

teeheehee

rjd, I was using an AV8 with my 3000+, it'll do you proud, I could have easily done more than the 2.4Ghz I managed, but it was mid-summer and silly hot in my room.

Roll on winter, I want to get my 4000+ to 3.1Ghz :D
 
Hi krooton, that's good to know.

Following locutus12's advice and setting the FSB to 222 I appear to be getting similar performace to a AMD 64 3200+ without changing the vCore and at the same temps as before.

I am happy with the 'free' increase but do you think I could do any better without increasing Vcore and without any rise in temp?

If so how far should I go? 244 FSB?

If I don't increase Vcore and temp remains as before I OCed am I right in thinking I am not overstressing my CPU and it should not impact on stability or lifespan?
 
You need to up the fsb about 5 at a time. If the pc at some point refuses to boot or you have to reset the cmos then you know that thats as gar as you can go on stock voltage. Then you have the choice of running your pc at the last fsb that worked, or trying the fsb that failed again using slightly highter voltage.
 
rjd said:
Hi krooton, that's good to know.

Following locutus12's advice and setting the FSB to 222 I appear to be getting similar performace to a AMD 64 3200+ without changing the vCore and at the same temps as before.

I am happy with the 'free' increase but do you think I could do any better without increasing Vcore and without any rise in temp?

If so how far should I go? 244 FSB?

If I don't increase Vcore and temp remains as before I OCed am I right in thinking I am not overstressing my CPU and it should not impact on stability or lifespan?

Heat is generally the only killer mate.

If you don't up the vcore, there wont be any temp increase.

You may as well find the upper limit of your stock volts then, try 240 and test in Super Pi or Prime95.

If you get a fail, try 235, and so on until you find the best fsb for stock volts ;)
 
So if I still get the same temp/don't increase the Vcore, OC won't impact/do any harm. Is that correct?

I’m now up to 244 FSB and Everest (2.20) reports the CPU as a 3500+ with the HTC at 978 and RAM effective clock at 410.

Everest also shows under Chip Bus Properties, Real Clock 81 MHz (ODC), Effective Clock 652 MHz and Bandwidth 652 MS/s.

Everest reports as follows:

FSB 200 Latency 51.7 Read 5352 Write 2156

FSB 244 Latency 43.3 Read 6199 Write 2494

Does this all look ok to you?

It appears to be stable under load so I’ll leave it at that for now (although I can see how this OC malarkey can get addictive)

I would appreciate your comments.
 
rjd said:
So if I still get the same temp/don't increase the Vcore, OC won't impact/do any harm. Is that correct?

I’m now up to 244 FSB and Everest (2.20) reports the CPU as a 3500+ with the HTC at 978 and RAM effective clock at 410.

Everest also shows under Chip Bus Properties, Real Clock 81 MHz (ODC), Effective Clock 652 MHz and Bandwidth 652 MS/s.

Everest reports as follows:

FSB 200 Latency 51.7 Read 5352 Write 2156

FSB 244 Latency 43.3 Read 6199 Write 2494

Does this all look ok to you?

It appears to be stable under load so I’ll leave it at that for now (although I can see how this OC malarkey can get addictive)

I would appreciate your comments.

That sounds fine, you wont damage anything by not upping the vcore :)

You will need to stress test it though, just running windows and a few things doesn't put the cpu through it's paces, and osmething intensive like a game could make it crash.

Get Prime95 and do a toture test for a few hours , some people swear by 24, I'm happy with 10 (the hint is to start it when you leave for work).

If it fails, it will show you in the program, and you will need to either decrease the fsb or up the vcore.
 
i was like this at first mate....but its all trial and error....

you will get there in the end....dont change the volts and you can make as many "mistakes" as you want without frying anything....

cheers :)
 
rjd said:
Hi krooton, that's good to know.

Following locutus12's advice and setting the FSB to 222 I appear to be getting similar performace to a AMD 64 3200+ without changing the vCore and at the same temps as before.

I am happy with the 'free' increase but do you think I could do any better without increasing Vcore and without any rise in temp?

If so how far should I go? 244 FSB?

If I don't increase Vcore and temp remains as before I OCed am I right in thinking I am not overstressing my CPU and it should not impact on stability or lifespan?


i had my venice on 255 at stock volts. you wont need to increase the voltage for anything less i wouldnt of thought, and certanly not more than 1.450v for the kind of clocks i had.
 
Up the vcore and give it some stick man!

Depending on the bios version that mobo wont go past 266HTT so whack it on 267 with 1.44v and find out. If it wont post either accept 2.4 ghz or change the bios.

You wont hurt the chip with less than 1.6v provided its sub-60c unless your using bh-5 with mega volts
 
Back
Top Bottom