Posts by wanderingbadger16

Regarding processors:
I still find myself using my old 286 (every once in a while), even though it’s about 15 years old now.
Right now, I've got an Athlon running on a Socket A board, and I plan to keep pushing it until it finally gives up the ghost.

Buying brand-new hardware every single year feels like throwing money straight down the drain.

Aux1 said:I bumped my FSB to 182 MHz to hit roughly 2 GHz. I've had Prime95 running for about 20 minutes now and everything seems solid (the readme mentions that any potential errors usually pop up within the first few minutes). My CPU temp has leveled out at 74°C (it maxes out at 68°C when it isn't overclocked). Is that range acceptable? Also, if I pop the side panel off the case, the temps drop by about 3-4 degrees, but then the fan noise becomes a real nuisance...

Your CPU temperature is running a bit hot🙂. It sounds like you might have a subpar heatsink or perhaps the thermal application isn't quite right. I'd suggest picking up some high-quality thermal paste and applying a very, very thin layer to both the processor and the heatsink.

restlesslynx said:If I just nudge the settings up bit by bit and proceed with extreme caution, does that mean there's no real risk of burning anything out? I have this gut feeling that overclocking is inherently risky, but then again, I feel like if you're constantly monitoring temperatures and following the right procedures, it shouldn't be that dangerous...

Look, I'm running a Duron 800 MHz, so logically I should have plenty of incentive to push the clocks, especially since I've got an nforce2 ultra chipset and memory rated at 400MHz. However, I'm choosing not to overclock for two specific reasons:
1. I'm currently using an old cooler—it feels like one meant for a Pentium II—that spins at nearly 5000 RPM. I really don't feel like swapping it out for the new one I already bought just yet, because I'm waiting until I can upgrade to a better processor. Right now, my CPU temperature sits steady at 66°C. For some people, that's what they see when they're overclocking, but for me, it's more like the upper limit where a chip can run for a long, long time without giving up the ghost.
2. Overclocking always carries a degree of risk. Pushing hardware beyond its factory-rated specifications will inevitably shorten its lifespan, and in extreme cases—if someone gets reckless—it can lead to a total system failure.

I actually wanted to try bumping up the memory speed instead, since theoretically (and practically), it could run twice as fast as the bus. My FSB is 100MHz while the memory is 200MHz(400MHz). I didn't manage to pull that off, likely because my motherboard (according to the manual) doesn't support the specific processor I've been using on this board for about two years.
So, my only remaining options are to set the FSB:MEM ratio to:
100MHz:100MHz(200MHz)
100MHz:133MHz(266MHz)
100MHz:166MHz(333MHz)
Out of those three configurations, the first one is actually the fastest. This is due to the synchronized operation of the FSB and memory, and perhaps just as importantly, the lower RAM latencies, which in my case sit at a crazy 2-2-2-4 in that first setting.😁

restlesslynx said:You can just paste it right here...

I can't paste it here because the file size is a bit too large, so the system won't let me.

restlesslynx said:So, what if I set it to 1:1 and then just push the FSB as high as it'll go?

Yes.

restlesslynx said:I ran the Sandra burn-in test, and at FSB 185 MHz, it finished all the tests without any errors (once I bumped it up to 190, I hit a blue screen). At 185, my processor will be at 2035 MHz and the memory at 370... what do you think about those numbers?

That seems fine.👍 The main thing is ensuring Windows stays stable. You should probably run a few more benchmarks to really stress the machine and make sure it won't crash on you later.

If you're interested, I can shoot you an email with the benchmark results I ran using various memory timings and FSB settings so you can draw your own conclusions. <- 1:1 is the optimal setting here
Just make sure you set the SPD to the memory's rated speed.
The answer is YES.

Yes, the SPD will set your memory to 400MHz (your BIOS should show "By SPD," meaning the RAM is running at its rated speed of 400MHz). For instance, if you were using 433MHz memory, the SPD would automatically configure it to that specific frequency. On the other hand, if you manually set the memory percentage to 100% of the FSB, then your memory will always run in a 1:1 ratio with the FSB.

As I mentioned earlier, you really can't go wrong by keeping the FSB and memory at a 1:1 ratio. Based on the benchmarks I've run myself, that's where the system performs most reliably. If you bump up the FSB in the BIOS while leaving the memory set at 100%, you'll consistently maintain that 1:1 ratio.
Using SPD simply means the memory will default to the exact settings hardcoded into the memory chip, just as you noted. If you select SPD, the memory will always run at its rated speed, which for PC3200 would be 400MHz.

The memory runs at exactly 100% of the FSB in terms of actual MHz, though your BIOS will report it's running twice as fast because of its effective speed.
Essentially, if you see an FSB of 166MHz and the memory is clocked at 166MHz, the BIOS will display 333MHz.
So, if you bump the FSB up to 200MHz, the BIOS should show the memory running at 400MHz.
!!! Just don't push it too hard or you might fry your processor—make sure you're constantly monitoring your temperatures with some utility software.

PS. Grab CPU-Z from the web (just search for it on Google)—it’s a handy little tool that gives you all your system specs.
Otherwise, ASUS ROG Maximus comes with a program called EasyTune on the driver CD, which lets you overclock just about anything right within Windows. You'll need to set certain parameters to AUTO in the BIOS first, though; the motherboard manual has a specific section on this under "EasyTune." I've messed around with it, and it’s actually decent, but I personally find the BIOS offers much more precision and stability when you're overclocking.
As for the AGP, I can't say for certain, but it most likely stays at the standard 66MHz frequency if you have it set to NORMAL in the BIOS. You might be able to check the frequency via EasyTune once you start tweaking things.
Best of luck.😉

restlesslynx said:The BIOS gives me options for the AGP frequency ranging from "Auto" up to anything from 50 to 100 MHz, plus memory frequency settings where I can choose "by SPD" or a range from 50 to 200%. I'm a bit out of my depth here—how would you guys configure these if the plan is to bump the FSB up in 10MHz increments?

Setting the memory to 100% essentially means it runs at the same frequency as your FSB.
For the AGP, just leave it on AUTO (it shows as NORMAL on my system). You really want the AGP to remain independent from the FSB.
From there, you can start stepping up those FSB clock speeds.🙂

PS. I'm not entirely certain how the NORMAL setting behaves, but my assumption is that it stays locked at the standard 66MHz
regardless of whatever you do with the FSB.

restlesslynx said:My motherboard is an ASUS ROG Maximus
I have PC3200 memory, so can it handle 400MHz? Does that mean regarding the memory itself, I can bump up the bus speed to 200MHz without any risk?
By the way, I just bumped it from 166 to 171MHz in the BIOS just to test things out, and now it shows a processor frequency of 1.88 GHz.

I am downloading SiSoftware Sandra right now; I seem to recall it having overclocking tests. In your opinion, what is the best way to stress test a processor after bumping up the frequency?

Give PCMark04 a shot. I'm not sure if there's a newer version available. I actually found this one on a disc by Bugov.

The trick with syncing the FSB and the memory is this: I ran some tests using various memory speed settings, and here is what I gathered:
I have a Duron 800MHz with a 200MHz (100MHz) FSB and PC3200 memory, running on an nForce2 board similar to your ASUS ROG Maximus.
When the FSB and RAM run at a 1:1 ratio (200MHz:200MHz), I noticed that PCMark actually produces better results in most tests than when the memory runs faster—say 266MHz or 333MHz—while the processor stays fixed at 200MHz.
Of course, the differences aren't massive.
My takeaway is that it’s generally best to set the FSB and memory speeds to run in sync.
I tried pushing the memory up to 400MHz, but Windows kept crashing constantly. This is likely due to the aging processor or perhaps the motherboard, since the manual states support for processors starting at 1.4GHz.

