FSB vs Multiplier, What is Better?

[Cube]

Hey all, what are your thoughts on FSB vs Multipliers for overclocking?

I have an Athlon 1ghz, and when I use the Multiplier I can OC the CPU up to 1200 (100x12). But if I set the multiplier back to 10, and raise the FSB up to 110, the system is somewhat stable. I say Somewhat because I notice that when I use the FSB option, one of my PCI cards seems to be affected since Win2k takes longer to "Prepare Network Connections...".

Now, what should I do? Should I just stick to the Multiplier and leave the FSB alone? Should I do the opposite? Or should I combine the two (if that is possible)?

What would you do?

Jeremy

[Placid]

Usually Fsb but in your case either way will probably be about equal.

Run some benchmarks and see what is better.

[-Exi|e-]

You can mix a little bit of both. The FSB overclocks the whole system as opposed to the multiplier wich overclocks only the processor. If upping the multiplier makes your system more stable compared to more FSB , go for the multiplier or, like i said, a little bit of both, it depends on what you prefer. Try upping the FSB until your system is stable enough, then up the multiplier until you get what you want out of it, but watch your temps!

[m1066ad]

Try buying a new nic card. A friend of mine swears by any card that uses a Realtek chipset. I have the same prob, and nic cards don't cost much, but I'm broker than a Christmas toy on New Year's Day :(

[UnseenMenace]

Now Im confused what does a comment about NIC's have to to with FSB vs Multiplier overclocking, in the wrong place perhaps?

I think Placid gave the best advice, run some benchmarks and see what is better

[badgers]

the nic card is holding back the possible FSB settings.
110 is somwhat unstable because his NIC can't take it.

Getting a nic that can take the speed could allow the 110 FSB.

[Cube]

I think it is the nic too, since Win2k seemed to slow down during it's boot process when it says Preparing Network Connections. I had the machine upped to about 1280 MHz or around that, and Windows wouldn't go past that point.

Now here's a strange thing... My MB has one of those jumpers that allows you to physically set the FSB between 100 and 133. Last night after posting my original post, I decided to lower the multiplier to 7.5 and remove that jumper short to make the default fsb = 133. It booted at 1 GHz and was very stable, even the nic card was working. Temps were fine as well. So right now, I have it OC'ed to 135*9 (1215 MHz).

My CPU temp is hanging right at 50 celcius. I also unfortunately have a stock HSF so my temps aren't as low as they should be. Good thing one that I ordered should be here any day now. Until then I'm not going to give my cpu a reason to get really hot (games, etc).

Thanks for the advice everyone :)

[dugans]

To clarify:
switching fsb from 100 to 133 improved things because it changes the bus clock ratios: @100 mhz fsb pci bus (stock) runs at 1/3 fsb speed=33 and at 133 it switches to 1/4 fsb=33 (approx on both)

Upping the fsb speeds up the communication between cpu/ram/ io cards but some cards are more sensitive to this than others, so they don't run well at high fsb speeds, which caused the nic problem.

With the fsb set at 133, the pci bus is running slower (stock bus speed of 33) than with the fsb set at 110 (110 divided by 3=36) so most cards run better.

AND you have room to up the bus speed again!!

I NEED MORE MHZ!!!!!