Intel Publishes First Microcode Replace for Raptor Lake Stability Difficulty, BIOSes Going Out Now

Following Intel’s run of monetary woes and Raptor Lake chip stability points, the corporate might use some excellent news on a Friday. And this week they’re delivering simply that, with the primary model of the eagerly awaited microcode repair for desktop Raptor Lake processors – in addition to the primary detailed clarification of the underlying situation.

The brand new microcode launch, model 0x129, is Intel’s first stab at addressing the elevated voltage situation that has seemingly been the reason for Raptor Lake processor degradation over the previous yr and a half. Intel has been investigating the difficulty all yr, and after a sluggish begin, in latest weeks has begun making extra important progress, figuring out what they’re calling an “elevated working voltage” situation in high-TDP desktop Raptor Lake (13^th & 14^th Era Core) chips. Again in late July the corporate was concentrating on a mid-August launch date for a microcode patch to repair (or reasonably, forestall) the degradation situation, and simply forward of that deadline, Intel has begun transport the microcode to their motherboard companions.

Even with this new microcode, nevertheless, Intel isn’t achieved with the soundness situation. Intel remains to be investigating whether or not it’s attainable to enhance the soundness of already-degraded processors, and the general tone of Intel’s announcement could be very a lot that of a beta software program repair – Intel received’t be submitting this particular microcode revision for distribution through working system updates, for instance. So even when this microcode is profitable in stopping ongoing degradation, it appears that evidently Intel hasn’t closed the guide on the difficulty fully, and that the corporate is presumably working in the direction of a repair appropriate for wider launch.

Capping At 1.55v: Elevated Voltages Beget Elevated Voltages

So simply what does the 0x129 microcode replace do? In brief, it caps the voltage of affected Raptor Lake desktop chips at a still-toasty (however in spec) 1.55v. As famous in Intel’s earlier bulletins, extreme voltages appear to be at the reason for the difficulty, so capping voltages at what Intel has decided is the right restrict ought to forestall future chip injury.

The corporate’s letter to the group additionally outlines, for the primary time, simply what’s going on underneath the hood with degraded chips. These chips which have already succumbed to the difficulty from repeated voltage spikes have deteriorated in such a method that the minimal voltage wanted to function the chip – Vmin – has elevated past Intel’s unique specs. In consequence, these chips are now not getting sufficient voltage to function.

Seasoned overclockers will little doubt discover that this can be a acquainted story, as this is among the ways in which overclocked processors degrade over time. In these instances – because it seems to be with the Raptor Lake situation – extra voltage is required to maintain a chip secure, notably in workloads the place the voltage to the chip is already sagging.

And whereas all indicators level to this degradation being irreversible (and a whole lot of RMAs in Intel’s future), there’s a ray of hope. If Intel’s evaluation is right that degraded Raptor Lake chips can nonetheless function correctly with the next Vmin voltage, then there may be the potential of saving at the very least a few of these chips, and bringing them again to stability.

This “Vmin shift,” as Intel is looking it, is the corporate’s subsequent investigative goal. Based on the corporate’s letter, they’re aiming to offer updates by the “finish of August.”

Within the meantime, Intel’s keen motherboard companions have already begun releasing BIOSes with the brand new microcode, with ASUS and MSI even leaping the gun and sending out BIOSes earlier than Intel had an opportunity to correctly announce the microcode. Each distributors are releasing these as beta BIOSes, reflecting the final early nature of the microcode repair itself. And whereas we count on most customers will need to get this microcode in place ASAP to mitigate additional injury on affected chips, it will be prudent to deal with these beta BIOSes as simply that.

Alongside these strains, as famous earlier, Intel is simply distributing the 0x129 microcode through BIOS updates at the moment. This microcode won’t be coming to different programs through working system updates. At this level we nonetheless count on distribution through OS updates to be the tip recreation for this repair, however for now, Intel isn’t offering a timeline or different steerage for when which may occur. So for PC fanatics, at the very least, a BIOS replace is the one strategy to get it for now.

Efficiency Impression: Typically Nil – However Not All the time

Lastly, Intel’s message additionally supplies a little bit of steerage on the efficiency impression of the brand new microcode, based mostly on their inside testing. Beforehand the corporate has indicated that they anticipated no important efficiency impression, and based mostly on their expanded testing, by and huge this stays the case. Nonetheless, there are going to be some workloads that endure from efficiency regressions consequently.

To date, Intel has discovered a few workloads the place they’re seeing regressions. This consists of PugetBench GPU Results Rating and, on the gaming facet of issues, Hitman 3: Dartmoor. In any other case, nearly every part else Intel has examined, together with widespread benchmarks like Cinebench, and main video games, will not be exhibiting efficiency regressions. So the general end result of the repair isn’t fairly a spotless restoration, but it surely’s additionally not resulting in widespread efficiency losses, both.

As for AnandTech, we’ll be digging into this on our personal benchmark suite as time permits. Now we have yet another CPU launch arising subsequent week, so there’s no scarcity of labor to be achieved within the subsequent few days. (Sorry, Gavin!)

Intel’s Full Assertion