400 strap works for you? Strange :shrug:
Anyway, seems like you pump as much volts through the NB as me, and I'm using the 333 strap and even higher FSB so I'll stick with the 333. Also, my everest score @1100 is about the same as yours...
400 strap works for you? Strange :shrug:
Anyway, seems like you pump as much volts through the NB as me, and I'm using the 333 strap and even higher FSB so I'll stick with the 333. Also, my everest score @1100 is about the same as yours...
I'm currently using these settings for 24/7:
http://www.abload.de/thumb/440_ddr2-1174_08295kq.jpg
Memory copy performance could be better but all in all performance is alright now with new BIOS.Code:CPU Feature
- Thermal Management Control: Enabled
- PPM(EIST) Mode: Enabled
- Limit CPUID MaxVal: Disabled
- CIE Function: Auto
- Excecute Disable Bit: Enabled
- Virtualization Technology: Enabled
- Core Multi-Processing: Enabled
Exit Setup Shutdown: Mode 2
Shutdown after AC Loss: Disabled
CLOCK VCO divider: Auto
CPU Clock Ratio Unlock: Enabled
CPU Clock Ratio: 8
- Target CPU Clock:
CPU Clock: 440
Boot Up Clock:
DRAM Speed: 400/1066
- Target DRAM Speed:
PCIE Clock: 100mhz
PCIE Slot Config: 1X 1X
CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled
SATA Spread Spectrum: Disabled
Voltage Settings
CPU VID Control: Auto (1.2325)
CPU VID Special Add Limit: Enabled
CPU VID Special Add: Auto
DRAM Voltage Control: 2.1V
SB Core/CPU PLL Voltage: 1.510V
NB Core Voltage: 1.530V
CPU VTT Voltage: 1.260V
Vcore Droop Control: Enabled
Clockgen Voltage Control: 3.45V
GTL+ Buffers Strength: Strong
Host Slew Rate: Weak
MCH RON Offset Value: 00
MCH RTT Offset Value: 00
MCH Slew Rate Offset Value: 00
MCH VREF 1 Value: 00
MCH VREF 2 Value: 00
MCH VREF 3 Value: 80
GTL REF Voltage Control: Enabled
x CPU GTL1/3 REF Volt: 90
x CPU GTL 0/2 REF Volt: 87
x North Bridge GTL REF Volt: 90
DRAM Timing
- Enhance Data transmitting: Fast
- Enhance Addressing: Fast
- T2 Dispatch: Enabled
Clock Setting Fine Delay
DRAM CLK Driving Strength: Level 6
DRAM Data Driving Strength: Level 8
Ch1 DLL Default Skew Model: Mode 1
Ch2 DLL Default Skew Model: Mode 1
Fine Delay Step Degree: 70ps
Ch1 Clock Crossing Setting: Auto
- 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: Auto
- 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: Auto
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: 6
REF to ACT Delay (tRFC): 54
Performance LVL (Read Delay) (tRD): 6
Read delay phase adjust: Enter
Ch1 Read delay phase (4~0)
- 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)
- 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): 14
Rank Write to Read (tWTR): 11
ACT to ACT Delay (tRRD): 3
Read to Write Delay (tRDWR): 8
Ranks Write to Write (tWRWR): 6
Ranks Read to Read (tRDRD): 6
Ranks Write to Read (tWRRD): 5
Read CAS# Precharge (tRTP): 3
ALL PRE to Refresh: 6
ah so you need a bios update to run the 4870x2?
edit * sorry i posted in wrong thread. was meant to be in x48 duh !
*** sorry wrong thread as well ***
Someone tried the new 2008/10/02 beta bios?!
I wonder about this:1. Added F9 Hot Key function. ?
Just got another one of these boards from a friend who's just grown frustrated with it =)
Setup:
DFI LT LP x38-T2R
Core2Quad Q6600 (1.325 VID) + TRUE 120 Extreme
4 x 1GB Ballistix Tracers (D9GMH)
2 x Sapphire HD3870 Atomic
1 x Samsung 160GB SATA
1 x Samsung 500GB SATA
Corsair 620HX
The only "mods" done to the board is removing the pushpins on the NB and PWM heatsinks to bolt them down instead. The Q6600 is lapped and the TRUE is lapped and washer modded.
Best I can do with this setup is 3.6GHz (either 8x450 or 9x400). Anything higher is completely unstable. My voltages are pretty low (see settings below) but increasing voltages or messing with GTLs doesn't help. If I increase the PLL voltage to 1.6 I can get the system game / wPrime stable (but not OCCT / Prime stable) up to 3.8 without adjusting any other voltages besides vcore (which I need at least 1.46).
Pretty sure it's the board as it's also showing typical DFI board problems (cold boot, random POST error messages that can be cleared with a few resets). Also it's a China board so I didn't very high expectations in the first place.
Using BIOS 314 as anything higher mean more instability (can't even do 3.8 game stable with higher BIOS).
Temps with the settings below are 62 / 62 / 58 / 58 full load with room temp at around 23C.
Settings:
Definitely going to dump this board once I find something else that clocks quads well.Code:CPU Feature
- Thermal Management Control: Disabled
- PPM(EIST) Mode: Disabled
- Limit CPUID MaxVal: Disabled
- CIE Function: Disabled
- Virtualization Technology: Disabled
- Core Multi-Processing: Enabled
Exit Setup Shutdown: Mode 2
CLOCK VCO divider: Auto
CPU Clock Ratio: 8
- Target CPU Clock:
CPU Clock: 450
Boot Up Clock: Auto
DRAM Speed: 266/667
- Target DRAM Speed: DDR2-1128
PCIE Clock: 100mhz
PCIE Slot Config: 1X 1X
CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled
SATA Spread Spectrum: Disabled
Voltage Settings
CPU VID Control: 1.30625 (Anything less disables VID Special Add Limit)
CPU VID Special Add: 106.61% (CPU-Z reports 1.424V)
DRAM Voltage Control: 1.985V
SB Core/CPU PLL Voltage: 1.510V
NB Core Voltage: 1.504V
CPU VTT Voltage: 1.233V
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: Grayed
x CPU GTL 0/2 REF Volt: Grayed
x North Bridge GTL REF Volt: Grayed
DRAM Timing
- Enhance Data transmitting: Fast
- Enhance Addressing: Fast
- T2 Dispatch: Enabled
Ch1 Clock Crossing Setting: More 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: More 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: 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):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): 28
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: Auto
- 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: Auto
- Channel 2 Phase 2 Pull-In: Auto
- Channel 2 Phase 3 Pull-In: Enabled
- Channel 2 Phase 4 Pull-In: Enabled
MCH ODT Latency: Auto
Write to PRE Delay (tWR): 14
Rank Write to Read (tWTR): 11
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): 3
ALL PRE to Refresh: 6
Why do I have such low results in Everest with 400x8 and DDR2-960 5-5-5?
http://img232.imageshack.us/img232/461/61864040ya4.jpg
http://img232.imageshack.us/img232/6...jpg/1/w539.png
also t2 dispatch is dissabled and the cross channel settings need to be set to aggressive or more aggressive
and diabo should do like 1200mhz so try 266:800
any 1 notice how the newer two non beta bios are alot more thursty on NB volts, well since the 45nm code was added?
its seem quite the oppersite on lower clocks tho, the NB can go alot further on its stock 1.265v then what it could on say the 2008-03-14 bios.
I mean that system with default settings runs much slower than it should be.
Here
http://www.anandtech.com/mb/showdoc.aspx?i=3294&p=4
it goes 333x9 DDR2-1066 5-5-5-15 with everest results (read write copy latency) 6254 7021 7607 82.1
and mine with same 333x9 DDR2-1066 5-5-5-15 give only 5876 5572 5018 84.0.
I use load optimized settings in bios with only changes: memory freq set 1066, PL 7, T2 dispatch disabled.
The same slowness, comparing with results of others, I noticed with different FSB and memory freqs .
May it be because of Vista or drivers?
Few posts above there is the post of merlin76
http://www.xtremesystems.org/forums/...postcount=3452
I used his settings, with only difference in voltages and PL, memory won't go with PL lower than 7.
http://img178.imageshack.us/img178/9...age2cp3.th.jpg
Look at his results and mine.
I'm using latest 10-02-08 BIOS and 2x1Gb D9GMH sticks.
I just cant fugure how it could be 1.5 times difference :shrug:
set your mhc odt delay to the same as the PL, and set the phases to eaeee/eaaee. and set the 2 things above t2 dispatch to fast t2 enabled and drop the trfc to 40
and are u memtest stable
LOL I did it :rofl::rofl:
http://img142.imageshack.us/img142/3...pimage3py4.png
http://img142.imageshack.us/img142/n...png/1/w537.png
Just compare it with my previous everest screen a few posts above, especially L1 and L2.
All conditions are same (i e just loaded optimization settings in bios with only change in settings 400x8 and DDR2 960, all other settings are untouched).
But now it is ~1.5 times faster and it is finally just how it must be.
I've tried all the possible - various bioses, reinstall os, drivers, different everest versions, hundred changes in bios setiings, different memory slots etc, spending whole day on it.
Nothing helps. My results always was near 1.5 times slowler.
And at the end of these researches I occasionly noticed that my box cooler was covered with a thick dust rig.
So I cleared cooler. One more thing I did - remove 2 PCI cards.
And suddenly it started to work :D
I guess processor did some kind of throttling, bypassing cycling due to constant overheating.
That's my happy end story :up:
PS One more question - I can boot system up with xeon 3110 only at 500MHz, 510 won't start, with all voltages at high levels. Is it due to processor FSB wall or Mobo?
i cant get past 506 on mine but i dont know if it was the DFI or the cpu, i havnt tried again since i switched to a blackops
and if u now do what i suggested affter u fixed it it will get much better copy
Well, I have tested my Xeon 3110 on Asus P5Q-E
There are no any probs with it. With 570x6 you can work in BIOS already, 540x6 it can load OS and work in apps.
Optimal and stable result is near 500x8.5.
But DFI pass only 500x6 and hangs at 510x6. Same FSB wall on motherboard I saw at other people, and even in some reviews.
It seems that many x35 chipsets, especially first revisions, just couldn't go over 500 :down:
Those people in DFI was too fast at this time with x35, before they made new models with some time lag.
Time to move to i7?
Oh, so you think it's not the board but my unproper hands?
It makes me hope :)
To be honest I didn't try any GTL or other tweaks. Only voltages were changed from default settings, all other was in auto. Ok, I'll try GTL and other things.
You know, I have one more problem - with the memory.
I have quite good 4x1Gb sticks with D9GMH, 8-layer PCB. But they want to run 1200 only with 2.3v, and even at this voltage they are not fully stable.
Also as I know many of them (CSX) may run 1200 fully stable only at 2.1v.
But here I've tried alot different timings and other memory settings. No progress.
What may you recommend to check at first?
I gonna check these DIMMs on P5Q-E too, but only net week.