Since the damage is already done, it's only a matter of time before everyone encounters instability, so the only real fix is to provide a replacement. The micro code patch might only prevent brand new processors from getting damaged.
If only AM5 supported DDR4, they would already have been market leaders. DDR5 still costs ~2x of DDR4
After going through the statement provided, it's not the processor which is faulty, but the microcode.
If a mere alteration of code will help, why do they want owners to send back their chips?
Because the chips that have already started exhibiting instability are already fried beyond repair. They will continue to degrade and get increasingly unstable.
www.theverge.com
If you have a 13th/14th gen that's running without issues, lower power and Vcore limits manually immediately, and wait until the patch drops.
www.theverge.com
Yes, already mentioned earlier in the thread. If the damage is already done, only option is to get it RMAd.There is no fix for Intel’s crashing 13th and 14th Gen CPUs — any damage is permanent
We got some answers from Intel, and more are on the way.
The patch won’t fix crashing CPUs apparently ( they say this likely cause of the oxidization issues they suspect for some batches).
Even though it's already thought that it would be bad this is the worst possible outcome. Can the cpu run the risk of damaging the motherboard too?There is no fix for Intel’s crashing 13th and 14th Gen CPUs — any damage is permanent
We got some answers from Intel, and more are on the way.
The patch won’t fix crashing CPUs apparently ( they say this likely cause of the oxidization issues they suspect for some batches).
Many home-grown local pre-assembled companies have used the 13th and 14th chips. I wonder if they are aware of this or just simply don't care. And if my concern regarding the potential to damage other components is present then things could get out of hand especially if warranty isn't applicable. What a mess it will be!There is no fix for Intel’s crashing 13th and 14th Gen CPUs — any damage is permanent
We got some answers from Intel, and more are on the way.
If you have a 13th/14th gen that's running without issues, lower power and Vcore limits manually immediately, and wait until the patch drops.
Avoid buying 13th/14th gen on the used market, they might already be unstable. Don't buy brand new either since 15th Gen and AMD 9000 is on the horizon.
This could be catastrophic, If motherboard goes then expect RAM and nvme SSD's to follow and God knows if other connected devices are hit as well.
CPU instability can usually cause WHEA errors, which might corrupt data on storage devices, but nothing else AFAIK. This was one way to tell if a manual OC wasn't 100% stable.
The worst situation to be in is if the processor is partially damaged. The micro code might prevent further degradation but you won't be reaching the performance levels at purchase.There is no fix for Intel’s crashing 13th and 14th Gen CPUs — any damage is permanent
We got some answers from Intel, and more are on the way.
The patch won’t fix crashing CPUs apparently ( they say this likely cause of the oxidization issues they suspect for some batches).
I have a 13600K ... 16 months old, on a Z790 mobo .. working fine till now... no oc or ramping up stock values on cpu & ddr5 ram of 64GB ....
Now the main point - ANYONE OUT HERE ON TE hit by this damm Intel Truth or Lie ?
