Hmm, I'm unconvinced. If his was an "early batch", maybe just bad silicon, bad luck.
My 3600 is from "early batch" (bought it the night of, or the night after release), I've run it @ 127C (according to Ryzen Master) for several hours, using a fixed-clock OC, around or above 4.0Ghz, @ 1.38V or so, it needed that much for my PrimeGrid workload.
Then I basically set defaults for CPU clock, had RAM (TridentZ RGB "for AMD" 3600) @ XMP 3600, FCLK 1800 on my Asus B450-F ROG STRIX.
Had weekly crashes/lockups.
Recently, set all-core OC again, using AGESA 1.0.0.4 patch B / UEFI BIOS 3003, to 4.0GHz @ 1.3685V. Seems stable for mining software on CPU and GPU.
Although, for the first time since setting all-core OC using this AGESA version, I couldn't wake monitor from sleep this morning, and had to manually use physical RESET button on front-panel to reboot. Could have been my RX 5700 too, I recently OCed the VRAM again from 1750 to 1800. It seems over time (12+ hours), VRAM temps creep up, or something, and things start to crash. Now running at 1775 VRAM clock in Wattman/Tuning / ADR2020.
Anyways, I'll let the forum know if my R5 3600 gets knackered due to all-core OC. Temps are OK, 82C max, under 240mm AIO WC (CM MLL 240).
It's unclear to me whether buildzoid's 3700X was under air or water from that linked thread.
There was mention that he set Vddg (is that the same as Vsoc?) to 1.15V, which, Vsoc is only supposed to go to 1.10V max, I read.
I also wonder about degradation due to LLC settings, sometimes overly-aggressive LLC, combined with fixed-voltage / clock OC, will cause voltage overshoot.