[robin_reala]

Also worth reading this thread on the subject: https://mas.to/@gabrielesvelto/116630047156991279

Regarding the Raptor Lake bug I received a couple of messages from confused users that had read articles on Tomshardware and Neowin. They asked about erratas and microcode updates which puzzled me, because that was part of my early investigation into the bug and we know that the failure is not caused by a known errata and microcode updates cannot fix broken CPUs. So why did they ask? As it turns out it was slop. Both articles are 100% slop full of confusing and inaccurate claims.

[websg-x]

Because it's a known problem. It's called Vmin Shift Instability issues. The affected CPUs are broken. One needs to RMA the CPUs. Intel also extended CPU warranty for 2 more years.

Because there still are many broken CPUs out in the wild. Firefox works around the crash so the broken CPUs won't flood the channel with crash reports.

[samlinnfer]

Sorry it's still not clear what he means? When a CPU is "broken", is it already failing or is it "broken" in the sense it will fail?

For example:

Does he mean all existing 13th/14th gen CPUs (prior to Intel's discovery of the vmin issue) are broken in the sense that they are susceptible to damage and can only be replaced.

OR

Does he mean that the microcode updates, applied by Intel to existing CPUs that are susceptible to damage, will only slow degradation and the CPUs will eventually fail and can only be replaced.

OR

Is he saying the 13th/14th gen CPUs which have already sustained damage, cannot be fixed by microcode updates.

[websg-x]

Only the desktop 8p+16e cores(13600/700/900,14600/700/900)k are susceptible. The CPUs are safe with the fixed bios/microcode. The notebook version of 8p+16e CPUs are also safe from vmin shift since notebook computer cannot go insane with voltage.

If the CPU is damaged already, the new microcode wont fixed the problem. It broken. You have to RMA the CPU.

The vmin shift instability is fixed. There are no new report of mass failures of 13th/14th gen CPUs after the new bios/microcode release.

[bananaboy]

I don't think he's right about this AI slop comment (and I am anti AI slop!). The tom's hardware article might have used AI but it doesn't say that microcode updates fixed it, just that the microcode updates mitigated it. Yes it mentions the errata, but a human could have come to that conclusion based on the bug report. And firefox.com release notes for 151.0.1 specifically claims it has a fix for this bug! https://www.firefox.com/en-US/firefox/151.0.1/releasenotes/