2 overclocking questions

Le Québécois

Senior member
Dec 1, 1999
560
3
81
I'm new to the overclocking business I just OC my Barton2500 to 3000 by doing 12.5x173mhz. At maximum cpu charge with prime95 running the temp reach 50C ( mobo at 21C ). If i try to boost up the fbs the cpu is unstable. Questions:

1- Is there any danger for OC my cpu from 2500 to 3000? By danger I mean the cpu burning itself up in one year or so...I'm low on money, that's why I just deceided to OC, I dont want to have to buy another CPU in 1 year.

2-Is there a way to overclock it more? I see the temp only goes up to 50C....I read around the web it could go up until 60C before getting error. Why cant i go highter? I know it has to do with the Vcore but I have no idea how set it correctly ( how do i know 1.7 is ok for 180mhz and 1.75 for 190mhz for exemple ).
 

Vee

Senior member
Jun 18, 2004
689
0
0
Originally posted by: Le Québécois
I'm new to the overclocking business I just OC my Barton2500 to 3000 by doing 12.5x173mhz. At maximum cpu charge with prime95 running the temp reach 50C ( mobo at 21C ). If i try to boost up the fbs the cpu is unstable. Questions:

1- Is there any danger for OC my cpu from 2500 to 3000? By danger I mean the cpu burning itself up in one year or so...I'm low on money, that's why I just deceided to OC, I dont want to have to buy another CPU in 1 year.

2-Is there a way to overclock it more? I see the temp only goes up to 50C....I read around the web it could go up until 60C before getting error. Why cant i go highter? I know it has to do with the Vcore but I have no idea how set it correctly ( how do i know 1.7 is ok for 180mhz and 1.75 for 190mhz for exemple ).

I normally avoid posting on subjects like OC and PC builds, since my views on these matters tend to generate heated debates - in forums mostly populated by young males - that I'm not really interested in. But since you haven't got any other answers:

1: Yes, your CPU will get a reduced lifespan from OC. OC equipment tend to develop various strange quirks over time. However, it's not possible to say how long lifespan. A moderately OC CPU can last for years and years... Or it may not last much at all. (nVidias new FX6800 GPU seems rather sensitive to OC)

1b: 2500+ is an excellent choice for performance on a budget. You made the right choice. IMO you really don't need to OC it. The performance gains you will achieve are, IMO, not something you will notice much. The 2500+ already performs much better than its rating suggests. That is due to AMD somewhat 'inflating' later numbers, as well as the fact that Intel's P4s don't perform as well in 'real life' as popular, custom tailored benchmarks implies.

The experienced OC'ers will carefully check their systems with various benchmarks. You may not really get what you think you get, by OC'ing. One pitfall is the way the memorybus clock depends upon the FSB. If you set the FSB to a nonstandard value, you will get some change on the DDR-bus, and it won't be what BIOS claims, and it might be slower, resulting in a slower system from OC. (Or it might be faster, I suppose something like this could also be the reason for your system's instability, what kind of RAM are you using, and what memory clock do you *think* you're running?) Same goes for AGP-clock. Most straightforward way to OC a locked CPU, is to select a standard FSB clock (or close). Like going for 3200+, 200MHz on the FSB clock, then either 166 or 200 on the memorybus (DDR333 or DDR400).

Another pitfall, for Intel users, is the P4's tendency to 'throttle', when you ask much of it. Happy P4-OC'ers may cheerfully believe they have a kickass system, just because the resilient P4 happily accepts the outrageous clockrates thrown at it. In reality, soon as it gets some longhaul heavy work to do, it will kick down the internal frequency, and run slower. To the OC'ers delight: "It runs real cool too".

2. Well, yes maybe. I've already suggested one could try fool the chipset into believeing it's a 3200+. You will then surely get your 166MHz/DDR333 memorybus, if that's what you've got dialed in, and correct AGP clock. That is not a "moderate" OC, mind you. (But I've tried it briefly, and it worked. I experienced no strong reasons for continuing the OC though.)

But basically, I believe that worthwhile (performance) OC'ing is an expensive practice. Not a budget choice for the poor. If the performance gain is going to be truly noticable in practice, it has to be _real_ (which I strongly suspect is failing some OC'ers), and secondly it has to be greater than any 2-10%. For that, you need a select cpu with unlocked multiplier, and you need to try several, which is expensive. And you need some serious cooling, a freezer that will take the CPU down to -40C. That way you can accomplish 40-50% overclock. But mind you, it's an expensive hobby. Not something for the poor.

My advice to you is thus: Don't OC, run your 2500+ as such and enjoy it. It will cope with any game, provided you partner it with a decent videocard (R9800 128MB, FX5900xt upwards). On serious applications, you will mostly enjoy very, very respectable performance.

Veritest Winstone2003 benchmarks are excellent benchmarks for correlating to application performance that can be expected in real life. Winstone2002 contains less CPU optimizations, than can be expected in recent versions of mainstream apps. But still, relations between family members are valid. Check out the 2500+ vs. the 3200+ on this page:

