**Official DFI LanParty UT X48-T2R(and LT) Discussion

[adya]

hmm dude try messing with the NB GTL Setting.. like lower it for higher fsb..
and lower the vtt..
working great for me..
now running 1.15vtt for 500fsb.. 8x500..
will post in a minute
Proc: E8500 @ 500x8ghz 1.275v
Ram: Team Xtreem PC2-8500 CL5 4x1gb @ 1000mhz CL4-4-4-8 333/667 tRD 7
The vtt /gtl and nb is rock solid..
will try to lower the vcore.. but afaik tested this proc on maximus and gigabyte p35dq6.. the vcore for 4ghz is 1.272v..[/QUOTE]


i thought for 4ghz u would need atleast 1.4v thats amazing. and a 500fsb/+4x1gb @1000mhz? thats pretty cool, ill have to take ur advice and lower my vtt. i thought the higher vtt the better for getting above 450fsb. guess i was wrong.
any chance of getting template of ur settings? not to cpy but to see where im going wrong.
there wouldnt be a huge difference between an e8500 and and a x6800 when it comes to voltage needed? ive got mine at 1.49v im not happy about having it so high but i want stability.

[cstkl1]

well yes but the problem with the vtt voltage for 500 fsb is not the CPU GTL's
its the NB Gtl's
will post my template and u sill see what i mean.

Example for Default leaving it at auto i need 1.4vtt and NB at 1.67 voltage
changing GTL to 70 i need vtt 1.2, NB at 1.63v
and the current gtl as follows
so i guess mess with lowering the NB gtl.. not too sure as how the 65nm would work on this board as i dont have any left..

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

Exist Setup Shutdown: Mode 2
Shutdown after AC Loss: Disabled
CLOCK VC0 divider: AUTO
CPU Clock Ratio: 8x
- Target CPU Clock:4000 
CPU Clock: 500
Boot Up Clock: AUTO
DRAM Speed: 333/667
- Target DRAM Speed: 1000
PCIE Clock: 110MHz ( Not advisable for Ati Cards)
PCIE Slot Config: 1X 1X

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

Voltage Settings
CPU VID Control: 1.275 
CPU VID Special Add: Auto
DRAM Voltage Control: 2.19V
SB Core/CPU PLL Voltage: 1.510V
NB Core Voltage: 1.60v
CPU VTT Voltage: 1.149v
Vcore Droop Control: Disabled
Clockgen Voltage Control: 3.45v
GTL+ Buffers Strength: Strong
Host Slew Rate: Weak
GTL REF Voltage Control: Enable
x CPU GTL1/3 REF Volt: 90
x CPU GTL 0/2 REF Volt: 85
x North Bridge GTL REF Volt: 60

DRAM Timing
- Enhance Data transmitting: FAST
- Enhance Addressing: FAST
- T2 Dispatch: Disabled

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

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

Ch1Ch2 CommonClock Setting: More 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): 4
RAS# to CAS# Delay (tRCD): 4
RAS# Precharge (tRP): 4
Precharge Delay (tRAS): 8
All Precharge to Act: 4
REF to ACT Delay (tRFC): 23 ( Followed my SPD timings)
Performance LVL (Read Delay) (tRD): 7

Read delay phase adjust: Enter

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

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

MCH ODT Latency: AUTO
Write to PRE Delay (tWR): 11 (Memset/Everest Reads as 10)
Rank Write to Read (tWTR): 14 (Memset/Everest Reads as 13)
ACT to ACT Delay (tRRD): 3
Read to Write Delay (tRDWR): 8
Ranks Write to Write (tWRWR): 5
Ranks Read to Read (tRDRD): 5
Ranks Write to Read (tWRRD): 5
Read CAS# Precharge (tRTP): 3 (Memset/Everest Reads as 5)
ALL PRE to Refresh: 4

Felix here is another one
Set tWR to 11.. memset reads as 10
Set tWTR to 14 .. memset reads as 13




Well this setting is rock hard stable.. kekeke..
when i ran occt for 4 hours it was running 99.60% CPU load

for others 45nm C2D.. just change the vcore my guess
and for ure rams if 2x2gb just change to 5-5-5-15 Performance Level 8 and Leave the tRFC to auto
This board gets better and better once u know what ure doing ..

