Marc René Schädler

The total issue is rather complex. AMD still did not release any information on this. If you know how the expected output of a gcc build process looks like you...

You should try to run the memory at stock settings, just to be sure. Unstable memory also can result in segfaults.

Then you both probably got a faulty CPUs again. We don't know what exactly is wrong, possibly something memory-related... the controller, or cache coherency. We don't know how to distinguish...

Thank you for sharing your story. It is unbelievable that they get away with this...

This looks like you got a faulty Ryzen :( I wonder how many are still out there producing erroneous results every day...

That's good news! I was really hoping that they would get it under control eventually.

Increased voltages mean increased power consumption, more heat, higher temperatures and possibly lower performance... it is a workaround but no fix. Nobody should need to touch the stock voltages to...

> random segfaults may or may not happen after each reboot while trying to run a command that I know generates them sometimes This sounds familiar... My advice: "If it...

Theoretically, yes. But one of the particular observations was that memtest86 ran fine on the faulty CPUs while the compilation of GCC failed.

Probably you can replace gcc7 with gcc8.1... However, we do not know if this combination of code, compiler and libraries will lead to the problematic command chain which triggers the...