Ryzen system won't post occasionally.

[CasualGamer...]

I have a system with a 1600 at 3.6ghz at stock vcore, 16gb vengeance 3200mhz, and an Asrock AB350m pro4 motherboard.  Most of the time the systems boots up just fine, but today it would not post correctly. Basically it tried to post but it failed, turned off, turned on again, same thing. It did this a few times and finally booted. Is there any way to stop this from happening? I am using the latest bios, and my ram is running at 2933mhz, and I haven't touched the timings. I believe that the problem may be the memory, but I don't know how to correctly set up ram timings. 

[Guest]

May be memory. I had the same issue earlier when I tried to push my 2666 kit past 2666. Have you tried raising the voltage?

[TheSneakinSpider]

if you have it just try different memory

[CasualGamer...]

3 hours ago, Abyss Gaming said:

May be memory. I had the same issue earlier when I tried to push my 2666 kit past 2666. Have you tried raising the voltage?

What's the limit for memory, 1.35v? 

[Guest]

Just now, CasualGamer... said:

What's the limit for memory, 1.35v? 

You could push to 1.4, but try 1.35 first

[johndms]

I have the same board and processor, just a different kit of ram.  My Setup  I've noticed the first time I dial in a new memory overclock, or change the voltage..when I save changes and reboot, sometimes it'll power off a few times.  I'm not entirely sure, but I think this is an intentional method of the UEFI attempting to "train" the memory to run at the new settings.  If they work, it'll boot as expected, but if something's incorrect, for whatever reason.. it'll try 3 times before it gives up and loads defaults.  I even think there's a setting in the uefi ddr4 timings page called 'Fail Attempts' or something similar.  I've left mine at default 3.

 

Like you, my system seems to work just fine and randomly upon reboot it cycles off 3 times and resets the ram to 2133.  I'm using bios 2.60.  I knew when I purchased my Ryzen setup last month that I'd probably have stupid little issues like this, but I fully expect these things to be ironed out with each future bios update.  For now, I just save my current profile and load it if things reset.

 

My R5 1600 is at 3.8GHz, 1.35625v (crashes at 1.350).  My 3000MHz ram kit has no issues at XMP values, 2933 at 1.35v.  I've seen numerous people claim CPU overclocks at stock voltage, but I doubt they seriously stress test to ensure stability.  I've had overclocks appear to run fine with Cinebench and RealBench, only to fail after 45 minutes of Aida64.  My recommendation, overclock JUST the CPU to 3.6 at 1.35v and leave the ram at 2133, auto timings.  Stress test the hell out of the processor to ensure stability.  Once you're satisfied, then move to clocking your ram properly.  Your issue may be as simple as too little voltage on the CPU.

[CasualGamer...]

3 hours ago, johndms said:

I have the same board and processor, just a different kit of ram.  My Setup  I've noticed the first time I dial in a new memory overclock, or change the voltage..when I save changes and reboot, sometimes it'll power off a few times.  I'm not entirely sure, but I think this is an intentional method of the UEFI attempting to "train" the memory to run at the new settings.  If they work, it'll boot as expected, but if something's incorrect, for whatever reason.. it'll try 3 times before it gives up and loads defaults.  I even think there's a setting in the uefi ddr4 timings page called 'Fail Attempts' or something similar.  I've left mine at default 3.

 

Like you, my system seems to work just fine and randomly upon reboot it cycles off 3 times and resets the ram to 2133.  I'm using bios 2.60.  I knew when I purchased my Ryzen setup last month that I'd probably have stupid little issues like this, but I fully expect these things to be ironed out with each future bios update.  For now, I just save my current profile and load it if things reset.

 

My R5 1600 is at 3.8GHz, 1.35625v (crashes at 1.350).  My 3000MHz ram kit has no issues at XMP values, 2933 at 1.35v.  I've seen numerous people claim CPU overclocks at stock voltage, but I doubt they seriously stress test to ensure stability.  I've had overclocks appear to run fine with Cinebench and RealBench, only to fail after 45 minutes of Aida64.  My recommendation, overclock JUST the CPU to 3.6 at 1.35v and leave the ram at 2133, auto timings.  Stress test the hell out of the processor to ensure stability.  Once you're satisfied, then move to clocking your ram properly.  Your issue may be as simple as too little voltage on the CPU.

Ok, good to know. My memory is at 2933 even after the power off cycle, strange. My cpu passed 30 minutes of Aida64 at 3.6ghz at stock voltage, so I am pretty sure that the cpu isn't the problem, but I may increase the vcore as temps are not bad at all.

[johndms]

4 minutes ago, CasualGamer... said:

Ok, good to know. My memory is at 2933 even after the power off cycle, strange. My cpu passed 30 minutes of Aida64 at 3.6ghz at stock voltage, so I am pretty sure that the cpu isn't the problem, but I may increase the vcore as temps are not bad at all.

