• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

OC'ing XP-M woes

R

rustbucket

n00b
Joined
Sep 9, 2004
Messages
41
I've got a Shuttle AN-35 Ultra motherboard. Until today I had a Athlon XP-M 2500+ overclocked to 2.4 ghz using a 200fsb X 6.0.

I picked up an Athlon XP-M 3000+, and can't get the system to boot at a proper speed. 200 X 6 nets me 1.2ghz, where it used to net 2.4ghz... The only change to the system is the processor, and a shiny new si-97 heatsink.

same multiplier, same fsb, half the speed? help!

ps - what is the stock multi for a 3000+? I'd like to just get it to boot at stock speeds at this point...
 
man, this dude was probably wondering why is overclocked xp-m @ 2.4GHz was running so slow! :) maybe why he went out and bought the new processor.
 
Maybe he's thinking 6x systembus instead of fsb, which would be 6x400 = 2400. But yea..you need a 12x multy to get 2.4ghz
 
IceBawx said:
Maybe he's thinking 6x systembus instead of fsb, which would be 6x400 = 2400. But yea..you need a 12x multy to get 2.4ghz
Click to expand...

i apologize - i am thinking systembus. and no i wasn't running my 2500+ at 1.2ghz, it shows the chip speed on bootup, I run mbm, and have seen it in my computer properties, etc... I was pretty thorough about the overclocking process on that chip, using clockgen to up the fsb slowly, and making sure it was prime stable etc... So i'm not stupid. I just have no idea why this is happening.

With the old processor it happened once - the bios listed the chip at 1200mhz. I reset the system and it went right back to 2400mhz

bios settings are exactly the same as when i had the 2500+ installed.
 
funny people aren't so quick to respond now that they aren't making fun of me :p. can anyone offer some genuine help? :) :confused:
 
As I said, check your BIOS to make sure you have 12x selected, as well as an actual 200MHz FSB in BIOS. Also look for any safety jumpers on your motherboard- my DFI has a "100MHz jumper" to cancel OC's, so my CPU booted at 1.1GHz the first time I plugged it in.

You may also want to up the voltage to the CPU; you may have a smart board that won't run the chip at that speed if it's underpowered.
 
Reset the BIOS by clearling the cmos and let the MB recognize the cpu again then set your OC setting again, also you may want to check if there is a newer bios for your MB than what you are running!
Hey half the fun in OC'ing is getting that "puter" to do what you want it to do, not what it wants to do ! :)
 
Okey - I reset the bios, let it autodetect the processor. That didn't work very well - it detected an unknown processor at 600mhz.

So I:
Set the 'FSB Frequency' to 133mhz.
locked the memory to the bus speed ( Memory Frequency = 100% ).
resulting memory speed was listed as 133mhz. Logical.
Set the multiplier to 8.0 ( 266 * 8.0 = 2128. stock speed = 2200mhz ).
Set the voltage to 1.650 (stock)
set the RAM voltage to 2.7 (why not...)
Save and Close.

boot screen:
Main Processor: Unkown Cpu type 1066mhz
Memory Speed: 266mhz

one of these things is just not right - if the memory is locked to the fsb, the math doesn't work.... Part of the confusion here is the distinction between system bus and fsb... my understanding was that a 133mhz fsb = 266 system bus, and if the memory was locked, a 266 memory speed... but the processor speeds it's booting at aren't bearing this out...

does anyone have any help for me? I'm wondering if I a.) got a bad proc/cracked/chipped the core or b.) my motherboard is shot...

I'm just completely lost. This is a Shuttle AN35 Ultra, Phoenix AwardBIOS, btw.

Oh, it's also the most up to date rev. of the bios (which is from like 2003).
 
Your processor runs at the speed of your fsb times your multiplier. Right now, that would be 133*8 = 1066. If you want to run at the stock speed of 2.2 GHz, set it at 200*11.
 
when you set the multy to 8.0, you got 1066mhz because that multy is the FSB multy, not the systembus multy. 8*133 = 1064. In order to get ~2200mhz you need a multy of 16 with a fsb of 133.

EDIT....what he said... :p
 
if i set the fsb to 200, the ram clocks to 400mhz when i put it at 100%. That was the case with my old proc too - i had the fsb set to 200, the ram clocked to 400, and with a 6.0 multi, it netted 2.4 ghz...so it was actually running a 400 fsb * 6.0... The fsb in my bios only goes up to 250mhz, btw, and this is a modern board... In the past setting that was always half of what i ended up with.
 
rustbucket said:
if i set the fsb to 200, the ram clocks to 400mhz when i put it at 100%. That was the case with my old proc too - i had the fsb set to 200, the ram clocked to 400, and with a 6.0 multi, it netted 2.4 ghz...so it was actually running a 400 fsb * 6.0... The fsb in my bios only goes up to 250mhz, btw, and this is a modern board... In the past setting that was always half of what i ended up with.
Click to expand...

This should definitely be a 12x multi, not 6x. But we've been through all this already.
8x133=1066
12x200=2400

Just like mine runs:
11x218=2400, because it's locked at 11x.
 
you know, people keep telling you that you are doing simple math wrong, and you get technical in response.......................

seriously, your core speed is calculated in the way that mavalpha just outlined for you.

i run 13x200, my ram is 1:1 ratio. this gives me a real clock of 2600 MHz (aggressively cooled, and volted up high) my ram is reported as being DDR 400, however it's real clock is only 200. there is a very difference between saying that a bus is at a given speed, and talking about it's DDR speed.
 
I apologize to all if i'm souding aggressive - y'all make sense, beleive me. What's got me confused is that it's a change from the settings for my old proc, a slower version of my new one... That and it doesn't boot when I set it up the way y'all describe.
 
Well, I'm an idiot and you all are right

I'm going to go hang my head in shame and see how high i can get my proc to clock. I'm not sure why it wasn't booting before, but it is now... Sorry to everyone for being so stubborn. Nothing like asking for advice then ignoring it sorry.
 
You must log in or register to reply here.
Back
Top