|
Login to view full posting options
|
| Author |
Message |
Google
AdSense
|
|
| Back to top |
|
 |
Cisco
nForce Padawan

Joined: 21 Feb 2003 Posts: 565 Location: Vancouver, BC
|
Posted: Thu Mar 09, 2006 12:37 am Post subject: A8N32 Quickie OC guide |
|
|
|
First of all...This is meant to be a basic, quick, overclocking guide for the A8N32 MB. It is based on my own personal experience and will not take you to extremes. It's meant simply for those who want to get started overclocking this MB manually in a safe and logical way.
However, any kind of OC has risk...make sure you understand that, before you start.
Second...you shouldn't even be thinking of doing this unless you have everything 100% stable at the default settings. If you don't, you'll never know if the crashes and glitches you're seeing are due to overclocking or something else entirely (bad driver, corrupt install, bad components, etc.)
Third...I'm deliberately oversimplifying in some cases (HTT is really 2X FSB X LDT = 2000...not 1000, "FSB" is really mislabeled, K8>NB is really the LDT, etc.) just to keep the terms the same way this MB uses them. I'm also using an oversimplified Memory Divider formula. (For the complete accurate and cumbersome formula see the next post.)
FYI...my system is based around an X2-4400, 2 X 1GB of OCZ PC3200 low latency ram and 2 X BFG 7800 OC cards. I am using BIOS 1009.
Settings you should lock (not overclocked):
Cool and quiet: disable
Peg Link: disable (auto by default, but disable it) Peg Link is all about overclocking your video cards--don't even think of doing that at this stage...do it later after you have your CPU/FSB/RAM overclocked if you want. And even then you probably shouldn't do it with PEG link. Riva Tuner and Coolbits is what you should use for GPU overclocking.
SB>NB Frequency: Take it off auto and set it to 200
SB>NB Multiplier: 5X-- This and the previous setting will lock the second HTT that is unique to this MB (to the SLI X16 chipset actually) to 1000...any less and you will loose SLI performance (read the recent review at X-bit labs for more info about this if interested.)
SB>NB Linkwidth: 16/16
K8>NB Linkwidth: 16/16
CPU vCore: for X2 CPUS, set it to 1.2875 to begin. This MB will automatically add 0.0625v to that, giving you 1.35 which is the AMD recommended (1.3 - 1.4) setting for X2 CPUs.
All overvoltage settings=off
PCIe frequency=100
USB legacy: disable...if enabled it WILL cause problems with Memtest (test 5 & 6) and perhaps, with RAM performance. More info about this at the Memtest support forums.
Memory command rate= 1T...the default is Auto but you should set it to 1T if you can. If you have 4 sticks of ram then you just have to live with 2T. There is performance degradation going to 2T from 1T.
Overclocking:
FSB = 250. This is a 25% OC of the FSB...this MB can do much, much more...this is a mild OC.
CPU multiplier: For an X2-4400 set it to 10...this overclocks the CPU to 2.5 GHz from the stock 2.2 GHz...A modest 13.5% overclcok: why this setting? Because it's more than what the ASUS AI OC will do (max 10%) and is still very safe at default voltages...just to wet your appetites With a different CPU that has a different default clock setting, set whichever multiplier gives you something in the 10 to 15% range above the rated speed. For example if the default is 2.0 (200 X 10), 250 X 9 gives you 2.25 for a 12.5% OC.
NOTE: there are no guarantees here...some CPUs are dogs and someone unfortunately ended up with them... a 15% OC is not guaranteed for ALL CPUs. Personally, I've never had a CPU that couldn't do that, but your mileage may vary.
K8>NB Multiplier: 4X. The default FSB and HTT in an nf4 AMD64 system are 200 and 1000 respectively. HTT is simply the FSB multiplied by the K8>NB multiplier (LDT)...so default for the K8>NB is 5X. This motherboard has been reported to be able to do well with an HTT as high as 1200 (300 X 4—Hardocp review)...that's the good news. The bad news is that there is absolutely zero measurable performance increase to be gained from overclocking the HTT...play it safe and always keep the FSB X K8>NB at 1000 or lower.
Memory limit: set it to 166...166/200 X 250 (FSB setting) = 208...this is a tiny 4% ram overclock. All PC3200 ram should be able to handle this with the tightest timings which is why I'm being so conservative here. Ram overclocking is a different art and when you want to max your ram settings you are going to have to start making 1000 little tweaks that are very specific to your ram. You'll be better off going to the ram support forums for your type of memory and looking for clues there on what your sticks should be able to do and the looser settings to get you there.
All other memory settings...leave at Auto. This should keep your ram at the tightest timings it tells the MB it can do. In general, when overclocking ram with an AMD64, tighter timings are better unless the looser timings get you more than 20 MHz more. This is simply my own "rule of thumb" based on my own benchmarking and observations made by many others who have tested this...take it with a grain of salt (you may get a performance increase in whatever you use to benchmark with just 12 more MHz ) but it works for me.
Don't pay any attention whatsoever to whatever the BIOS post screen says your memory is clocked at...it will not report the FSB X divider/200 results...use something like Everest or CPUz in windows to check the ram frequency.
Testing and benchmarking:
There are many good utilities out there for testing your memory (Memtest) overclocks and the overall Windows 2D overclock (Prime95, etc.) And you should use those when you're ready to max things...personally I skip those and go straight to 3Dmark 2006. Why? Because I have never had an OC that would do 3Dmark well and fail elsewhere...but the opposite is definitely true…and ultimately, with an SLI system, 3D game stability is what I'm interested in...It’s not 100% OC Geek certified methodology...but it works for me. I do use Memtest and Prime95--just not for "quick & dirty" overclocking when I have a good feel for whether I'm pushing things or playing it relatively safe.
Quick and dirty troubleshooting hints:
If adjusting the BIOS results in no boot and a black screen (worst possible case) try to access the BIOS set-up by pressing and holding the INSERT key (not the delete key) This usually will get you to the BIOS screen but sometimes you’ll just have to go and reset the CMOS manually…first time you do, you will curse ASUS for putting the jumper right under the retaining clip for the bottom video card.
If your CPU can't do 15% at default voltage settings there are 2 things you should do:
1. Leave everything else the same but start reducing the FSB from 250 by 5 at a time until you reach stability. This will tell you what it CAN do at stock voltage.
2. Take it back to 250 and start increasing the voltage 1 notch at a time until you reach stability with the FSB @ 250...watch your temperatures whenever you add voltage. Now it's your call whether you want to take the lower OC from #1, the higher voltage from #2 or something in between.
If you suspect your memory can't do the tiny 4% OC: 1. take the divider down to 133...this will take it out of the equation...if you still have the same problems, it wasn't the memory. If the problem is fixed by taking it down to 133, then bring it back up to 166 and increase the ram voltage a notch...you can keep trying this all the way up to 2.9 afely. Or, go seek help at the memory manufacturer's forums. Just as an example...my memory will do 230 @ 2.7 volts but I have to loosen timings from 2-3-2-5 to 2.5-3-3-7 to do so.
Where to go from here:
http://forums.anandtech.com/messageview.aspx?catid=28&threadid=1497607&enterthread=y
Anandtech's quick and dirty overclocking guide: If you want to get serious about finding what your components can really do, this guide will help you find the maximum FSB this MB can handle (probably 330+), the maximum frequency your CPU can handle and the maximum speed your RAM can do...and then integrate those 3 factors to give you the best possible overall overclock for your system.
Have fun and don’t blame me when your system blows up!
(Note: I originaly posted this at the ASUS A8N32 forums a couple of days ago.)
Last edited by Cisco on Thu Mar 09, 2006 1:05 am; edited 1 time in total |
|
| Back to top |
|
 |
Cisco
nForce Padawan

Joined: 21 Feb 2003 Posts: 565 Location: Vancouver, BC
|
Posted: Thu Mar 09, 2006 12:38 am Post subject: Mem Divider calculations |
|
|
|
(Thanks to Ridesy from the ASUS A8N32 forums for this)
| Quote: |
It is NOT a simple "mem limit" divided by "base clock" (200) x CPU FSB/HTT = "effective Mem Speed"!!!!!
The calculation involves calculating two new values:
1. "Effective BASE CPU Default Speed" - This is basically what the CPU would run at if the CPU FSB were set at the default 200. (i.e. if you have K8>NB multi at 11x this = 200 x 11 = 2200Mhz, if K8>NB Multi is at 10x = 200 x 10 = 2000Mhz etc......)
2. "Effective CPU/RAM Ratio" - This is the value of "Effective BASE CPU Default Speed" divided by the Mem Limit value you have set, but the value is then rounded up to the nearest whole number (no decimal places). i.e. if Effective BASE CPU Speed is 11 x 200 = 2200 and Mem Limit is at 183, the Effective CPU/RAM Ratio is 2200/183 = 12.02186, which rounded up to nearest whole number is 13.
OK now we have the two "new" values needed to work out effective mem speed, as Asus say the board works it out as follows:
Effective Mem Speed = (CPU Multiplier divided by CPU RAM Ratio) multipled by CPU FSB.
In this example: CPU FSB - 235, CPU Multiplier x11, Mem Limit 183.
Effective BASE CPU Default Speed = 200 x 11 = 2200
Effective CPU/RAM Ratio = 2200/183 = 12.02186 rounded up to 13.
Therefore Mem Speed = (11/13) = 0.846154 x 235 = 198.8Mhz or DDR397!!!! |
Also...Oskar Wu (DFI MB designer) posted this table at the Xtremesystems Forums a few months ago...you may find this useful as well:

Last edited by Cisco on Thu Mar 09, 2006 12:46 am; edited 1 time in total |
|
| Back to top |
|
 |
Cisco
nForce Padawan

Joined: 21 Feb 2003 Posts: 565 Location: Vancouver, BC
|
Posted: Thu Mar 09, 2006 12:38 am Post subject: On-line OC Calculator |
|
|
|
So... you want to try other settings and hate the math involved in the mem-divider calculations above?
This is an on-line best possible overclock calculator. (ALL CREDIT TO THE GREAT gOGAR FOR MAKING AND HOSTING THIS GREAT LITTLE TOOL) In my original post, I suggested using the Anandtech A64 OC guide as a next step. It will let you find out a) Your Max FSB (HTT) independent of CPU speed, b) your Max CPU speed and c) your max memory speed. After you know all that, you still have several options on how to set things. The calculator I'm linking does the job for you and gives you a list of settings---best at the top followed by next best and so on.
However...You can use the calculator for less than maximum settings also
And it simplifies things quite a bit. Here's how to do it: (Don't worry or adjust the right hand side box...just leave it alone at the defaults)
Adjust only the left hand values:
CPU: put in the maximum your CPU can do OR the more conservative value you want to do for now. For example if you want to hit 2500 for now, set it to that.
RAM: The maximum your ram can do OR be conservative (as I was in my guide) and give it something close to default (200)
HT: This is the maximum that this motherboard can do for FSB X K8>NB Multiplier...conventional wisdom says 1000 max here but the A8N32 has been shown to handle much more than that (up to 1200) Set it at 1000 unless you want to experiment with higher numbers
HTT/FSB: In the A8N32 ours is labeled "FSB" Put in the maximum FSB you can do OR what you want to do for now
Multi: This one is simply the default or maximum multiplier for your CPU (for example, 11 on an X2-4400
So..let's say you want to OC your X2-4400 to 2500 with the FSB @ 250 while keeping the memory close to 200...let's say, 210 or below? You would input 2500, 210, 1000, 2500, 11 and press Go. You'll get a set of possible settings including what mem divider to use.
By the way, in the example above the top of the list will have you set the FSB to 250, multi to 10X, mem divider to 166 and K8>NB multi to 4X....exactly my suggested settings above...coincidence? Nope, lol...those settings were chery-picked to work very nicely ahead of time
Link to the calculator: http://math.gogar.com/athlon64.cgi
Last edited by Cisco on Thu Mar 09, 2006 1:03 am; edited 1 time in total |
|
| Back to top |
|
 |
garikfox
X File Ultra nForced

Joined: 11 Dec 2002 Posts: 8855 Location: Arizona
|
Posted: Thu Mar 09, 2006 12:40 am Post subject: |
|
|
|
. hehee  |
|
| Back to top |
|
 |
caintry_boy
nFHQ Member

Joined: 20 Sep 2005 Posts: 10 Location: Kansas USA
|
Posted: Sat Mar 11, 2006 12:50 am Post subject: |
|
|
|
WoooHooo! You guys are rockin'!!
Bless you! Bless you too!
 |
|
| Back to top |
|
 |
garikfox
X File Ultra nForced

Joined: 11 Dec 2002 Posts: 8855 Location: Arizona
|
Posted: Sat Mar 11, 2006 3:14 am Post subject: |
|
|
|
 |
|
| Back to top |
|
 |
whitedragon
nForce Padawan

Joined: 03 Jan 2004 Posts: 878 Location: Abilene, Texas
|
Posted: Sun Mar 12, 2006 4:35 pm Post subject: |
|
|
|
Great guide! On a related question, what's the max safe voltage for A64 X2's?
I've been looking around, and I can't find a clear answer. |
|
| Back to top |
|
 |
Gilly
-- Meow -- Ultra nForced

Joined: 08 Feb 2004 Posts: 6015 Location: West Yorkshire | UK
|
Posted: Sun Mar 12, 2006 5:51 pm Post subject: |
|
|
|
| whitedragon wrote: |
Great guide! On a related question, what's the max safe voltage for A64 X2's?
I've been looking around, and I can't find a clear answer. |
thats user defined! how high you want to take it stock is the "safest" way in voltage terms, think 10% would be ok overvolt personally, 0.1 above 1.4 would give plenty of headroom. I dont like the idea of more than 1.5 on a chip though.... |
|
| Back to top |
|
 |
whitedragon
nForce Padawan

Joined: 03 Jan 2004 Posts: 878 Location: Abilene, Texas
|
Posted: Sun Mar 12, 2006 11:52 pm Post subject: |
|
|
|
| Well, I understand it's all personal chioce, but I was hoping that someone had run across actual specs detailing how much voltage these chips can take. I'm also hesitant to go above 1.5v, but I was curious as to the actual physical tolerances of the X2 series. |
|
| Back to top |
|
 |
wardog
Exited the premises. Ultra nForced

Joined: 28 Jan 2003 Posts: 2510
|
Posted: Mon Mar 13, 2006 12:37 am Post subject: |
|
|
|
| whitedragon wrote: |
| Well, I understand it's all personal chioce, but I was hoping that someone had run across actual specs detailing how much voltage these chips can take. |
See Section 7 titled Absolute Maximum Ratings
AMD Functional Data Sheet, 939 Pin Package < AMD Tech Doc #31411 (PDF)
(Referred to the above from AMD Athlon™ 64 X2 Dual-Core Product Data Sheet < AMD Tech Doc #33425 (PDF) )
Last edited by wardog on Mon Jan 15, 2007 11:16 am; edited 1 time in total |
|
| Back to top |
|
 |
Google
AdSense

|
|
| Back to top |
|
 |
|
|
nForcersHQ supporters: Impar, wardog, MiniMax, envoid, jasonh, Krips, VAIOMAN, Zetro, sensai, me&er, RElliott, ScottRempel, JHogarth, IcemanIX, Etraman, KA, Tabajara, Xiomberg, ruddywarrior, hookahmike, MMoore, RHodgson, RGilson, powerarmour, Sepal, RRavat, DigitalRuin, HammerheadTech, Bane, DHunt, Fat Jez, baikal, Jumpin' Jon, MGadzikowski, JBishop, RDeBok, JDavies, HDHyland, TMorris
|
|
| |