AMD fixed the problem in week 25 (mid-June) so Ryzen processors shipping today no longer have this errata. Phoronix received a new Ryzen processor and confirms things are now running solidly without faults:
I will continue running this Ryzen 7 1800X processor overnight but so far things are running solid under the enduring load thus far. With that, I am now very happy with Ryzen and still running the Ryzen on my main Fedora Workstation production system, even with a pre-week-25 model it's still fine for all of my day-to-day workloads; my only remaining critique of Ryzen outstanding is in regards to having Ryzen thermal monitoring support under Linux with no hwmon/thermal driver yet being available to read CPU temperatures. Stay tuned for AMD Ryzen Threadripper 1950X benchmarks on Phoronix in the next few days; Linux tests on AMD EPYC to follow after.EPYC and Threadripper processors are not affected by the issue. Affected Linux users with a Ryzen CPU manufactured before week 25 can contact AMD Customer Care to get an RMA. Windows users are not affected by this bug.