So as you know I went for 3.8GHz with +106.25mV offset with 2133MHz RAM. My voltages were all as when UEFI defaults used except VCORE. So that profile lead to ~1.319V on DMM on x264 loading CPU. As stated earlier this need more VCORE than RB. Repeated testing of 10 loops x264, 2hrs RB and f@h for 4-6hrs, all was well.
I then wanted 2400MHz RAM, I have CMK8GX4M2A2400C1
4 , it is single sided RAM. Selecting D.O.C.P 3 gets me the correct XMP profile on RAM. With this setup my SOC: [Auto] went from ~0.838V to ~1.050V. I still had errors in f@h and Y-Cruncher, at intermittent times after say few hours.
I set SOC manually to 0.925V (~0.944V on DMM), as thought I'm not really pushing out of current Official supported RAM speeds. I still had a few errors but after longer length. I then started increasing VCORE and have gone all the way from +106.25mV to +131.25mV (~1.348V on DMM).
So testing went like so (+125mV 0.925V):-Warning: Spoiler! (Click to show)
When I stopped f@h I'd done ~14hrs, 12hrs in one go and then ~2hrs after setting Sense MI Skew: [Disabled] (as Elmor suggested to another to use that to get correct temps).Warning: Spoiler! (Click to show)
So then I thought throw Y-Cruncher at profile.Warning: Spoiler! (Click to show)
All good passed ~14hrs f@h and ~4hrs Y-Cruncher (system had been in use for ~38hrs of stability testing/tweaking). So i went for x264 48 loops.Warning: Spoiler! (Click to show)
I then upped VCORE to +131.25mV.Warning: Spoiler! (Click to show)
My i5 4690K CPU: 4.9GHz Cache: 4.4GHz RAM: 2400MHz testing was a continuous run on final setup. It passed 48 loops of x264, then 2hrs RB, ~1-2hrs gaming and 17hrs f@h, all in one continuous run.
I do not know if these issues are due to immaturity of platform, AFAIK x264 / Y-Cruncher / f@h is supported in Ryzen, my OS is fresh clean install with bare min of apps, my setup is simple (CPU/RAM/MOBO/HSF/ std SATA SSD/HDD/no RAID, etc).
If I can not get the kind of stability I'm used on my i5 4690K for an OC, on R7 1700 at 3.8GHz within a few days I reckon I may have to jump the Ryzen ship