All Bartons core XP's overclock roughly the same...they generally max out at about 2.5GHz. Your 2500+ *should* be able to run at 2.2GHz but it may require a voltage increase. As always, you need the right board, the right RAM & a decent power supply. For best performance, the CPU:RAM frequency ratio absolutely MUST be kept at 1:1! Hopefully you have DDR400 or better.
As for the 2400+ XP-M vs the 2800+, the XP-M definitely has an unlocked multiplier, the 2800+ most likely does not. If you expect to hit 2.5GHz, you're definitely gonna have to throw a hefty amount of voltage at the CPU. I ran the same 2400+ (AXMH2400FQQ4C) on an Asus A7N8X-X & also on a Shuttle AN35N Ultra & the best I could do was 2.31GHz (11 x 210MHz). I don't recall the voltage setting but I believe it was 1.725v, which is quite an increase from the stock 1.45v. I *may* have been able to go higher with more voltage, but I didn't feel it was worth the risk for another 100MHz or so.
current 2500+ run at slightly over 2.04ghz(?) @ 1.85v(cpu:fsb = 1:1) on abit nf7-s rev2.0. Areo 7 copper hsf. can't go further, don't know why? psu is a 450W HEC.
Axp 2800+ default clock at around 2083MHz? So, to be on the safe side, it should be better than axp-m 2400+ right?
Do you have these CPUs or are you buying them? It's really not worth investing too much in a socket A system. Remember that the socket A platform does not benefit from dual channel memory, so don't be afraid to try single channel mode to see if it helps with the overclocking.
What are you running the FSB at now? If the multi is locked at 11x, it would mean you've stalled at approx 185MHz? If you're running DDR333, that's what's holding you back. But if you have DDR400, you may wanna try thrwoing a little voltage at the motherboard chipset, if that's a BIOS option.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE