Simple timing query

Neken

Neken

Neken

Associate
Joined
28 May 2006
Posts
53
A quick and no doubt simple query for you please :)

I've got some of the Ballistix 6400C4 and I've set it to 800MHz but am not 100% sure of the timings required in the bios (for stock settings)

On my ASUS P5W DH Deluxe the options I have are:
1. CAS# Latency
2. RAS# Precharge
3. RAS# to CAS# Delay
4. RAS# Activate to prechrage
5. DRAM Write Recovery Time

I believe 1-4 should be 4-4-4-12 - correct?

But what should 5 be set to?

Thanks
 
16 mefinks :D Thats a guess though. You might be better off knowing 100% before you set it at 16. If you know the default SPD table on your ram type to be at an optimum setting other than a 'failsafe default' then set it to auto and check in CPU-Z 'Memory' tab and all will be revealed for you to set all in the bios manually
 
Last edited:
Thanks for the reply. CPU-Z shows the following.
memory.gif
spd.gif


Is "Bank Cycle Time (Trc)" the same as "DRAM Write Recovery Time" or is that just coincidence?

(it's at 390Mhz as the motherboard doesn't seem to like 400Mhz anymore :()
 
Last edited:
No, DRAM Write Recovery is tWR and it should be similar to the CAS latency figure eg. 4 or 5.
 
The Column Address Select figure is the minimum time it takes to position the RAM cursor to read or write to a specific column location on a RAM row.

The RAM write recovery time has to be the same as or greater than the CAS figure otherwise the RAM cannot locate the place it has to write the data to. For safety (to avoid corruption) it is probably safer to have it set to CAS+1 as that way there is always adequate time for the RAM to write and then prepare itself to write again.

It's not hard to get your head round these numbers, you just have to sit down and work through how the RAM actually works.

You could set it to 16 and it would make little difference, but setting it to 4 or 5 will allow the memory controller to work smarter if everything else is optimal.
 
You must log in or register to reply here.
Back
Top Bottom