Technology

59377 readers

3239 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

997

There is no fix for Intel’s crashing 13th and 14th Gen CPUs — any damage is permanent (www.theverge.com)

submitted 3 months ago by mox@lemmy.sdf.org to c/technology@lemmy.world

270 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] ichbinjasokreativ@lemmy.world 3 points 3 months ago (1 children)

That was asus applying too much voltage to the x3d skus

[–] mox@lemmy.sdf.org 6 points 3 months ago (2 children)

Where do you think Asus got the specs for that voltage?

[–] ichbinjasokreativ@lemmy.world 4 points 3 months ago (1 children)

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.

[–] mox@lemmy.sdf.org 1 points 3 months ago* (last edited 3 months ago)

Then why were there essentially no blow ups from other motherboard manufacturers?

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.)

[–] frezik@midwest.social 2 points 3 months ago (1 children)

Not from AMD. From the autogenerated transcript (with minor edits where it messed up the names of things):

amd's official recommendation [f]or the cut off now is 1.3 volts but the board vendors can still technically set whatever they want so even though the [AGESA] update can lock down and start restricting the voltage the problem is Asus their 1.3 number manifests itself as something like 1.34 volts so it is still on the high side

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.

[–] mox@lemmy.sdf.org 2 points 3 months ago* (last edited 3 months ago)

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.