ram causing strange boot behaviour with ryzen

[kalnick]

I picked up an Asrock X370 Killer SLI during the cyber monday sales. It was a good deal with rebates $110 off regular price.

I upgraded to the x370 from an Asus Prime B350 Plus. I wanted to play more with overclocking my 1600.

I have a 16gb kit of Corsair Vengeance LPX CMK16GX4M2B3000C15 it worked just fine at 2933mhz in the Prime B350 but in the X370 when I set xmp to 2933 the system reboots there are 3 short beeps then it power down for a couple seconds then powers back up, it does this 2 more times then posts and boots into windows. Hwinfo reports 2933mhz, the bios reports and the system works. If the system is shut down for any length of time or there is a windows 10 update it goes through the whole process all over again. That a long post process to go through

 

If I set the ram to 2666mhz I get no issues with reboots.

Doesn't matter if the cpu is overclocked or set at stock it still happens.

I'm assuming its a matter of finding the right timing settings but I really have no idea where to start hoping someone out there has had the same issue with this board and ram and can guide me to a solution.

 

On another note this is the 3rd AM4 board I have worked with so far the other being the Asus ROG B350-F and the entry level or "cheaper" Prime B350=Plus appears to have the best memory compatibility so far that I have seen.

 

I am running the latest bios P3.40

I have tried the ram installed in slots A1&B1, but the manual says to use A2&B2 so that is how they are setup currently.

The QVL for this board is very short, and old. This is my first Asrock board 

[FuzzyLogic]

Is the BIOS updated to the latest version?

[kalnick]

Just now, thegreengamers said:

Is the BIOS updated to the latest version?

Yes that was the first thing I did after setting up the board. I'm running P3.40

I should have mentioned that sorry

 

I thinking of maybe trying to go back one version.

[ImNotThere]

try looser timings, like 17-17-17-35, might help get the speed back, otherwise consult the qvl list for your motherboard

[johndms]

41 minutes ago, kalnick said:

when I set xmp to 2933 the system reboots there are 3 short beeps then it power down for a couple seconds then powers back up, it does this 2 more times then posts and boots into windows.

This seems to be normal for ASRock and some other boards. Mine does it as well. It's a "feature" and I'm not entirely sure of the purpose.  The number of these power cycles corresponds to "Fail Count" in DRAM Timing Configuration. It helps when setting aggressive memory overclocks to raise this from 3 (my default) to 5 or higher, but I think if your system is booting properly, you can disable AM4 Advance Boot Training to stop the power cycles completely. Just remember to turn it back on if you ever adjust your memory settings, or perhaps if the "cold boot bug" wipes your overclocks.

 

You can also try increasing DRAM Voltage to 1.36 or 1.37 to see if it stops the power cycling or cold boot issues. You can safely go as high as 1.40v on DRAM Voltage. Also, ensure VDDCR_SOC Voltage is at least 1.1v. Anywhere between 1.1 and 1.2(max) is useful for ram overclocks. Overclocks being anything above 2666MHz, I believe.

 

I'd also recommend saving any working settings to a user profile. Much easier to load a user profile if your overclocks get wiped. Note, the profiles may be erased when updating bios or if you remove the cmos battery. I back my profiles up to usb drive.

[kalnick]

2 hours ago, ImNotThere said:

try looser timings, like 17-17-17-35, might help get the speed back, otherwise consult the qvl list for your motherboard

those appear to be the default timings.

 

[kalnick]

ok so I set voltage to 1.37 and timings to 16-17-17-35 and it booted up on the first try. going to run some Prime 95 and see how stable.

 

I have the 1600 set to 3.9ghz at 1.327v and that seems to be rock solid.

[johndms]

10 minutes ago, kalnick said:

ok so I set voltage to 1.37 and timings to 16-17-17-35 and it booted up on the first try. going to run some Prime 95 and see how stable.

 

I have the 1600 set to 3.9ghz at 1.327v and that seems to be rock solid.

