Overclocking Athlon Xp-M Help

Associate
Joined
27 Aug 2005
Posts
128
Hey everyone..

Ok So, I've got a pc that I've been trying to overclock.

The specs are..

Amd Athlon Xp-M 2400+

MSI KT6V motherboard

256MB PC3200 DDR SDRAM

NVIDIA MX420 ( Lol, Will be a 5700LE once I can be botherd to change it )


Anyway, when I try and overclock the CPU if i go past 1900MHZ it starts to crash..

At the moment its at 13.5X 140Mhz and thats stable...

The memory is at 200Mhz

The volts on the Cpu are 1.6

Any tips on how I can get it higher :confused:

I was hoping for over 2000mhz!

Cheers!
 
Read the newbie overclocking guide which is a sticky.

You want the FSB to be high really. Dont bother setting the ram different from fsb.
So if your on 13.5x140 then set the ram to 140 too.

9.5x200 would be better :)


What heatsink do you have. Get as many info tools as you can on the screen and take a screenshot, cpu-z and so on


I dont know that board, I have a MSI upstairs and it was good mainly because of the integrated graphics making it a good all round system. Not sure if they clock well, does it lock the agp speed. Think we managed a wobbly 180FSB on ours
 
Last edited:
Ok i cant post a screen shot today because I dont have it on the internet..

The mobo is an MSI KT6V, as stated above :) ( I cant lock agp and pci I dont think :S )

And the fan is an Akasa AK825 Sutable for up to 3400+

last time I put the fsb that high it wouldnt boot atall :S I will try again tho

Edit: I just tyed it at 9.5X 200 and it wudnt boot.. DAMNIT BOIS RESET AGAIN!!


lol
 
lol

Read the newbie guide, you should edge it up gradually

The lack of an AGP lock is going to stop you overclocking that processor. You can try anyway but there is a risk of data corruption on the hard drives I think
 
Delete the swearie above or they'll delete you :p

That temp is fine, anything under 60 is still fine.


What settings are you on, 2.2k sounds about the best your'll get with no agp lock

To take a screenshot you press the prtscr button, paste in paint. save it to the desktop and host it for free somewhere, like the one in my sig. 800x600 is best
 
No, he still has the multiplier to play with. I wouldn't advise overclocking the FSB much, that was the source of earlier instability. But at 200 MHz FSB, every extra half multi gives another 100 MHz. I think he probably has headroom left in that chip.
 


Wasnt appearing for some reason. Nice one anyway.
I think these chips are supposed to run at 166mhz anyway so maybe your pci/agp is still at stock speeds.

2.2k is when it starts to get hard to overclock it more, Ive found in the past. I think you have a good stepping though, in theory it might go higher. I had one that did 2.66k on air

Says in your picture as well but you've upgraded yourself to 3200+ performance there :)
 
:D 3200+ thats better than my main rig :'( :'( I payed 10 times more for that one as this whole sytem cost me 60 quid.

Lol good tho

the system is now at 39*c :\ that high??

That chip is supposed to run at 133.. it says on CPU-WORLD..
 
A little confused here - CPU-z says you're running at 163FSB*13.5 multi, but your core centre says 200*12 - which is it? You're not running the memory on a divider are you (real no-no for Socket A systems.)

If your motherboard supports it run the FSB at 200 (which shouldn't oc your AGP/PCI) then using various voltages you can slowly up the multiplier to find out your max overclock. The advantage of the mobile chip is that you can play with the multiplier without pushing the rest of your system.

(If it does 24hrs prime it's stable)
-might be worth running memtest (the dos bootable one) as well to find out the best memory settings)
 
Ye I know... the corecentre lies its crap software!!

Im a bit confused about devider stuff but in the bios ive got my memory at 400mhz?

So do you think I should try and get more out of it??

Today the temps are.. 40*c Idle and 45*c On full load.

Lastnight the case temp did get to 40*c
 
Those temps are absolutely fine - might be worth getting a bit more airflow through your case though - try to keep it as cool as possible - It would be helpful if you could post a screenshot of the memory page of CPU-z so we can tell exactly what is going on!

If it is running at 200FSB then you've somehow manage to get a divider set up, which will hurt your performance! Try running your FSB at 200 and the Multi at 11 as it had on core, that should give you the same clock, but hopefully it'll get all your components running at the same speed. The just up the multi until you're happy. As a guide, I wouldn't run the CPU voltage above 1.8 on air, but feel free to explore 1.7+.

What options do you have to play with in the bios to control voltages - ideally you want to control the Cpu/memory/NorthBridge.

Before you change anything - make a note of what you've got - can be very frustrating if you get a good clock stable, then lose the settings through tinkering and can't get back to where you were ;)
 
Ok in cpu-z it says...

Type DDR

Size 256mb

Frequency 196.4

Cas 3.0 clocks

Ras to Cas 3 clocks

Ras precharge 3 clocks

Cycle time (tras) 8 clocks
----------------------------------


When i tryed 200Mhz (lastnight) it would not boot.

In the bios i can change cpu vcore

ddr vcore

and agp
 
How very odd! There's no reason why it shouldn't boot but there are a couple of things you can try:

Set your memory setting to 2.5,3,3,11 (cas 2.5 is better on nforce2 boards than 3 and 11 (tras) is better than 8 as it places less stress on your ide devices.)

Try 200FSB with the multi set to 10 initially - not much point going lower, but you can try for 9.5 if it doesn't work.

The DDR Vcore is probably defaulting to 2.6, worth raising to 2.7
What's the CPU voltage? (1.6?) Try it at 1.725

You may well find that it is your mobo that's limiting you, some of the older nForce2 boards weren't rated to 200FSB (they were originally designed to go to 166 only) - if this is the case then set the fsb to 166 and the multi to 13 (that'll give you just shy of 2200) - If that works you've then got 2 choices:

1. Leave the FSB at 166 and push the multi until it falls over and find the max clock that way.

2. Put the multi back down to 10 and slowly increase the FSB until it falls over (clockgen lets you do this in windows so saves rebooting - gives a quick way to find a *rough* oc limit ;)

(Ideally you want the FSB as high as possible with Socket A mobo's, but if you can't lock the PCI/AGP you run a very real risk of corrupting your install of windows...)
 
Back
Top Bottom