Originally Posted by turkletont
Hello I just have a bunch of questions I'd like to ask about my Memory and timings etc. I have some kingston hyper x 1600 mhz @ 1.65 volts, 8gb. running i5 3570k on asrock extreme 4..
A. FSB:DRam ratio is 1:6 does this mean anything? is it relevant at all?
B. Command rate is at 2t, is this what it should be at?
C. How do I read CPU-Z under the "SPD" section?
It says Max Bandwith PC3-10700 (667mhz) isn't this wrong? Shouldn't it be higher if it's running at 1600 mhz?
Also where it says JEDEC#1-4 under the CAS timings they are all different and do not say 9-9-9-27 like I set it up in bios.
Also the voltage says 1.5v under jedec1-4 even though I set it to 1.65 in bios.
A: It means that your mobo's clock and your ram clock have that relation between them. No relevant at all. In the past it was easy to have 1:1 with core 2 duos, but that was more of an epeen thing.
B: it should be at what is specified by your RAM or at whichever is stable.
C: I don't really remember but it will show you your profiles - what timings you ram should be running at the respective clocks and voltages.
DDR is Double data rate, which means that it's DOUBLE data rate, so in short 1334mhz is actually 667mhz. Dual channel makes 1334mhz ram run truly at 1334mhz.
You can run your ram at a higher clock, if you overclock it. But where does it says PC3-10700? If it's a reading something must be out of place.
I just realised you are talking about the SPD section. Well, like I said, those are the profiles your ram could run at.
1.5v under jedec1-4 mjeans that those profiles jedec1-4 use only 1.5v
Want my advice? Don't bother with your RAM unless you are an extreme benchmarker. Are you? Then loose the timing, don't mind overckocing your ram. Keep it below or on default specs. The reason for this is that it's really hard to OC ram and the gains are minimal.
Going from single to dual channel (1066mhz ddr2) in a game in the source engine, for example - when I did this test, I went from 192FPS to 192,5. That's more than 1% gain (in this case the GPU was the bottleneck, however even when it's not the GPU your gains are too small)