Dfi X48 and Q6600 GTL Woes

[Rinaun]

So basically I dont think there is a combo of gtls or such I havent tried with this board. MY config currently is:
Q6600
Dfi X48 T2r
G.Skill PC8000 2gbx2
pcp&c 750 quad silencer

Settings:

CPU Feature
Thermal Management Control: Disabled
PPM(EIST) Mode: Disabled
Limit CPUID MaxVal: Disabled
CIE Function: Disabled
Execute Disable Bit: Disabled
Virtualization Technology: Disabled
Core Multi-Processing: Enabled

Exist Setup Shutdown: Mode 2
Shutdown after AC Loss: Disabled
CLOCK VC0 divider: AUTO
CPU Clock Ratio Unlock: Enabled
CPU Clock Ratio: 9
Target CPU Clock: 3852
CPU Clock: 428
Boot Up Clock: Auto
DRAM Speed: 333/800
Target DRAM Speed: 1040-ish (Forget the math; will check next reboot)
PCIE Clock: 105mhz
PCIE Slot Config: 1X 1X

CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled
SATA Spread Spectrum: Disabled

Voltage Settings
CPU VID Control: 1.5000V
CPU VID Special Add: .23%
DRAM Voltage Control: 2.150V
SB Core/CPU PLL Voltage: 1.510V
NB Core Voltage: 1.55V
CPU VTT Voltage: 1.415V (Read on measurement point: 1.4385)
Vcore Droop Control: Enabled
Clockgen Voltage Control: 3.45v
GTL+ Buffers Strength: Strong
Host Slew Rate: Weak
GTL REF Voltage Control: enabled
x CPU GTL1/3 REF Volt: 140
x CPU GTL 0/2 REF Volt: 130
x North Bridge GTL REF Volt: 116

DRAM Timing
Enhance Data transmitting: Fast
Enhance Addressing: Fast
T2 Dispatch: Enabled

Clock Setting Fine Delay
Ch1 Clock Crossing Setting: Aggressive
DIMM 1 Clock fine delay: Current
DIMM 2 Clock fine delay: Current
Ch 1 Command fine delay: Current
Ch 1 Control fine delay: Current


Ch2 Clock Crossing Setting: Aggressive
DIMM 3 Clock fine delay: Current
DIMM 4 Clock fine delay: Current
Ch 2 Command fine delay: Current
Ch 2 Control fine delay: Current

Ch1Ch2 CommonClock Setting: Aggressive

Ch1 RDCAS GNT-Chip Delay: Auto
Ch1 WRCAS GNT-Chip Delay: Auto
Ch1 Command to CS Delay: Auto

Ch2 RDCAS GNT-Chip Delay: Auto
Ch2 WRCAS GNT-Chip Delay: Auto
Ch2 Command to CS Delay: Auto 

CAS Latency Time (tCL): 5
RAS# to CAS# Delay (tRCD): 5
RAS# Precharge (tRP): 5
Precharge Delay (tRAS): 15
All Precharge to Act: AUTO
REF to ACT Delay (tRFC): 54
Performance LVL (Read Delay) (tRD): 8

Read delay phase adjust: Enter

Ch1 Read delay phase (4~0)
Channel 1 Phase 0 Pull-In: Enabled
Channel 1 Phase 1 Pull-In: Enabled
Channel 1 Phase 2 Pull-In: Enabled
Channel 1 Phase 3 Pull-In: Enabled
Channel 1 Phase 4 Pull-In: Enabled

Ch2 Read delay phase (4~0)
Channel 2 Phase 0 Pull-In: Enabled
Channel 2 Phase 1 Pull-In: Enabled
Channel 2 Phase 2 Pull-In: Enabled
Channel 2 Phase 3 Pull-In: Enabled
Channel 2 Phase 4 Pull-In: Enabled

MCH ODT Latency: 2
Write to PRE Delay (tWR): AUTO
Rank Write to Read (tWTR): AUTO
ACT to ACT Delay (tRRD): AUTO
Read to Write Delay (tRDWR): AUTO
Ranks Write to Write (tWRWR): AUTO
Ranks Read to Read (tRDRD): AUTO
Ranks Write to Read (tWRRD): AUTO
Read CAS# Precharge (tRTP): AUTO
ALL PRE to Refresh: AUTO

Basically I've tried every combo under the sun, and so far come up with nil. I ended up taking out my multimeter and measuring the VTT using my ground plugged into a molex ground, and measuring as shown on the guide. Instead of a droop, I actually got an .02 increase, so I used 1.4385 x .67 = .963 I then used the GTL charts supplied by clunk, and have tried anything above 66% to 70% and found little success.

