Intel has finally released a statement on the faulty i9 processors.
The months-long search for the cause of crashing or defective Core i9-14900K and other Intel CPUs has come to an end – more or less.
After a long period of silence, the manufacturer has published a statement in which the issue is addressed in more detail. However, some questions remain.
That’s why this is important: Especially in the last few days, there have been increasing reports from private users and companies that the Core i9-14900K is increasingly struggling with crashes.
As a result, the CPU manufacturer was accused of bringing “defective processors” onto the market. You can find an overview of all the problems here:
In detail: During the night from Monday to Tuesday, Intel published a message in its own support forum referring to the problems surrounding the 13th and 14th generation.
- As a result, Intel was able to determine through “a comprehensive analysis that increased operating voltage causes instability issues in some desktop CPUs.”
- This is “due to a microcode algorithm that leads to incorrect voltage requirements.”
A microcode patch is being provided to resolve the issue, but will not be distributed to partners until mid-August after full validation.
Customers affected by instability should contact Intel Support for further assistance.
The oxidation problems of the 13th and 14th Intel generations alleged by the video portal Gamer's Nexus are said not to be directly related to the problems.
According to Intel, these issues occurred in some earlier 13th generation processors, but only a “small proportion” of the faulty CPUs could be linked to the instability.
Link to YouTube content
Open questions remain
However, this report does not provide complete clarification of the situation. It is still unclear which voltage values are causing the problems and which limits are being exceeded.
There are also no measures that buyers of the Core i9-14900K and the other affected CPUs can take now – after all, not everyone wants or can wait until mid-August.
So at least for now, all we have to do is be patient until mid-August, when Intel releases the promised microcode update. This should finally make it possible to determine the exact values.