Since all the other boards have something like this, I figured.. why not?
I waited months for the nforce3 250, but it still is a no show. I managed to earn quite a bit of money from my part time job so I scratched my itch and bought the Gigabyte GA-K8N Pro. I should be getting my system up and running by thursday, but in the meantime I think we should gather our knowledge about the athlon 64 and try to list things we can do to squeeze as much speed out of the cpu as we can.
From months of research, I've come up with a components list of an athlon 64 system using the nforce3 150 chipset that I think will be most successful for overclocking without breaking the bank. This system also happens to be what I am building
Goal:
-250+ fsb
-DDR500
-600+ HTT.
Special Parts:
-CPU: Athlon 64 3000+
-Motherboard: Gigabyte GA-K8N Pro
-Memory: 2x512mb Geil Ultra Platinum PC4000 (For overclocking, i'll start with a single stick of 512mb)
-Storage Controller: Promise FastTrak S150 TX2plus (Supports up to 66mhz PCI frequency)
Sound Card: Audigy 2 ZS (I heard this card can withstand up to 50mhz on the PCI clock)
-Cooling: Dtek Custom Flowmaster XT Water Cooling kit. (whitewater block and hydor30 pump)
Comments?
Issues:
Now I need some advice on what multiplier's I should try...
From what I've seen, many people clocked their FSB to outrageous 300+mhz speeds, but crippled their HTT speed by setting the LDT as low as 2. Also, the motherboard bios is known to only allow a maximum of 225fsb so overclockers are forced to use Clockgen to lower the multipliers and inflate their fsb.
My questions are, what is the point of high fsb if your HTT speed is limited? How does the synchrony of the memory affect system performance? Is there a way of getting high fsb without the use of clockgen? How will removing PCI speed sensitive devices to allow high fsb help improve performance if you are forced to keep HTT speed @ nominal? How high can I raise the Vcore under the conditions of my system and not significantly raise my chances from falling victim to the famous Athlon64-sudden-death syndrome?
I waited months for the nforce3 250, but it still is a no show. I managed to earn quite a bit of money from my part time job so I scratched my itch and bought the Gigabyte GA-K8N Pro. I should be getting my system up and running by thursday, but in the meantime I think we should gather our knowledge about the athlon 64 and try to list things we can do to squeeze as much speed out of the cpu as we can.
From months of research, I've come up with a components list of an athlon 64 system using the nforce3 150 chipset that I think will be most successful for overclocking without breaking the bank. This system also happens to be what I am building
Goal:
-250+ fsb
-DDR500
-600+ HTT.
Special Parts:
-CPU: Athlon 64 3000+
-Motherboard: Gigabyte GA-K8N Pro
-Memory: 2x512mb Geil Ultra Platinum PC4000 (For overclocking, i'll start with a single stick of 512mb)
-Storage Controller: Promise FastTrak S150 TX2plus (Supports up to 66mhz PCI frequency)
Sound Card: Audigy 2 ZS (I heard this card can withstand up to 50mhz on the PCI clock)
-Cooling: Dtek Custom Flowmaster XT Water Cooling kit. (whitewater block and hydor30 pump)
Comments?
Issues:
Now I need some advice on what multiplier's I should try...
From what I've seen, many people clocked their FSB to outrageous 300+mhz speeds, but crippled their HTT speed by setting the LDT as low as 2. Also, the motherboard bios is known to only allow a maximum of 225fsb so overclockers are forced to use Clockgen to lower the multipliers and inflate their fsb.
My questions are, what is the point of high fsb if your HTT speed is limited? How does the synchrony of the memory affect system performance? Is there a way of getting high fsb without the use of clockgen? How will removing PCI speed sensitive devices to allow high fsb help improve performance if you are forced to keep HTT speed @ nominal? How high can I raise the Vcore under the conditions of my system and not significantly raise my chances from falling victim to the famous Athlon64-sudden-death syndrome?
Facebook
Twitter