So my current questions are:
Do I need to measure the reference volts for more help?
Are one of my main voltages too low, causing these crashes?
Does it matter when I use my meter where ground is, other than the fact that it needs to be consistent?
Since my cpu VTT has Vrise, does the gtl chart still apply for me (or is it different per board)
Do the cpu gtls crash differently than the northbridge gtl?

The only comment I have is on the last question. I remember reading if its a random core, its the northbridge gtl. It seems that right now I have random cores failing, so I'm guessing my issue is the nb gtl. Any help would be appreciated, as I'm getting close to just giving up and waiting for a P45 board.

[Clunk]

I notice you have the PCIE frequency at 105, how come? Is it stable with 333/667 strap?

Have you tried with GTL Ref disabled?

That VTT is very high, and so is the vcore and so is the NBcore for that overclock.

It might just be that your CPU isn't a great overclocker, in which case, no amount of voltage is going to work.

[Rinaun]

Thanks for the speedy response clunk I have it set at 105 because it allows slightly better overclocks and benchmarks for 24/7 use on the Gfx card I believe. I'll try the 333/667 strap, but isn't it better overall to use the 333/800 strap for better memory usage? The voltages are set high because I was wondering if the voltages were causing the issues. I've tried anywhere form stock to 1.6 on most settings.

Now I have one more question, when do you know you have your NB gtl off, when you dont even know if your cpu gtls are on? I noticed after getting close to what seems to be a close setting, my computer just bsods instead of running prime, not testing one core, and failing. I noticed this because usually one core doesn't even test itself, but when I get supposedly close, they all test themselves, just one or two cores very slower than the other cores. then, when I move just one setting from that, I get maybe one test in on each core, then bsod. Its basically like "101 bsod, 102 prime for 6, 103 prime for 40, 104 all cores working ,prime95 for a long time, then I move one up and bam, bsod. Should I stop there and try my cpu gtls, or am I crazy for thinking this? thanks for the help!

Edit: I tried with the reference off, and it doesnt even work stock. The ram is stable, so is the cpu, but I think my board just has a VTT overvolting issue or something strange, I'm not really sure.

[Clunk]

You may find that you have more success with an 8x multi and a higher FSB, this would still allow you to run your memory faster, but then you can keep 1:1.

Start with my Q6600 settings from page 2 or 3 of this thread, or fromt he DFI overclocking guide add on.

I suspect that if you can't run with GTL Ref disabled at stock, then you have problems elsewhere with your system.

The GTL REF voltage setting turns on/off the voltage adjustment for all 3 GTL REF settings.

[Rinaun]

Alright I'll reset my settings and try those in a second. Can you explain to me why my VTT was .02 more than I set in bios, rather than LOWER then the option? I don't think I've heard of it overvolting VTT before.

[Clunk]

I'm not sure why your VTT is 0.2 over, maybe your DMM isn't accurate?

[Rinaun]

Well, I'm measuring from the point suggested by a picture on this site, and using a ground off a molex connector for the psu. Wouldn't my ground source affect the voltages displayed? if so what should I use for a ground? I'll check my meter again once I reboot.

[Rinaun]

So basically I tried a ton of settings in 333/667, and my board just HATES that. I can rarely get it to boot with those settings and any voltages. currently I'm using 417 x 9 on the 333/800 to achieve around 3.75Ghz, all GTL's on auto. I fail OCCT at around 2 hours 11 minutes, and I can't figure out what needs more (or less) volts.

CPU VID Control: 1.48V (Real) I'm almost positive my core has issues with 2 cores being stable past 3.8 as determined by some research on my batch #
CPU VID Special Add: .23%
DRAM Voltage Control: 2.150V (2.1 Real)
SB Core/CPU PLL Voltage: 1.510V
NB Core Voltage: 1.504V (1.47 Real)
CPU VTT Voltage: 1.327V 
Vcore Droop Control: Disabled
Clockgen Voltage Control: 3.45v
GTL+ Buffers Strength: Strong
Host Slew Rate: Weak
GTL REF Voltage Control:DISABLED
x CPU GTL1/3 REF Volt: 
x CPU GTL 0/2 REF Volt: 
x North Bridge GTL REF Volt:

[Clunk]

Originally Posted by Rinaun

Well, I'm measuring from the point suggested by a picture on this site, and using a ground off a molex connector for the psu. Wouldn't my ground source affect the voltages displayed? if so what should I use for a ground? I'll check my meter again once I reboot.

The molex ground will be fine.

[Clunk]

Looks to me like it could be a few things.

Poor CPU - Gone as far as you can.
RAM on the way out?
Faulty motherboard.

I say this because you say that you can't run at stock with GTL ref disabled.

You need to start testing your parts individually, that's really the only solid advice I can offer at this point