2600 being seen as 2000?

Dfresh

Weaksauce
Joined
Mar 22, 2004
Messages
79
I've got an Asus A7V266 that currently has a 1700+ in it. I'm putting together an HTPC system and got a 2600+ for it and decided to just swap cpu's since I could use the 2600+ for gaming. When I popped the 2600+ in my A7V266 it keeps detecting it as a 2000+. I can't find any options in the bios that make any difference. Tried oc'ing to get 2600+ speed, but it hangs after rebooting. I realized the 2600+ I bought has the 333FSB. Could this be the problem? I also found a set of jumpers on the mainboard that are for Palomino Frequency processors. Should I change this to that instead of the current standard Athlon/Duron setting it's at?
 
If its a 333FSB processor then its going to have to run below its rated speed. It will be running (multiplier x 266) instead of (multiplier x 333). No way around it unless you can "overclock" the 266FSB as close to 333 as you can. Keep in mind that you might push your AGP or PCI speed unless that board has a divider for it.
 
So actually it's not possible to get the rated speed at a lower FSB? Never knew that. Thanks
 
Tech Report has a handy chart where you can see the differences in multiplier, front side bus, etc. http://techreport.com/cpu/. Looks like you have the Thoroughbread 2600+, because according to that chart its multiplier is 12.5. 12.5x133(266DDR) is 16655Mhz or 1.6Ghz, the frequency of the 2000+.
 
bottom line, youre running at 1600MHz... 16x100MHz...

looks like your 2600 is a 16x133 cpu...

set the bus speed to 133 and it should be detected as a 2600+

Run crystalcpuid or cpu-z to verify the multiplier...

Later
MD
 
MD_Willington said:
bottom line, youre running at 1600MHz... 16x100MHz...

looks like your 2600 is a 16x133 cpu...

set the bus speed to 133 and it should be detected as a 2600+

Run crystalcpuid or cpu-z to verify the multiplier...

Later
MD

I'm speechless... :confused: Make sure you aren't running in Pentium 4 mode as well... :rolleyes:
 
According to crystalcpuid the fsb is set to 133. When I go into the bios the default settings for the 1.6Ghz speed is 12.5/13 multiplier and 133/33 System/PCI Frequency.
 
Every time I set the fsb to 166 it hangs. The system/pci frequency is the fsb setting in the bios right? The board is set for jumper free mode. I shouldn't have to do this manually should I?
 
What is your RAM rated at? Maybe its being overclocked and running 1:1 (333 as well).
 
Bingo. Make sure your RAM is running at 133 or 266, however it reads in your BIOS. You might have to set some kind of divider, I dont remember what that BIOS looks like. I know this might be getting old, but check the manual to see how you change the RAM speed.
 
I'm not at the comp right now so I'm goin by memory, but I do remember a couple settings in different areas. One gave me the choices of Auto, 100:133, or 133:133. Then I also remembers settings that allowed me to choose speeds of Auto, 7ns, or 8ns. I had it set for 133:133 and 7ns. It still hung every time.
 
Even if its set to jumper-free mode, I'd still go and mess with those jumpers. That board is supposed to support 333, that includes ram. Those settings you listed though are only for 200/266 DDR (or PC1600 and PC2100) so theres something that needs to unlock the whole 333 option but hopefully leave you a RAM divider to run the RAM at the lower speed. Some boards make you switch between 100/133 and 166/200 via a jumper and then after that its jumper-free. Have you tried resetting the BIOS and then changing only the CPU/RAM info (no changes to timing, etc)? Try 11.5 for the multiplier maybe if it lets you mess with it. It should auto-detected, but who knows. I would seriously first check that jumper though (J11 I believe, the manual says where its at on page 231).
 
I'm not sure I'm following how the A7V266 supports a 333FSB when the manual says it's only 266. I'm not sure what jumper you mean by J11 on page 231. The manual only has 110 pages. Do you mean the I/O Voltage jumper? I'll try leaving the timing at auto as I think I put it to 7ns from the start. Sorry for all my confusion.
 
HOLY CRAP talk about mixed up. Completely wrong thread, I was helping someone else out with something similar but a different motherboard. DOH! My sincerest apologies. :(
 
LOL! That's ok. At least I know I was thinking correctly now. I was starting to get really confused on how to get this to work. Thanks for the help anyways.
 
Yeah you can ignore the previous 4 posts completely. The sarcasm for willington still applies though. :p
 
Back
Top