Here's another straight from someone who just worked the entire evening (paet jud kung call center

)
Settings Used:
******Gigabyte EP45 UD3R******
CPU Clock Ratio [ 11 ]
Fine CPU Clock Ratio [ 0 ]
CPU Frequency 3.66 GHz [ 333 x 11 ]
******DRAM Performance Control******
Performance Enhance [ Extreme ]
Extreme Memory Profile (XMP) [ Disabled ]
(G) MCH Frequency Latch [ Auto ]
System Memory Multipler [ 333B ]
Memory Frequency 800 [ 400 ]
DRAM Timing Selectable [ Manual ]
CAS Latency Time [ 4 ]
tRCD [ 4 ]
tRP [ 4 ]
tRAS [ 12 ]
******Motherboard Voltage Control******
Load-Line Calibration [ Disabled ]
CPU Vcore [ 1.2875 - default ] [ 1.325 ]
CPU Termination [ 1.20 - default ][ 1.22 ]
CPU PLL [ 1.50 - default ][ 1.57 ]
CPU Reference [ 0.760 - auto/default ][ Auto ]
MCH Core [1.1 - default ][ 1.16 ]
MCH Reference [0.760 - auto/default ][ Auto ]
MCH/DRAM Refernce [0.900 - auto/default ][ Auto ]
ICH I/O [1.500 ][ Auto ]
ICH Core [1.100 ][ Auto ]
DRAM Voltage [1.800 - default ][ 2.000 ]
DRAM Termination [0.900 - auto/default ][ Auto ]
Channel A Ref [0.900 - auto/default ][ Auto ]
Channel B Ref [0.900 - auto/default ][ Auto ]
******Voltage Fluctuations******
vCORE [1.325]
vDROP [1.280] ~ .045
vDROOP [1.248] ~ .077
I increased the FSB to 333 because it is somewhat a lot easier to manage the memory with standard speeds rather than in increments through this, I managed to maintain the tight timings even as I raise the overall CPU frequency. From here on, the 333 Mhz FSB speed will be maintained and only the CPU Multiplier will be adjusted as I increase the overclock.
SuperPI 1M results dropped from 17 seconds to 15 seconds which in my opinion is awesome.

I'm sure I can still lower vCORE once I have the chance to play with GTL voltages and clock skews as the system can POST at default voltage (1.2875) but Core 1 fails Prime95 or Intel Burn Test. This may probably be due to out of range GTL settings or vdrop/vdroop.