An exclusive gaming industry community targeted
to, and designed for Professionals, Businesses
and Students in the sectors and industries
of Gaming, New Media and the Web, all closely
related with it's Business and Industry.
A Rich content driven service including articles,
contributed discussion, news, reviews, networking, downloads,
and debate.
We strive to cater for cultural influencers,
technology decision makers, early adopters and business leaders in the gaming industry.
A medium to share your or contribute your ideas,
experiences, questions and point of view or network
with other colleagues here at iVirtua Community.
Never Lower the CPU Multiplier when OC'ing the Athlon 64. :) The problem is that the Memory Controller feeds off the CPU Multiplier. The faster the Multiplier the better overall system performance.
Now if you have a CPU with a locked multiplier & you cannot go over 10x then leave it @ 10x. And just play with the HTT. P.S. The Athlon 64's have no FSB they have HTT.
The HTT is 200MHz default. The HTT multiplier is 5x default. So, 200MHz x 5 = 1000MHz (2000MHz DDR) CPU Frequency = 2.00GHz ((HTT 200MHz x 10(CPU Multiplier)) If you change the HTT anywhere between 201 to 250 then you need to reduce the HTT multiplier to 4x.
The HTT is 250MHz OC. The HTT multiplier is now 4x. So, 250 x 4 = 1000MHz (2000MHz DDR) CPU Frequency = 2.50GHz ((HTT 250MHz x 10(CPU Multiplier)) Can you see how this works? You are keeping the HTT speed at a stable speed while OC'ing the CPU Frequency.
The HTT is 280MHz OC. The HTT multiplier is now 4x. So, 280 x 3 = 840MHz (1680MHz DDR) CPU Frequency = 2.80GHz ((HTT 280MHz x 10(CPU Multiplier)) Now with this, you increase the CPU Frequency to 2.80GHz but lose on the HTT speed. This is why you NEVER Lower the CPU Multiplier when OC'ing.
I could of done this. The HTT is 280MHz OC. The HTT multiplier is now 4x. So, 280 x 4 = 1120MHz (2240MHz DDR) CPU Frequency = 2.80GHz ((HTT 280MHz x 10(CPU Multiplier)) But there may be stability issues due to the HTT being higher than the 1000MHz mark. Especially when you have an OC of 2.80GHz.
well i did lol. It seems to be more stable and runs cooler. I gained nothing on speeds but at least i didnt loose speeds. I find that going to high after droping the multi will cost you on stats. If i go to 260 its unstable.
well i did lol. It seems to be more stable and runs cooler. I gained nothing on speeds but at least i didnt loose speeds. I find that going to high after droping the multi will cost you on stats. If i go to 260 its unstable.
It could still be somehing simple, like you have maxed out your CPU Vcore & you need more &/or your system is getting too hot, even though it's only 50C or so. Your motherboard may be set @ default to auto restart when Temps go up. :)
Last edited by Super XP on Fri Feb 04, 2005 4:21 am; edited 1 time in total
Wait, so on Athlon 64's it's better to increase the multiplier, rather than the FSB?
Because I believe in Athlon XP's, it was the other way around.
Yes, Either keep the Athlon 64 CPU Multi @ default or increase it. DO NOT Decrease it. The Athlon XP performs better with increasing the FSB & lowering the Multi.
There is a fine balance to over clocking. I have found that if your having a hard time over clocking enough to fully power the PC 4000 ram that requires a FSB of 250 you can drop the CPU multiplier by 1 and up the front side buss. It seems the memory multiplier can be very tricky. Do not over clock to far or you will loose performance when dropping the multi.
There is a fine balance to over clocking. I have found that if your having a hard time over clocking enough to fully power the PC 4000 ram that requires a FSB of 250 you can drop the CPU multiplier by 1 and up the front side buss. It seems the memory multiplier can be very tricky. Do not over clock to far or you will loose performance when dropping the multi.
Digg Topic
Tag topic on On del.icio.us
Technorati Search
Post to Slashdot
