I finally decided to take a chance and try some overclocking...

[Mole]

I have an AthlonXP 2500+... Right now, it's overclocked to 3200+!

1.8Ghz to 2.2Ghz!

I haven't tried any games yet, but if this setup proves to run unstable, what could I do, increase the voltage?

[Mole]

Update:

I tried Oblivion, the main menu froze... So I went back into the BIOS and increased the CPU voltage from 1.6 to 1.7, and RAM voltage from 2.6 to 2.7, and it seems to have fixed it. I put the RAM voltage back to its default, though, gonna see if it works that way too...

[Mole]

No good, it froze up within 20 seconds. :(

Maybe I'll just get an AthlonXP 3200+ in the meantime, as I am saving up for a new rig in June. They're cheap now, right?

[White_Rooque]

No good, it froze up within 20 seconds. :(

Maybe I'll just get an AthlonXP 3200+ in the meantime, as I am saving up for a new rig in June. They're cheap now, right?

yep

[BloodyL]

You should have kept on trying, I'm running my Mobile 2500+ (Barton core) at 2.4Ghz right now, vcore is 1.8v and memory is at 2.7v.

By the way, you didn't mention what fsb and multiplier you were using? my system tops out at 200fsbx12 but I think that the memory is at fault due to them being very mismatched.
(1x single sided stick and 1x double sided stick, both sticks offer different default timings.)

[sj_hurst]

I just upgraded to an el cheapo copper heatsink (from the aluminum stock one), so for the 1st time I tried to O/C my Mobile AthlonXP 2600+. The new heatsink is rated up to a 3200+, which i thought made it safe enuf to take the risk. Anyways, I've only been able to hit 2100MHz stably so far. I'm still trying tho, playing around with the Vcore.

[opus512]

I had a 2500+ Barton that all I did was kick the multiplier up a couple of notches and ran it as a 3000+ for almost a year, no problems, almost no heat increase. Never messed with voltage or memory timings either.

[Mole]

I used one of the parameters that the BIOS has, it kicked the FSB from 166 to 200. Left the multiplier alone (11x). I can't change the multiplier on mine... Seems to be locked.

I'm gonna try again, because when I tried Oblivion, I had put the RAM voltage back down.

[sj_hurst]

I used one of the parameters that the BIOS has, it kicked the FSB from 166 to 200. Left the multiplier alone (11x). I can't change the multiplier on mine... Seems to be locked.

I'm gonna try again, because when I tried Oblivion, I had put the RAM voltage back down.

Mole, my systems been locking almost every time I fool with the FSB. My last try, however, I set the FSB to 200MHz & low multiplier of 9.5x.. then I set the Vcore to 1.75V and memory to 2.7V. Next, I left the FSB alone while increasing the multiplier in 0.5x increments (+0.5x, reboot, +0.5x, reboot, and so on). I've got it stable at 2400MHz now. Dare i try for 2500MHz by raising the multiplier to 12.5x? :D

long story short.. My m/b seems very finicky when I mess with FSB settings too much.

Also, uping the Vcore from 1.45V (the mobile cpu's default) to 1.75V seemed to help alot.. tho, I'm not sure that it's really necessary. I'm gonna try gradually lowering the Vcore & see if it's still stable.

[sj_hurst]

and btw, I've always had my memory at 2.7V even though the motherboard default was 2.6V.. it was never stable at 2.6V the whole time i owned the m/b, even before i ever messed w/ overclocking. But at least this Geil memory has always run at it's rated 400MHz dual channel, lowest timings without a hickup.

[labat]

figure out if you can change your multiplier.
I down clocked my memory freq and turned down my multiplier from 11 to 10 and then pushed my FSB really bad ;) got mine x2 4400 (2.2ghz) rock stable @ 2.7ghz. minor voltage adjustements on both cpu and memory to.
good brand memory is a + also
took me couple of hours to get the memory timings to work...but it was well worth the job!

good luck :)

[sj_hurst]

hit 2500MHz, still at 1.75Vcore. nice. :bigthumb:

now to see if it remains stable w/ lower Vcore..

[sj_hurst]

1.65Vcore locked during Windows logo 1st try. 2500MHz and 1.675Vcore seems to be the sweet spot for my old AthlonXP system.

[nightstormer]

Make sure your RAM timings are real conservative. Sometimes folks have their timings cranked and don't realize it, and this locks the PC if you try and overclock. Also, increase the vcore a little at a time. My old 2500+ XP ran at 3200+ at 1.75v stable, so you might try and increase it bit by bit until you find a stable setting. Most 2500+ WILL run stable at 3200+ settings (11x200, no need to mess with multiplier), you just have to find the right combination of RAM settings and vcore.

[Mole]

I just don't want to break anything, if I fry something, I'm screwed...

I'm trying the 11x200mhz again w/ 1.7 core and 2.7 mem.

If if locks up again, I'll try to adjust memory timings.

[sj_hurst]

I experimented with the memory timings. My RAM only reaches 430MHz (FSB 215x2) stable even with CAS 3 timings. I figure I'm better off leaving the RAM at 400MHz w/ tight timings and up the multiplier instead.

I've been gaming w/ the 2500MHz and, so far, still no problems.

[sj_hurst]

I just don't want to break anything, if I fry something, I'm screwed...


Unlikely, but it can happen. For the most part though, it's exposing your cpu to higher Vcore settings over a long period of time that shortens its lifespan. I realize turning my Vcore up to 1.75V for a few minutes probably won't do any damage. And even if it did do some minor damage, most people (and myself) will have upgraded long before their cpu's burn out.

Other than high cpu temperatures, excessively high Vcore is the only thing you should be wary of. Most AthlonXP overclockers seem to be relatively safe w/ a 1.75 - 1.8V from what i read on the 'net (so i'd say 1.75V is not too high, for most AthlonXP's). But if you can achieve an overclock w/ lower Vcore, that'd be a good thing.

[labat]

this settings works exellent for me.

FSB 270mhz (200 default)
DDR voltage 2.80v
chipset voltage 1.6v
cpu multiplier 10x (11x default)
cpu voltage 1.475v
pci clock 33mhz
hyper transport freq 4x (5x default)

cas latency = 2
ras to cas delay 3
row precharge time = 3
write recovery time = 2
1T/2T memory timing = 1

35% OC rock solid for couple of months now :)

