Friday, June 14th 2024
![Intel](https://tpucdn.com/images/news/intel-v1723816949774.png)
Intel Isolates Root Cause of Raptor Lake Stability Issues to a Faulty eTVB Microcode Algorithm
Intel has identified the root cause for stability issues being observed with certain high-end 13th- and 14th Gen Core "Raptor Lake" processor models, which were causing games and other compute-intensive applications to randomly crash. When the issues were first identified, Intel recommended a workaround that would reduce core-voltages and restrict the boost headroom of these processors, which would end up with reduced performance. The company has apparently discovered the root cause of the problem, as Igor's Lab learned from confidential documents.
The documents say that Intel isolated the problem to a faulty value in the microcode's end of the eTVB (enhanced thermal velocity boost) algorithm. "Root cause is an incorrect value in a microcode algorithm associated with the eTVB feature. Implication Increased frequency and corresponding voltage at high temperature may reduce processor reliability. Observed Found internally," the document says, mentioning "Raptor Lake-S" (13th Gen) and "Raptor Lake Refresh-S" (14th Gen) as the affected products.The company goes on to elaborate on the issue in its Failure Analysis (FA) document:
Source:
Igor's Lab
The documents say that Intel isolated the problem to a faulty value in the microcode's end of the eTVB (enhanced thermal velocity boost) algorithm. "Root cause is an incorrect value in a microcode algorithm associated with the eTVB feature. Implication Increased frequency and corresponding voltage at high temperature may reduce processor reliability. Observed Found internally," the document says, mentioning "Raptor Lake-S" (13th Gen) and "Raptor Lake Refresh-S" (14th Gen) as the affected products.The company goes on to elaborate on the issue in its Failure Analysis (FA) document:
Failure Analysis (FA) of 13th and 14th Generation K SKU processors indicates a shift in minimum operating voltage on affected processors resulting from cumulative exposure to elevated core voltages. Intel analysis has determined a confirmed contributing factor for this issue is elevated voltage input to the processor due to previous BIOS settings which allow the processor to operate at turbo frequencies and voltages even while the processor is at a high temperature. Previous generations of Intel K SKU processors were less sensitive to these type of settings due to lower default operating voltage and frequency.Identifying the root cause of the problem isn't the only good news, Intel also has a new microcode ready for 13th Gen and 14th Gen Core processors (version: 0x125), for motherboard manufacturers and PC OEMs to encapsulate into UEFI firmware updates. This new microcode corrects the issue, which should restore stability of these processors at their normal performance. Be on the lookout for UEFI firmware (BIOS) updates from your motherboard vendor or prebuilt OEM.
107 Comments on Intel Isolates Root Cause of Raptor Lake Stability Issues to a Faulty eTVB Microcode Algorithm
Restore stability at their nominal performance, sure. Lower tolerances and you get same performance. Make it make sense.
But the key point is raptor lake was factory-pushed further to the limit (of stability) than previous Lakes.
And Intel states that it is "still investigating" looking for a root cause.
The bottom line is Intel pushed these chips too hard due to the fundamental design not matching AMD chips.
www.techpowerup.com/321959/intel-statement-on-stability-issues-motherboard-makers-to-blame
It looks like Intel owes a lot of apologies. Oops. :slap:
"Win_Benchmarks_At_Any_Cost=YES"
And this is the fix
"Win_Benchmarks_At_Any_Cost=NO"
I expect now the push for better bios defaults will suddenly vanish, as Intel will want this out the news asap, and the board vendors will want to continue pushing bios's that default to out of spec. The solution for both of those is to let the bios situation drop. They are still not innocent, running the spec does stabilise chips. Just looks like there is 2 triggers to the problem.
Pat is a criminal genius. lol