this post was submitted on 27 Jul 2024
99 points (98.1% liked)

PC Gaming

8576 readers
381 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 1 year ago
MODERATORS
top 15 comments
sorted by: hot top controversial new old
[–] gravitas_deficiency@sh.itjust.works 22 points 3 months ago (1 children)

How does this not devolve into a massive class-action? Like, it’s got to, right?

[–] towerful@programming.dev 4 points 3 months ago (1 children)

If Intel makes it right, it won't.
There might be something for enterprise level with loss-of-revenue or something.
But if the microcode patches fix the issue, and they replace any already-damaged CPUs, then it's clear Intel is doing what they can to fix it.
Lawsuits aren't for mistakes that get "made good", unless it's a contract breach

From what I’m hearing, they’re not planning on making it right.

[–] ech@lemm.ee 21 points 3 months ago (1 children)

Glad I chose an AMD setup for my last overhaul. Sympathies for those affected or left to completely redo their rigs to avoid intel.

[–] PerogiBoi@lemmy.ca 9 points 3 months ago (1 children)

Literally just paid for the final part for my LGA1700 rig… saved up for months. Fuck this shit.

I’m running my i5 13600h until the computer can’t turn on anymore. I’m not made of fucking money.

[–] ech@lemm.ee 5 points 3 months ago (1 children)
[–] PerogiBoi@lemmy.ca 3 points 3 months ago (1 children)

We’ll see if it lasts a couple months I guess.

[–] towerful@programming.dev 3 points 3 months ago (1 children)

Hopefully the microcode patches fix the issue before it has done any damage for you. Or if the issue has already done damage, hopefully you get a replacement

[–] PerogiBoi@lemmy.ca 2 points 3 months ago (1 children)

Microcode patch doesn’t fix the oxidation problem that they all inherently have. I’ll be lucky if the the cpu lasts a couple months of minimal use.

[–] towerful@programming.dev 2 points 3 months ago (1 children)

My understanding was that the microcode was causing too much power draw which caused the oxidation.

Tbh, I've read/heard lots of speculation, and I don't exactly trust Intel to be telling the entire truth.

[–] PerogiBoi@lemmy.ca 2 points 3 months ago

My understanding is that there are two issues. Manufacturing defects cause the copper to oxidize, and the processors themselves request more voltage than required or needed, causing excess oxidation damage. Intel said they cleared up the manufacturing defect issue sometime around October 2023

[–] yeahiknow3@lemmy.dbzer0.com 16 points 3 months ago* (last edited 3 months ago)

No offense, but Intel has been shit for a decade. Far too much power draw for marginal gains. Their whole schtick is terrible for the planet and comically anti-innovation. Why would anyone have an Intel processor? It’s totally irrational.

[–] DebatableRaccoon@lemmy.ca 3 points 3 months ago (1 children)
[–] quixotic120@lemmy.world 18 points 3 months ago (1 children)

which means if you’re impacted after a ton of paperwork and emails you’ll get a check for $200 6 years from now to make up for the fact that your $650 processor was a lemon. justice served!

[–] DebatableRaccoon@lemmy.ca 11 points 3 months ago

Sadly, this is the way. Good to see Intel giving AMD leg-up in the market though. Accidental MVPs are always interesting to see.