• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Dumb KT333 questions

G

GnatGoSplat

Golden Member
I have a Shuttle AK35GT2 currently running XP1700+ at XP2000+ (1.67GHz=133x12.5).
It has the KT333 chipset, which I understand can run RAM at 333MHz which is a clock-doubled 166MHz.
So the CPU can definitely run the CPU with a 166FSB and the PCIClk will be at its proper speed (33MHz), correct?

2nd question: If my RAM won't handle 333MHz and I have to run it at 266MHz, can the CPU still be run async at 166? Or is it better to keep the speeds sync'd and stick with 133?

I would just answer my 1st question by trying it, but I'm at work right now. 🙁
 
I'm not familiar with that MB, But ... If it has no lock on the PCI or AGP,,, then your PCI and AGP fsb will increase with fsb.

You can drop your multiplier on the CPU (if its unlocked) and raise your FSB to 166 if you wish.
(to keep your CPU non-overclocked)

You need a BIOS divider adjustment to run async.

Running sync is best.

Use memtest86 to test your ram at 166.
Let it run 10 loops with cache ON to be sure.
You want NO errors.

My KT333 mb (KX7-333) runs stable at 185 with PC2100
 
Thanks for the reply.
It doesn't seem to want to run at 166FSB. It tries to boot, but the screen goes all screwy during the XP boot process and hangs.
Either everything runs overclocked that way, or my cheap RAM won't handle it.
 
Yes, I sure did. The screen messing up makes me think it's the RAM. If I get bored enough, I might pull the PC2700 from my other machine and try it in this one to see if it is indeed the RAM.
It was super cheap RAM so it wouldn't surprise me if it doesn't like 333MHz.
 
Ok ,,, just checkn ...

You can use memtest86 to find out how far the mem will go ...

As soon as you have errors ... either up the voltage, relax the timings, or backoff the fsb ...
 
As far as I am aware the KT333 chipset has no official support for 166mhz (333 DDR) CPU's....just the memory running at that speed.....

KT133 = 133mhz Mem, 100mhz CPU
KT133A = 133mhz Mem, 133mhz CPU
KT266/KT266A = 266mhz Mem, 133mhz CPU
KT333 = 333mhz Mem, 133mhz CPU
KT400/KT400A = 400mhz Mem, 166mhz CPU

Jamie
 
I think this motherboard should support it according to these BIOS updates:

AK35S20F Date : 12/19/2002 Checksum : 0E0
1. Set FSB166 RomSip table is normal mode.
2. Support AthlonXP 2500+ & 2800+ (CPUID=6A0h) Barton CPU.
AK35S20G Date : 01/16/2003 Checksum : 5B00
1. Support AthlonXP 3000+ CPU

I did flash to the latest BIOS.
If I have time tonight, I'll switch that RAM and see what happens (given we're not taking cover from tornados).
 
Can anyone else confirm if the KT333 supports Barton and other 166mhz Socket A CPU's??

If so...Woohoo! (I have Biostar M7VIF - KT333)

Jamie
 
I had my Xp2600 in my KX7-333 running 189.9 fsb.

I think if you do a SEARCH here ... and in Overclocking ,,, you'l find the Bartons work ...

But,,,

You wont have access to some of the higher multipliers, since BIOS doesnt have them.
(in my case anyway ,,,, with my Abit KX7-333,,, check your MB website BIOS features.)

(but you wont need them with a high FSB ...right?)

3dM's
15,074 with Xp1600

Xp2600 - 16,149
 
Originally posted by: TheCorm
As far as I am aware the KT333 chipset has no official support for 166mhz (333 DDR) CPU's....just the memory running at that speed.....

KT133 = 133mhz Mem, 100mhz CPU
KT133A = 133mhz Mem, 133mhz CPU
KT266/KT266A = 266mhz Mem, 133mhz CPU
KT333 = 333mhz Mem, 133mhz CPU
KT400/KT400A = 400mhz Mem, 166mhz CPU

Jamie
Click to expand...

The DDR SD RAM used with a KT266/266A chipset MB runs memory(officially) at 133MHz or or because of the two hits per cycle, 266 equivalent. KT333 has official support for 166MHz or 333 equivalent. Same idea for KT400.
 
Hmmm, this is strange.
I set the memory bus to 166MHz (333DDR) and it booted and ran just fine.
So I ran memtest86 and it passed 100%.
I had to keep the CPU at 133MHz, however, so it's running async.

I guess the BIOS isn't setting the AGP or PCI divider correctly when I set the CPU to 166MHz.
Hmmm...???
 
I find it odd your CPU wont run at 166 at default

(an XP1700 is a 166 chip isnt it...?)

166fsb isnt going to put the AGP or the PCI bus that far outta spec on your cards.

(you may have a heat issue instead)

You might have to help the CPU out ..

Did you try upping the voltage on the CPU and dropping the multiplier?
try mult 10
... and no more than 1.70v

(no more than that for 166 I think)

make sure to check your temps thou ...

You want around 45c to 50c at idle...
(my happy range... even less is better)

If that get it booting ... then run Prime95 to see if your stable.
When running Prime95 ...your CPU will be at it's hottest ... check your temps again

I like under 58c on full load. (under 60c)
 
I think I know what it is... no 1/5 divider for some reason, and I am using the latest "G" BIOS.
I got it to boot ONCE into XP with a 166FSB and SiSoft said my AGP was running at 84MHz and PCI at 42MHz.
So the divider definitely is stuck at 1/4. I tried to look for other settings, but couldn't find them.
I would think this board should be capable of a 1/5 divider.

The XP1700+ is actually designed for a 133FSB but my other machine with an MSI mobo runs an identical CPU with a 166FSB so I know it's not the CPU. It's most likely the BIOS.
 
i remember having a KT333 CD and CE revision
the CD does not have the 1/5
the CE has the 1/5
this was because VIA never expected AMD to launch the 333MHz FSB chips so soon
 
Originally posted by: GnatGoSplat
That could very well be it. I'll see tonight if I can figure out the chipset Rev.
Click to expand...

try taking off the northbridge cooler and seeing the revision
 
opps ... sorry 'bout my mental lapse ...

I seen lots of those 1700's do 200fsb ... (my excuse) 😛

Good luck ... sorry I couldnt help more.
 
Well, I pulled the heatsink off the Northbridge and it's a CE version so I don't know why it doesn't have a 1/5 divider. Crappy BIOS I guess.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top