Is there any link for the NB Gtl, Cpu Gtl..? or anyone can guide me..? i stuck at 363x8 for now..

owh..haha still stay calm coz didnt oc yet in new mobo..nope..as i tols stratos oso i dunno much bot ram setting n tweak myb u can ask others bout it

Haha.. same here.. i search but cant find related to this board.. so anyone..?

its ok man...i langsung dono how some of them can achieve CL 4 and running on 500fsb
tried this? i guess maybe this link shud be pasted on the main page of the thread 

http://www.clunk.org.uk/forums/hardware/32...therboards.html

http://www.clunk.org.uk/forums/overclockin...rs-dfi-add.html

just get tis info from gsan and tried it, all UT user should disable the vdrop control option in bios, after i disabling it, my vcore reading seems more less ripple and i can run my proc with lower vcore settings in bios...

just get tis info from gsan and tried it, all UT user should disable the vdrop control option in bios, after i disabling it, my vcore reading seems more less ripple and i can run my proc with lower vcore settings in bios...

Additional Setting Ranges:

MCH ODT Latency: ODT (On Die Termination) is used to match the MCH output impedance to the termination resistance of the RAM. Use of 1-2 is fine in most cases. Even for 4GB overclocking we did not find that more than a setting of 1 was required.

Write to PRE Delay (tWR): Range is from 10-13. For high RAM speed, use 12 and above for stability; for benchmarking 10-12 will be faster. Lower is faster.

Rank Write to Read (tWTR): Range is 9-11. Use 11 for stability and 10 or 9 for benchmarking. Lower is faster.

ACT to ACT Delay (tRRD): Range is 2-5. 3 is a good setting that allows high enough FSBs for most users. Higher numbers result in less memory read performance.

Read to Write Delay (tRDWR): Range is 8-9. 8 is ideal for most users; higher values are slower.

Ranks Write to Write (tWRWR): AUTO
Ranks Read to Read (tRDRD): AUTO
Ranks Write to Read (tWRRD): AUTO

The ranges for all these settings are quite well manipulated by SPD and BIOS. For those wishing to experiment, 4 is the lowest and most aggressive setting. 5-4-5 may work for SuperPi type benching. There is a slight write/copy speed increase with tighter settings, but this is only useful for the extracting the last ounce of performance. For stability these are best left on AUTO

Read CAS# Precharge (tRTP): 2-3 works well on this board for most users. 2 is used for benchmarking while 3 and upwards are best for stability.

ALL PRE to Refresh: Range is 4-5. 4 works fine with quad-core CPUs all the way to 475 FSB. A setting of 4 is fine for most benchmarking, unless shooting high over 500FSB.

GTL REF Voltage control: Enable / Disabled
"CPU VTT reference voltage for determining host bus high / low level." - This setting can be useful or detrimental and is highly dependant on your individual CPU. You may find that you can acheive a higher and more stable overclock by tweaking these values. The values are strongly tied in with the CPU VTT voltage, so it can take a bit of experimenting to find the correct settings. See the VTT/GTL REF guide here.

Update: After further testing with another 45nm dual core cpu (E8400 & E8500), I have found that on my systems, there was absolutely no need to have the GTL REF Voltage Control set to Enabled. I was able to hit 500FSBx9.5 with relative ease, and 540FSBx9.5 later on - Of course, as VTT & GTL REF settings can be different for each setup, you may find that a small amount of tweaking will work for you. The trick is, for 24/7 overclocks of relatively sane proportions, less is more for the VTT (i.e. Leave it alone unless you are unstable), and the same goes for GTL REF.

One of the reasons that the board can retain stablity when the GTL REF is set to Disabled is that rather than it actually being disabled, it is simply fixed at 67% and 67% is what DFI have found to be the optimum value for GTL REF at any given VTT.

Enabling the GTL REF setting will allow you to fine tune the percentage figure should your setup require it, however, it is very easy to tweak these settings too much +/- and miss that sweet spot, and often, you will find that the sweet spot was at 67% to begin with.

I have tested with a Q6600 G0 and this responded well to the 67% (Disabled) setting. Again, this doesn't automatically mean that yours will. My last Q6600 G0 responded better to fine tuned GTL REF and a slight bump in VTT, so it really is a case of experimenting and seeing what works best for you.

There is another factor that can have adverse effects on your VTT/GTL tweaking results and that is temperature. From my own tests, I have found that GTL REF tweaking is less effective when using air cooling and a higher Vcore, and similarly, when using sub zero cooling, I found the GTL REF to be incredibly sensitive and the slightest changes caused adverse affects - This is something that I would like other people to comment on because I would like to explore it further

Also, if you would like a more in depth read on GTL REF, click here to go to EdgeOfStability.com.

I will add more as I get to it...

UT/LT P35/X38/X48/790FX & DK X38/X48/790FX got this function, but DK P35 dont have   

btw, anyone DK P35 user running 500fsb with 1:1 (cpu/ram) ? did you experience double post? and how the double post look like?

UT/LT P35/X38/X48/790FX & DK X38/X48/790FX got this function, but DK P35 dont have   

btw, anyone DK P35 user running 500fsb with 1:1 (cpu/ram) ? did you experience double post? and how the double post look like?

u mean dual start after we unplug or switch off the psu... mobo not on standby then when start the pc it will on then off before turning on again? i also getting tis problem, i heard only OC'ed proc will happens.. if stock FSB then it wont happen....

u mean dual start after we unplug or switch off the psu... mobo not on standby then when start the pc it will on then off before turning on again? i also getting tis problem, i heard only OC'ed proc will happens.. if stock FSB then it wont happen....

yup, double post when no current supply to the mobo and switch on the psu again. so far I experience few situations regarding this double post.

1. pc on automatic off and on automatic
2. pc on and no POST, press reset (while current is supplies to the mobo) and everything goes as normal.
3. pc on and got POST, but come to windows loading bar, hang at there. Press reset (while current is supplies to the mobo) and everything goes as normal.

no matter which situation, the system need 2 times to run it. so I wonder, which double post you guys experience?

mean its like u reset ur cmos?it run the off then run back rite?i didnt hv any issue with that unless i clear the cmos