http://www.anandtech.com/cpuch...c.aspx?i=1834&p=5


Overclocking successfully to 3200+ will gain you 10% increase in performance.
And this page:

<br>[url]http://www.anandtech.com/cpuc...c.aspx?i=1834&amp;p=6
[/url]

You stand to gain 8%, if you overclock to 3200+.

Is that worth all the possible problems and risks? If you're on a tight budget?
 

Vee

Senior member
Jun 18, 2004
689
0
0
(- Sigh) Not only does my message get screwed up, when I include links, I can't even edit it. The server app crashes.
Anyway, the next link is the next page from the link that works. And it should be "minus 40C", whatever you're reading there.

You should also consider that a good deal of that 8% and 10% increase above, is due to FSB increasing from 333 to 400, and memorybus increasing from DDR333 to DDR400. Just OC'ing the CPU internally wouldn't have resulted in as much.

 

Navid

Diamond Member
Jul 26, 2004
5,053
0
0
Originally posted by: Le Québécois
2-Is there a way to overclock it more? I see the temp only goes up to 50C....I read around the web it could go up until 60C before getting error. Why cant i go highter? I know it has to do with the Vcore but I have no idea how set it correctly ( how do i know 1.7 is ok for 180mhz and 1.75 for 190mhz for exemple ).

Have you read the guide on this same page?
http://forums.anandtech.com/me...3208&amp;enterthread=y
 

Stormgiant

Senior member
Oct 25, 1999
829
0
0
Another pitfall, for Intel users, is the P4's tendency to 'throttle', when you ask much of it. Happy P4-OC'ers may cheerfully believe they have a kickass system, just because the resilient P4 happily accepts the outrageous clockrates thrown at it. In reality, soon as it gets some longhaul heavy work to do, it will kick down the internal frequency, and run slower. To the OC'ers delight: "It runs real cool too".

Do you see this situation much ?
Maybe the utilities that show in real time the clock of the cpu lie about it ?!?!?

I thought that they switch into throttle mode when reaching high temperatures, normaly above 70...

Any support on this declaration ?
 

Stormgiant

Senior member
Oct 25, 1999
829
0
0
Originally posted by: Le Québécois
So OC from 2500 to 3000 is not worth it?
Anyone think the same?

Why don't you answer youself....

Does it feel faster ? Applications start faster ? Games run faster ?
It's noticeble ?

For me, every overclock is worth, because i don't go beyong the point theres an eminente risk.
 

Gamingphreek

Lifer
Mar 31, 2003
11,679
0
81
Originally posted by: Le Québécois
So OC from 2500 to 3000 is not worth it?
Anyone think the same?

Youll be fine! Doing this probably wont reduce the life of your CPU. YOur CPU lifespan will only go down if you keep your VCORE up around a constant 1.85 or something.

It is worth it. I however leave mine at 1.7VCORE and a 10x200 to achieve 2Ghz on the nose. It is plenty for summer. ALso im using the Asus A7N8X-E Deluxe board so OCing... eh doesn't do so hot.

-Kevin
 

Le Québécois

Senior member
Dec 1, 1999
560
3
81
ok.
What 's better .... more mhz on the fbs or more multiplier? mine is at 12.5x 173 on a A7N8X-DX should i lower the multiplier and increase the fbs? Is there any real difference?

Oh and Yes i do see a diffencre with UT2k4.
 

Vee

Senior member
Jun 18, 2004
689
0
0
Originally posted by: Stormgiant
Do you see this situation much ?
Today, I strongly suspect I saw it a lot with my first P4. I did suspect it at the time too, but was too lazy or busy to ever check it out thoroughly.
Northwoods seem better, and this page is somewhat reassuring:

http://www.digit-life.com/arti...throttling/index.html


Just as you say, throttling seem to only cut in at about 70C.

However, just a few days ago I discovered one of my P4s is throttling (which may be why I'm in a panic now ;) ), when it has been fed numerical crunching for 10-15 minutes or more. And, quite frustrating, temperature indicates only around 50C. This too I came to suspect earlier, but the temperature readings reassured me. However, I finally timed a piece of work comparing to an A64 and another P4. Just to clinch the case, I resorted to the drama of blowing compressed air on the heatsink, resulting in half the computing time. That prooves it to me.

Also, I remember a guy on a newsgroup posting results, from throttle testing, that showed some throttling
above similar temperatures.

Maybe my P4 is defective in some way, but there may be another explanation. There are two types of throttling, automatic and 'on demand'. It may be this 'on demand' throttling is enabled someway. I may dig into this some more. However, my first next step will be to remove and remount the heatsink.

Maybe the utilities that show in real time the clock of the cpu lie about it ?!?!?
Well, yes, I think they do, don't they? Indeed, yes. Throttling is done by the cpu generating stopclock requests internally. This stops the clock for most of the CPU internals, for a short moment. I can't see that this is visable to any external software. The cpu core speed remains the same during throttling. You must measure performance.