Is it just okay having my CPU run at 1200(100) when my SDRAM is PC133?

[Tamahome]

Hello all...

I have an Athlon CPU with the speed of 1200... now the prob is everytime i set it to the BIOS for this setting 1200(133)... everytime I scroll down to any application... my system hangs...

The only solution I could get is to set it into 1200(100).. :( And I am worried for damaging my PC bec. my SDRAM is PC133... is it just okay having my CPU run at 1200(100) when my SDRAM is PC133? If not... is there any solution on how to fix this problem so I can setup my CPU at 1200(133)?

Thanks with all your help.

My PCs current spec is:

Athlon 1.2
Abit KT7A ver 1.3
Kingston 256 PC133 SDRAM
Inno3d GEforce 2mx Video Card
Creative Vibra
IBM 30gb ATA 100 Deskstar

[Bovon]

Hi, The RAM is designed to run at 133 mhz if the cpu and board fsb will run at 133 mhz...but, the RAM will run at 100 mhz just fine. The RAM runs at the speed the CPU runs at I think, so if the CPU is running at 100 mhz, so is the RAM modules.

To get your CPU to run at 133 mhz fsb you will problably have to unlock it. Most AMD CPUs come locked. This was done at the factory by laser cutting the L1 bridges on the CPU just out on the side of the core on the ceramic base. These bridges can be reconnected with a conductive material...some people use a lead pencil and graphite the links back together, but this is not a permanent solution and most people are now using a conductive ink pen. Once the bridges are reclosed, you will be able to run your CPU at 133 mhz fsb...and the RAM will run at that speed as well...and probably higher if needed to overclock.

The following artical deals with unlocking a 1.2 ghz Tbird for the purpose of overclocking, but it also shows you how to unlock the processor.

http://www.sharkyextreme.com/hardware/articles/amd_oc_10-00/

[Tamahome]

Thanks for the input... I am just wonderin... is the Athlon 1.2 Ghz, really set as 100Mhz on default? Should I need to unlock it? to use its 133Mhz FSB speed?

Thanks again!

[Bovon]

You will have to look at your processor. Most were shipped with the L1 bridges cut, there for they are locked. If the CPU is locked, it will run at the mainboards default 100 mhz fsb settings. Usually these can be bumped up to about 132 mhs in the 100 mhz default settings, but to get the mainboard to run at 133 (and above) mhz the CPU must be unlocked. The mainboard will recognize if the CPU is unlocked and if it is, the board will allow the 133 mhz fsb settings to be used, if the CPU is locked, the board will not allow the 133 settings. This is for the more recent mainboards...some of the first mainboards that were manufactured with the 100/133 fsb settings would allow the user to attempt to set it up for 133 mhz, but if the COU was locked, it did not work, and the board would not boot.

[Mafiosy]

But first think twice before touching the CPU!
You'll be sending threads about why your computer stoped beeping , and theres no power supply to the display.
I advice you to stick to what you already have and not engeneer your own CPU.

Maf.:cool:

[Rugor]

There are two versions of the Athlon 1.2, Athlon-B and Athlon-C. The Athlon-B version uses 12x100 FSB and the Athlon-C uses 9x133 FSB. If your CPU is defaulting to 12x100 you are running an Athlon-B. It is clearly marked on the die which version it is. Both versions were often shipped with the multiplier locked.

As to the memory, the KT7A motherboard supports running both a synchronous and an asynchronous memory bus. This means the memory can run at either 100 or 133MHz regardless of which the FSB is set to. You get the best performance if both are set to 133MHz but it is possible to run the FSB at 100MHz and the memory at 133MHz and this will give a performance increase over running the memory at 100MHz.

[Bovon]

Hey Bro. Rugor...hate to bust the bubble for you, but they all come locked sometimes. I just so happen to have a 1.2 gig C Tbird thats locked (or was, till I unlocked the sucker) I also have a 1 gig C that was also locked. There were rumors all over the place about this time last year...or maybe a month or so earlier that when th 1.2 C series hit the market they would all be unlocked...sence then, there has been a **** load of dissapointed people that bought some that were locked ...including yours truly!

Mafiosy, not trying to start anything you understand, but whats wrong with unlocking a CPU?...the machine actually runs better at 133 fsb. Without even overclocking it, most everything benchmarks a little better. Hundreds of thousands of Durons and Tbirds have been unlocked ever sence they hit the market and socket A boards became available. Sure, you can blow it up if you are not carefull...but, hey...you can blow up a stock one just as easy if you are not carefull. Its all part of the game, win a few...loose a few...but have fun and learn in the process. There have been as many processors killed by clip on heat sinks like those terrable ORBs that chip the core as there have been damaged processors from unlocking them.

[Rugor]

I guess I wasn't clear enough Bovon, I meant that it was very common for both the 200 and 266 FSB Athlons to come locked.

A few were shipped unlocked but not that many.

[Ifish25]

If the memory rate is variable with the CPU, the lower setting for memory may actually work better for some gaming apps. My 1300 Athlon with 100/133 setting works great for all programs except action gaming. Red Ace will lock it up every time with 133 memory setting. It might as well be a painting on the wall. My computer is in deep freeze and must be restarted. When I set memory to run as PC100, games works perfectly, so I opt for 100/100 setting, even though memory is PC133.
Until I discovered this option, I was ready to can my ECS K7S5A.

[Bovon]

Originally posted by Rugor
I guess I wasn't clear enough Bovon.

Yep, you were very clear...I just need to read. I didn't catch your last comment about both versions being shipped locked sometimes...sorry, I just gotta stop this speed reading!! ;)

[Bovon]

Originally posted by Ifish25
Red Ace will lock it up every time with 133 memory setting. It might as well be a painting on the wall.

That just could be a bad stick of ram, or a poor quality brand. I read last year where one guy was having simular problems running at 133 fsb and some apps locking the machine as well as blue screens ect, but the machine would run fine at 100 mhz fsb. Somebody suggested he swap out the ram for a test...he did, and it worked. May or may not work for you, but it is a possibility. Also ram timing in cmos can cause problems...what works at 100 mhz may fail at 133 mhs.

[Brian48]

I don't think it's a bad stick of RAM at all. I think he just needs to play around with the BIOS settings. I used to have this motherboard. Unlike the K7S5A, it runs much faster in asyncronous mode 100/133.

[Atomic Rooster]

Tamahome -
With KT7A you can run the ram at 133 by going into the BIOS under SoftMenu III Setup and setting the DRAM Clock to HCLK+PCICLK. :D

[morpheus kain]

You don't need to unlock your processor to run at 133 bus. And I would suggest you try moving that dimm into a different slot. Don't ask but I did that on my buddy's k7s5a and it then ran fine. Also, remember that at 133 you will be getting 133X12=1596. Your processor might not run at that kind of frequency. BTW I took a 1ghz ayhja tbird all the way to 2ghz on an 8k3a at 2.2 volts with water and pelt. (had to brag sorry)

[Rugor]

But that's something to brag about, 2GHz out of a T-bird.

Congratulations, though I don't think you could have done it without water and pelts.

[morpheus kain]

Thanks! I truly appreciate a compliment form such a wise man Rugor! I coulda done it with just water but I woulda worried cuz if it fried I would've had to buy my friend a new one. It was a bet to see if could a double oc outta his cpu cuz he always said oc'ing is a waste of time. So to prove him wrong I went to a local store and found another oc'ing enthusiast and got him to let me use his rig. God I'm glad he had an Ayhja! Really I guess since it wasn't entirely my setup it wasn't that big of an accomplishment though.......:(