Important BIOS Functions

We have picked out a few of the more important BIOS functions for a breakdown of their use and application. The "Advanced Tweaker" BIOS screen has quite a few secondary memory timing options; for the most part these can be left to board/SPD default values. We are providing the best "bang for the buck" manual settings below.

AI Overclock Tuner: Set this function to manual for overclocking; the Auto function enables preset overclocks automatically when the system is under load.

OC from CPU Level Up: ASUS enabled overclock profiles based upon the processor type in use; for manual overclocking, leave this function at Auto. If low level automatic preset overclocking is preferred, select either the CPU type or "Crazy" mode. Setting either of the latter two options adjusts all board voltages to preset values. The preset values themselves can be higher than is absolutely necessary for the applied overclock. The Auto overclock functions can be useful for beginners who are getting to grips with overclocking, with the option to move to manual overclocking later. We suppose this guarantees stability via a somewhat brute force approach. For long-term use, we recommend using a manually set overclock.

FSB Strap to Northbridge: Unlike older chipsets, performance hits of using the higher MHz Northbridge straps are virtually non-existent. Synthetic latency and read figures across any of the 266/333 or 400 straps are almost identical. There are small variances in overall stability, for quad processors running over 400FSB - the 333 and 400 straps worked better for us. For benching with dual-core CPUs, we found the 266 strap allowed us sufficient overhead to run the board up to 550 FSB. Between 550-575 FSB, we were limited to the 333 and 400 NB straps depending on memory timings. The 200 NB setting offers inadequate FSB potential to consider it worthy of use with Intel's latest processors.

PCI-E Frequency: If the ICH9R SATA ports are used then a setting around 115 MHz is safe, though scores do not seem affected by the minimal 15MHz overclock. We noticed anything over 118MHz would cause problems with the drives or even the POST routines. Benchmarkers as usual are best off using an IDE drive, turning off all the peripherals, and then trying to maximize the bus speed.

DRAM Frequency: The available dividers for the 266/333/400 NB straps are:

NB Staps and Dividers
266 4:5/2:3/1:2
333 1:1/5:6/5:8/1:2
400 1:1/3:4/1:2

DRAM Command Rate: Sets either 1N or 2N memory timing. Our test sample is perfectly capable of holding 1N command rate at up to DDR3-1840Mhz. The synthetic performance advantage of 1N over 2N is around ~1.8ns (1-3%). As the board has no issue using 1N at high speeds, it becomes almost mandatory to set 1N for all overclocking.

DRAM Timing Control: Set this to Manual to obtain control of all primary and secondary memory timing ranges. The BIOS shows primary and secondary timings above both respective timing sections. Users may wish to enter the shown timings manually for each setting and then experiment with tighter timings where possible. The board defaults are generally tight enough for 24/7 use. For benchmarking, Memset allows access to setting ranges that are not accessible in BIOS. We look at a few timing ranges below.

RAS To RAS Delay: The BIOS generally defaults to 4 for this setting; for benchmarking, we have used 3. At high FSB speeds, a setting of 5 may provide more stability with the counter effect of a small loss in performance.

Row Refresh Cycle Time - aka TRFC: For benchmarking TRFC can be set as low as 45-50; if shooting for stability values of 60 and above are fine. A lower setting gives big gains in bandwidth and can affect benchmarking scores quite drastically.

Write Recovery Time: Default value here is 8. This setting works fine over a broad range of FSB and memory speeds. If stability issues are experienced, it may be worth experimenting with a setting of 9. Lower is tighter and gives small gains in memory write performance.

Read to Precharge Time: A range of 3-6 is usable. For stability testing with high RAM speeds in excess of DDR3-1700, 1N command rate may require a setting of 6. For benchmarking, values as low as 3 are possible, though stability will be dependent on the benchmark in question. A setting of 3 applied via Memset is best.

DRAM Static Read Control and DRAM Dynamic Write Control: Both these functions are best set to 'Disabled' for overclocking. We could not substantiate any significant memory bandwidth or latency gains using the 'Enabled' setting. Further, setting 'Enabled' may actually hinder overclock success.

AI Clock Twister: We recommend use of the "Strong" setting wherever possible. Setting "Weak" reduces overall bandwidth and access latency.

