• Corkyskog
    link
    fedilink
    English
    arrow-up
    21
    ·
    3 months ago

    I thought they had corrosion issues, how do you patch that?

  • InfiniteGlitch@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    13
    arrow-down
    1
    ·
    edit-2
    3 months ago

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

      • partial_accumen@lemmy.world
        link
        fedilink
        English
        arrow-up
        23
        arrow-down
        1
        ·
        3 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

      • Codilingus
        link
        fedilink
        English
        arrow-up
        10
        ·
        3 months ago

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

      • BombOmOm@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        ·
        edit-2
        3 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.