That is a massive victory! Getting a stable compilation on an overclocked 4-stick Ryzen configuration under a full Linux kernel compilation load is the ultimate stability achievement. Most stress tests (like Prime95 or AIDA64) cannot replicate the intense, erratic, and highly concurrent execution shifts that GCC/Clang throws at a system memory controller.
## Why Your BIOS Tweaks Fixed the Segfaults
When your system crossed 85°C, the Integrated Memory Controller (IMC) on your Ryzen chip degraded physically in signaling speed due to the thermal energy. By manually locking down your values, you created a highly resilient electrical boundary:

* DRAM Voltage to 1.40V+: Supplied enough sheer electrical power to keep the memory waveforms sharp and clean, overcoming the increased trace resistance caused by the heat wave.
* ProcODT to 48 ohms: Altered the physical resistance on the motherboard signal lines. This completely dampened electrical echoes and noise bouncing between your 4 populated RAM slots.
* CAD Bus Strengths (24 ohm): Amplified the drive strength of your Clock, Address, and Command signals, ensuring the data blocks landed in their precise CPU execution windows without dropping bits.

------------------------------
## Essential Reading for Ryzen Compilation Stability

* The Original Ryzen "Kill-Ryzen" Script (Zen 1 & 2 GCC Segfaults)
* The Resource: conorross/kill-ryzen (GitHub)
   * Why it matters: This is the legendary bash script created by the open-source community during the early Zen eras. It fires up loops of simultaneous kernel compilations inside a RAM disk (tmpfs) to intentionally trigger loop errors and segmentation faults on marginal Ryzen silicon. It remains the gold standard for testing memory controllers.
* AnandTech’s Deep Dive on Ryzen Topology & Precision Boost Overdrive
* The Resource: Look up AnandTech's Ryzen 3000 Review and Overclocking Analysis.
   * Why it matters: This resource explains the physical architecture of the Ryzen multi-chip layout—specifically how the independent Core Complexes (CCDs) dump heat directly under the heat spreader right next to the critical I/O Die (which contains the memory controller).
* The Gentoo Linux Forum & Wiki Memory Overclocking Compendium
* The Resource: Search Gentoo Forum: Common compilation segmentation faults on AMD Zen.
   * Why it matters: Gentoo users compile their entire operating systems from scratch. Their community forums hold the absolute best documentation on fine-tuning ProcODT, RTT_PARK, and CAD Bus Drive Strengths to keep high-capacity 4-DIMM memory layouts stable under GCC.
* AMD’s Official Technical Spec Sheets for Zen 2/3 Memory Topologies
* The Resource: Look up AMD Ryzen 3000 Memory Overclocking Guide by Robert Hallock.
   * Why it matters: This presentation breaks down exactly why filling 4 slots drops the official supported JEDEC speed floor, and outlines how the Infinity Fabric clock (FCLK) must remain perfectly synchronized (1:1 ratio) with memory frequencies to prevent microcode cache drops.