#581 ·
Since the processor is incredibly cheap, I don't even know what to say, but having two cores for $367 that damn thing!
Overclocking (Main Thread)
Started by dustypilot23 · · 👁 81 views · 3.3K replies
#582 ·
After unlocking all the vertices and pipelines, I decided to push the overclocking further, moving from 300/700 up to 380/800. I hit a wall with the software I was using (ASUS SmartDoctor), so that's where it ends. My score in Deutsche Mark03 jumped to over 9400—it was sitting at 6200 at Equity, and climbed to 8400 after the softmod 🙏. I configured the HyperDrive setting so the frequency only ramps up when I actually launch a 3D game. I didn't spot any artifacts during the 3DMark run, and I don't think the GPU temperature even crossed 75C during the ten-minute stress test, as I didn't hear the cooler ramp up (you can adjust the fan curve based on temperature within ASUS SmartDoctor)
.
I won't be pushing it any harder; the memory on this card lacks passive heatsinks and my case isn't exactly high-end in terms of airflow, so I have no intention of being reckless 😉
.
Ultimately, I want to know if this means I can safely run this card at 16/6 & 380/800 MHz (instead of 8/4 & 300/700) MHz since everything looks stable right now, or am I just inviting future headaches and stability issues?
If I can actually get away with this, then this card might just be the absolute best value for the money out there! 🙏
.
I won't be pushing it any harder; the memory on this card lacks passive heatsinks and my case isn't exactly high-end in terms of airflow, so I have no intention of being reckless 😉
.
Ultimately, I want to know if this means I can safely run this card at 16/6 & 380/800 MHz (instead of 8/4 & 300/700) MHz since everything looks stable right now, or am I just inviting future headaches and stability issues?
If I can actually get away with this, then this card might just be the absolute best value for the money out there! 🙏
#583 ·
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.
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.
#584 ·
wanderingbadger16 said:Where did you pick up that card? Is it the PCIe or the AGP version?
In my estimation, unlocking those additional pipelines is perfectly acceptable—assuming they are functional, which seems to be the case here. However, I find pushing the clock speeds to extremes to be questionable for long-term stability; I have encountered several technical articles discussing how aggressive overclocking inevitably compromises the lifespan of the hardware.
It should be noted, however, that while enabling extra pipes does increase the GPU temperature, it doesn't hit nearly as hard as overclocking does.
Consequently, regarding potential future failure, it remains an uncertainty.
My general stance is that excessive heat from any component will shorten its operational life.
It is quite fascinating, though, that my old 286 machine still runs flawlessly despite having zero cooling whatsoever. The processor temperature barely sits above room temperature.
The AGP 8x version, purchased via Best Buy.
I needed something to allow me to run Oblivion with decent settings on my aging 2.5GHz rig (AMD Athlon 2600+, 1GB RAM...) without breaking the bank. I specifically opted for the Nvidia GeForce 8800 GTX because the word is that you can unlock the pipes and get a solid overclock out of it. In its Equity state, it isn't particularly fast, but once you crank it up like I have, it sits right between the 6800 and the 6800GT—at least according to my 3DMark results. This ASUS SmartDoctor utility is actually quite impressive; it makes monitoring and fine-tuning everything remarkably easy. It appears that even with the overclock, temperatures during gameplay don't exceed 70°C, and the fan stays at a steady medium speed of about 2000RPM. I suspect it could spin two or three times faster if needed, though it would likely sound like a vacuum cleaner 😁.
My only grievance is the lack of heatsinks on the memory modules, but if the readings from ASUS SmartDoctor are accurate, the temperature peaks at only 65 degrees.
I find it somewhat surprising that things aren't running hotter; perhaps the cooler is just high quality, given that the passive portion is copper...
And yes, I only push the frequency while playing—roughly three hours a day at most.
Having 256 MB would have been ideal, but that wasn't an option within this budget. 😉
#585 ·
I’m starting to feel a serious itch to try overclocking my Athlon. Has anyone here actually pulled this off with a 2500+ model? I need to know the process. Right now, it’s sitting at 68°C under full load, though that drops to 65°C if I just pop the case open. It's running at its stock 1.83 GHz, but I’ve been browsing some forums suggesting people have pushed these things to 2.2 GHz without any major issues...
For context, I'm running an nForce2 chipset with PC3200 memory—does that setup limit my overclocking potential at all?
For context, I'm running an nForce2 chipset with PC3200 memory—does that setup limit my overclocking potential at all?
#586 ·
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.
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.
#587 ·
Hey everyone!
Thanks for the help with the graphics cards. Here is my current setup:
AMD Athlon 2600+, 1GB of PC 3200 RAM (2x512), 160GB WD hard drive, ASUS 9600 XT, Soltek SL-75FRN2 motherboard with an nForce2 Ultra 400 chipset, and more...
I was wondering if anyone could tell me what this configuration is actually worth on the market right now.😕
Thanks for the help with the graphics cards. Here is my current setup:
AMD Athlon 2600+, 1GB of PC 3200 RAM (2x512), 160GB WD hard drive, ASUS 9600 XT, Soltek SL-75FRN2 motherboard with an nForce2 Ultra 400 chipset, and more...
I was wondering if anyone could tell me what this configuration is actually worth on the market right now.😕
#588 ·
You can bump up the FSB without any real headache if your motherboard BIOS supports asynchronous operation. On my board, I increase the processor bus speed while keeping the memory and AGP clocks constant. This way, I've never run into stability issues with the CPU or any other components on the board. At factory settings, my processor runs at 1912 MHz, but by cranking up the bus speed, I managed to push it to 2.2 GHz. Just a heads-up though—the multiplier isn't unlocked on Barton cores; you have to manually short the L1 and L2 contacts on the chip to unlock it, which isn't exactly a simple task to pull off.
#589 ·
wanderingbadger16 said:There are two ways to approach overclocking:
1. Overclocking the FSB—increasing the front side bus speed directly impacts both the processor and memory speeds. This implies (regarding memory) that you need high-quality RAM capable of running at frequencies higher than what you intend to achieve via the FSB.
For an nForce2 setup, the maximum FSB speed is 400MHz, which means if you want to push the FSB, you’ll need memory rated for higher clock speeds. Furthermore, pushing the FSB requires a high-quality motherboard.
2. Overclocking the CPU multiplier—here, you are strictly increasing the processor speed. The FSB speed is multiplied by the multiplier to reach higher CPU frequencies while the FSB remains constant. To pull this off, you need an unlocked multiplier on your processor, which isn't the case with the Athlon (I'm not certain if this applies to all models—feel free to correct me if I'm wrong).
Your FSB is currently running at 333MHz (166MHz) because of the specific processor you have installed. Assuming you have memory rated for 400MHz (200MHz), you technically have the headroom to overclock the FSB. However, in my experience, the most effective results come from raising the CPU multiplier; pushing the FSB is generally not recommended.
So, if you have a decent BIOS, try bumping up the multiplier.
My motherboard is a Gigabyte GA-7N400E.
I'm using PC3200 memory, so does that mean it can handle 400MHz? Does that imply I can safely bump the FSB up to 200MHz without risking any damage to the memory?
Actually, I just tested it in the BIOS by moving from 166 to 171MHz, and now it reports a processor frequency of 1.88 GHz.
I am currently downloading SiSoftware Sandra; I seem to recall it having benchmarks specifically for overclocking. In your opinion, what is the most reliable way to stress-test a processor after increasing its frequency?
#590 ·
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!🙂
#591 ·
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.
#592 ·
The BIOS offers several settings for the AGP frequency, ranging from "Auto" to a manual selection between 50 and 100 MHz, along with memory frequency options that include "by SPD" or a range from 50 to 200%. I'm not entirely clear on the optimal configuration here; how would you recommend setting these if the intention is to incrementally bump the FSB in 10MHz steps?
#593 ·
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.
#594 ·
wanderingbadger16 said:Set the memory to 100%, which ensures it runs at the same frequency as the FSB.
As for the AGP, set it to AUTO or select NORMAL if available. The AGP should remain independent of the FSB.
Once that's done, you can start pushing the FSB clock speeds.🙂
PS. I'm not entirely certain about the AGP settings; I'll need to check my own rig.
I misspoke earlier—for the AGP setting, it actually specifies NORMAL rather than auto. 😉
Furthermore, when I set the memory frequency to 100%, the resulting frequency ends up being exactly twice the bus frequency.
Does this imply that I can begin incrementally increasing the frequency without risking damage to components other than the processor?
#595 ·
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.😉
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.😉
#596 ·
black35 said:What do you guys think about this processor? Intel Pentium D 805 2.66 GHz
- 2 x 1 MB cache
- Socket LGA 775
- BUS 533 MHz
- Prescott core
- EM64T
- Dual core intel d 805
I'm currently running a Barton 2600 and I'm super happy with it, but I was thinking about picking up an AMD Athlon 3200 64 bit. This one caught my eye though because the price is pretty low, around $367
It's basically dual-core for the masses! It costs about the same as a slightly beefier Celeron, yet you still get that dual-core performance. The only real downside is the 533MHz FSB, but if you pair it with a decent motherboard and overclock everything by about 25%, you can push the FSB to 666 😈MHz and hit 3.18 GHz on the CPU—which isn't bad at all for $367.
Anyway, staying on topic, my Pentium D 820 (2.8GHz) is running totally smooth and stable at 3.64 GHz. That's with a 1040 MHz FSB and memory (DDR2 667) bumped up to 867MHz.
#597 ·
wanderingbadger16 said:The memory actually runs at exactly 100% of the Intel frequency in MHz, but your BIOS will report it's running twice as fast because its effective speed is doubled.
This means if you see an Intel of, say, 166MHz and the memory is running at 166MHz, the BIOS will display 333MHz.
So, if you bump the Intel up to 200MHz, the BIOS will show the memory at 400MHz.
!!! Just don't push it too far or you might fry your processor—keep a constant eye on your temperatures using some monitoring software.
PS. Grab CPU-Z off the internet (just search for it on Google)—it's a handy little utility that gives you all your system specs.
Otherwise, ASUS has this program called MSI Afterburner that comes on the driver CD, which lets you overclock just about anything right within Windows, though you have to set certain things to AUTO in the BIOS first (check your motherboard manual under the MSI Afterburner section for details). I’ve messed around with it, and it’s decent enough. Still, I find the BIOS much more precise and reliable for actual overclocking.
As for PCI Express, I'm not entirely certain, but most likely it stays at the standard 66MHz if you leave it set to NORMAL in the BIOS. Maybe MSI Afterburner can show you what the frequency is once you start tweaking things.
Good luck.😉
I was just experimenting with some overclocking using MSI Afterburner (it's useful because it displays the frequencies for the PCI Express, memory, and processor...).
You can probably assume my rig is still breathing if I'm posting this. 😁
By default, when nothing is overclocked, my Intel sits at 166MHz while the memory shows 400. It really should be at 333, but since the BIOS lists the memory clock as "by SPD," I assumed that maybe this
SPD refers to a standardized way to access manufacturer information from a computer memory module.
SPD claims it can hit 400 (though I'm not entirely sure... if the Intel is at 166, where is it pulling that 200x2 MHz memory clock from? Perhaps some kind of frequency multiplier? I'm just guessing... 🙂
You can set the PCI Express to "async" to keep it locked at 66MHz. When I switch the Intel to manual, it stays at 166MHz, but the memory stops being "by SPD" at 400 and drops to 333. I pushed it up to 185 MHz (which puts the memory at 2x185) before hitting a blue screen. So, it seems possible to hit something like 180 Intel (with memory at 360), but the frustrating part is that by overclocking the processor this way, I'm actually losing that 400MHz memory speed; I only get back to it if I max out the Intel. Consequently, unless someone can tell me how to lock the memory at 400 regardless of the Intel—which I suspect is impossible without two separate clock generators—I'm calling it quits on the overclocking. Fortunately, nothing actually broke. 🙏 😎 😁
#598 ·
My system has finally returned to its standard operating frequency. Upon reviewing the data in CPU-Z, I see an FSB of 166 MHz, a BUS of 333 MHz, and a CPU multiplier of 11x; meanwhile, the memory is reported at 200 MHz, which puts the Double Data Rate at 400 MHz. It also indicates an FSB:DRAM ratio of 5:6, implying a multiplier of 6x and a divider of 5x. This explains why my memory sits at 200x2 when the FSB is set to 166. However, the moment I switch the FSB setting to manual, that 5:6 ratio disappears and reverts to 1:1, forcing the memory down to 166x2 while the FSB remains at 166. If there were a way to fine-tune this multiplier/divider ratio—for instance, adjusting it to a 9:10 ratio—I could potentially hit 200x2 MHz with an FSB of 180. I am currently unsure if such granular control is even possible, let alone how one would go about achieving it.
#599 ·
Set that ratio to 1:1........
That's how you get the best performance............
On an nforce2 chipset, that driver just drags everything down........
That's how you get the best performance............
On an nforce2 chipset, that driver just drags everything down........
#600 ·
Kenneth White17 said:Just set it to 1:1........
That’s how you get the best performance............
Because on an nforce2 chipset, that divider just slows things down........
Is that so? I fail to see how it would slow anything down; if you feed it a 166MHz clock, it multiplies that by 1000 and divides by 5, yielding a 200MHz clock which likely stays in phase with the 166MHz clock every 30 cycles or so—that's just my educated guess, but you get the idea.
If it truly causes a slowdown, you'll need to provide a theoretical explanation for why! 😁
Regardless, I'll track down a benchmark and test both configurations myself. 🙂
🔗 Similar threads
- The "Main Event" problem in TV · Jul 30, 2026
- Does anyone else feel like niche sports are becoming the new main event? in Fans · Jul 29, 2026
- The "Main Character" Era of Sports: Is anyone else feeling the exhaustion? in Fans · Jul 28, 2026
- The absolute chaos of modern hobbies and why we need "unrelated" threads in Random / Off-topic · Jul 28, 2026
- The "Niche to Mainstream" Pipeline: Why do we care about certain sports all of a sudden? in Fans · Jul 28, 2026