@Pauven I would like to add my name to the list of Ryzen builders that greatly appreciates the work you put into troubleshooting the stability issue. I spent days pulling hair out, trying different motherboards, 3 sets of RAM modules, MemTest86 runs, re-seating CPU/paste/coolers, and was this close to giving up on this build. The "Global C-State Control" disable took me from complete instability to rock solid performance. I am so glad I found this thread. Also it should be noted that I started with an ASUS PRIME B350-PLUS motherboard, which I could not boot at all. It must have shipped with the v1 BIOS, but would not boot with 2 different QVL RAM sets. I had no idea how to update the BIOS without getting POST, so had to RMA it, and went with the AB350 Gaming instead (in hindsight I probably should have gone with the more updated Gaming-3, but I missed it).
For reference, my build so far:
Motherboard: Gigabyte AB350-Gaming (not the Gaming 3)
CPU: AMD Ryzen 5 1600
RAM: 32GB G.Skill FORTIS F4-2400C16D-32GFT
GPU: (a really cheap silent Nvidia PCIe x16)
Chassis: Norco RPC4220
Cache: Samsung EVO 850 250GB
Parity: 1x 4TB WD RED (not yet installed, still bench testing)
Array: 3x 4TB WD RED + a few other smaller HDDs (only one installed so far)
I am currently waiting on my SAS breakout cables to make use of the Norco hot-swap bays, but obviously right now I am just happy to have a stable system (even if it is a little power hungry until a solution is found). Looking forward to seeing updates on the C-State compatibility.