Comment

Comment on There is no fix for Intel’s crashing 13th and 14th Gen CPUs — any damage is permanent

tal@lemmy.today ⁨1⁩ ⁨month⁩ ago

They do say that you can contact Intel customer support if you have an affected CPU, and that they’re replacing CPUs that have been actually damaged. I don’t know – and Intel may not know – what information or proof you need, but my guess is that it’s good odds that you can get a replacement CPU. So there probably is some level of recourse.

Now, obviously that’s still a bad situation. You’re out the time that you didn’t have a stable system, out the effort you put into diagnosing it, maybe have losses from system downtime (like, I took an out-of-state trip expecting to be able to access my system remotely and had it hang due to the CPU damage at one point), maybe out data you lost from corruption, maybe out money you spent trying to fix the problem (like, on other parts).

But I’d guess that specifically for the CPU, if it’s clearly damaged, you have good odds of being able to at least get a non-damaged CPU at some point without needing to buy it.

source

Sort:hotnew top

RootBeerGuy@discuss.tchncs.de ⁨1⁩ ⁨month⁩ ago
Replacing it with what exactly. Another 13/14th gen chip?

source
- tal@lemmy.today ⁨1⁩ ⁨month⁩ ago
  Yeah. They can’t replace it with their upcoming 15th gen, because that uses a new, incompatible socket. They’d apparently been handing them out to large customers to replace failed processors, according to one of Steve Burke’s past videos on the subject.
  
  On a motherboard that has the microcode update which they’re theoretically supposed to get out in a month or so, the processors should at least refrain from destroying themselves, though I expect that they’ll probably run with some degree of degraded performance from the update.
  
  source
MudMan@fedia.io ⁨1⁩ ⁨month⁩ ago
"Clearly damaged" is an interesting problem. The CPU would crash 100% of the time on the default settings for the motherboard, but if you remember, they issued a patch already.

I patched. And guess what, with the new Intel Defaults it doesn't crash anymore. But it suddenly runs very hot instead. Like, weird hot. On a liquid cooling system it's thermal throttling when before it wouldn't come even close. Won't crash, though.

So is it human error? Did I incorrectly mount my cooling? I'd say probably not, considering it ran cool enough pre-patch until it became unstable and it runs cool enough now with a manual downclock. But is that enough for Intel to issue a replacement if the system isn't unstable? More importantly, do I want to have that fight with them now or to wait and see if their upcoming patch, which allegedly will fix whatever incorrect voltage requests the CPU is making, fixes the overheating issue? Because I work on this thing, I can't just chuck it in a box, send it to Intel and wait. I need to be up and running immediately.

So yeah, it sucks either way, but it would suck a lot less if Intel was willing to flag a range of CPUs as being eligible for a recall.

As I see it right now, the order of operations is to wait for the upcoming patch, retest the default settings after the patch and if the behavior seems incorrect contact Intel for a replacement. I just wish they would make it clearer what that process is going to be and who is eligible for one.

source