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

What should I clock my sucky AthlonXP mobile at?

Finally got my new system up and running. Unfortunately, I have not been able to OC my Athlon XP mobile 2400+ very high - i've reached my limit at 2.3GHz. At this speed, I have to use a whopping 1.8v for the core to get it stable, which runs at 55C under full load. For comparison, i can run it at 2.2GHz only using 1.675v stable, 49C full load. I can get memory timings of 2.5-3-3-7. Does anyone have any advice what I should run the processor at? Is 55C too hot? Should I just keep it at 2.2ghz and be happy?
 
55C is a little warm, but the mobile chips are good up to around 80-90C. It's a matter of personal preference, but as long as you're under 60C under full load, you'll be fine.
 
Originally posted by: BlueWeasel
55C is a little warm, but the mobile chips are good up to around 80-90C. It's a matter of personal preference, but as long as you're under 60C under full load, you'll be fine.

I agree with him
 
my situation is very similar, i have the 2400 Mobile, and I can run 2.2 at 1.625V, but i can't even get a stable 2.3 up to 1.725 (haven't tried higher). I'm a little dissapointed at this overclock.
 
Originally posted by: CletusTheDwarf
my situation is very similar, i have the 2400 Mobile, and I can run 2.2 at 1.625V, but i can't even get a stable 2.3 up to 1.725 (haven't tried higher). I'm a little dissapointed at this overclock.
all the good cores are being used in the 2600+ mobiles now.. The 2600+M is probably your best buy even over the 3200XP+ if you overclock..
 
Keep it a lower speed.
I am in a somewhat simillar boat. I recently upgraded my P3 800 to Mobile 2500. RIght now I am doing some short runs with Prime95 using 12*200 (2400) at 1.7v. My load temp is farly high 53-55C, but I am using Silent Boost cooler, which is silent but not very effective. I will try to figure what I would need to run at 12.5*200 (2500), but I will not go over 1.8v for now. After I figure limits of my system I will scale it back to probably 10*200 (2000). It is still is goging to be extremely fast for games and some coding stuff, but will prolong life of my CPU. Then (say in a year and a half, maybe?) when 2000 will be kinda slow I will probably tru to push it harder. Coming games HL2 and Doom3 will probably be more then happy with 2000 speed. Let you CPU relax for now and then abuse it later on, when I'll be easier /cheaper to replace it if you kill it.
 
Originally posted by: Jigglelicious
Finally got my new system up and running. Unfortunately, I have not been able to OC my Athlon XP mobile 2400+ very high - i've reached my limit at 2.3GHz. At this speed, I have to use a whopping 1.8v for the core to get it stable, which runs at 55C under full load. For comparison, i can run it at 2.2GHz only using 1.675v stable, 49C full load. I can get memory timings of 2.5-3-3-7. Does anyone have any advice what I should run the processor at? Is 55C too hot? Should I just keep it at 2.2ghz and be happy?

it really isn't that bad...2.3GHz is still faster than a 3200+, or a 3.2GHz P4.

/edit: Oh, and if that's an nforce2 mobo you'll probably get better performance setting your timings at 2.5-3-3-11
 
/edit: Oh, and if that's an nforce2 mobo you'll probably get better performance setting your timings at 2.5-3-3-11

I thought lower numbers = faster performance for CAS timings? Why would 11 be faster than 7? When I set my BIOS to use turbo memory settings, it sets it to 2.5-3-3-7. Wouldn't that be the fastest that my mem can handle?
 
Currently using a Thermalright SK6. Its still an awesome heatsink, IMO. I don't think the issue is overheating though. Although 55C is a bit hot, it shouldn't be causing the instability i'm seeing.
 
Back
Top