Intel has yet to develop a tool to detect whether or not a device is affected by the crash problem that occurs with 13th and 14th generation CPUs



Intel's 13th generation Core processor 'Raptor Lake' and 14th generation Core processor 'Raptor Lake Refresh' have a flaw that causes applications to crash or terminate, and Intel has acknowledged its existence. Although several months have passed since Intel acknowledged the existence of the flaw, it has become clear that the company has not yet been able to develop a tool to detect whether or not a crash problem has been affected.

Intel doesn't have a tool to detect if a chip is affected by crashing errors yet — Intel Default Settings still recommended after patch is applied, but power limits can be raised | Tom's Hardware
https://www.tomshardware.com/pc-components/cpus/intel-doesnt-have-a-tool-to-detect-if-a-chip-is-affected-by-crashing-errors-yet-chipmaker-recommends-intel-default-settings-even-after-0x12b-patch-is-applied



Beginning in early 2024, users of Intel's 13th and 14th generation Core processors began reporting frequent game crashes. Initially, it was speculated that the cause was processor power consumption, but in April 2024, Intel reported that the cause was the use of overclocked motherboards.

However, some users were not convinced by this report and were trying to find out the cause . Then, in July 2024, Intel admitted that the defects in the 13th and 14th generation CPUs, such as 'game crashes' and 'software not working properly,' were 'caused by their own microcode.'

Intel finally admits that its own designs are causing problems with its 13th and 14th generation CPUs - GIGAZINE



Intel has released multiple microcode updates to mitigate crash issues with 13th and 14th generation CPUs, with the third update released in September 2024. The third update fixes the problem seen in 13th and 14th generation CPUs where 'abnormal voltage rise occurs when idle or under light load.'

Intel releases third update for 13th and 14th generation CPUs with frequent crashes - GIGAZINE



However, this microcode update cannot undo the damage caused when the crash issue occurs, but Intel has announced an additional two-year warranty for all affected CPUs.

The list of CPUs that qualify for an additional 2-year warranty is as follows:

- 13th generation Core processor
i9-13900KS
i9-13900K
i9-13900KF
i9-13900F
i9-13900
i7-13700K
i7-13700KF
i7-13790F
i7-13700F
i7-13700
i5-13600K
i5-13600KF

- 14th generation Core processor
i9-14900KS
i9-14900K
i9-14900KF
i9-14900F
i9-14900
i7-14700K
i7-14700KF
i7-14790F
i7-14700F
i7-14700
i5-14600K
i5-14600KF

When technology media Tom's Hardware reached out to Intel, the company acknowledged that it has not yet been able to develop a reliable tool to detect whether or not a system is affected by the crash issue. Intel responded to Tom's Hardware only by saying that it is 'continuing to investigate the possibility of a detection tool' and that 'an update will be released when available.' Additionally, Intel said that it plans to release new microcode to mitigate the error on CPUs that are not affected by the crash issue.

In addition to the microcode update, Intel recommends using Intel's official power profile 'Intel Default Settings' as a measure to mitigate the Vmin (minimum operating voltage) that causes the crash problem. In addition, 'In addition to the Intel Default Settings, microcode '0x12B' (0x125 and 0x129) is also a complete mitigation for the Vmin shift instability issue on Intel's 13th and 14th generation CPUs.'

Although Intel recommends using the default power profile even after applying the microcode update, users are free to increase the PL1 and PL2 power limits beyond the 'recommended values' (up to 4096W) with some restrictions, such as keeping safety settings like IccMax enabled to receive the warranty.

In addition, Intel warned that 'users who wish to overclock or use higher power delivery settings than recommended do so at their own risk, although overclocking may void the warranty or affect the health of the system.'

in Hardware, Posted by logu_ii