Help with memory timings...

jarvis82 · 4 Jun 2012 at 18:06

Hi all,

Could I pick the brains of those in the know, with regard to my memory.

CPU Z is showing that the memory is running at 700. Times that by two, and it seems I'm only getting 1400mhz, yet I have DRAM frequency set to 1603 in the BIOS...So have I set something wrong??

My i7 970 overclock is 4.2ghz from 21 x 200. DRAM bus voltage is 1.64.

My 12GB of tri-channel Kingston HyperX 1600, has quoted latencies of 8-8-8-24, but as CPU Z reports the latencies at 9-9-9-24, thats what I've entered into the BIOS - I guess I could tighten these up to the quoted latencies?

Any input appreciated - thanks!

Surveyor · 4 Jun 2012 at 18:12

Are you sure your overclock is 21x200MHz?

Check the CPU tab.

24x175MHz also equals 4.2GHz.

175MHz x8/2 (the FSB : DRAM ratio) = 700MHz.

This also ties in with your NB Frequency which is 16x the bus speed.

16x175MHz = 2800MHz.

jarvis82 · 4 Jun 2012 at 18:56

Hmmm, genuinely mystified now, as you are absolutely right - CPU Z reports that its 24 x 175. But in the BIOS it is definitely set to 21 x 200.

I do have load line calibration and speedstep enabled, so the multiplier drops when it isn't under full load. But why would it not be working to what I have set in the BIOS?
:confused:

EDIT - I wonder if its Turbo mode, as I think the higher multiplier is locked on the 970 unless Turbo mode is active. I'll have a look at my BIOS again.

jarvis82 · 4 Jun 2012 at 20:49

Well, Turbo is disabled, but I think that CPU Z is giving duff info...

Noticing that Coretemp is showing 21 x 200 overclock, I downloaded CPU Tweaker, low and behold that also shows 21 x 200...

I then went back into the BIOS and changed it to 24 x 175, and surprise surprise both Coretemp and CPU Tweaker showed the 24 x 175. So if they are reading correctly, surely the issue has to be with CPU Z?

On a separate note, I figured since CPU Z must be reading wrong, and my memory is at 1600, I'd try the 8-8-8-24 timings - BSOD on boot up. Set it back to 9-9-9-24 and loaded fine. Should prob have tried it a second time on the lower settings to make sure...

Anyone heard of CPU Z giving duff information before like this?

:confused: