- Joined
- Mar 23, 2016
- Messages
- 4,839 (1.64/day)
Processor | Ryzen 9 5900X |
---|---|
Motherboard | MSI B450 Tomahawk ATX |
Cooling | Cooler Master Hyper 212 Black Edition |
Memory | VENGEANCE LPX 2 x 16GB DDR4-3600 C18 OCed 3800 |
Video Card(s) | XFX Speedster SWFT309 AMD Radeon RX 6700 XT CORE Gaming |
Storage | 970 EVO NVMe M.2 500 GB, 870 QVO 1 TB |
Display(s) | Samsung 28” 4K monitor |
Case | Phantek Eclipse P400S (PH-EC416PS) |
Audio Device(s) | EVGA NU Audio |
Power Supply | EVGA 850 BQ |
Mouse | SteelSeries Rival 310 |
Keyboard | Logitech G G413 Silver |
Software | Windows 10 Professional 64-bit v22H2 |
As a quick update to the AMD Linux "Performance Marginality Problem" affecting some early Ryzen processors under heavy load, today I received a new Ryzen 7 processor and indeed it's been running strong now for the past few hours under demanding load and has yet to hit the compiler segmentation fault bug.
As a reminder about the issue, this performance marginality problem is exclusive to certain workloads such as running many Linux compilation tasks in parallel. Compiling most software you should be fine unless really hammering the system hardware. Under normal Linux desktop workloads, gaming, etc, all Ryzen processors should work just fine.
AMD has not provided an official public explanation of the fundamental problem, but from those in our forums and elsewhere, it appears to affect Ryzen CPUs manufactured prior to week 25. This Ryzen 7 1800X was from "week 30" where as my original Ryzen 7 1800X review sample was from "week 5" as well as the Ryzen 7 1700.
Week 25 is the middle of June. The week number is shown on the processors in the second line as "UA 1705" where the 17 is representing the year and the next two digits showing the week, in this case 2017 week 5. I am unaware of any way that the date can be queried short of looking at the heat spreader.
Source: Phoronix