Intel (hopefully) concludes Raptor Lake instability saga with a final microcode update

I know 4 people using 13700K and 14700K and they have had no issues, so how many does this really affect?

If they don't implement that microcode then their good fortune might change and remember that Intel is only giving a return for a specific amount of time. If their CPU starts to show issues afterward then they are on their own.
 
If they don't implement that microcode then their good fortune might change and remember that Intel is only giving a return for a specific amount of time. If their CPU starts to show issues afterward then they are on their own.
Until the class action lawsuit kicks in.
 
No I believe in actual facts and proper sources. That is what we use in the university!
I agree with Hom3r here. We already knew it was "enough" by reading that article. If he was looking for something more specific like an estimated percentage of users, then I too am interested in that figure. To answer with "enough" implies it is a pointless question but I think where they drew the line is critical for the future of equipment failures and how we manage expectations. Was it when 2% of processors failed, 10%, higher? I'm very interested in where Intel drew the "we f'd up" line. Very good question Homer.
 
And the sources of these claims? Some random stores across the world? No big resellers said anything. I don't trust it sorry!
I agree with Hom3r here. We already knew it was "enough" by reading that article. If he was looking for something more specific like an estimated percentage of users, then I too am interested in that figure. To answer with "enough" implies it is a pointless question but I think where they drew the line is critical for the future of equipment failures and how we manage expectations. Was it when 2% of processors failed, 10%, higher? I'm very interested in where Intel drew the "we f'd up" line. Very good question Homer.
I respect your skepticism, but it sounds like you just read a few headlines and made up your minds about it. If you research this topic (not saying that you should), you will see that there already is decent data out there reported in first- and second-hand accounts by reputable tech outlets like Level1Techs, Gamers Nexus, Hardware Unboxed, Jayz2Cents, etc. Wendell from Level1Techs had a couple of very good pieces on this topic, and here is one of them. He even shares data from a pretty reliable sample.


And, to those who blame the mobo manufacturers for this issue, Intel bears by far most of the blame. It allowed and even encouraged said manufacturers to do their thing with its processors while failing to implement proper controls in its own microcode and in its guidance to the manufacturers.
 
Last edited:
I know 4 people using 13700K and 14700K and they have had no issues, so how many does this really affect?
Those people you know that have these cpu's might not feel the effect of the problem at this stage doesn't mean the installed cpu wont show signs of deterioration in the future quicker than they should. Plenty of people have been effected other wise Intel wouldn't even be releasing a patch yet alone extending the warranty's for these cpu's for an extended period of time.
 
And that information is coming from what source? Intel itself?

Right... trustworthy...
I don’t think anyone here is gonna do your homework to convince you.

If anything, consider the fact that Intel has retroactively increased the warranty period by 2 years for all these CPUs. That ought to mean something because when has any corporation increased warranty periods out of kindness???
 
Last edited:
Cool, then here are some more actual facts for you to ignore.
I have 10 PCs in my firm with 13 and 14 series CPUs.
3 of them started showing symptoms and within months were unusable for anything more than web browsing.
And all 3 had similar indicators of this flaw.
Started with overheating, then blue screens and the now famous "PAGE_FAULT_IN_NONPAGED_AREA" message. And the Event Viewers showed the "wdf01000.sys" red flag in its log.

All but one already are replaced, but that one is an HP machine so, yeah, that is taking MUCH longer.




Just an FYI, but the internet is also known for ignoring the completely obvious.
3/10 is still an excepion; not a rule. The sum of either resilient or failed cpus is too anectdotal to quantify as assured facts on eithe side.
 
3/10 is still an excepion; not a rule. The sum of either resilient or failed cpus is too anectdotal to quantify as assured facts on eithe side.
3/10 is good enough if you’ve never had 3/10 CPUs fail like that before. Of course, these CPUs could belong to a one-off batch. But this anecdotal evidence was given in response to that other dude who said his friends’ CPUs were fine.

This whole ordeal started with anecdotal evidence, which was then tested at a larger scale and confirmed.

  1. Level1Techs did a fantastic case study using a sizable sample of processors. Wendell provides data figures.
  2. Motherboard manufacturers changed their default Intel CPU profiles to less aggressive ones.
  3. Intel released several microcode updates in quick succession this summer.
  4. Intel increased its warranty for 13- and 14-gen CPUs by 2 years globally.

If that’s not good enough of an indicator, I don’t know what is.
 
Last edited:
3/10 is still an excepion; not a rule. The sum of either resilient or failed cpus is too anectdotal to quantify as assured facts on eithe side.
Really? I can repeat my own, personal, assured facts if you like.
Somehow, saying I have had it worse than others does not change my situation.
And I'm in this situation because of Intel. NO other reason.
 
The higher then intel recommend default profiles? Sure. But the CPU microcode is supposed to protect against that in any case, and it looks like there were MULTIPLE problems Intel had to fix.
It’s a bit of a mix, motherboard vendors probably knows deep down that they’re allowing unsafe levels of voltage to get the competetive edge - historically this would cause great speeds for short bursts - and throttling if you maintain the load on the cpu. In this case, the cpu can suffer permanent damage from these bursts - which should’ve been communicated more clearly.
The microcode fix here isn’t any magic wand fixing anything - they’re working with the third party vendors to limit this voltage back to safe levels.
 
Back