[Linux] Freezes on Asrock X370 Taichi + C6 enabled

PetrolHead wrote: The XMP profile contains values determined by the manufacturer and the BIOS reads the values from the profile. Even if it needs to calculate something, every manufacturer will rather use safe values than tight values in order to not cause instabilities.

Right, but that doesn't really answer the question, how values provided by the above calculator produce more stable result, than values set by the firmware for the profile.

PetrolHead wrote: Furthermore, XMP is more accurately Intel XMP, which means that the overclocked profiles are not really specified with Ryzen in mind (with maybe the exception of the few DDR4 modules that are meant for Ryzen).

That can be the difference, but at least in my case the RAM is specifically supposed to be for Ryzen (by G.Skill), so whatever profile is provided should be supposedly good already?

PetrolHead wrote: Then there's the fact that manufacturers rarely push their hardware to the absolute limit. Think of factory overclocked GPUs; some of them still have noticeable headroom for manual overclocking.

That's as above. Supposedly that calculator can produce values that are more stable for the same frequency. My point is not to push the RAM to the limit, but to make it work stably to begin with at the frequency it was made for (3200 MHz).

ok let me clear a few points up

the pre programmed xmp is meant for intel , and am4 really dosnt do well at using these

next point the flarex designed for ryzen STILL dosnt work as well as advertised it was picked timings from a very early stage in am4 launch

next point the calculator dosnt read different generated timings depending on system if you read the instructions it tells you to scroll down and read the xmp profile ,entering these into calculator basically tells the p[rogram the quaility of the ram chips, this then works off tables to produce the ryzen tested and tweaked timings

example petrolheads tridents have highly binned samsung b dies which would have better xmp timings than my 3200 cl15 samsung b dies tridentz
so some of his suggested settings would be a click or two lower than the results given for my sticks

in particular the flarex has some timings that really struggle and get loosened up a little ,and quite a lot of timings way to loose so get tightened for better performance

i know it sounds strange that gskill cant update the flarex with better knowledge now ,but hey they just want your money,like the new flarex for threadripper.............seems it has identical timings to the ryzen flarex haha  but costs you more as its for threadripper

datonyb wrote: next point the calculator dosnt read different generated timings depending on system if you read the instructions it tells you to scroll down and read the xmp profile ,entering these into calculator basically tells the p[rogram the quaility of the ram chips, this then works off tables to produce the ryzen tested and tweaked timings

I didn't think the calc reads anything, but assumed may be Thaiphoon tool does. From what you explain, Thaiphoon step can simply be skipped, if needed values can be obtained otherwise (they should be fixed for each model).

This video: https://www.youtube.com/watch?v=6-XkaF_Rp0c uses timing input and "memory type". I suppose I need to determine that for my flare x. And then figure out how to run actual calculator.


Edited by shmerl - 22 Dec 2017 at 7:37am

I saw, thanks! Trying one suggestion from there now.

Nope, soon after writing the comment I got another freeze %)