Will ASRock EVER fix this???

all settings i suggested are not in HEX my bios dosnt need to convert to hex thankfully, unless im setting p states

datonyb wrote: ok good ram so try this first (your issue is as said an unstable overclock on ram ) settings : 14/14/14/14/28/44    trfc 256 geardown disable/cr1t/bgs disable/bgs alt enable/ proc odt 53 ohms/dram powerdown disable/am4 advanced boot training set to auto/boot try set to 5 its often the untouched minor settings on the am4 that causes issues although your primary tRAS is ambitious hence why i advise 28 and not 24 in your case it having problem initilaising the ram when everything is cold , hence the windows testing being fine, ive been there and got the tee shirt my friend,alter the minor settings and then tweak the primary ones a bit lower i test in reverse to normal methods on am4.............. eg i try settings test to windows run a cinebench AND THEN TURN THE DAM THING OFF FOR 5-10 MINS and see if its going to cold boot before wasting time on windows based testing and this very weekend im back in 'play mode' due to having a very nice deal this week on 4x8gb kit of tridentz 3866, so i'll be doing just this same thing

OK guys ...

I took some time last night and tried all the stuff you said.
Short version: didn't work

Everything was very promising, I felt like "that's gona be it, now it will work" but then. But ok, here's what I did.

First I checked my settings and my trc was already higher than your suggestd value. But I set the values you gave me just to be sure. When I came to trfc I was confused, my board offers 3 different trfc settings (trfc, trfc2 and trfc4) so I assumed you where talking about the first one. But then again confusion, my board need the values set in HEX (which is ridiculous btw.) but converting 256 to HEX gives me 100 but the auto value was 138, so I thought lowering the value would be even worse!? However, I tried all the settings you told me and again, Windows and everything was OK. But after turning of and wait for the caps to run empty it won't boot again. Same issue.

I took another round of research on the web and found a tool from overclockers.com (ryzen ram calculator) and gave it a shot. I took the "save values" to calculate upon my XMP settings and it sounded plausible. I had to convert all the values in HEX and it was confusing.

For the basic timings (14/14/14/14) you have values in the bios you can chose, of course in HEX, it should be 14 on each, so 14 > HEX = E ok but in the settings I have 0Eh (ok that's 14 ...) but in the next one there's 0xE (no E or 0Eh) but that's also 14 but why?! WHY can't they just give us a damn DECIMAL input!?

So assuming that I didn't mess up any of these dec to hex coversions I set ALL the DRAM settings according to the results of the calculator and gave it a try. Again everything ran fine, I played like an hour AC Origins which was running nice on medium 900p btw. and then simulated a cold boot again and ... no post. 5 retries, back to 2133 MHz.

This can't just be unstable OC, there's no way. Maybe you can call it that if the system can't boot but if it's otherwise stable why should I call these instable settings...

btw. I also set command rate and all the stuff you told me and I had my VDIMM at 1.4 V all the time.

I think there's a problem or bug in the uefi that causes this. Or can I do any other test to see if the settings are stable under normal conditions, which is where it counts, not in the 5 seconds where the uefi boots up... dang it

@ night stalker

i too use the ryzen ram calculator its been a blessing to me

but ive also learnt to enter every single suggestion and setting
even these cad bus block etc cldo voltages everything

it may well be a bios issue not having enough brains to iron out the flaws and issues as it has to make/try some settings itself based on what your xmp asks for or you manually enter

not trying to rub salt in the wound but i got 3433 cl14 first try with the new tridentz 3866 ram this weekend on mine ,

i had several issues aswell,

Thenightstalker wrote: [URL=][/URL]OK guys ... I posted and tested alot here, I was trying to help finding new and testing old bugs and I thnink I also posted my specs but if not I'm sorry! I tested to keep my PC plugged to the wall but unfortunately it didn't help. It feels like there's capacitor that runs down and causing the issue on reboot. Why? Because when I turn of and on within a short time it's OK but if the system is of over night for example it would not boot. The System runs FLAWLESS with all the Settings I ever tired, I ran Memtest tu ensure my RAM settigns are stable. I played AC Origins for hours and also ran 3D Mark with this settings without any Problem. I know how an instable system behaves, especially with bad RAM but this doesn't look anything like that. Which doesn't mean it couldn't be a problem with the RAM settings, maybe an option/seting that causes this problem but I am not aware of... I'm new to this CBS stuf and the way these OC Settings work is really wired and not intuitive to me so probably there's a eror I just missed all the time. Here's my full spec: Board: Fatal1ty AB350 Gaming-ITX/ac CPU: Ryzen 5 2400G RAM: G-Skill 4000 C19 16GB Kit (Samsung B Die) Drive 0: Samsung 960 EVO 500 GB nVME SSD (M2) Drive 1 Samsung 840 128 GB SATA SSD Case: Silverstone Raven RVZ03 (LED and 2 Fans connected) Cooler: Noctua <span ="st">NH-L9x65 AM4 Display is curently my 47" Philips LCD TV over HDMI. OS: Windows 10 Professional (latest build, all Updates) Drivers are used from Windows except Chipset and GPU, those I downloaded from AMD and installed in the correct order (first Chipset then GPU). So far everything works fine except the throttling issue in games, so I runed of the Turbo in CBS. Here's my UEFI Settigns: First, I did a cmos clear by Jumper (have no button). I changed the configuration to CBS and set the DDR Voltage to 1.4 V In CBS I set GFX mode to forced and specified Framebuffer > 2G In the DDR settings I set Command Rate ot 2T I set Frequency to 1600 Mhz Timings: Top down - 14/14/14/14/24/48 everything else on AUTO This was tested as I said above and it worked. I also tried setting these over AMD Ryen Master and it also worked. I aldo don't understand why ASRock doesn't support to enter these values as simple decimal numbers instead of HEX which can also cause errors ...?! However, now you should have all the informations, maybe there's a solution??? </span>

You're Problem May not be memory related at all. Are you running the latest firmware for that Samsung NVME Drive? Research Samsung NVME boot issues.