Intel finally announces a solution for CPU crashing and instability problems — claims elevated voltages are the root cause; patch coming by mid-August [Updated]

Intel
(Image credit: Tom's Hardware)

Intel has announced that it has found the root cause of the crashing issues plaguing its CPUs. The company will issue a microcode update to address the issues by mid-August, ostensibly ending the long-running saga that began when the first sporadic reports of CPU crashing errors surfaced in December 2022 and grew to a crescendo by the end of 2023. Intel's response comes after complaints about the issue, which causes PCs to inexplicably crash/BSOD during gaming and other workloads, reached a fever pitch in recent weeks. However, the microcode update will not repair impacted processors. Intel also confirmed a rumored issue with via oxidation in its 7nm node, but said those issues were corrected in 2023 and didn't contribute to the failures.

Intel's advisory says an erroneous CPU microcode is the root cause of the incessant instability issues. The microcode caused the CPU to request elevated voltage levels, resulting in the processor operating outside its safe boundaries. Intel is now validating a microcode patch to correct the issues, with its release slated for mid-August. This patch will be distributed through BIOS updates from motherboard OEMs and via Windows updates, so the timing for end-user availability could vary. 

Latest Videos FromTom's Hardware
Paul Alcorn
Editor-in-Chief

Paul Alcorn is the Editor-in-Chief for Tom's Hardware US. He also writes news and reviews on CPUs, storage, and enterprise hardware.

  • bit_user
    Intel said:
    Intel is currently targeting mid-August for patch release to partners
    So, they think they've found the cause and a solution, but they're going to just let this problem fester for another month before a solution can realistically get into the hands of end users??

    Wow, I'm sure glad I don't have a Raptor Lake that's continuing to degrade, in the meantime. You'd think they could at least post some tips for enthusiasts to follow, in order to minimize damage until then. I guess the community is left to follow the advice people have discovered on their own.

    I'm guessing they're trying to ride a knife's edge of undervolting, to avoid sacrificing either too much performance or risking instability due to too little voltage. I'll bet the voltage window is really narrow, at those higher frequencies. That's the main reason I can see why it'd take them so long to perfect their solution, before letting anyone else even have a beta version.
    Reply
  • Notton
    I thought it was the cache or the interconnect between CPU and cache that was burning out?
    Reply
  • Eximo
    Too high of voltage could certainly have that effect.

    Oxidation of vias (degradation) is the rumored underlying symptom, and excess voltage could certainly do that too.
    Reply
  • sergeyn
    Nice that Intel has admitted the problem and got to the root cause of it.
    Reply
  • thestryker
    This would certainly explain why it has taken so long to narrow down and predominantly affects high clocking chips. The T series may be low power, but they have higher boost clocks than i5s.
    bit_user said:
    Wow, I'm sure glad I don't have a Raptor Lake that's continuing to degrade, in the meantime. You'd think they could at least post some tips for enthusiasts to follow, in order to minimize damage until then. I guess the community is left to follow the advice people have discovered on their own.
    So much this as I understand why it's taking so long to fix, but to give no advice as to what to do in the meantime or mitigation techniques is bad. At this point I think Intel needs to add two years to the warranty period for boxed processors.
    Reply
  • DS426
    RMA for what? Get another defective same model or a step down to an i7 or i5? Get money back and then swap out the whole platform for AMD? (I know I would if I was one affected by this problem)

    I just want to know how Intel is going to make it right for the customers. While that's great that they finally came out and said something, they're leaving too many questions on the table this far into the debacle.
    Reply
  • hotaru251
    honestly I dont buy it as the real reason.

    theres claims of MB's that run tame settings that have issue (some server grade ones) and likely voltage on them was never near being too much so even if it was voltage issue likely wouldnt of been too high for those ones yet still had issue.

    this just sounds like a "best excuse w/o getting sued" statement.

    also if it IS true its hilariously comical as Intel's always been joke only getting better by pushing more voltage every generation and it biting em in butt finally would be icing on cake.
    Reply
  • Avro Arrow
    LOL, Intel
    Reply
  • -Fran-
    Hm... This doesn't pass the sniff test for me.

    I'm looking forward to hearing about this fix in systems which run these CPUs 24/7 and independent media/testers.

    Regards.
    Reply
  • phitinh81
    sergeyn said:
    Nice that Intel has admitted the problem and got to the root cause of it.
    Root ? Not so fast.
    Reply