Rauf Posted September 16, 2016 Share Posted September 16, 2016 Raufâ€™s guide to memory overclocking on ASUS ROG Rampage V Edition 10 Version: 2016-09-16 Hereâ€™s the guide in pdf format: Link Introduction In the early days of Haswell-E, memory OC could be a real pain in the ass. But fear no more, with improved boards, bioses and ICs, memory OC is now easy. Memory overclocks higher and tighter and is much more fun and rewarding. I will be using the ASUS ROG Rampage V Edition 10 paired with 2x8GB G.Skill B-die retail memory matched with 2x8GB Galax wazza memory (yes you can mix brands just fine). The CPU of choice (my only X99 CPU) will be a 6950X. One of the best parts of BW-E memory overclock is that since you cannot reach anywhere near the frequencies of Skylake, you donâ€™t need to bin memory that hard. Most B-die sticks will do, even your Skylake rejects should be fine. Software In this guide I will mostly be using Geekbench v3 for testing memory performance. The reason is that I rather like the benchmark because itâ€™s fast, consistent and it scales very well with memory speed and timings. Also, the subtest Dijkstra is pretty hard on memory, so if it can pass that it will easily be able to do all other relevant benchmarks as well. Bear in mind that your memory score in Geekbench scales with CPU speed, so keep your CPU and cache close to your baseline speeds when you test. I used 4000 MHz core and 3500 MHz cache. I have also noticed that while your memory score might increase, you can actually get worse overall score when pushing mem OC. This is likely due to Dijkstra being the hardest subtest to pass and if it barely passes you can get a low score here which affects your overall score. Dijkstra wonâ€™t affect your mem score since is not actually a mem subtest. I wouldnâ€™t look too much on the overall score when testing mem OC, so concentrate solely on memory score. You will have more headroom for memory OC when youâ€™ve got your CPU on LN2 anyway. And all other benchmarks will be fine at that speed also. OS used for tests was Win 7 SP1 x64. Apart from Geekbench, I will also be using the ASUS MemTweakIt tool. It is a great little tool that gets too little attention. It has two uses, first is to check your timings, second is to actually adjust timings in OS. Most timings work surprisingly well when adjusting in OS so this tool will save you a lot of time. You can even adjust your main timings, and even CL, but keep in mind that your RTLs and IOLs wonâ€™t change with it so it will not be â€œtrueâ€ CL 10 for example. However there is still a gain going from CL 11 to CL 10 in OS. Remember to click "Apply" when changing timings as "OK" actually doesnâ€™t save your changes and just closes the window. I also did a few test with XTU and SPI 32M just to check consistency. The XTU tests surprised me a bit, but more on that later. What to aim for? You will max out on frequency pretty fast compared to Skylake, due to IMC or platform limit. Max frequency will be somewhere around 1700-1800 MHz. So what you need to do is tighten the timings, A LOT! Donâ€™t be afraid to enter numbers you wouldnâ€™t even dream of on Skylake, as you will see here you can bench at some pretty amazing timings. The memory I used in these tests are all capable of 2000+ 12-11-11 with wazza on Skylake, so they are really good. Still, I havenâ€™t been able to get higher frequency than some reached at the world tour event at Computex with random Zadak memory. What Iâ€™m getting at is that once you reach your limit, it is not likely to be your memory. If youâ€™re not happy with your mem OC, start binning your 6950Xs for IMC Basic settings As your memory most likely wonâ€™t be the limiting factor you donâ€™t need to worry about which order you put your sticks in. Just plug them in and start benching. Set 1.8 or so Vdimm, leave everything else auto. I have not found that raising SA or IO helps at all. Disable the usual SVID etc. Set max current capabilities etc (donâ€™t really know if it helps but it doesnâ€™t hurt at least). Use 125 strap, it is the most efficient one. And of course, donâ€™t forget maxmem! Weâ€™re using Bdies here! Timings See the picture below for a good set of timings. Here they are in dial-in form for your convenience These are the best timings I have been able to find, I donâ€™t share the decent ones and keep the really good ones for myself. But try it yourself, you might find even better ones. Note that I could actually pass Geekbench with tWR 4 and tRTP 2 sometimes, but anything below 8/4 on those would not be stable enough to pass Geekbench consistently. I didnâ€™t touch the thirds too much, basically they werenâ€™t really possible to tighten down that much from auto, and they did little for performance. However, what you actually need to focus on are your RTLs, as you will see they will make the biggest difference. Best for me was 51-51-51-51. 51-49-51-49 is much worse at same speed. Unfortunately I wasnâ€™t able to successfully set any RTLs/IOLs manually, not even a full dial in with the same values as auto gives. So you need to try to boot at different speeds and figure out how to get your best RTLs with your best mem frequency. For me I needed to boot at the 3500 mem strap and then reduce blck in OS or set blck lower than 125 in bios. Maxing out You will be maxing out frequency, timings and actually most importantly RTLs. So you will need to test your best combination. I started out by setting 3333 MHz frequency and then went as tight as I could on timings. After that I started to increase frequency until I could go no further. Note that you will run into a wall of around 130 bclk, maybe due to DMI/PEG freq I donâ€™t know really. But if you need to go higher you have to set a higher mem multiplier. Next one is 3500 MHz, which might be pushing it for your setup, at least for Geekbench. My setup maxed out at 1745 MHz C11-11-11, so I needed to downclock in OS or set lower bclk in bios. Do note that Geekbench will complain about internal timer error if you do too much bclk adjustments in OS, even if you use Win 7. You can do ~1.5 MHz adjustments before Geekbench will give you an error and refuse to present a score. Keep an eye on your RTLs as they will go from 51-49-51-49 at 3333 MHZ to 51-51-49-51 at some point when you boot at higher frequency. When you boot at around 1720 MHz you will get 51-51-51-51, which was best for me. Of course this might vary a little from setup to setup and maybe benchmark to benchmark. Loosening timings shouldnâ€™t get you much frequency wise but you can always try and see what performs best if it scales with looser timings. But in general I would in fact recommend the opposite, to find your max speed at C11-11-11, and then try C11-10-10 as you most likely will be able to do that if C11-11-11 works. If you canâ€™t boot it, set it in windows, it will work fine with MemTweakIt. You can also change to C10-10-10 and see if you can do that, it is not impossible, but will be hard when you are close to your frequency limit. This will only work from within OS though as setting it in bios will get you too tight on RTLs. Results Now to the fun part, results: Baseline score, 1667 MHz C11-11-11-20 220 1T, auto subtimings: "Skylake subs", 1667 MHz C11-11-11-20 220 1T: About 275 points increase in memory score. Optimal subs, 1667 MHz C11-11-11-20 180 1T: 350+ points increase in memory score from baseline. Overall score has increased by almost 600 points. Max mem frequency of 1745 MHz: Almost 500 points increase in memory score from baseline. Overall score is ~900 points above baseline, and this is with slightly lower CPU speed. This was the highest frequency I could run Geekbench at. Note that Geekbench is quite hard on memory, in other benchmarks such as XTU and 3DMark physics you can push your memory a fair bit higher. 1711 MHz, RTL 51-49-51-49: For testing impact of RTLs. Next two screens shows the same mem frequency, same subs, the only difference is in the RTLs. 1711 MHz, RTL 51-51-51-51: +100 points from RTL only 1625 MHz C10-10-10-20 180 1T, RTL 49-47-49-47: Lower score, just for reference Why no XTU? You may wonder why there havenâ€™t been any XTU tests, they are after all kind of standard when focusing on memory performance. Well, hereâ€™s why: 1667 MHz C11-11-11-20 220 1T, auto subtimings: 1750 MHz C11-11-11-20 180 1T, optimal subtimings: 1750 MHz C10-10-10-20 180 1T, optimal subtimings (not "true" C10, changed in windows so RTL isnâ€™t correct for C10): Just some other XTU-tests for "fun" 1625 MHz C10-10-10-20 180 1T ("true" RTL): 1625 MHz C9-9-9-20 180 1T (not "true" RTL): Conclusion, XTU is bunnyextraction benchmark Note that one of the tests was run with both higher frequency and tighter timings (C10-10-10) than what I could do in Geekbench. I actually havenâ€™t tested max frequency in XTU because of the non-existent scaling. SPI 32M Because XTU was soâ€¦should I say, consistentâ€¦ I ran some 32M to verify that Geekbench wasnâ€™t just playing me tricks on memory performance. 1667 MHz C11-11-11-20 180 1T, optimal subtimings: 1750 MHz C11-11-11-20 180 1T, optimal subtimings: Thatâ€™s all folks, thanks for reading! Written by: Tobias "Rauf" BergstrÃ¶m Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.