In my view, you should be able to increase the bus speed without issue as long as it stays at or below 400MHz. You can push the bus higher too, but the question becomes how stable that PC3200 memory really is; plus, the latencies get much higher, which isn't ideal for Athlon chips. So, you really have to find a sweet spot.
If you go down that route, I think it would be worth investing in slightly faster memory.

hollowjackal13 said:you can bump up the FSB without much headache if your motherboard BIOS supports asynchronous operation. On my board, I increase the processor bus speed while keeping the memory and AGP speeds constant, so I've never run into stability issues with the CPU or the rest of the components. At factory settings, my processor runs at 1912 MHz, but by pushing the bus speed, I managed to get it up to 2.2 GHz. With Barton cores, the multiplier isn't unlocked; you have to unlock it by shorting the L1 and L2 contacts on the chip, which isn't exactly a simple task.

True, it all really comes down to which motherboard you're running. In my case, when I push the FSB, the memory speed jumps up automatically unless I manually go into the BIOS and set the memory ratio to a lower percentage relative to the increased bus speed. As for the AGP, mine stays steady, though some boards will cause the AGP clock to climb right along with the bus speed, requiring you to lock the parameters so it stays stable. Some motherboards handle this with a specific "Fix AGP" option, or on mine, I just set the AGP frequency to normal.
I haven't tested how the memory behaves when you push past its rated speeds, but as far as the processor goes, it works fine.
Ultimately, overclocking the bus is the kind of job where you need to know your stuff to avoid frying something. You clearly know what you're doing, hollowjackal13. Keep up the good work!🙂

There are essentially two ways to approach overclocking:
1. Front Side Bus overclocking—increasing the FSB speed directly impacts both your processor and memory performance. This implies that (in terms of RAM) you really need high-quality modules that can handle speeds higher than the target frequency you're aiming for via the bus.
With an nForce2 chipset, your maximum FSB is capped at 400MHz, which means if you want to push the bus, you'll need memory rated for even higher clock speeds. Additionally, pushing the FSB requires a high-quality motherboard.
2. Multiplier overclocking—this method focuses solely on increasing the CPU speed. In this scenario, the FSB speed is multiplied by the multiplier to reach higher processor frequencies while the bus itself stays at the same speed. To pull this off, you need an unlocked multiplier on your processor, which isn't typically the case with an Athlon (I'm not entirely certain if this applies to every single model—please feel free to correct me if I'm wrong).

Currently, your bus is running at 333MHz(166MHz) because of the specific processor you're using. Assuming your RAM is rated for 400MHz(200MHz), you do have the headroom to overclock the bus. However, in my experience, the most effective results come from bumping up the CPU multiplier; I wouldn't personally recommend focusing on the bus speed.
So, provided you have a decent BIOS, try increasing the multiplier first.

Where did you pick up that card? Is it the PCIe or the AGP version?
In my view, unlocking those extra pipelines is perfectly fine, provided they are functioning correctly—which seems to be the case with yours. That said, I don't think pushing the clock speeds is particularly wise for the long haul. I’ve come across several articles online regarding overclocking, and there was quite a bit of discussion about how it inevitably shortens the lifespan of the card.
It is worth noting, however, that while unlocking additional pipes does raise the GPU temperature, it doesn't spike it nearly as much as overclocking does.
So, as far as potential future issues with the card go, it’s really anyone's guess whether they'll actually happen.
Generally speaking, my stance is that high temperatures in any piece of hardware will ultimately shorten its service life.
It is funny, though—my old 286 is still running today despite having absolutely no cooling system at all. The processor temperature stays just slightly above room temperature.

The graphics cards are all solid choices; if you’re chasing raw speed, go with the Nvidia 6800 GS, but if you want better image quality, the X1600XT is the way to go.
As for Intel, I'm a bit undecided, though personally, I'd probably lean toward an Athlon.