[adya]

oh man thats like gold to me right now. ok im going to start again, i might have to keep a higher vcore than urs though as i doubt my x6800 will like 1.31v. i noticed ur fsb is much higher than mine to so ill up that even more.
i thought u meant cpu vtt i see what u mean now. ill reset my nb vtt see how it goes.
thanks alot for that .
ps- im also shocked that ur core temp is only 15c ! im on water and occt on 90%plus load has it at almost 60c!!

[cstkl1]

update.. i was a bit suspscious of the tWR and tWTR setting as i coudlnt remember what i was running at for the OCCt 4 hours..

checked and rechecked
that memset reading 9 and 12 is unstable..
so the last two benchies is actually unstable.3dmark06 and everest

changed to setting 11 and 14 memset read 10 and 13

those thats .. thats the coolit freezone elite on mid setting working..
heck i usually have to run it at low..for 24/7
and for benching at those voltage mid

living in malaysia.. so will get serious condensation issues

[Clunk]

hey clunk i saw ure review

hmm i have the same proc

for 500fsb u used 1.2vtt??
nb???
and left the gtl on manual right??

cause i seriously think the gtl on auto is way off...

will post my result soon to show this..

Yes, you don't need a lot of VTT for a Wolfdale. I was using the stock 1.1v right up to 500FSB and at that point it needed 1.2v.

No, the GTL was set to disabled for these tests.

The GTL ref values are intended as a ball park figure, because your own board will probably measure slightly different to the one that DFI used to get those tables.

If in doubt, grab a DMM and measure the voltages of your board, it's the only 100% way to do it really

[adya]

ok ive got my vtt set at -
-1.453
-130
-120
-for nb gtl i have 70 instead of 100. i lowered it somewhat .

vore- in bios reads 1.49 in smart gaurdian its alot less its 1.47
nb -1.52 smart guardian
vdim -2.2
i had these volts alot higher and they gave me occt stability for 2hours. but now i lowered hoping its still stable. occt is running now.

[karateo]

new here!
with the latest official bios, it seems that the special vid add is not enabled. Am i right?

[Clunk]

The vcore needs to be above a certain amount before you can access the Special VID now.

It appears to be when the numbers change colour, then you can access it.

[Praz]

When my UT board gets here I'll ask that the Special VID Add is changed back. Oskar was able to do it for the P35 board when I asked.

[zsamz_]

What's up with your X38?

its verry picky on ram clunk
i'm using my ballistix 8500 now cause its the only sticks that give me no problems"i was saving them i dont want no i 1 sided stix if i rma"
my mushkin xp8500 are a pain on it "d9gkx" c1 on coldboot and can only run cas 4
my kingston hyperx 8500 "d9gkx"getting c1 on coldboot

[RobPuba]

What heatsink are you guys using ??

[CoolZone]

When my UT board gets here I'll ask that the Special VID Add is changed back. Oskar was able to do it for the P35 board when I asked.

do you have an ETA for the UT board?The X48?

[Clunk]

its verry picky on ram clunk
i'm using my ballistix 8500 now cause its the only sticks that give me no problems"i was saving them i dont want no i 1 sided stix if i rma"
my mushkin xp8500 are a pain on it "d9gkx" c1 on coldboot and can only run cas 4
my kingston hyperx 8500 "d9gkx"getting c1 on coldboot

That's a bit odd mate

I used a set of Tracers and a set of Ballistix, both 8500 D9 and they were fine, the only problems I had on my X38 that were similar to yours were when I had a dying stick of RAM.

[Clunk]

When my UT board gets here I'll ask that the Special VID Add is changed back. Oskar was able to do it for the P35 board when I asked.

Thanks

[Praz]

do you have an ETA for the UT board?The X48?

Don't know anything more then anybody else as to a firm date. What little I've heard puts the board around mid May.

The Special VID Add is a big deal for me. Except for benching I'm a believer in using VDROOP the way Intel specs it. Makes life much easier on both the processor and the power section of the board. But without Special Add idle voltage is unnecessarily high.

[karateo]

I got the board today with a new WD 2500AAKS hard disk.

