Raptor Lake Degradation Issue (RPLDIE): FAQ 1.0
only processors of the 13th and 14th core generation with an actual Raptor Lake die are potentially affected
processors of the 13th and 14th core generation, which still rely on the Alder Lake die, cannot be affected
Raptor Lake dies at desktop are all K/KF/KS models, all Core i7 & i9, the Core 5-14600 /T, and as well as those in the B0 stepping for the smaller models (rare)
Raptor Lake dies at mobile are all HX models, below which 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 should not be affected, but this remains an open question before a technical justification is available
starting point of all problems is probably too high CPU voltages, which the CPU itself incorrectly applies
affected processors degrade due to excessive voltages and over time
all processors with Raptor Lake die are affected by this, 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 mainly occur in games when compiling shaders, especially in Unreal Engine titles
a frequently occurring error message is “Out of video memory trying to allocate a rendering resource”
this problem can therefore be tested at all UE titles (during shader compilation), although no perfect test is known at present
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 these fixes are part of newer BIOS updates from motherboard manufacturers, the upcoming microcode patch will be included in mid-August
any degradation of the processor can no longer be reversed, the Intel fixes only prevent further degradation
processors that are already unstable are therefore RMA cases
processors that are not yet unstable may nevertheless have already suffered a certain degree of degradation, which reduces their life span
Intel intends to provide a tool with which processors already affected in this way can be identified
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
a manufacturing problem from Intel (“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
updated to v1.03 on Jul 28, 2024
What Raptor Lake users should do now:
1. check whether a Raptor Lake die is actually present
2. in the case of a Raptor Lake die with pre-existing instabilities = RMA case
3. in the case of a Raptor Lake die without existing instabilities:
3.1. install the latest BIOS updates, which force the “Intel Default Settings” and fix the eTBV bug
3.2. waiting for the next BIOS update from mid-August, which Intel intends to use to correct the excessively high voltages
3.3. from this point onwards, the processor should not degrade any further
3.4. waiting for a test tool from Intel to determine the actual degree of degradation
(с)
https://old.reddit.com/r/hardware/co...rpldie_faq_10/