"It actually makes so much sense to overclock the Core i5 from its 133 MHz base clock to a little more that we recommend this to every user who is interested in getting more risk-free performance at zero cost. Moving from a 133 MHz BCLK to 150 or 160 MHz, which was the maximum setting in our tests that didn’t require a voltage increase, does not increase your total system idle power. Apparently, the processor power saving features keep idle power in check very efficiently. Peak power, which would be our top reason against high overclocks, still doesn’t explode. We measured less than a 6% increase in peak power on the MSI P55-GD65 when going from a 133 to 160 MHz clock. This had the processor reaching 3.36/3.84 GHz maximum clock speeds in the two applicable Turbo Boost modes (one to two and three to four cores used)."
I don't game, and am just looking for the most bang, without a constant high overclock, and the resulting power consumption. I specifically got the 1600MHz Ram so at the 160 BCLK, and the native 10X Ram multiplier, it will run at it's 1600MHz rating.
OK, so assume all that, now I'm looking for confirmation of correct timings. At stock, the MB sets the 1333MHz Ram to 9-9-9-24. If I just change the BCLK to 160, it sets the timings at 7-7-7-18. It appears from data sheet that correct settings for 1600MHz is 8-8-8-24.
Sandra Lite has this info:
Notice CPUZ says PC3-10700, which is 1333MHz . Everest Ultimate says the same thing, but I can visually confirm it is the correct 1600MHz HyperX Ram I noted above...weird, but not a concern.
So, long story long . What do you think? 8-8-8-24? 8-8-8-20? Any help, information, advice appreciated. I'm not looking to overclock Ram, or get some radical setup. Just the correct , best timings. Thanks in advance, A Guy
Thanks for anwering Saint, your answer is best by default, lol. I set BCLK to 160, set Ram to 1600MHz, 8-8-8-24. Ran Prime 95 4 hours, and memtest 6 hours after that. Looks like I'm good to go. Now to google why everything recognizes my Ram as PC3-10600, even memtest... Thanks again, A Guy