A recent R5 5600 build ran for a few hours before stopping. It now has no output, no screen, and no sound.
A recent R5 5600 build ran for a few hours before stopping. It now has no output, no screen, and no sound.
It's strange your CPU shut down. It might be because your cooler isn't working well (it really is) and your paste job cost nearly as much as the cooler itself. I haven't found anyone else with the same problem. Also, the Wraith cooler already has RGB lighting. It could be that the CPU had issues beforehand, and you discovered this before sharing it with your friend and dealing with all the trouble.
Absolutely unusual situation. I usually keep an MX-4 at home since I sometimes assemble PCs for friends. The R5 Ryzen CPUs come with no RGB lighting, which is why we opted for the budget cooler we bought (never again). I felt the same way initially—I assumed the issue was with the processor itself, but the benchmarks didn’t confirm it. There’s still uncertainty about whether the motherboard might be faulty; I wasn’t sure if replacing it would help or cause further problems. I didn’t notice any broken pins or damage on the board, and it looked perfectly normal. If you’re like me, should we consider swapping the motherboard or just install a new CPU?
No one else has encountered these problems with this specific board (or any general GB board), so it's fine. The reported temperatures indicate the sensors are functioning properly. Personally, I think you could be extra sure if you want to double-check. The wraith prism with ARGB is only available on X700 or newer models.
I'm waiting response from RMA and I think I won't return the mobo since it behave same when faulty cpu inserted into my gigabyte b450, also sensors was working as you said and I think even bios flash(no cpu, no ram) feature worked well so I think mobo is fine. Thanks for the opinion and help I'm gonna update the thread when I get a new CPU
Have you come across the bathtub curve? Components generally fail at the start or end of their life. The CPU likely performed well during initial production runs but eventually stopped under stress tests. Even with a modest cooling system, it wouldn’t cause extreme overheating that would trigger throttling but lead to failure. Unless a major user mistake destroyed the board, memory, power supply, and CPU itself.
It seems you realized something new now. I don't think there was any user mistake—this might be a faulty product that could improve over time. I'll be more cautious about benchmarking new items going forward. Also, I'm not sure if this is just the battery curve, but it could be related to other factors.
The curve indicates the products don't repair themselves; it reflects their ongoing performance. If they haven't failed, they should last longer. What occurred was actually beneficial—you resolved the problem promptly. Running a stress test after development is strongly advised to avoid future issues by identifying weak points early. The only mistake was stopping during the test, which prevented you from understanding the outcome completely.