214
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Jul 2024
214 points (100.0% liked)
PC Gaming
8568 readers
493 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- 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
Obviously did the maths where lawsuits would cost less than a recall
recall, immediately foot the bill and still have to fix something they probably haven't fix yet. (the article mention maybe microcode update in August. ) taking lawsuits, they can drag it on and buy themselves time to figure out how to deal with it.
the legal side thing is, unless the claimant can prove that intel "knew" about this and still selling the broken item, there is not much they can do about it other than going through warranty process and get a replacement. However, now many outlet prove that to be a case from small companies to big data centers, they can't keep selling those units as if they are not broken. Some thing needs to be done properly(like as MS for a mandatory update if detect such CPU or work with MB for BIOS update with a feature block) from their legal dept and make sure new buyers have ways to mitigate it.