intel CPUs are literally falling apart

Intel CPUs have been failing all over the world. But why? In this video, we talk about two major issues with the 13th and 14th generation of CPUs.

Writeups:

Press:

🛒 GREAT BOOKS FOR THE LOWEST LEVEL🛒

🔥🔥🔥 SOCIALS 🔥🔥🔥

[everyhandletaken]

Ed: "should try Rust"
Intel: "we have more rust than we would like to, actually.."

[NotherPleb]

Not trusting the hardware is a whole another level of debugging nightmare

[AngelOnFira]

Sounds like Rust wasn't the fix for this one

[CrispyMuffin]

Userbenchmark: the lastest intel CPUs are so amazing they cant even contain their own power!

[alderonmatt]

Most developers wouldn't even consider that the Compiler or CPU has a bug thats causing their code to crash. It certainly took us 4 months to figure out it was actually the CPU.

[toms]

Transistors weren't oxidizing, the vias were. A via through is a "wire" that travels in the up/down direction in the cpu when the cpu is laid flat on a surface to allow connections to different layers of the cpu. The transistors were getting excessive voltage causing the semi-conductive state along the 5-7 nanometer transitive area of a transistor to lose the semi-conductivity by having those atoms in there shift position due to the excessive voltage.

[makebreakrepeat]

Oxidation? Sounds like Rust was the issue 😅

[rumplstiltztinkerstein]

Get ready for thousands of these defective CPUs flooding the market,

[gljames]

Userbenchmark is going to implode. Lmao.

[Seoanee]

Intel just doesn't wanna recognize that they have an "off by one volt" error in code

[zhd-net]

Not new for Intel. Back in the 70's we had major failures with Intel EPROM's (yes I'm that old). They blamed everything except their product. "You're not flashing them right" (Intel programmer), "...not protecting from UV light" (Intel foil labels), "...not erasing them right" (Intel eraser), "...wrong voltage" (Intel developer system), "...etc., etc." They never admitted it to us, didn't even offer free replacements (well they did, but with similarly defective components). Years later I read an acknowledgement in an Intel biography by one of their senior company officers that it happened, and that they were frantically trying to deflect from their production pending an internal fix. Dissembling again?

[jackzugna]

Intel to Crowdstrike: "Well, I will continue what you started."

[dalehorton]

I still wonder if it'll ever come out if the CrowdStrike devs were running 13th/14th gen CPUs and their deployment issue/corruption was actually Intel's fault.

[dfauthmph]

Enshittification is spreading into hardware.

[SterileNeutrino]

"Microcode update to fix oxydation issues" has the same bad smell as "software patch to make a MAX 737 behave like a 737". "Small number of reports" ditto.

[AyushKumar-mdut]

seeing Intel and Boeing, companies were once leaders of engineering in their spaces, going up in flames like this is really disheartening.

[omninull]

Level1Techs and Gamers Nexus have both been digging into this issue and have videos I'd highly recommend going deep into this issue.

[StefanH]

If my game is failing, there's at least a thousand things I'd blame before I would ever consider thinking the CPU itself is actually starting to rot. Especially as a game developer this is a ballsy move but kudos do them!

[luketurner]

5:36 made me replay in my head the compilation of Louis Rossmann reading "small number" in numerous Apple press releases/recalls/warranty extensions. Because we all (should) know that when a manufacturer uses the term "small number", they are trying to gaslight us into thinking the issue isn't as widespread as it actually is

[jsrodman]

The problem is worse than this. Intel is still issueing misleading press releases about the problem, and we now have information that Intel refused rmas for affected CPUs when they knew they were caused by flaws in manufacture.