Is Intel’s nightmare finally over? One final patch could fix 13th and 14th generation CPU instability issues
Intel has finally concluded its investigation into the problematic 13th and 14th generation CPUs. It has finally listed the four main factors that caused the instability issues. It has also been announced that an additional patch is needed to fix the fourth stumbling block.
Video cardz noted that Intel communications manager Thomas Hannaford a further update posted to provide this information.
The final patch needed as a preventative measure to mitigate the gremlins of future 13th and 14th generation processors is microcode update 0x12B. This addresses the latest issue discovered by Intel, which is: “Microcode and BIOS code requesting elevated core voltages, which may cause Vmin shifting, particularly during periods of idle and/or light activity.”
This patch incorporates the two previous microcode fixes, namely 0x125 and 0x129. These fixes respectively address issues with the way Thermal Velocity Boost (TVB) was not functioning properly and increased operating voltages due to an unreliable algorithm.
Those are the three main factors involved in the instability on Intel’s side, with the fourth point – and the first point Intel raises – being that the motherboard’s power settings have been improved over Team Blue’s guidelines. That led Intel to clarify new default power settings for CPUs from these two generations.
Analysis: No performance loss is promised with the new solution
Now that this fourth root cause has been revealed, it’s a little worrying that the elevated voltages are occurring during periods when the PC is doing nothing or very little, as this means that the chip degradation is potentially happening at a near-constant rate. As you may recall, Intel has extended the warranty for these processors to five years – but after that, you could still be faced with a CPU that fails earlier than it should, perhaps due to these early-life issues. Not a pleasant thought.
We don’t know when this latest microcode update will arrive – Intel isn’t giving us any kind of time frame – but it will presumably be fairly soon. And it will presumably be the last, as the statement provided is certainly worded as if Intel has concluded its investigation (notably, the investigation was said to be ongoing when the latest microcode update was announced).
As with the previous microcode patch, there will be a delay as Intel works with motherboard manufacturers to ready the new 0x12B update and package it into the various BIOS releases from those hardware vendors. All you can do is keep an eye on your motherboard manufacturer’s website for a new BIOS release, and it’s likely that the next one will include this latest fix.
The good news is that, according to Intel’s tests, the new 0x12B update has no impact on performance when compared to a PC with the first microcode patch applied. This applies to both active applications and games, which remain within the “run-to-run variation” (in other words, the difference is negligible).
That’s just Team Blue’s internal testing mentality, and of course the company notes that “system performance will vary depending on configuration and various other factors,” as always.
Intel has reaffirmed that the issues surrounding increased voltages and other gremlins with Raptor Lake and the current-gen refresh will not affect future CPUs. Team Blue specifically clarifies that this means the next silicon in line, Lunar Lake (laptop chips that have just debuted) and Arrow Lake (desktop processors that are coming soon, plus some high-end laptops) will be released.
There is one notable oddity in the statement, and that is that Intel says the new microcode update will be delivered via a BIOS release to “ensure all Users of Intel Core 13th/14th generation desktop processors” (bold added by us for emphasis).
It was previously announced that all Core i3 and Core i5 (except the 14600K and 13600K) processors were unaffected and did not need to be patched – so will the entire 13th and 14th generation lineup get patched in the coming days? This could simply be an oversight by Intel, and the company could mean that all affected Intel CPUs – we’ll have to wait for further clarification. Those Core i3 and i5 models shouldn’t need a patch now, if they didn’t before.