I have connected a raptor-x, 2x 2500KS, 1x 2500AAKS and a seagate to the ICH9R set as RAID in bios.

Now, my problem is that I cannot make all of my drives to perform at maximum (talking about random access time).
Sometimes my new drive gets 13ms but most of the time 16ms
I tried to swap a cable with another drive but then the old fast one got 16ms and the new "crap performer" scored 13ms.

I thought it was the sata cables...nothing changed when changing ALL of them.

This is my 3rd dfi motherboard! Two P35 and this one (X48 LT).
Has anyone else experienced something similar? Can someone reproduce my problem?
If I can't get it work by tomorrow I am going back to ASUS

[cstkl1]

The vcore needs to be above a certain amount before you can access the Special VID now.

It appears to be when the numbers change colour, then you can access it.

for my proc i can use it above 1.2v
here is the catch if u guys want to use it rather than increasing the stock vid

example for my case
go higher than stock vid auto setting
then increase the special vid
and then change back stock vid to auto..
kekek it works..

but the vcore still overvolts on bios and cpuz reading
vmm shows different story that its about 0.02-0.04v less

[Clunk]

I just spoke to Jimmy at DFI and he said that the reason they set the Special VID to work >1.2v is that when the Vcore is under 1.2v, there can be additional ripple caused if the Special VID is used, so to avoid any power issues, they decided to only allow the Special VID after 1.2v.

That's all the info I have, hope it fills in some blanks

[zsamz_]

That's a bit odd mate

I used a set of Tracers and a set of Ballistix, both 8500 D9 and they were fine, the only problems I had on my X38 that were similar to yours were when I had a dying stick of RAM.

all my sticks 100% mate my board just too picky
i'll run the ballistix if they die i'll just get some gskills
i'm running 4x1 now 511fsb need only 2.1v 1226mhz

this board just loves my balistix tested 2.1v for this

[Bitgod]

Ok, got my hardware in today, thumbing through the manual, I had 3 questions.

1) This is my first water cooling job, will the system freak if it sees no RPMs on the CPU and NB fan bus?

2) I assume the port marked LAN port 1 is the one I want to be using? Whats the difference between the 2 marvell chips?

3) Regarding the 2 FDD connectors on the mobo, if I'm using 1 video card, should I have 1 or both plugs plugged in?

Thanks.

[fireice2]

The Special VID Add is a big deal for me. Except for benching I'm a believer in using VDROOP the way Intel specs it. Makes life much easier on both the processor and the power section of the board. But without Special Add idle voltage is unnecessarily high.

QFT! I also believe in safe overclocking for 24/7 use. Except for benches having Vdroop makes sure the processor gets the right amount of power.

[Rinaun]

Hey guys,

I'm having some problems with subtimings with these 2gbx2 pc28000 g.skills. I cant pass stable at 500 without errors or corruption. I'm almost positive its my subtimings, since I set some to auto because of countless options for memory on this board. Any suggestions for some of the finer ram timings?? Using 333/800 strap for now, but would like to move to 333/667 after I figure out these timings.

[cstkl1]

Hey guys,

I'm having some problems with subtimings with these 2gbx2 pc28000 g.skills. I cant pass stable at 500 without errors or corruption. I'm almost positive its my subtimings, since I set some to auto because of countless options for memory on this board. Any suggestions for some of the finer ram timings?? Using 333/800 strap for now, but would like to move to 333/667 after I figure out these timings.

eh u do realize the the amount of NB and ram voltage u going to need at the lowest trd for 333/800 at 500 fsb 1:1..heck i even wont go there unless the latencies are right...

i suspect all ure voltages is unstable.. NB and VTT..and VCore..

[zsamz_]

eh u do realize the the amount of NB and ram voltage u going to need at the lowest trd for 333/800 at 500 fsb 1:1..heck i even wont go there unless the latencies are right...

i suspect all ure voltages is unstable.. NB and VTT..and VCore..

500fsb 1:1 333/800=1200mhz i doubt they gonna do that speed slight chance if they were pc2-8500

[Clunk]

Review made it onto the DFI front page

http://us.dfi.com.tw/index_us_noflash.jsp?SITE=US