Intel’s 13th and 14th Gen CPU instability damage is irreversible, and it can happen to way more chips than we thought

What you need to know

  • Intel says it has identified the root cause of 13th and 14th Gen desktop CPU instability; a microcode fix is expected mid-August.
  • More Intel CPUs than first thought are potentially affected by the microcode bug, including K, KS, KF, and non-K 65W (and higher) variants.
  • Intel isn’t planning on a full recall, instead urges affected users to contact customer support.

As a tech enthusiast with years of experience building and tweaking my own PCs, I can’t help but feel a mix of frustration and relief upon hearing the latest updates from Intel regarding the instability issues affecting its Raptor Lake CPUs. The frustration stems from the fact that this issue has been ongoing for over two years now, with reports of crashes and BSODs plaguing Intel’s most recent desktop chips. But the relief comes from the fact that Intel has finally identified the root cause and is working on a microcode fix.


Intel has faced significant challenges with its latest “Raptor Lake” and the refreshed 14th generation desktop processors (CPUs). These chips, introduced two years ago, have been marred by instability issues that continue to persist.

For years, Intel has been investigating numerous reports of crashes and Blue Screens of Death (BSODs). But on July 22, we, as Intel community members, received exciting news. Intel engineer Thomas Hannaford announced on the community board that they had finally identified the source of the instability issues. Here’s what he revealed:

Through thorough examination of Intel Core 13th and 14th Gen desktop processors that have been returned due to instability problems, we’ve identified that an increased power voltage is responsible for the instability in certain processors. Our investigation reveals that this heightened voltage arises from a microcode algorithm, leading to inaccurate voltage demands to the processor.

As a researcher investigating the issue with Intel’s Core 13th/14th Gen desktop processors and their susceptibility to elevated voltages, I can share that Intel is working on a microcode patch to address this root cause. We are diligently conducting validation tests to ensure that reported scenarios of instability are effectively addressed in the patch. Currently, Intel aims for a mid-August release to partners once comprehensive validation has been completed.

Intel takes responsibility for the instability issues affecting some of our 13th and 14th Gen desktop processors. We urge any affected customers to contact Intel Customer Support for additional help in resolving this matter.

Intel has admitted that the source of the instability issues lies with its microcode, which functions similarly to light firmware. They expect to provide a resolution through upcoming motherboard BIOS updates within the near future.

Intel’s Community Manager Lex Hoyos admitted that high voltages resulting from the microcode problem aren’t the sole cause of instability. In a post on the Intel subreddit, Hoyos disclosed a manufacturing defect that caused oxidation in certain 13th Gen chips produced in 2023.

Intel instability is more widespread than first believed

Previously, it was thought that this problem affected only specialized Core i7 and Core i9 processors, popular among tech enthusiasts. However, a recent interview by The Verge with Hannaford has shed new light on the situation, indicating that the issue is actually more widespread than initially assumed.

I observed Hannaford disclosing that Intel chips with a power consumption of 65W or more, such as Raptor Lake chips from the 13th and 14th generations, could potentially be impacted by this bug. This includes non-K models, in addition to K, KF, and KS variants. However, it’s essential to note that not all systems with these chips will necessarily encounter the issue. Interestingly, Intel mobile chips for laptops appear to be excluded from this concern.

What can you do about your faulty Intel Raptor Lake CPU?

Intel has identified the source of the problem causing instability in its microcode, yet it remains reluctant to initiate a recall. Instead, the tech giant intends to release an update through motherboard BIOS by mid-August. This development will bring relief only to those users who haven’t experienced the issue thus far.

According to Tom’s Hardware, this bug results in significant damage to the affected processors. Unfortunately, the microcode patch won’t be able to restore processors that have already encountered crashes. However, it is anticipated that this update will help prevent issues on processors not yet impacted by this problem. In the interim, Intel advises users to maintain their CPUs at default settings and keep their system BIOS updated as much as possible.

If your Intel processor is malfunctioning and there’s no official recall in sight, what can be your next steps? Intel advises contacting their customer support team, regardless of any past RMA applications that were denied. In case you’re uncertain whether your chip falls under this issue, Intel recommends checking out the informative Robeytech YouTube video for guidance.

What’s going on with AMD Ryzen 9000 CPUs?

Intel isn’t the sole company encountering challenges in the chip-making industry. Recently, AMD disclosed that the rollout of its Ryzen 9000 series desktop CPUs will be postponed. This setback is attributed to a less significant issue in production quality control.

Two of AMD’s Zen 5 chips, specifically the Ryzen 7 9700X and Ryzen 5 9600X, were incorrectly identified as higher-tier Ryzen 9 models. This discovery caused AMD to encounter a minor setback while addressing the labeling issue promptly.

AMD’s new chips, originally slated for release on July 31, have been distributed early to tech reviewers and influencers. These advanced copies are expected to reach consumers soon. It remains uncertain if these samples bear incorrect branding, but there’s a possibility that they may turn into valuable collector’s items due to their exclusivity.

Read More

2024-07-29 18:39