-
June 22nd, 2001, 11:58 PM
#1
[RESOLVED] Remarked T-Bird?
I just bought a 1.33 GHz T-Bird and an Asus K7V133 from NewEgg and two sticks of 256MB PC133 CAS2 RAM from Crucial.
When I first booted up it showed as a 1 GHz (10X100). I thought nothing of it, asumeing it defualted to a 100 MHz bus. The next day it reverted to a 100 MHz bus after I uped the FSB and RAM to 133. In the BIOS there was a message that it had failed to boot and went back the the standard setings.
Then through the AsusProbe untily it said the my CPU was running at 1333 MHz, but the maxium speed was 1200 MHz.
Do I have a remarked CPU, bad RAM, or am I just missing somthing in the BIOS.
The core dose say 1333C, AXIA K Stepping (if that helps).
-
June 23rd, 2001, 12:07 AM
#2
Sounds like the BIOS for the board needs updating to recognise the faster CPU.
-
June 23rd, 2001, 12:43 PM
#3
Have you tried setting the FSB using jumpers rather than the bios?
-
June 23rd, 2001, 12:52 PM
#4
Registered User
is`nt the CPU clock locked at 100 Mhz?
Some of the Duron and Athlons need L1 bridges shorting to go over 100Mhz.
-
June 23rd, 2001, 01:23 PM
#5
Flash Bios. Doesn't sound like you have latest update. Board could have been sitting around for a while while chip makers were getting faster.
Must not strangle users. Repeat. Must not strangle users.
-
June 23rd, 2001, 02:30 PM
#6
The L1 bridges unlock the multiplier, not the fsb. Besides, this is an Athlon "C", which is designated to run at a 133 fsb.
-
June 23rd, 2001, 09:33 PM
#7
I do have the newest BIOS, but I'm running well in jumper mode.
-
June 24th, 2001, 01:41 AM
#8
Registered User
When you were talking about an asus k7v133, I'm pretty sure you meant asus a7v133.
I put in a t-bird 1.2 ghz running at 133 (266) mhz fsb. I was using the jumperfree mode. Turned out the fsb bus is automatically set at 100. Just like what you did, I set the cpu settings in the bios from standard to user define to properly get the cpu to display the correct speed. Seemed to work at 1st. Then the customer phoned and said we sold him a t-900 and not a t-1200 (133)!!!! Turned out he subscribed to a 1 month free high speed internet service and they came to his house to install a pci nic into that same computer. When they did that it reset the asus mb bios settings to default. So, I had to have him bring it down and I set it back up in the bios under user define and showed him how to set it again if it happens another time. I think I should have set the jumpers instead!! <IMG SRC="smilies/rolleyes.gif" border="0"> <IMG SRC="smilies/redface.gif" border="0"> Haven't heard from him in the past little while, so it must be working okay for him.
-
June 24th, 2001, 03:04 PM
#9
Senior Member - 1000+ Club
is`nt the CPU clock locked at 100 Mhz?
Some of the Duron and Athlons need L1 bridges shorting to go over 100Mhz.
Not if it's an AXIA, they are totally unlocked.
Perhaps a 1Gig Axia sold overclocked?
I'm in charge and I say we blow it up
-
July 2nd, 2001, 02:35 PM
#10
Clear the cmos and then set the jumpers to 133.
If this is a new board you should always clear the cmos before first boot.
I see a lot of people saying flash bios,This is never needed unless the board maker has an issue that needs fixing like compatability issues,These issues are related to add on cards almost never is a bios flash a processor related issue.
That mother board is designed to run the processor you have so clear the cmos and start over GOOD LUCK
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Bookmarks