GMP damaging Zen 5 CPUs?
gmplib.org
GMP damaging Zen 5 CPUs?
1–10 of 240 posts
Re: GMP damaging Zen 5 CPUs?
#2Re: GMP damaging Zen 5 CPUs?
#3[0] https://upload.wikimedia.org/wikipedia/commons/2/2d/Socket_A...
Re: GMP damaging Zen 5 CPUs?
#4> Modern CPUs measure their temperature and clock down if they get too hot, don't they?
Yes. It's rather complex now and it involves the motherboard vendor's firmware. When (not if) they get that wrong CPUs burn up. You're going to need some expertise to analyze this.
Re: GMP damaging Zen 5 CPUs?
#5Re: GMP damaging Zen 5 CPUs?
#6I feel like if this was heat related, the overall CPU temperature should still somewhat slowly creep up, thereby giving everything enough time for thermal throttling. But their discoloration sure looks like a thermal issue, so I wonder why the safety features of the CPU didn't catch this...
Re: GMP damaging Zen 5 CPUs?
#7These big x86 CPUs in stock configuration can throttle down to speeds where they can function with entirely passive cooling, so even if the cooler was improperly mounted, they'd only throttle.
All that to say, if GMP is causing the CPU to fry itself, something went very wrong, and it is not user error or the room being too hot.
Re: GMP damaging Zen 5 CPUs?
#8As there is ongoing drama with Zen 5 and power issues, there are people with the instruments and the motivation to investigate this. You should consider contacting Gamers Nexus, and help them to get your test suite running. They can measure power draw and do a thermal analysis of this CPU, and they'd likely be eager to do it, given the possibility of making a bunch of dramatic YouTube content about design flaws in wi…
Re: GMP damaging Zen 5 CPUs?
#9I've heard some really wild noises coming out of my zen4 machine when I've had all cores loaded up with what is best described as "choppy" workloads where we are repeatedly doing something like a parallel.foreach into a single threaded hot path of equal or less duration as fast as possible. I've never had the machine survive this kind of workload for more than 48 hours without some kind of BSOD. I've not actually killed a cpu yet though.