AGESA 1.0.0.6a

Windows98 wrote: I thought it was pretty clear, but I'll lay out the scenarios: My sticks are rated @ 3000 with 15-15-15-35 timings.  1. Resetting BIOS to defaults sets my memory at 15-15-15-35 @ 2133. (which is fine) 2. Loading XMP defaults properly loads the timings (15-15-15-35 @ 3000), but BIOS seems to ignore the CL of 15 and sets it to 16. No matter how much changing I do, it always reverts back to 16.  In scenario 2 my machine randomly BSOD's once a week or so. I feel this is related to the CAS timings, of which I can't change for some damn reason.  If I back the speed off to 2666 with the same "bad" timings, it also appears stable.  So in other words, I can't tighten my timings to their appropriate values because the BIOS is being stupid.

I'm assuming you have Geardown mode control on the Gaming K4? If so, try setting it to disabled and then see if it allows the uneven values @ 3000.

I'm not sure if this will work or not, I know the Geardown setting will override the Command Rate and for some reason I think it also overrides the CAS value, but I could be misremembering.

Uneven CAS values like 13 or 15 are not supported by AMDs AGESA code for (correct if if im wrong) 2666mhz and higher. So this is a limitation that applies to all AM4 boards.
What you can do is either run with CAS 16, or try CAS 14 with GearDown enabled for example, if it works you might also want to try with GearDown disabled.
I dont know if AMD has plans to allow uneven CAS in the future, but at the moment there is nothing you can do about it.

As i said before, it is not possible to use uneven CAS values.

GearDown only helps stability by internally increasing some timings, it does not set 16 to 15 or sth. like that.

I assembled my new system few days ago and first of all updated BIOS to AGESA 1.0.0.6а Then of course I started to overclock my CPU and RAM. Finally I got 3800MHz at 1,275v on a CPU and 2800MHz on RAM with XPM profile and manual adjustment of timings to 14-14-14-28. My RAM is m-die and I managed to overclock it to 2933MHz max at stock timings (16-18-18-38) with an XMP profile. However it was not stable at passing POST - when I set just 2933 I got triple turn off and return to default 2133, but when I overclocked step by step from 2400 to 2933, it finally passed the POST after one turn off sequence. Didn't try to increase timings to get it boot at 3200, but saw one review where guy with same m-die chips managed to get stable work with timings 20-22 something. I hope Asrock will push the compatibility with RAM even further to get 3200+ with m-die chips

Edited by Maddreg - 09 Aug 2017 at 2:38pm

BoneCrusherXes wrote: Uneven CAS values like 13 or 15 are not supported by AMDs AGESA code for (correct if if im wrong) 2666mhz and higher. So this is a limitation that applies to all AM4 boards. What you can do is either run with CAS 16, or try CAS 14 with GearDown enabled for example, if it works you might also want to try with GearDown disabled.