Unable to load image

Intel claims it's a voltage issue, microcode issue coming in August

https://community.intel.com/t5/Processors/July-2024-Update-on-Instability-Reports-on-Intel-Core-13th-and/m-p/1617113#M74792

Based on extensive analysis of Intel Core 13th/14th Gen desktop processors returned to us due to instability issues, we have determined that elevated operating voltage is causing instability issues in some 13th/14th Gen desktop processors. Our analysis of returned processors confirms that the elevated operating voltage is stemming from a microcode algorithm resulting in incorrect voltage requests to the processor.

Intel is delivering a microcode patch which addresses the root cause of exposure to elevated voltages. We are continuing validation to ensure that scenarios of instability reported to Intel regarding its Core 13th/14th Gen desktop processors are addressed. Intel is currently targeting mid-August for patch release to partners following full validation.

Intel is committed to making this right with our customers, and we continue asking any customers currently experiencing instability issues on their Intel Core 13th/14th Gen desktop processors reach out to Intel Customer Support for further assistance.


Other link - https://www.tomshardware.com/pc-components/cpus/intel-finally-announces-a-solution-for-cpu-crashing-errors-claims-elevated-voltages-are-the-root-cause-fix-coming-by-mid-august

Intel statement on via oxidation

Short answer: We can confirm there was a via Oxidation manufacturing issue (addressed back in 2023) but it is not related to the instability issue.

Long answer: We can confirm that the via Oxidation manufacturing issue affected some early Intel Core 13th Gen desktop processors. However, the issue was root caused and addressed with manufacturing improvements and screens in 2023. We have also looked at it from the instability reports on Intel Core 13th Gen desktop processors and the analysis to-date has determined that only a small number of instability reports can be connected to the manufacturing issue.

For the Instability issue, we are delivering a microcode patch which addresses exposure to elevated voltages which is a key element of the Instability issue. We are currently validating the microcode patch to ensure the instability issues for 13th/14th Gen are addressed. - Intel representative via Reddit.

:marseybang#fast:

56
Jump in the discussion.

No email address required.

Hey guys sorry our silicon is oxidizing heres some microcode to make up for it!! (normies will never install it)

Jump in the discussion.

No email address required.

(normies will never install it)

Both Windows and Linux automatically update CPU microcode.

Jump in the discussion.

No email address required.

They can't even update a bios from desktop

Jump in the discussion.

No email address required.

You can on both, Linux has "fwupd" to handle firmware updates on modern-ish system (13th and 14th would totally qualify).

Jump in the discussion.

No email address required.

This is completely unrelated.

I think you have the wrong mental model how microcode updates work. You don't flash a CPU with new microcode, you load it at startup, it's temporary. Both BIOSes and operating system kernels have the ability to load microcode.

https://www.intel.com/content/www/us/en/developer/articles/technical/software-security-guidance/best-practices/microcode-update-guidance.html

The operating system (OS) should check if it has a more recent microcode update (higher update revision) than the version applied by the BIOS. If it does, the OS should load that microcode update shortly after BIOS hands off control to the OS.

And indeed, here's an example Windows update with Intel microcode:

https://support.microsoft.com/en-us/topic/kb4346085-intel-microcode-updates-2eb8dbe3-7548-be9d-5153-50027073ea5e

Jump in the discussion.

No email address required.

they can. even some windows xp era mobos could.

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.