How to OC Samsung with ASRock on z87 OCF

[Splave]

How to OC Samsung with ASRock z87 OCF

If you have benched haswell for a while you notice that its a very quirky platform.
Here are some tips to get your Samsung 32m and overall memory performance boosted up a bit.


Ever get that feeling that when you go from 2666 to 2800 adding 134mhz to your clocks should benefit you more than it does?
Blame your RTL's :P


First off lets go into the memory configuration page and at the bottom disable MRC fast boot so that memory will train on each boot.


Then go ahead and apply 2666 profile for samsung in the memory config page as well as setting 2666 memory divider.
Resist the urge to tighten the settings "You know" will be faster for now.


Instead apply the settings and save and exit to allow it to train at 2666.

Go back into bios and check out where your RTL and IO-L are at. They should be approx 42/43 4/4.

Okay so now lets go back into bios and set 2800 and see where they lay. Should be around 47/43 9/4



Okay so now lets explore the memory training threshold setting. This will allow you to pull in your RTL tighter as well as gain some
stability. I was also able to train at lower voltage when settings where correct.


Auto should be 11 by default. so first try 13 and check your rtls again, and if that works try 15.
15 should give you the same rtl by auto as 2666 divider.



You will notice you are getting much faster 32m with rtl nice and tight.

Once you find a happy setting, lock it in by setting it manually before you change second and tertiary timings because setting these before hand may cause your rtl to auto looser.
For me it was 42/43 4/4. You will look like a 32m god even with some loose subtimings!!


Another thing to touch on is the common practice of training at lower divider then bumping up it up without retraining. IE 2666->2800 you will notice the system does not shut down
completely and retrain. In this case RTL will look tighter but performance will be poor as you can see below..This should be around 7m24.750....


Lets hear some questions

[Alex-Ro]

nice info lol @avatar

[donkel]

Hi,
Super Guide !
Can You give me a tipp for 3000mhz, what for voltages i need, have 2666 mhz cdp Ram,
mean Agent and io voltages

[Alex-Ro]

First of all make sure that your ram can do it Usually boards have the auto-rules for voltages regarding memory pretty good set,however if you feel like something is not right(e.g random 55 code or various shutdowns when system is running) you can test manual voltages.Usually +0.400 for vccsa,and +300/350 for io a/d should max out IMC on air/water,however every IMC is different

[cadaveca]

Thanks Splave, great tips.

[Dumo]

Good info, thanks Splave

Found out that mfr ss with base settings 3000~3100 CL11 optimized @ 51/51/10/8

[chispy]

Well done Allen , great guide , thank you.

Kind Regards: Angelo.

[kikicoco1334]

rock out mr.spalve!

[XBrytanX]

No one who achieves success does so without acknowledging the help of others. The wise and confident acknowledge this help with gratitude.

Thanks buddy

[Splave]

appreciated mate

[thebanik]

This thread is getting quite high views but sadly not many replies, . Thanks a lot Allen for such a wonderful guide. But why is it not on OCA??

[The|Hunter]

Hi, thanks for this interesting info,


Well I experienced the same thing.. My Crucial Balistix Elite 2133mhz CL9 4x4gb can do 2400mhz CL10 and 2666mhz CL11, but yeah in both cases it auto raises tRTL & tIOL waaay to much..


2133MHz



2400MHz CL10



2666MHz CL11

Auto should be 11 by default. so first try 13 and check your rtls again, and if that works try 15.
15 should give you the same rtl by auto as 2666 divider.

Now I tried manual 2400mhz tRTL 41/42, 42/43, 43/44 and tIOL 4/4, 5/4, 6/5 but it just wont boot. Which is this value at 11? I can't seem to find in Asus uefi (z87-deluxe)

[The|Hunter]

Ok, here its DRAM Clk Period that makes a big difference

Im at 9 atm and at 9 it looks like its default 2133mhz (few major adv. timings), 1-2 are even tighter

2400mhz CL10-12-11-32-2T



I think I will need to fine tune some more, 2 times it auto shut down (I used 7), 1 time it froze in x264 benchmark (at 8 and little looser timing), now Im at 9.