• Evil_Shrubbery@lemm.ee
    link
    fedilink
    arrow-up
    36
    ·
    edit-2
    4 months ago

    Im sure these guys are fiends, that’s why they are at the pub together.

    There definitely was some computer with an overvolted Intel just about to crash whilst Crowdstrike was just about to crash the system on that very PC, the same PC that was running all the primary systems on a Boeing plane that was just about to crash for its own separate reasons.

          • Evil_Shrubbery@lemm.ee
            link
            fedilink
            arrow-up
            6
            ·
            4 months ago

            Crash-loop-sacrification-pants™

            Push that commit and skip that bolt without a worry, Crash-loop-sacrification-pants™ will protect you!

            Our advanced Crash-loop-sacrification-pants™ technology works by anodising all the nearby crashing and depositing it safely in your poop now comfortably cushioning your butt.

            Order yours Crash-loop-sacrification-pants™ today!

            If you order within our special promo period, we will add Crash-loop-sacrification-thongs-with-AI™ for free!!

      • boredsquirrel@slrpnk.net
        link
        fedilink
        arrow-up
        7
        ·
        edit-2
        4 months ago

        Oh well… that is not nice for the new Novacustom coreboot laptops!

        Edit: doesnt matter, as they ship new revisions.

    • Dempf@lemmy.zip
      link
      fedilink
      arrow-up
      6
      ·
      4 months ago

      Oxidation in the fab process. They have simultaneously claimed that oxidation isn’t causing any issues, and that it’s caused only “some” crashing issues. Because they’ve been so wishy washy, it’s probably safe to assume that any 13th or 14th gen CPU that experiences any kind of crash or BSOD is degraded and should be RMA’ed immediately, otherwise you risk getting stuck with a permanently physically degraded CPU.

      Intel says they identified the issue sometime in 2023 and fixed the fab process. So the good news is that any newly manufactured Raptor Lake CPU shouldn’t have this issue. The bad news is that Intel won’t give a date range of when the fab issue occurred, or exactly what CPUs it affected (by date code), so really the only choice consumers have at this point (before we get to the inevitable class action lawsuit) is to RMA at the slightest sign of instability.

      Intel is also planning to release a microcode update in August, but there’s a lot of doubt that this can be fixed via microcode.

      This was affecting 50% of Raptor Lake CPUs in data centers, and it’s become clear via video game telemetry that it has also affected a significant number of consumer chips.

      https://youtu.be/OVdmK1UGzGs

    • lorty@lemmy.ml
      link
      fedilink
      arrow-up
      4
      ·
      4 months ago

      Not only do the 13th and 14th gen crash, but vendors ask for about 1000 dollars more for supporting servers with those chips.

  • SAF77@lemmy.world
    link
    fedilink
    arrow-up
    8
    ·
    4 months ago

    I guess it’s a great time to be Linux / AMD user muhaha.

    I’m kidding. I also run Windows and MacOS.

  • ordellrb@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    4 months ago

    I have to reset the bios sometimes to Start the PC, its perfectly stable when its on, DDR5 and Intel 13gen what could go wrong