This is going to be a solid 75%+ boost to performance, given I regularly max out my machines threads. Pretty amazing improvement in 2 years.
This is going to be a solid 75%+ boost to performance, given I regularly max out my machines threads. Pretty amazing improvement in 2 years.
Ryzen runs them tight to spec, whereas intel is more relaxed. Here tight is better, but it also means exposing lies in manufacturer specs on ram.
Cheapening on ram is never a good idea, but there's always the option of configuring more relaxed timings on the firmware settings, if the ram isn't up to its advertised spec.
It's also possible your CPU is one of the first iteration of 1800x which had this issue that famously caused segfaults when compiling software on Linux. This was only seen on the first months of 1800x, and AMD offered free replacements to those affected. It's likely a bit late for that, but you're better off upgrading to Ryzen 3xxx anyway.
I backed the memory clocks down from 3200 (which it's supposed to be rated for) to 3000 and it passed with no errors.
This is the issue they're certainly talking about: https://www.phoronix.com/scan.php?page=news_item&px=Ryzen-Se...
And it is assuredly not a problem with any Ryzen processors manufactured after the very first few months.
I never experienced it myself but in my BIOS there's an option about "power on idle" that's suggested to not turn off for compatibility (I don't recall the correct words but I could check).
It usually depends on MB manufacturers and BIOS/AGESA versions.
After applying workarounds, I still see some strange crashes, not sure if at least some of those are still related to the CPU hangs from the bug above. TBF this might not be the CPU's fault. This is all quite annoying to me and time intensive to investigate (where do I even start?). Even though I really like AMD's tech I am quite frustrated and I haven't had these problems with my previous Intel builds so far...
sudo ZenStates-Linux/zenstates.py --c6-disable
(I've got 29 days of uptime right now and the last reboot was due to a system upgrade)