December 26, 20178 yr For several weeks now, I have been struggling to diagnose my seemingly random Unraid freezes. The crashes tend to occur after around 24 hours of uptime. I have seen the crashes on 6.3.5, and several of the 6.4 releases as they have come out. Sitting here now on rc17b with no relief, I am finally coming to the forums. I recently wiped and reinstalled Unraid and rebuilt everything just to experience the same problems. Hardware: MSI - X370 SLI PLUS (MS - 7A33) Ryzen 7 1700x 16 GB RAM 3x3TB Drives in Array 1x6TB Parity 1x250GB SSD Cache I am completely new to the forums, so if I have posted in the wrong place or have given incomplete information please let me know. tower-diagnostics-20171225-1936.zip FCPsyslog_tail.txt
December 26, 20178 yr Welcome to the forums! Not sure if you have read the forum thread below, but most Ryzen issues have been related to C-State. If disabled within the BIOS, the system remains stable. Some have been fine running with the latest BIOS updates with C-State enabled; however, I have had to keep it disabled to remain stable. Only other instability issues I've read about have been due to memory... make sure it's on your motherboards approved list. https://forums.lime-technology.com/topic/55150-anybody-planning-a-ryzen-build/ Edited December 26, 20178 yr by luisv
December 26, 20178 yr Author Lusiv, I actually haven't come across that specifically. I'll go disable that in the BIOS now and see if that gets me to stable. Thank you very much for the tip. Merry Christmas!
December 26, 20178 yr Same to you, Merry Christmas! Hopefully that resolves your freezing issue. Until I came across that thread and traded a bunch of PMs with a fellow Ryzen owner, my system acted like yours. Once disabled, I've managed to remain stable. Keep us posted.
December 28, 20178 yr Author As an update to this thread until further notice: I found a setting in my motherboard that allowed me to disable the "C6 Sleep State" (I'm pretty sure that was the text of the option). Now I'm sitting at two stable days of uptime. It seems to be the fix, but I'll update if I find the case to be something else.
Archived
This topic is now archived and is closed to further replies.