Yeah, I've had my Ryzen 5 1600 at 3.9 at 1.4125v, but I wouldn't try that on a stock cooler.  Not sure what cooler you have.  My CPU seemed mostly stable at 3.9, but I'm not comfortable with voltage over 1.4.  As I mentioned, I've ran Aida64 for 45+ minutes at times before it failed.  I've also ran it for 6.5 hours with no issues, then had a blue screen the following morning while playing Overwatch.  It's frustrating.  I think it may just be a matter of waiting for improved bios versions and memory support.  I'm back to my most stable clock now.. 3.8 at 1.35625v, XMP profile 2933 at 1.35v.

[CasualGamer...]

3 hours ago, johndms said:

Yeah, I've had my Ryzen 5 1600 at 3.9 at 1.4125v, but I wouldn't try that on a stock cooler.  Not sure what cooler you have.  My CPU seemed mostly stable at 3.9, but I'm not comfortable with voltage over 1.4.  As I mentioned, I've ran Aida64 for 45+ minutes at times before it failed.  I've also ran it for 6.5 hours with no issues, then had a blue screen the following morning while playing Overwatch.  It's frustrating.  I think it may just be a matter of waiting for improved bios versions and memory support.  I'm back to my most stable clock now.. 3.8 at 1.35625v, XMP profile 2933 at 1.35v.

I am using a cryorig h7, I got it mostly because the stock cooler is too loud for me when trying to overclock. I might just keep my ram at 2133 for now, and wait for bios updates, as I just set my ram to 2133 and my system posted noticeably faster than 2933. Also, you said you are using bios 2.6? On asrock's website the latest is 2.5, maybe I am mistaken?

[scottyseng]

1 hour ago, CasualGamer... said:

I have a system with a 1600 at 3.6ghz at stock vcore, 16gb vengeance 3200mhz, and an Asrock AB350m pro4 motherboard.  Most of the time the systems boots up just fine, but today it would not post correctly. Basically it tried to post but it failed, turned off, turned on again, same thing. It did this a few times and finally booted. Is there any way to stop this from happening? I am using the latest bios, and my ram is running at 2933mhz, and I haven't touched the timings. I believe that the problem may be the memory, but I don't know how to correctly set up ram timings. 

The BIOS is up to date right? If not, go update it, it may help.

 

Ryzen is pretty touchy with RAM.

[CasualGamer...]

3 hours ago, scottyseng said:

The BIOS is up to date right? If not, go update it, it may help.

 

Ryzen is pretty touchy with RAM.

I am using the latest bios, at this point I think the only solution is just waiting for new bios updates. I just set my ram to 2133 and plan on keeping it there for a while, I would rather everything be stable.

[scottyseng]

Just now, CasualGamer... said:

I am using the latest bios, at this point I think the only solution is just waiting for new bios updates. I just set my ram to 2133 and plan on keeping it there for a while, I would rather everything be stable.

That seems like a good idea. I hope future BIOS updates patches it for you .Ryzen's speed is really tied to how fast the RAM is for it.

[CasualGamer...]

3 hours ago, scottyseng said:

That seems like a good idea. I hope future BIOS updates patches it for you .Ryzen's speed is really tied to how fast the RAM is for it.

Well, I game at 75hz, so I think the performance difference would be very small between 2933 and 2133, am I mistaken?

[johndms]

19 minutes ago, CasualGamer... said:

id you are using bios 2.6? On asrock's website the latest is 2.5, maybe I am mistaken?

It seems you have the Micro-ATX version of my ATX board.  The names are identical, I just missed the 'm' in yours.

 

http://www.asrock.com/mb/AMD/AB350 Pro4/#BIOS - Seems 2.50 is the latest for yours, though.

[scottyseng]

Just now, CasualGamer... said:

Well, I game at 75hz, so I think the performance difference would be very small between 2933 and 2133, am I mistaken?

Ah, at 75Hz, I don't think you'd see much of a difference. But for rendering, you would / high fps gaming.

[CasualGamer...]

btw I am using bios 2.50.

[CasualGamer...]

(deleted)

Edited July 10, 2017 by CasualGamer...
Forgot to quote

[CasualGamer...]

3 hours ago, scottyseng said:

Ah, at 75Hz, I don't think you'd see much of a difference. But for rendering, you would / high fps gaming.

Ok good. I don't do any rendering/editing on my system at the moment, I may in the future though.

[CasualGamer...]

3 hours ago, johndms said:

It seems you have the Micro-ATX version of my ATX board.  The names are identical, I just missed the 'm' in yours.

 

http://www.asrock.com/mb/AMD/AB350 Pro4/#BIOS - Seems 2.50 is the latest for yours, though.

Ah, thats why. Thanks for clearing that up..