ASUS Striker II Extreme: Mucho Bang, Mucho Bucks
by Kris Boughton on April 11, 2008 7:00 AM EST- Posted in
- Motherboards
Complete BIOS Tuning Guide - "Over Voltage" (Cont'd)
CPU GTL_REF(0~4) Ratio - [Auto, Default, -226mV ~ +224mV] Gunning Transceiver Logic (GTL) voltages are nothing more than reference thresholds used by the CPU and SPP (MCH) in determining if the voltage potential on a FSB data or address signal line is intended to represent either a logic level 1 (high) or logical level 0 (low). These voltages are generated by the motherboard, usually though the use of precision voltage dividers or high-accuracy, programmable digital potentiometers. Although the most common way to specify these values is as a percentage (or ratio) of full scale CPU VTT Voltage, NVIDIA has decided to provide these settings as simple offsets meaning a little math will be involved if you want to make a change.
These reference values are particularly important when overclocking quad-core CPUs, especially when venturing above about 475MHz FSB. The ability to tune these values per die can mean the difference between achieving a stable overclock at 475FSB and one at 500FSB. The real power seen in GTL reference tuning comes in the ability to provide each quad-core die with separate reference values. (Recall that current quad-cores from Intel are an MCM design consisting of two dual-core dies on a single substrate package.)
This can get tricky though as each die receives two GTL reference voltages - one for the FSB Data Bus (running at the full FSB transfer rate) and one for the FSB Address Bus (running at half the FSB transfer rate). This means CPU GTL_REF0 Ratio is for the Core 0/1 Data Bus, CPU GTL_REF1 Ratio is for the Core 2/3 Data Bus, CPU GTL_REF2 Ratio is for the Core 0/1 Address Bus, and CPU GTL_REF3 Ratio is for the Core2/3 Address Bus. CPU GTL_REF2 Ratio and CPU GTL_REF3 Ratio will have no affect with a dual-core CPU installed, in which case CPU GTL_REF0 Ratio is for the Core 0/1 Data Bus and CPU GTL_REF1 Ratio is for the Core 0/1 Address Bus. As a rule, adjustments are normally made to FSB Data Bus values first. These lines are consistently heavily loaded and as such are more susceptible to the detrimental effects of reduced signaling margins.
Intel's GTL specification dictates that each reference voltage should be tightly controlled as 67% of the current VTT voltage (0.67 times CPU VTT Voltage). Typically, changes in VTT are automatically compensated with standard voltage divider circuits dedicated to the generation of each GTL reference voltage. Historical data has shown that dual-core CPUs (in particular 45nm dual-cores) often clock to higher FSB levels when the GTL reference values are closer to 63 ~ 64% of VTT while quad-core CPUs usually need the full strength value or even a little more voltage (67 ~ 70% of VTT).
As an exercise in the application of basic math, consider the following. With VTT at 1.10V, the GTL reference voltages at 67% would be 0.737V (0.67 times 1.10V). If VTT increased to 1.26V, the new GTL reference voltage would be 0.844V, calculated the same as before. If we wanted to adjust this down to 63%, we would simply multiply the current VTT voltage by the difference between the actual and desired percentages of full scale VTT (67% minus 63% equals 4% or 0.04) and then convert this to mV by multiplying by 1000. At 1.26V, the result would be 50mV and since we want to reduce the GTL reference voltage we would pick the value closest to -50mV. Sometimes tweaking VTT slightly up or down can help if none of the available values is close enough the desired offset. Of course, you will need to repeat the calculation using the new VTT.
Proper GTL reference level tuning can sometimes allow for a dramatic reduction in VTT and in some severe cases even permits the use of a lower core supply voltage (Vcore). The most recent x64 build of Prime95, version 25.6 build 6, provides an excellent means for testing the effectiveness of CPU-specific GTL tuning. Simply load the program, select the Blend type Torture Test, and watch for any instance to drop out. Note the instance number (which will correlate to the core in question), reset and enter the BIOS, make a small adjustment to the corresponding GTL reference value(s), and then start a new test run. If the test runs for a longer period of time then you can be confident that you are at least moving in the right direction. Continue this process until the system is sufficiently stable with the current settings.
Those that want to know more about GTL reference voltages and related tuning issues are encouraged to carefully examine more in-depth articles on the subject posted here and here.
NB GTL_REF Ratio - [Auto, Default, -126mV ~ +160mV] The NB (SPP) GTL reference voltage provides the same functionality as those for the CPU, the only difference being that the Northbridge uses only a single value. Tuning in the right GTL reference voltage (usually near the nominal 67% value) can sometimes lead to lower stable VDIMM requirements.
DDR3 CHA(1~2)/CHB(1~2) Ref Voltage - [Auto, Default, -126mV ~ +160mV] These voltages work like GTL references for memory, except that VTT for the memory is defined as one-half VDIMM. Small adjustments in either direction can sometimes bring additional stability or higher memory overclocks; however, testing the effectiveness of any change is exceedingly difficult and time consuming. Most of the time these are better off simply left on Auto.
23 Comments
View All Comments
seamusmc - Friday, April 11, 2008 - link
For folks considering this board, I strongly recommend visiting xstremesystems.org's forums.Several people are experiencing data/OS corruption when performing any FSB overclocking. (Brings back memories of the early days of the 680i.)
nomagic - Friday, April 11, 2008 - link
LGA775 Core2 Duo/Extreme/Quad, Pentium EE, Pentium D, Pentium including next-generation 45nm CPU supportWhich would include Nehalem, I suppose? Should I also assume that a BIOS update would be required for Nahalem support? Is it possible that a custom board like this might have trouble supporting Nehalem when the times comes?
TemjinGold - Friday, April 11, 2008 - link
No. NOTHING out right now can support Nehalem as that's a completely different socket (different pin count too).