And somehow, all those crashes stabilised each other, allowing the plane to land safely. Only the pilot needed to change their pants afterwards.

Yeah... Their desktop CPUs are in all the news right now for crashing linke crazy

Intel says 13th and 14th Gen mobile CPUs are crashing, but not due to the same bug as desktop chips

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

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

Run everything, and you can always be smug about something ;D

The debian edition of croudstrike crashed some weeks earlier but it was not used in that many critical environments 🤷🏻‍♀️

no way, bog.