For months, Intel’s highest-end desktop gaming processors have had a strange tendency to occasionally cause games to crash — and while you may have seen this earlier today, Intel says it hasn’t yet targeted the 13th generation And the 14th generation Intel Core i9 provides the ultimate solution “Raptor Lake” and “Raptor Lake S” chips have not yet been launched.
“Contrary to recent media reports, Intel no Intel spokesman Thomas Hannaford said in a statement: “We have confirmed the root cause and continue to investigate with our partners regarding issues with unlocked Intel Core 13th and 14th Gen (K/KF/KS). ) User reports of instability issues on desktop processors.
It continued: “The microcode patch cited in the news report fixes an eTVB bug that Intel discovered while investigating reports of instability. While this issue may cause instability, it is not the root cause.
Official Intel statement cites (and partially confirms) leaked internal Intel documents Igor’s laboratory Earlier today. The documents suggest that part of the problem is how Intel’s chips mistakenly overclocked their own cores using a feature called Enhanced Thermal Speed Boost (eTVB), even though they should have known they were running too hot to do so.
“The root cause is incorrect values in the microcode algorithms related to eTVB functionality,” the leaked document begins. It continues:
Failure Analysis (FA) of 13th and 14th Generation K SKU processors has shown that the minimum operating voltage of the affected processors has changed due to accumulated core voltage increases. Intel® analysis has determined that a confirmed contributing factor to this issue is an increase in the voltage input to the processor due to previous BIOS settings that allowed the processor to run at Turbo frequency even when the processor was hot. frequency and voltage operation. Previous generations of Intel® K SKU processors were less sensitive to such settings due to their lower default operating voltage and frequency.
Intel® requires all customers to update BIOS to microcode 0x125 or higher by July 19, 2024.
This microcode includes an eTVB fix for an issue that could allow the processor to enter a higher performance state even if the processor temperature exceeds the eTVB threshold.
However, while Intel confirmed that eTVB may be part of the problem, it is clearly not the “root cause” of the entire problem.
Hopefully we can get a full fix soon.