Transaction Booster: Ranges here are from 1-8 (1-3 are usable changes in BIOS), with either the "Enabled" or "Disabled" setting. A setting of 1 with "Enabled" selects the default tRD level for the NB strap and memory divider combination. Each digit increase to the Transaction Booster with the "Enabled" setting will subtract 1 from Performance Level, providing us with higher memory bandwidth and lower access latency. The "Disabled" function inreases tRD (tRD +1) and/or tRD phases with each additional digit over 1, meaning an upward scale increase or boost is less aggressive with Transaction Booster set to "Disabled".

AI Clock Skew Channel A and Channel B: Timing unison between both channels of memory is essential for stability. PCB trace length variance between Channel A and Channel B can lead to an offset of signaling between both Channels. Delaying Channel A or advancing Channel B may be required to realign clock timing at high memory speeds - thus improving stability. Generally, we used either a delay of 50-100ps on Channel A with Channel B set to "Normal". Alternately, we can advance Channel B by 50-100ps with Channel A set to "Normal". Users may need to experiment between various levels of "Skew" to find optimal settings.

XP Overclocking Benchmarks BIOS, Continued


View All Comments

  • markglh - Sunday, January 13, 2008 - link

    Does the Thermalright Ultra-120 Extremem fit ok on this motherboard in a position so that it blows air out of the case? I was worried that the fusion waterblock and the heatsink at the top of the board might be too tall.

  • astronaute - Wednesday, December 26, 2007 - link

    Can someone explain please why in BIOS screenshots we can see FSB 400 and QX6600 FSB is more then 1000 ?

    Sorry if my question is stupid :)
  • Rajinder Gill - Sunday, December 30, 2007 - link

    The BIOS screenshots shown are provided only to illustrate which BIOS functions are available for the user. They have no direct correlation whatsoever with a Q6600 or it's FSB.


  • qquizz - Thursday, December 13, 2007 - link

    With a name like Maximus Extreme the board better be one bad mofo, err... i mean mobo. Reply
  • Zak - Monday, December 10, 2007 - link

    Something's not right, C2D Extreme and 8800Ultra??? I get over 12000 in 3D Mark 2006 with a $99 Gigabyte mobo, 3GHz C2D @3.8Ghz with Tuniq Tower, 800MHz DDR2 and 8800GTX slightly overclocked.

  • Azured - Monday, December 10, 2007 - link

    No that seems allright. The test is run with a Q6600 (actually a QX6850 with a lower multiplier to simulate the Q6600) at stock 2.4GHz. considerably slower than your C2D at 3.8GHz. Reply
  • Zak - Monday, December 10, 2007 - link

    Oh, I must have misread something then, thanks:)

  • takumsawsherman - Monday, December 10, 2007 - link

    Now this blows me away. $350 and still no Firewire800! How much money should you have to pay before you get a feature that was commercially introduced 4 years ago. Instead, you get the slower variant that first saw real action 8 years ago. What's next, USB 1.1?

    Maybe I didn't read the Newegg price tag correctly, but if I did, this is a travesty. And of course, no room for a PS/2 mouse port. I mean, a single PS/2 port, in a non-standard position. At first, it may seem to be no big deal, but why make it different that almost every other config? So when muscle-memory leads you blindy around the back of the case when you install a keyboard, you have to hunt around more. Not to mention that most PS/2 devices are pretty static in that people aren't switching them all the time. USB, on the other hand, is more frequently connected and disconnected. Having the PS/2 keyboard plugged in gives you limited room to change USB stuff, especially if you have another USB device plugged in. If the PS/2 port was on the bottom, you can stack a USB connector on top and still have finger room to add or remove another, without risking disconnection of another cable (PS/2 for example).

    A ridiculous board, at a ridiculous price.
  • retrospooty - Monday, December 10, 2007 - link

    not to burst your bubble but, Firewire 800 is never going to take off. Before it got started it was surpassed and totally obsoleted by eSATA. You wont ever see it as a standard feature on even high end motherboards. If you have use for it, you need to by an adaptor card for it. Reply
  • Etern205 - Monday, December 10, 2007 - link

    Yes, eSATA is faster than Firewire 800 which is why eSATA is gaining popularity than Fire800. As for only 1 PS/2 port, if those articles or rumors are correct, then by the time ICH10 comes out we'll not see anymore PS/2 ports or PCI slots.

    In a question unrelated to this article, for those of you that have a usb wireless mouse or keyboard are you able to switch between the OSes if you guy have a dual or mult-boot system?


Log in

Don't have an account? Sign up now