IS CPU-Z sure I have a Barton?

[mazeroth]

My buddy gave me his old AMD Athlon 2800+ and said it was a Sempron. He's not super knowledgable with computers so we'll leave it at that. I set my ASUS to auto and it is running this CPU at 133mhz bus x 12.5 multiplier = 1668 mhz. When I run CPU-Z it says I have a Barton chip, which should be running at something like 2083mhz. I tried manually setting my FSB in BIOS to 166mhz. It will boot, but once 3DMark runs for a few minutes it will lock up. I tried upping the voltage from 1.65 to 1.70 with no luck. The memory I have is PC3200 Corsair Value Select 2x512mb.

So, is it really a Sempron and CPU-Z is wrong? Or do I need to work on getting it up to its Barton speed? Check the attached pics of CPU-Z, if you will.

Thanks!

http://geocities.com/mazeroth9/cpuz.jpg

 

[Green Man]

512KB L2 cache size indicates it is a Barton.

 

[3chordcharlie]

It is an athlon 2800+, and yes, it is a barton.

You are running the chip at 133fsb, and it should be at 166fsb, which will give you 2.083ghz.

Edit - oops you already knew that - your chiset is kt333, I don't know for sure if the original kt333 supported 333fsb, or just 333ddr. Is it a 'real' 166fsb setting, (1/5 pci divider)? or was the system overclocked to 166fsb?

I would suggest looking for an updated bios for your motherboard.

 

[mazeroth]

I go into BIOS and set the FSB for 166/30 (something like that). It will boot just fine at 2083mhz but once I try to run 3DMark it will crash after a few minutes. Do I need to mess with the jumpers on the board? I think there's a RAM setting on there that I can manually change. He gave me the board as well.

Thanks guys!

 

[3chordcharlie]

Originally posted by: mazeroth
I go into BIOS and set the FSB for 166/30 (something like that). It will boot just fine at 2083mhz but once I try to run 3DMark it will crash after a few minutes. Do I need to mess with the jumpers on the board? I think there's a RAM setting on there that I can manually change. He gave me the board as well.

Thanks guys!

What is the 30?

The reason I asked is that crashing in 3Dmark may be caused by your ram or graphics card.

 

[mazeroth]

I went into BIOS and checked. When you set the Memory/PCI speed it gives options like this:

133/33
134/33
135/34
.........
150/37
.........
166/33

Also, when I go under Set CPU Frequency it gives me the option of 1250/1663/2083 (close to those numbers) and then it also gives manual. I'd love to get another 400mhz out of this baby! Any ideas?

 

[mazeroth]

I just found this on ASUS's website. Scroll to the bottom to the "333MHz FSB CPU support on A7V333"

http://support.asus.com/faq/faq.aspx?SLanguage=en-us&model=A7V333

How do I know if I have a version 2.0 PCB?

EDIT: I see CPU-Z says I have a revision 1.xx motherboard. I take it this means I'm screwed getting this Barton to 166mhz FSB?

 

[3chordcharlie]

Originally posted by: mazeroth
I just found this on ASUS's website. Scroll to the bottom to the "333MHz FSB CPU support on A7V333"

http://support.asus.com/faq/faq.aspx?SLanguage=en-us&model=A7V333

How do I know if I have a version 2.0 PCB?

EDIT: I see CPU-Z says I have a revision 1.xx motherboard. I take it this means I'm screwed getting this Barton to 166mhz FSB?

Not necessarily, if you have 166/33, that's the correct divider for pci and agp busses.

Your ram will have been 'overclocked' (and I say this because I don't know if it is ddr266/333/400) to 166 (333) when you changed your processor speed. You should adjust your ram timings to 2.5-3-3-6 or thereabouts, and possibly bump teh voltage up a little if it is at 2.7v or below. If this doesn't work, there may be a divider and/or +/-33mhz option for the ram that will let you run it at ddr266, while your processor stays at 333 fsb.

 

[Fox5]

Originally posted by: 3chordcharlie
It is an athlon 2800+, and yes, it is a barton.

You are running the chip at 133fsb, and it should be at 166fsb, which will give you 2.083ghz.

Edit - oops you already knew that - your chiset is kt333, I don't know for sure if the original kt333 supported 333fsb, or just 333ddr. Is it a 'real' 166fsb setting, (1/5 pci divider)? or was the system overclocked to 166fsb?

I would suggest looking for an updated bios for your motherboard.

The kt333 only had 333ddr support, it did not support a 333mhz fsb, though the better boards could overclock fairly close to it.

 

[3chordcharlie]

Originally posted by: Fox5

Originally posted by: 3chordcharlie
It is an athlon 2800+, and yes, it is a barton.

You are running the chip at 133fsb, and it should be at 166fsb, which will give you 2.083ghz.

Edit - oops you already knew that - your chiset is kt333, I don't know for sure if the original kt333 supported 333fsb, or just 333ddr. Is it a 'real' 166fsb setting, (1/5 pci divider)? or was the system overclocked to 166fsb?

I would suggest looking for an updated bios for your motherboard.

The kt333 only had 333ddr support, it did not support a 333mhz fsb, though the better boards could overclock fairly close to it.

I wasn't sure - I have a board that does support 166fsb, but maybe it's a kt333a or something. The dividers listed by the OP suggest his board does support 333fsb though.

 

[formulav8]

The kt333 only had 333ddr support, it did not support a 333mhz fsb, though the better boards could overclock fairly close to it.

That is NOT correct. The original KT333 were not 333fsb supported. But the 'CE' versions DID have true 333mhz support. You have to take the northbridge hs off to see if it is the CE version. But since it looks like in the bios of his board it has the 1/5 divider, he has the 'CE' version.

I also have a MSI KT333 board somewhere and it ran perfectly fine and stable and fast with a 2500+ Barton oced to 2ghz on the 333mhz fsb.

So, either his boards bios is not correctly setup to run the 333mhz fsb chips or one of his components doesn't like the increased frequency or the bios is bugged or a combination of things, he should be able to handle the 333mhz fsb. Need to check if his memory is running faster than its rated speed. That is the first thing I would check. I would also check the temp of the cpu and make sure it has a good hsf for the cpu.


Jason