1st OC

[Leoslocks]

I have build an xp1600 based system and am trying to overclock it.
Soyo KT333
xp 1600 (attempted unlock)
768 Crucial 2100 ram


The settings in the bios are a little hard to get a grip on.

1. The cpu frequency will only go to 132.

2. The multiplier will only go as high as 12.5

3. Where or how do the devicers come into play?

Attached is an overclock at 1.6 ghz. I think the cpu is at 128 and the multiplier is 12.5.

If I set the bios to default settings, it boots as a 1 gig Athlon. I assume the unlock works.??

[Leoslocks]

screen shot

[pdemitra38]

not bad...if u can change the multipler like that the unlock did work

stock should be 10.5 * 133 = 1400MHz

the soyo kt33 should have a 1/5th PCI divider which should start at about 166MHz or so. did u up the vcore at all? sounds very odd that it will only go 132. try upping the vcore little bits at a time and see if it helps. your temperatures may have come into play already also. what heatsinc and fan combo do u have?

cooling is always big issue..

[cfb44]

if your fsb only goes to 132, then there must be a jumper for 100/133 fsb. reset the multiplier to auto or 10.5 in bios, then reset the jumper to 133. it should post normal, then you should have options higher then 132 fsb. then you can lower the multiplier and raise the fsb as far as your RAM will go...

[Leoslocks]

OK, I am off to try the suggestions.

SLK 800 with an enermax adjustable fan. I tried to use an expensive quite Panaflow fan on the CPU but the board would not boot with the low rpm fan on it(CPU 1 header). Auto shutdown 8 seconds into the boot sequence.

I forgot to mention that I lowered the voltage to 1.6
Temps went down from 39-40 to 36C.

[Leoslocks]

You guys are right on the money.

I changed the cpu to 133.

The multiplier to 12.5.

Vcore to default 1.76

Running at 1.6 Ghz. 39 C.

I tried upping the fsb and couldn't boot into windows. I started much too high and worked down. That is quite backwards. Now that W2K is working ok I may try upping a cycle at a time.
How about trying a 136 fsb.

[pdemitra38]

try upping the vcore to 1.8 or more if needed be

my vcore is at 1.9 right now with idle temps at 40 usually and load temps of 46-47.

if i open the window i can get idle temps down to like 35 or so but then i freeze also

[Leoslocks]

138 @ 12.5 and I am running at 1.72 Ghz as an xp2100.

Temps stay at 42C with the case at 30C while running the CPU Benchmark in Sandra.

This is so cool. I may get adicted to this stuff. Well, I am more inclined to do the undervolting/silence thing when I get a good grip on how this works.

I saw the USB section showing the Bus speed at 48 MHz. Where could I find the PCI Bus speed in the standard edition of Sandra?

[pdemitra38]

use sisoft sandra and go to the mainboard information and scroll down untill u see pci...they also have agp if u were curious

[DuronClocker]

God I'm so jealous of those temps. That SLK-800 is so amazing.

Oh well, I'm into P4s now though.. hot stuff! Much hotter than my Athlon.. But I'm going watercooling soon enough

[pdemitra38]

Yeah those SLK-800s are rather nice. I think i may hafta pick up one for myself...maybe then i will be able to dip into the 1.9GHz range

[Leoslocks]

Well, I got the Raid 0 array set up on two IBM 30 gig drives. I couldnt get QIII to work on the other setup so the first thing I did after installing the Parhelia drivers was to install QIII. I could play it quite nicely but the task bar went to shreds when I exited the game. I tried backing down the OC but still had issues. So, I am running it at 133 x 10.5 and the game is so smooth. As soon as I install the onboard stuff, USB, Cmedia Sound, Lan . . . . QIII locks at a white screen trying to start.

Matrox calls it an IRQ conflict. I am unable to change the IRQ settings in W2K (acpi). I will try Matrox support this week and see if they can help. I really like the display with this card but if I can not get Q3 to work I may rma it or send it back to New Egg.

I couldn't find any Ti4600 or any dual Ti4200 cards locally. None on the shelf. I thought it was the dock strikes but found out that nVidia wasn't supplying any more "old" chips.

[pdemitra38]

try getting the latest drivers to everything...that always helps. a lot of times the drivers on the cds are out of date

[Leoslocks]

I thought I had downloaded all the lates drivers before I bought the Matrox Parhelia.
Got DirectX8.1b
Matrox Beta 1.2
.Net 1.1 (why it needs this I dont know)

I was behind on the via drivers.
4 in 1 4.43

Still the white screen lock. I talked with Matrox today and they refered me to their "Forum". How convienient. . . . I see good advice there but it seems that Matrox wants to remain isolated from the lone customer.