Support NeoGAF

[winjer]

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

You'll have to recognize the symptoms of a dying Intel chip yourself, as Intel doesn't have a tool for it yet.

www.tomshardware.com

Intel says it hasn’t developed a reliable tool yet to detect if a Raptor Lake or Raptor Lake Refresh processor has been affected by the instability issue that can permanently damage a chip. Nevertheless, the company told Tom’s Hardware that it “continues to investigate the possibility of a detection tool” and “will issue an update if one becomes available.” The company also clarified its stance on power limits with the new microcode that can mitigate the crashing errors with chips that haven't experienced instability yet.

Several 13th- and 14th-gen Intel Core chips have had instability issues that led to system crashes, but it took a few months for the company to find the root cause. The company finally released its findings in late September, plus a microcode update that is thought to fully address the issue once and for all—at least for processors that a degradation of the clock tree circuit hasn't yet impacted.

Unfortunately, any damage done to your processor cannot be reversed by the microcode update. So, even if you install it as soon as it comes out for your motherboard, you might still experience some instability.

Aside from the microcode code updates, the chipmaking giant has advised everyone to stick to the Intel Default Settings as part of the mitigation against the Vmin shift causing the instability issues. However, there are a few caveats. “The microcode update 0x12B (which includes previous microcode updates 0x125 and 0x129), in addition to Intel Default settings, is the full mitigation for the Intel 13th and 14th Generation Desktop Processor Vmin Shift Instability issue,” Intel said.

A tool that can detect whether a CPU already has damage from voltage degradation, could be very useful for users to identify problems, in a pre-emptive way. Rather than waiting to get crashes and having to troubleshoot the system, just to check it's not something else.

 

[Chiggs]

Alternative method: