AOpen AK89 Max: Overclocking and Stress Testing

FSB Overclocking Results

BIOS options don't mean much unless they can translate into improved performance. We have complained for months that the major reason we could not reach higher overclocks was not the poor headroom of the Athlon 64, but rather, the lack of a fixed AGP/PCI lock on the VIA and nVidia chipset boards that we were testing. Now, we get a chance to put our money where our mouth is.

Front Side Bus Overclocking Testbed
Default Voltage
Processor: Athlon64
2.0GHz
CPU Voltage: 1.5V (default)
Cooling: AMD Stock Athlon 64 Heatsink/Fan
Power Supply: Antec TruePower 430W
Maximum OC:
(Standard Ratio)
233FSB x10
2333MHz (+16.5%)
Maximum FSB:
(Lower Ratio)
347FSB x 6
(328x7 for CPU limited 2296MHz)

The above overclocking setup at default voltage allowed us to reach a stable FSB of 233. With such a limited top vCore, we had to consider the 1.55V as essentially the same as the default 1.50V. A voltage range to at least 1.7V to 1.85V would be preferred - especially since the AK89 Max turned out to be an incredible overclocker. Even without CPU voltage adjustment, we reached an astounding 347FSB using some common overclocking tricks. Take a look at the Extreme Overclocking section to see details on how we reached those levels. Screen captures are also included.

Front Side Bus Stress Test Results:

A full range of stress tests and benchmarks were run to ensure the AK89 Max was stable at each overclocked FSB speed. This included Prime95 torture tests, and the addition of other tasks - data compression, various DX8 and DX9 games, and apps like Word and Excel - while Prime95 was running in the background. Finally, we ran our benchmark suite, which includes Veritest Winstone 2004 suite, Unreal Tournament 2003, SPECviewperf 7.1, and Aquamark 3. 230MHz was the highest overclock that we were able to achieve with the AOpen while running these tests at default voltage and default multiplier.

Memory Stress Test Results:

The memory stress test is very basic, as it tests the ability of the AK89 Max to operate at its officially supported memory frequency (400MHz DDR) at the lowest supported memory timings that our Mushkin PC3500 Level 2 or OCZ PC3500 Platinum Ltd Modules will support. Memory stress testing was conducted by running RAM at 400MHz with 2 DIMM slots filled.

Stable DDR400 Timings - 2 DIMMs
(2/3 DIMMs populated)
Clock Speed: 200MHz
Timing Mode: N/A
CAS Latency: 2.0
Bank Interleave: N/A
RAS to CAS Delay: 2T
RAS Precharge: 5T
Precharge Delay: 2T
Command Rate: N/A

We had no problem running 2 DS 512MB DIMMs of our standard Mushkin PC3500 Level 2 or OCZ PC3500 Platinum Ltd in the AOpen AK89 Max. Both of these memories were completely stable at the Jedec standard memory voltage of 2.6V at DDR400 with the fastest 2-2-2-5 timings that we could select on this board. We were able to achieve the same fast timings with either 1 or 2 DIMMs.

Filling all available memory banks is more strenuous on the memory subsystem than testing 2 DIMMs. AOpen states clearly that only 2 DIMMs or a maximum 2GB of memory are supported at DDR400 speed, but we decided to try 3 DIMMs at that speed. 3 DIMMs only worked at DDR333 speed. This was consistent with AOpen's specification of a higher memory capacity of 3GB at DDR333. For best performance on the AK89 Max, we would recommend using 1 or 2 DIMMs. If you want more memory, use 2 of the new 1GB memory modules from Corsair, Kingston, OCZ, and others to allow 2GB of total memory using 2 DIMMs.

Stable DDR400 Timings - 3 DIMMs
(3/3 DIMMs populated)
Clock Speed: 166MHz
Timing Mode: N/A
CAS Latency: 2.0
Bank Interleave: N/A
RAS to CAS Delay: 2T
RAS Precharge: 5T
Precharge Delay: 2T
Command Rate: N/A

We tested the memory timings with 2 banks filled using several stress tests and general applications to guarantee stability. Prime95 torture tests were successfully run at the timings listed in the above charts. We also ran ScienceMark (memory tests only) and Super Pi. None of the three stress tests created any stability problems for the AK89 Max at these memory timings.

AOpen AK89 Max: BIOS AOpen AK89 Max: Extreme Overclocking 1
Comments Locked

23 Comments

