• 2 Posts
  • 90 Comments
Joined 1 year ago
cake
Cake day: August 15th, 2023

help-circle



  • Yeah /u/deadbeef@lemmy.nz kind of understated the problem. They were seeing insane failure rates in data centers like 50%. At this point, any 13th or 14th gen CPU that has experienced any crash or instability should be considered faulty unless you know the cause of the crash is from something else. This isn’t just me saying this, mainstream outlets like Gamers Nexus are saying it.

    If you’re a consumer and have one of those CPUs a replacement is probably in your future. And I wonder if Intel even has stock to replace that many at once…

    I can’t think of anything like this ever happening on this scale before in computing history.



  • 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