Oh my God my 1.4 cpu is a 1050!!!!

[EmoshBZ]

I am in shock here!!! I bought a Cpu that was suppose to be a 1.4 Mhz athlon but in the bios setting it has an operating frequency of 100mhz and a cpu clock multiplier of 10.5x. I can change the operating frequency to 133 or user defined....but the clock multiplier is a greyed out and I can't acess it. I was sure a week ago it said 1.417....and I have not interfared with the bios at all....this is too weird.....

what should I do?

its an Asus A7m-266 board
256 crucial DDr ram pc2100
windows 2000 service pack2


how can I tell if its a 1.4 they gave me or an overclocked processor?

 

[DisposableHero]

lol... bios doesnt mean anything.. u have to set the bios/jumpers.. look on ur chip to see it say 1400 somewhere

 

[zippy]

Silly newbie.

Heh, take a look at the chip itself. Take the heatsink/fan off and look at the little blue square and it should say something about 1.4 or 1400 on it- i think it's 1400.

Just put the "operating frequency" at 133MHz...see...10.5x133.33333333333333333333333 (etc)=1400.

 

[Spoon]

ROTFLMAO, oh man oh man

thanks I needed a good laugh

lol

 

[erikiksaz]

aye, lighten up on him guys. hah, we all have to learn one way or another.

 

[EmoshBZ]

Well I am a newbie to my "high end system".....hehe.....I just upgraded from a Win 95 p166 on June 27.....

anyway should I go into bios and set my frequency to 133* 10.5? that would bring it up to like almost 1400.....

how can I change my clock multiplier from 10.5 to 11? its greyed out and I can't highlite it!!!

I was hoping to overlcock at 11 * 133=1463



any suggestions?

 

[Keego]

sigh :disgust:

 

[Lucky]

"Just put the "operating frequency" at 133MHz...see...10.5x133.33333333333333333333333 (etc)=1400."


Take that advice.

Once you are able to do that (and no disrespect is intended), go to the overclocking forum so you learn how to overclock. Dont even mess, or try to mess with, the mult. right now.

 

[EmoshBZ]

Ok I admit that I was a bit panicky and I apologize....ok I will adjust it like you said and save it...

but on another forum one guy said that he had a problem where the settings would jump all around from week to week and funny other little probs....he said it was due to a cracked chip due to the heat sink being placed on it....I noticed my temps from my motherboard monitor was like 45 to 50 celsius and now 2 weeks later its like 38 to 41 celsius mainly...maybe nothing there but who knows....

thank you all....

cheers...

 

[MortaniuS]

heheh funny ass thread! ;-)

 

[EmoshBZ]

HEHE!!! I feel stupid now for posting that thread..lol!!!

Can I ever live this one down guys?

Anyway, I changed the settings and am at 1400 now....and the temps are risng now like before...


just one question now......I swear I never messed with my bios settings before...what the heck could of made it change back to 100? On the spec sheet the company gave me it said it came at 14.17 Mhz if you take their word for it....and I am sure I saw 1400 or something like that before then one day it just reverted back to 100mhz fsb......hmmm....just strange thats all...


cheers...

 

[Quickfingerz]

I say put the FSB to 140 mhz...

 

[theplanb]

1.4Mhz?? That's slower than 80088 Intel chip! :Q Intel rulez!
By the way, I heard that there ARE remarked athlons.. Very rare and easy to deetect. I've heard that there are remarked retail box intel chips..:Q and you can't really tell the difference unless you run CPUID or something..

 

[EmoshBZ]

I think I better run to the hills now...lol!!

MY majors are Economics and International Development studies....should of been computers eh


cheers...

 

[drewski]

if your computer crashes it may go into safe mode. my Asus A7V133 so i'd assume that your a7m266 does something similar.

it takes the default multiplier (in my case 7.5) and the low fsb (100) to make sure you can post. for me it shoots me right into the bios and on the right is some nice red text to the effect of "you crashed your system dumb @ss!! because either your FSB or multiplier were too high, yada, yada"

as they often say "it's not a bug, it's a feature!!!"