this post was submitted on 20 Aug 2024
66 points (100.0% liked)

Technology

59148 readers
1986 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. 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
[–] [email protected] 12 points 2 months ago* (last edited 2 months ago) (1 children)

And here I thought, it would be good to go for Intel. Recently got a new PC with 14600KF. However, I have not had any issues with performance besides Deathloop (Launches, black screen and then dissapears).

EDIT: So I guess, I'm forced to wait until my motherboard developer/ company (MSI) announces that their users can update their BIOS manually? I'm curious whether, I'm actually affected by this or not. Though I guess, never gonna go Intel again. Next new PC will be having AMD (unless AMD makes such a mess as well, then it does not matter).

[–] [email protected] -4 points 2 months ago* (last edited 2 months ago) (4 children)

e.g. https://www.yahoo.com/tech/ryzen-3000-fix-sinkclose-vulnerability-183025768.html AMD has these sorts of flaws too, I don't know enough to tell if AMD is significantly better at this when deciding to buy

[–] [email protected] 22 points 2 months ago

That AMD security vulnerability doesn't physically damage the CPU while this Intel flaw does. Thats a drastic difference so the two are not the same

[–] [email protected] 13 points 2 months ago

So far the AMD security flaws aren't causing physical CPU damage, so Intel definitely wins the screw up award.

[–] [email protected] 10 points 2 months ago

That exploit required kernel access to begin with, which at that point, you have much bigger problems.

[–] [email protected] 6 points 2 months ago* (last edited 2 months ago)

Unfortunately, this problem is larger than a micro-code update. The main issue the user is likely referring to is Intel shipping defective product (oxidation issues), denying warranty claims for said defective product, then staying quiet when it's proven they have been shipping defective product. Intel could have owned up to the issue and proactively recalled defective units, but, they didn't do the honorable thing, not even close.