989
There is no fix for Intel’s crashing 13th and 14th Gen CPUs — any damage is permanent
(www.theverge.com)
this post was submitted on 26 Jul 2024
989 points (99.5% liked)
Technology
59342 readers
5137 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's not true. It was just last year that some of the Ryzen 7000 models were burning themselves out from the insides at default settings (within AMD specs) due to excessive SoC voltage. They fixed it through new specs and working with board manufacturers to issue new BIOS, and I think they eventually gave in to pressure to cover the damaged units. I guess we'll see if Intel ends up doing the same.
I generally agree with your sentiment, though. :)
I just wish both brands would chill. Pushing the hardware so hard for such slim gains is wasting power and costing customers.
I think he was referring to "back-in-the-day" when Athlons, unlike the competing Pentium 3 and 4 CPUs of the day, didn't have any thermal protections and would literally go up in smoke if you ran them without cooling.
https://www.youtube.com/watch?v=yRn8ri9tKf8
When I started using computers, I wasn't aware of any thermal protections in popular CPUs. Do you happen to know when they first appeared in Intel chips?
Pentium 2 and 3 had rudimentary protection. They would simply shutdown if they got too hot. Pentium 4 was the first one that would throttle down clock speeds.
Anything before that didn't have any protection as far as I'm aware.
Some motherboards did have overheating protection back then though. Personally I had my Athlon XP computer randomly shut down several times back then, because the system had some issue, where fans would randomly start slowing down and eventually completely stop. This then triggered overheat protection of the motherboard, which simply cut the power as soon as the temperature was too hight.
Yeah. I just meant AMD cpus used to easily overheat if your cooling system had an issue. My ryzen 7 3700x has been freaking awesome though. Feels more solid than any PC I've built. And it's fast AF. I think I saved over $150 when comparing to a similarly rated Intel CPU. And the motherboards generally seem cheaper for AMD too. I would feel ripped off with Intel even without the crashing issues
Problem is that it's getting extremely hard to get more single-threaded performance out of a chip, and this is one of the few ways to do so. And a lot of software is not going to be rewritten to use multiple cores. In some cases, it's fundamentally impossible to parallelize a particular algorithm.
That was asus applying too much voltage to the x3d skus
Where do you think Asus got the specs for that voltage?
Then why were there essentially no blow ups from other motherboard manufacturers? Tell me if my information on this is wrong, but when there's only one brand causing issues then they're the ones to blame for it.
There were, including MSI, who also released corrected BIOS versions.
(But even if that were not the case, it could be explained by Asus being the only board maker to use the high end of a voltage range allowed by AMD, or by Asus having a significantly larger share of users who are vocal about such problems.)
Not from AMD. From the autogenerated transcript (with minor edits where it messed up the names of things):
This was pretty much all on motherboard manufacturers, and ASUS was particularly bad (out scumbaging MSI, good job, guys).
At the start of this Intel mess, it was thought they had a similar issue on their hands and motherboard manufactures just needed to get in line, but it ended up going a lot deeper.
That doesn't contradict anything I wrote. Note that it says AMD's recommended cutoff is now 1.3 volts, implying that it wasn't before this mess began. Note also that the problem was worse on Asus boards because their components' tolerance was a bit too loose for a target voltage this high, not because they used a voltage target beyond AMD's specified cutoff. If the cutoff hadn't been pushed so high for this generation in the first place, that same tolerance probably would have been okay.
In any case, there's no sense in bickering about it. Asus was not without blame (I was upset with them myself) but also not the only affected brand, so it's not possible that they were the cause of the underlying problem, now is it?
AMD and Intel have been pushing their CPUs to very high voltages and temperatures for small performance gains recently. 95°C as the new "normal" was unheard of just a few years ago. It's no surprise that it led to damage in some cases, especially for early adopters. It's a thin line to walk.