While Prime95 is nice, it's a bit more aggressive and doesn't really allow for much tweaking and monitoring of what's happening. Personally, I use Aida64's System Stability Test to verify CPU overclocks stressing CPU/FPU/Cache while keeping an eye on HWMonitor's Package Temperature. If you can do 3.9 at that voltage for at least an hour or two without Aida64 giving a red, failure screen, then I'd say you're fine. I let Aida64 run overnight (6+ hours) to make sure.

 

You can add Memory to the test after you verify the CPU is stable. I find it kinda pointless to stress everything at once. If something fails, you have no idea what caused it.

[kalnick]

53 minutes ago, johndms said:

While Prime95 is nice, it's a bit more aggressive and doesn't really allow for much tweaking and monitoring of what's happening. Personally, I use Aida64's System Stability Test to verify CPU overclocks stressing CPU/FPU/Cache while keeping an eye on HWMonitor's Package Temperature. If you can do 3.9 at that voltage for at least an hour or two without Aida64 giving a red, failure screen, then I'd say you're fine. I let Aida64 run overnight (6+ hours) to make sure.

 

You can add Memory to the test after you verify the CPU is stable. I find it kinda pointless to stress everything at once. If something fails, you have no idea what caused it.

Ya I left the ram at 2133 when I was doing the cpu and never had any issues with the reboot. system crashed though and rebooted again only failed 2 times. I did set the fail count to 5.

 

When it fails is it just trying to find the right config to work on its own?

[johndms]

2 hours ago, kalnick said:

When it fails is it just trying to find the right config to work on its own?

My assumption has always been something along those lines. I think the board is just trying to find working secondary and tertiary memory timings capable of posting, the ones usually left on Auto. But I've tried filling in as many as possible and it still power cycles. My memory kit is rated at 3000 (2933). I've noticed with the latest bios updates, it only does those power cycles when I attempt to overclock to 3200. If I leave it at 2933, it only rarely happens.

[ImNotThere]

16 hours ago, kalnick said:

those appear to be the default timings.

 

i dont mean to tell you what is and isnt your rams timings but the item you have stated has timings of 15-17-17-35

i believe i made a mistake perhaps 17-17-17-36

ignore if you have it booted to 2933mhz with the 16-17-17-35 timings

[kalnick]

14 hours ago, ImNotThere said:

i dont mean to tell you what is and isnt your rams timings but the item you have stated has timings of 15-17-17-35

i believe i made a mistake perhaps 17-17-17-36

ignore if you have it booted to 2933mhz with the 16-17-17-35 timings

16-17-17-35 appeared to be what the bios had set under auto. but it didn't remain stable. 2666mhz seems to be best I can do with this ram. Even when ity appears to be stable it still fails to post on cold starts and the occasional restart. I have a set of team group 3000mhz ram I'll try at some point. For now I'm just living with 2666

[ImNotThere]

5 hours ago, kalnick said:

16-17-17-35 appeared to be what the bios had set under auto. but it didn't remain stable. 2666mhz seems to be best I can do with this ram. Even when ity appears to be stable it still fails to post on cold starts and the occasional restart. I have a set of team group 3000mhz ram I'll try at some point. For now I'm just living with 2666

the performance difference between 2133 and 2666 is large, the difference between 2666 and 3000 is negligible, talking from experience here

[kalnick]

13 hours ago, ImNotThere said:

the performance difference between 2133 and 2666 is large, the difference between 2666 and 3000 is negligible, talking from experience here

ya I've noticed that, It working well enough at 2666

[Santo22]

I have the Crosshair VI Hero and it does the same exact thing only on cold boot. It does 3 cycles before posting. I've gotten used to it at this point and am hoping maybe in the next bios revision it will be fixed. I prefer to keep the ram at 3000mhz so I'm just living with it. It's basically the board reading and learning timing from what I've seen. Many people are having the issue and I think especially with the x370 boards.