[sj_hurst]

That's some nice O/C'ing.. i suspect your Athlon X2 4400 has superior thermal properties to any AthlonXP. I look forward to the day I upgrade again.

My AthlonXP setup maxes out at 2525MHz and 1.7Vcore. 25MHz is so incremental tho, I reverted back to 2500MHz and 1.675V. It's apparent that a 25% overclock is the limit w/ my PC.

That's not bad tho, considering my last AthlonXP (an early generation Thoroughbred core, 2400+) wouldn't overclock at all (though, I suspect it had more to do w/ the motherboard and sh!tty Corsair memory).

The "333MHz CAS2" Corsair XMS DDR really sucked. memory proggies revealed that it (both sticks, actually) were not true CAS2 memory (contrary to the advertised labeling). The Geil memory i'm currently using, however, is actually detected w/ lowest timings by the motherboard.. so it's been good stuff in meeting its specs.

however, the Geil RAM won't handle anything above 404MHz at the CAS 2 setting & DDR voltage of 2.7V. It did reach 436MHz at CAS2.5 & DDR volts 2.8V, but i think raising the CAS timing isn't worth it for an extra 32MHz. the Geil DDR does what it's advertised to, but not much more.

[Mole]

Well, I know not to try any settings that others may post... Everyone's setup is unique, and when it comes to overclocking, they each benefit from different settings.

My memory is 400mhz, but for some reason, my CPU doesn't like this RAM, it refuses to run at 400mhz alongside my overclocked CPU, so I have to adjust the ratio between the CPU and RAM... It seems to only work with 400/333.

Here's my setup, though:

Abit NF7-S 2.0 motherboard
AMD AthlonXP 2500+
1gb Corsair XMS3200

Here's the settings I've been trying:

200mhz x 11 (CPU)
166mhz (RAM)
Vcore 1.7v (stock 1.6)
RAM 2.7v (stock 2.6)

Don't remember RAM settings, but I usually run em in 2/2/2/5. This also seems to be the only settings this RAM likes.

[nightstormer]

Mole, try and raise the RAM timings to 3-3-3-8, or even higher for that matter, and then set your CPU back at 11x200. I know that sounds wimpy for the memory timings, but at least you could see if it's the memory holding you back. I know memory has been my main issue in the past when I'm trying to OC. The CPU usually will clock at what I want if I can get timings the memory likes.

[Mole]

Actually, I tried 3-3-3-8, wouldn't post, and gave me constant long beeps... I do believe constant long beeps have something to do with a RAM error.

Even when not overclocked, if I change the RAM timings from anything besides 2-2-2-5, it won't even boot up correctly, gives me a blue screen that says there's an IRQ conflict, never goes into Windows, and then restarts.

[sj_hurst]

I'm using the same motherboard as you, Mole. My RAM is rated at 2-2-2-5 as well (but it's Geil). It won't run at 3-3-3-8 either, but it did run at 2.5-3-3-6. So maybe you could give that setting a try.

Also, this m/b locked for me if I made too many adjustments or too big of adjustment at one time. So i recommend only making 1 adjustment at a time & smallest adjustment possible each time you go into the BIOS. Start with low, conservative settings and then gradually increase the multiplier (in 0.5X increments). But with each 0.5X, if it ever locks, then revert to an increase on the Vcore 1 notch (increasing the Vcore until it no longer locks, up to a certain threshold you're willing to try.. the 1.7V you seem to be aiming for). If it still locks at the 1.7V, then you know you've maxed out the o/c'ing and should step it back down to the last stable setting.

Also, i advise to try leaving the RAM/FSB alone (at 4:4, 400MHz) while doing the above. If all goes well, you should be able to keep your memory running at its stock speed while O/C'ing the cpu.

The above was the only method that allowed my m/b to reach the 2.5GHz and maintain stock 400MHz RAM speed.. anything else resulted in lockups or a very weak O/C.

[Ronhel]

Lock your pci/agp or you'll get shitty o/c

[Svperstar]

Welcome to the club :) I have been overclocking for almost a decade now, its pretty fun. Running my 2.2 ghz A64 @ 2.6 right now. The highest I have tried is 2.65 because the temps get pretty scary when I go really high.

+oc rep