ASRock has garnered borderline notoriety status because its data-analytics-id=”inline-link” href=”https://www.tomshardware.com/pc-components/cpus/amd-9800x3d-failures-deaths-reddit-megathread-indicates-the-vast-majority-may-be-happening-on-asrock-motherboards” target=”_blank” data-before-rewrite-localise=”https://www.tomshardware.com/pc-components/cpus/amd-9800x3d-failures-deaths-reddit-megathread-indicates-the-vast-majority-may-be-happening-on-asrock-motherboards”>motherboards keep killing off Ryzen 9000 processors. Throughout the year, we’ve seen various reports stemming from the r/ASRock subreddit detailing CPU after CPU hitting permanent sleep mode, with the company performing damage control to the best of its abilities. At least, up until now, the issue was data-analytics-id=”inline-link” href=”https://www.tomshardware.com/pc-components/cpus/third-ryzen-7-9800x3d-burnout-case-appears-kills-the-cpu-and-damages-the-motherboard-socket” target=”_blank” data-before-rewrite-localise=”https://www.tomshardware.com/pc-components/cpus/third-ryzen-7-9800x3d-burnout-case-appears-kills-the-cpu-and-damages-the-motherboard-socket”> largely reserved for X3D chips; now, one unlucky user reports that their ASRock motherboard killed off not one, not two, but three separate…