View All Comments

  • GooFy - Sunday, May 30, 2004 - link

    Could you somehow test some other memory modules with this board, i have a pair of Adata PC4000 that will not go over 230mhz @ original (Cas 3 8-4-4) or any other timings either yet they are stable @ 230 mhz fsb and Cas 2 6-3-3.
    I'm going to buy some new memory modules and i would like to know what options there are as it seems there are some other memories that will not go to 250+ fsb.
    Anyway i'm sure that it is the memory that's stopping me because i ran alot of tests with different timings and lower multiplier and so on.
  • TrogdorJW - Tuesday, April 27, 2004 - link

    What the crap... lost my post. Grrrr.... Okay, here's a recap of what was supposed to be in that last one:

    You're cruel, showing us scores of 200 * 10 and 250 * 8 and then holding out on the scores for the "Extreme Overclocking" setups. I don't want a screenshot, but I would have been curious to hear what sort of performance difference there was between the 233 * 10 and the 345 * 6.5 setups. Do the asynchronous RAM timings hurt performance a lot, or can the integrated memory controller deal with that okay? Would be nice to find out. Oh, well...
  • TrogdorJW - Tuesday, April 27, 2004 - link

  • MadAd - Sunday, April 25, 2004 - link

    thanks wesley, they did look nice and clear in this one, thats why I asked - ill wait for your review.
  • NegativeEntropy - Saturday, April 24, 2004 - link

    cnq,

    I know if I had to program Cool'n'Quiet there would be, at minimum, a sanity check to make sure the Hyper Transport (~FSB) frequency was 200 MHz and the multiplier is where it should be for that model CPU prior to doing anything. It's what Cool'n'Quiet would do after that that is up in the air (or so goes my reasoning):

    1) abort any attempt to engage Cool'n'Quiet (most likely given ease of programmability and official disdain for overclocking)
    2) override any current settings, do its thing, and not reimpliment the pre Cool'n'Quiet settings upon an increase in CPU usage (thus effectively 'undoing' any overclock)
    3) note the current state, engage Cool'n'Quiet, and then return to the pre Cool'n'Quiet state when CPU usage demands it (this is the scenario we dream about :)

    As long as I get confirmation Cool'n'Quiet works on this mobo (even w/o overclocking), I may get it and answer the other questions myself :)
  • cnq - Saturday, April 24, 2004 - link

    NegativeEntropy,

    Weird, I was about to ask the *exact* same question!

    ***This should be a FAQ.***

    Everyone likes to overclock the snot out of their boards, and everyone likes cool 'n' quiet to kick in when they are just web browsing. (Naturally, when we stop web browsing and resume gaming, we want the system to return, automatically, to the fully overclocked settings we were using before.)

    But is it technically possible for Cool'n'Quiet to coexist with overclocking? Just by reading AMD's technical docs (BIOS Guide), there is no answer on whether this will work. My fear is that overclocking can confuse the hell out of cool'n'quiet. Cool'n'quiet works by switching between P-states, which are combos of CPU frequency and CPU voltage. Problems could be:

    a) Cool'n'Quiet is ignorant of overclocking in general. The possible P-state transition values are supplied by the BIOS, who in turn gets them from AMD documentation. Naturally, there won't be a P-state setting for an overclocked system in the official tables. But it would be possible for this to work: the BIOS could use your overclocked settings to create an additional P-state that isn't part of the official docs.
    b) Even if this works, underclocking via Cool'n'Quiet is limited. P-states just define CPU speed and CPU voltage. There's nothing about FSB speeds in a P-state (and there should be, imo, along with RAM voltage). So, for example, when Cool'n'Quiet ramps down your CPU, does it also ramp down the FSB speed? If not, then it's pretty easy to see how things could crash here: a drop to (for example) 1000 MhZ might be done by setting the CPU multiplier to 5, on the (incorrect) assumption that your FSB is 200MHz, the "usual" value. But if you overclocked by lowering the CPU multiplier (already) and jacking up the FSB to outrageous amounts, then this CPU multiplier might actually _increase_ CPU speed rather than decreasing it. Not so much with a multiplier of just 5, but you get the idea.
    c) Even if this works (the CPU multiplier is set to 5 in the above example, your FSB is overclocked to, say, 250 instead of 200, so you get 1250MHz instead of 1000MHz)...fine, except that the P-state contained a CPU voltage that is only guaranteed to work well with 1000MHz. Such a low voltage (whatever it is) might not be enough to power 1250MHz, causing a crash. If it is enough to power 1250MhZ, it's just blind luck, and not very stable.

    Naturally, I hope I'm wrong on all of these points, as the combo of serious overclocking and cool'n'quiet would be fantastic.

    Can someone speak from experience on this? In general, can you enable cool'n'quiet yet overclock huge amounts? Wes?
  • NegativeEntropy - Friday, April 23, 2004 - link

    Wesley,

    Does Cool 'n' Quiet work on this MoBo?

    If it works, does it still work when overclocking (or is it borked because of the lower than stock multiplier or for some other reason)?

    The reason I ask: looking to build an HTPC -- CnQ would come in handy to reduce power usage, and this board would be more fun than the K8V :)
  • Wesley Fink - Friday, April 23, 2004 - link

    #13 and #14 -
    Just skip Extreme Overclocking 1 and 2, then it's a standard motherboard review. ALL performance charts, like always, are at default speed and default ratios. Since this is the first A64 board we have tested with a working AGP/PCI lock and working ratios that are available on the A64, it was the perfect opportunity for a "how-to" and why of high FSB overclocking. These features will be the most important thing about this board for many Enthusiasts, and of little interest to others.

    #15 -
    I normally use a Pentax *ist D digital SLR with a 50f1.4 or 28-105f2.8 lens - at 800 ISO, no flash, and adjusted color temperature. However, most of the shots in this review were with a $300 Kodak 5 megapixel digital we will be reviewing on AnandTech in the next few weeks.
  • MadAd - Friday, April 23, 2004 - link

    Its a bit of an OT question, sorry Wesley, what kinda of camera do you use to take the pictures of the board layouts/chips to use in the reviews please?
  • retrospooty - Friday, April 23, 2004 - link

    By that I mean, there are so many levels of OC, so many different ways to look at it. I am unclear what was screenshot stable, and benchmark stable, and I am unclear exactly what speed the final tests were run at. Maybe its just too early in the morning for me. :D

Log in

Don't have an account? Sign up now