Raptor Lake Degradation Issue (RPLDIE) : FAQ 1.03
Only processors of the 13th and 14th Core generation with actual Raptor Lake die are potentially affected
Processors of the 13th and 14th Core generation, which still use the Alder Lake die, may not be affected
Raptor Lake dies in the desktop have all K/KF/KS models, all Core i7 & i9, the Core i5-14600 /T , as well as those in the B0 stepping (rare) of the smaller models
All HX models have Raptor Lake dies in the notebook, below that it becomes unclear and you have to check for the presence of B0 stepping
can be checked using CPU-Z : an Alder Lake die is displayed as " Revision C0 " (smaller mobile SKUs as " Revision J0 "), a Raptor Lake die as " Revision B0 "
faster processors have a higher chance of actually being affected (Core i7/i9 K/KF/KS models)
According to Intel, mobile processors are not affected, but this remains an open question until a technical justification is available
The starting point of all problems is probably too high CPU voltages, which the CPU itself incorrectly applies
the affected processors degrade due to excessive voltages and over time
Basically, all processors with Raptor Lake die are affected, only the degree of degradation varies from CPU to CPU
The longer the processor runs in this state, the more it deteriorates until one day instabilities occur
the chance of instability with potentially affected processors is low to medium, the majority of users have stable Raptor Lake processors
The instabilities are mainly seen in games when compiling shaders, especially in Unreal Engine titles
A common error message is "Out of video memory trying to allocate a rendering resource"
This problem can be tested for in all UE titles (when compiling shaders), although there is currently no perfect test
As a remedy, Intel recommends its " Intel Default Settings ", the fix for the eTVB bug and the upcoming microcode patch against excessive CPU voltages
all of these fixes are part of newer BIOS updates from motherboard manufacturers, the upcoming microcode patch will be included in this from mid-August
Any degradation of the processor cannot be reversed, the Intel fixes only prevent further degradation
already unstable processors are therefore RMA cases
Processors that are not yet unstable may still have suffered a certain degree of degradation, which reduces their lifespan
Intel wants to provide a tool that can be used to identify processors that are already affected
a recall by Intel is not planned, they probably want to see how well the upcoming microcode patch works and will otherwise replace the affected processors via RMA
It remains unclear how Intel intends to deal with the issue of already degraded but currently still stable processors in the long term
an Intel manufacturing problem ("Oxidation Issue") from March-July 2023 has nothing to do with this (in terms of content) and was already solved in 2023
Sources: primarily Intel statements, but with a lot of reading between the lines
What Raptor Lake users should do now:
1. Check whether there is actually a Raptor Lake die
2. in the case of a Raptor Lake die with existing instabilities = RMA case
3. In the case of a Raptor Lake die without pre-existing instabilities:
3.1. Install the latest BIOS updates that force the "Intel Default Settings" and fix the eTBV bug
3.2. wait for the next BIOS update from mid-August, by means of which Intel wants to correct the excessive voltages
3.3. From this point on, the processor should not degrade further
3.4. Wait for a test tool from Intel, by means of which the actual degree of degradation can be determined
Source, 3DCenter.org
Sent from my SM-S908B using Tapatalk