The second AMD Ryzen 9 9950X is ‘cold as ice’
© Tech YES City ASRock has been pushing new AM5 BIOS updates after ongoing community reports about intermittent no-boot behavior and error codes. Earlier this month ASRock said it integrated AMD AGESA ComboAM5 PI 1.3.0.0a into beta BIOS 4.07.AS01 and later 4.10 stable released, and claimed the update is meant to address systems that fail to boot after being used for a period of time, with the goal of restoring normal boot functionality.
That beta started appearing across multiple AM5 boards, including X870 and X870E models, with short release notes that call out AGESA 1.3.0.0a, memory compatibility changes, and a fix for a boot failure “on certain CPU configurations.”
This is where Tech City Yes’ latest update arrives. According to the report, a second Ryzen 9 9950X died after roughly 3 to 4 months , on the same ASRock motherboard model (X870 Steel Legend WiFi) in the same type of use case, and he describes it as a repeat of the first failure.
© Tech YES City He also says he tried updating the BIOS, referencing ASRock’s recent BIOS announcement and the idea that the update might revive CPUs that appear dead but are actually stuck in a no-boot state. In his case, the CPU still would not boot in multiple boards, and he describes it as completely cold to the touch after power-on, quoting a song “you’re as cold as ice.”
Unlike most reports involving ASRock motherboards, Tech City Yes’ has access to a wide range of motherboards and CPUs, so this was an easy test to run. Also worth noting that this is also not an X3D CPU, which, according to the ASRock subreddit megathread, appears to be among the most affected SKUs.
He also mentioned that early rumors pointed to a specific batch of Ryzen CPUs as the cause, but he noted that the second CPU came from a completely different source , which makes that explanation less likely. Instead, it suggests there may be a problematic batch of ASRock motherboards contributing to these failures. Other reviewers, like Hardware Unboxed have tried to reproduce the issue on their own systems, but without success.
Source:
