Tighter timings.

[dbilz]

I figured since my pair of HZ's are running below their rated MHz I could tighen the timers except I dont know much about it.

Here are my settings

DRAM Frequency Set - 166=RAM/FSB:05/06

Command Per Clock (CPC) - Enable

CAS Latency Control (Tcl) - 3.0

RAS# to CAS# delay (Trcd) - 04 Bus Clocks

Min RAS# active time (Tras) - 08 Bus Clocks

Row precharge time (Trp) - 04 Bus Clocks

Row Cycle time (Trc) - 07 Bus Clocks

Row refresh cyc time (Trfc) - 14 Bus Clocks

Row to Row delay (Trrd) - 02 Bus Clocks

Write recovery time (Twr) - 02 Bus Clocks

Write to Read delay (Twtr) - 02 Bus Clocks

Read to Write delay (Trwt) - 03 Bus Clocks

Refresh Period (Tref) - 3120 Cycles

Write CAS Latency (Twcl) - 1

DRAM Bank Interleave - Enabled



DQS Skew Control - Auto

DQS Skew Value - 0

DRAM Drive Strength - Level 7

DRAM Data Drive Strength - Level 1

Max Async Latency - 8.0 Nano Seconds

DRAM Response Time - normal

Read Preamble Time - 5.0 Nano Seconds

IdleCycle Limit - 256 Cycles

Dynamic Counter - enable

R/W Queue Bypass - 16 x

Bypass Max - 07 x

32 Byte Granularity - Disable(4 Bursts)

 

Any help will be much appreciated.

[cellyboo]

Just a thought...

 

CAS Latency Control (Tcl) - 2.5

RAS# to CAS# delay (Trcd) - 03 Bus Clocks

Min RAS# active time (Tras) - 08 Bus Clocks

Row precharge time (Trp) - 03 Bus Clocks

Row Cycle time (Trc) - 07 Bus Clocks

Row refresh cyc time (Trfc) - 10 Bus Clocks

Row to Row delay (Trrd) - 02 Bus Clocks

Write recovery time (Twr) - 02 Bus Clocks

Write to Read delay (Twtr) - 01 Bus Clocks

Refresh Period (Tref) - try 2560 or 2592 Cycles

 

DQS Skew Control - increase

Max Async Latency - 7.0 Nano Seconds

DRAM Response Time - fast

IdleCycle Limit - 16 Cycles

[greatscott68]

You'll probably have better luck posting this in the OCing section. Putting it here doesn't make any sense, so you must have made a goof. In the meantime, check out this guide:

 

http://www.dfi-street.com/forum/showpost.p...179&postcount=4

 

It's always better to at least kinda understand what you're messing with, so when things go wrong (and they will), you'l have a better idea of where to start looking. Read the whole thing. Actually, read the whole guide. Great stuff there.