SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Advanced Micro Devices - Moderated (AMD)
AMD 238.54+2.9%11:46 AM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Paranoid who wrote (148975)1/25/2005 3:24:54 AM
From: BUGGI-WORead Replies (1) of 275872
 
@Paranoid - OC
Which board do you use - chipset?
There are mainly 2 crucial things. LDT speed and DRAM clock.

First, when you increase your "FSB" (HT) Clock, then your
LDT clock increases. Standard is a multi of 5, so, when you
increase HT, the platform gets fast very instable. Try to use
factor 4 or 3 (BIOS)!!!
Which DRAM do you use? When increasing "FSB", you should
setup SLOW!!! DRAM settings first, so you get a feeling,
how fast the A64 could go. Use CL3!!! first! Second, try
DRAM dividers like 133 or 166MHz, which reduce DRAM clock,
when you increase HT.
E.g. I went with 290MHz. Which DRAM could reach that with
fast settings? Nearly impossible. So when I setup (Nforce4)
a 166MHz setting (200 = standard), the DRAM goes down to
166/200*290= 240,7Mhz from 290. That is also very fast, but
the Samsungs (TCCC, better is TCCD) went fine. When your
moduls are not as good, try 133, which lead to 133/200*290=
193MHz.
With these settings, you should easily reach higher clockspeeds
. BTW - disable C&Q first. Many boards causes problems, when
you overclock your system. This is not because the K8 has a
failure, thats why many dividers will change. Thats more
complicating and because the dividers will change, e.g. DRAM
clock could reach a setting, on which it will not function
correctly. So disable it first.

BUGGI
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext