Tuesday, July 23rd 2024

Intel Statement on 13th and 14th Gen Core Instability: Faulty Microcode Causes Excessive Voltages, Fix Out Soon

Long-term reliability issues continue to plague Intel's 13th Gen and 14th Gen Core desktop processors based on the "Raptor Lake" microarchitecture, with users complaining that their processors have become unstable with heavy processing workloads, such as games. This includes the chips that have minor levels of performance tuning or overclocking. Intel had earlier isolated many of these stability issues to faulty CPU core frequency boosting algorithms, which it addressed through updates to the processor microcode that it got motherboard- and prebuilt manufacturers to distribute as UEFI firmware updates. The company has now come out with new findings of what could be causing these issues.

In a statement Intel posted on its website on Monday (22/07), the company said that it has been investigating the processors returned to it by users under warranty claims (which it has been replacing under the terms of its warranty). It has found that faulty processor microcode has been causing the processors to operate under excessive core voltages, leading to their structural degradation over time. "We have determined that elevated operating voltage is causing instability issues in some 13th/14th Gen desktop processors. Our analysis of returned processors confirms that the elevated operating voltage is stemming from a microcode algorithm resulting in incorrect voltage requests to the processor."
Modern processor power management runs on an intricate clockwork of collaboration between software, firmware, and hardware, with the software constantly telling the hardware what levels of performance it wants, and the hardware managing its power- and thermal budgets by rapidly altering the power and clock speeds of the various components, such as CPU cores, caches, fabric, and other on-die components. A faulty collaboration between any of the three key components could break this clockwork, as has happened in this case.

Intel is releasing yet another microcode update to its 13th- and 14th Gen Core processors, which will address not just the faulty boosting algorithm issue the company unearthed in June, but also the faulty voltage management the company discovered now. This new microcode should be released some time around mid-August to partners (motherboard manufacturers and PC OEMs), who will then need to validate it on their machines, before passing it along to end-users as UEFI firmware updates.
Intel is delivering a microcode patch which addresses the root cause of exposure to elevated voltages. We are continuing validation to ensure that scenarios of instability reported to Intel regarding its Core 13th/14th Gen desktop processors are addressed. Intel is currently targeting mid-August for patch release to partners following full validation. Intel is committed to making this right with our customers, and we continue asking any customers currently experiencing instability issues on their Intel Core 13th/14th Gen desktop processors reach out to Intel Customer Support for further assistance, the company stated.
It's important to note here, that the microcode update won't fix the issues on processors already experiencing instability, but prevent it on chips that aren't. The instability is caused by irreversible physical degradation of the chip. These chips will, of course, be covered under warranty.

Meanwhile, an interesting issue has come to light, which that some of Intel's processors built on the Intel 7 node are experiencing chemical oxidation of the die as they age. Intel responded to this, stating that it had discovered the oxidation manufacturing issues in 2023, and addressed it. The company also stated that die oxidation is not related to the stability issues it is embattled with.
We can confirm that the via Oxidation manufacturing issue affected some early Intel Core 13th Gen desktop processors. However, the issue was root caused and addressed with manufacturing improvements and screens in 2023. We have also looked at it from the instability reports on Intel Core 13th Gen desktop processors and the analysis to-date has determined that only a small number of instability reports can be connected to the manufacturing issue, the company stated.
If you feel your chip might be affected, you can file for an RMA.
Sources: Intel Community, Intel (Reddit)
Add your own comment

216 Comments on Intel Statement on 13th and 14th Gen Core Instability: Faulty Microcode Causes Excessive Voltages, Fix Out Soon

#26
JWNoctis
TomorrowNvidia Bumpgate ~2008. Permanently ruined their relationship with Apple. Nvidia blamed TSMC for it.
Was that the faulty GeForce 8-series GPU? I thought that one was faulty packaging. But yes, it's close.
Posted on Reply
#27
j_N_k
fevgatosSo amd overvolted their 3d chips in order to compete turning them into handgrenades and then Intel overvolted theirs resulting in crashes. Lovely market, competition is great
It was not amd who overvolted the cpus but the motherboard manufacturers with their bioses.

X3D cpus are voltage limited so overvolting them serve no purpose, especially if they are already winning.
Posted on Reply
#28
Tomorrow
JWNoctisWas that the faulty GeForce 8-series GPU? I thought that one was faulty packaging. But yes, it's close.
The Nvidia Bumpgate controversy refers to a significant issue that emerged around 2008 involving defective Nvidia graphics processing units (GPUs). These defects were primarily associated with the materials and manufacturing processes used in the GPUs, leading to widespread failures in laptops and other devices. Here are the key aspects of the controversy:

### 1. **Defective GPUs**
The problem was linked to a specific packaging material used in the GPUs. The solder bumps, which connect the GPU die to the package substrate, were prone to cracking under heat and stress. This was exacerbated by thermal cycling (repeated heating and cooling) which is common in laptop usage.

### 2. **Affected Devices**
The defective GPUs were used in a range of laptops from major manufacturers, including Dell, HP, Apple, and others. Users began reporting issues such as graphical artifacts, system crashes, and complete device failures.

### 3. **Nvidia’s Response**
Initially, Nvidia was slow to acknowledge the extent of the problem. However, as the issue became more widespread, Nvidia took some responsibility and set aside a substantial sum of money (around $200 million) to cover warranty claims and repairs.

### 4. **Legal and Financial Repercussions**
The controversy led to several class-action lawsuits against Nvidia and the affected laptop manufacturers. These lawsuits alleged that both Nvidia and the manufacturers knew about the defects but continued to sell the affected products without adequately informing consumers.

### 5. **Settlement and Compensation**
Eventually, Nvidia and the manufacturers reached settlements with affected consumers. These settlements typically involved extending warranties, offering free repairs, and in some cases, providing replacement devices.

### 6. **Impact on Reputation**
The Bumpgate controversy significantly impacted Nvidia's reputation. It highlighted the challenges of maintaining quality control in complex semiconductor manufacturing processes and underscored the importance of transparent communication with consumers when defects are discovered.

### 7. **Technical Specifics**
The issue was traced back to the high-lead solder bumps used in the GPUs, which were less reliable under the thermal stresses of laptop operation compared to more resilient materials like eutectic solder.

The Bumpgate controversy remains a notable example of the complexities and risks involved in high-tech manufacturing, as well as the potential consequences when these risks are not managed effectively.
Posted on Reply
#30
JWNoctis
So it was sufficiently well-known that ChatGPT could give a canny summary. Great.

Interesting how history repeats itself.
Posted on Reply
#31
Dr_b_
So many questions, how long did intel know about this? Is this really the only factor? What other CPU's might be or are impacted by this? Even if totally true, its going to be hard to convince the public otherwise. The performance/watt of Arrow Lake would have to be 2X that of Zen5 X3D, and Zen5 would have to be a hot unstable mess before considering it, and the likelihood of that happening is near zero. GG intel, are you sure you aren't in their rear view mirror now?
Posted on Reply
#32
Dr. Dro
TomorrowNvidia Bumpgate ~2008. Permanently ruined their relationship with Apple. Nvidia blamed TSMC for it.
That was actually around ~2006, though? Bumpgate affected G80 and its smaller subvariants, particularly in mobile where temperatures were higher and thermal expansion/contraction cycles punished the interposer more. By 2008 Nvidia was already moving to TSMC 55 nm process with GT200B (GTX 260 216, 275, 285, 295), from the original 65 nm GT200 (260 with 192 cores, 280). I believe G92 was not affected (9800 GTX, GTS 250)
JWNoctisWas that the faulty GeForce 8-series GPU? I thought that one was faulty packaging. But yes, it's close.
Yes.
Posted on Reply
#33
Zubasa
fevgatosSo amd overvolted their 3d chips in order to compete turning them into handgrenades and then Intel overvolted theirs resulting in crashes. Lovely market, competition is great
What did AMD overvolt to compete with?
The culprit was mostly just board makers trying to out do each other, AMD responsible for not gate keeping enough.
FYI the issue with VSOC has nothing to do with Vcore or much to do with performance at all.
The memory settings AMD used in their benchmarks nor just about every review (DDR5 6000) did not require high Vsoc.
Some boards wanted to claim DDR5 6600 support and cranked up the Vsoc hoping for the best. You put the same ram and same CPUs in different boards can result in vastly different Vsoc.

The stock Vsoc of Raphael is only around 1V. The 1.4V+ that Asus fed into the IOD resulted in well over double the SOC power.
The new limit of 1.3V Vsoc still gives you around a 200% margin over stock, that seems pretty reasonable.




The stock V/F curve of 13/14th gen on the other hand is programe by Intel at the factory, and this is killing chips running at stock without any OC.
Posted on Reply
#34
azrael
j_N_kIt was not amd who overvolted the cpus but the motherboard manufacturers with their bioses.

X3D cpus are voltage limited so overvolting them serve no purpose, especially if they are already winning.
ZubasaWhat did AMD overvolt to compete with?
FYI the issue with VSOC has nothing to do with Vcore or much to do with performance at all.
The memory settings AMD used in their benchmarks nor just about every review (DDR5 6000) did not require high Vsoc.
Some boards wanted to claim DDR5 6600 support and cranked up the Vsoc hoping for the best. You put the same ram and same CPUs in different boards can result in vastly different Vsoc.

The stock Vsoc of Raphael is only around 1V. The 1.4V+ that Asus fed into the IOD resulted in well over double the SOC power.
The new limit of 1.3V Vsoc still gives you around a 200% margin over stock, that is pretty reasonable.

The V/F curve of 13/14th gen on the other hand is programe by Intel at the factory, and this is killing chips running at stock without any OC.
So it seems I didn't remember incorrectly. From what I do remember it was a board issue (well, manufacturers running things out of specs for that teeeny little bit of bragging power). AMD did take the blame on themselves, though, and replaced the CPUs.

As for that voltage issue Intel now seems to blame, from what I can tell, they don't as much talk about the voltage going into the chip, but how said power is distributed internally. Which apparently is in a way resulting in these defects.
Posted on Reply
#35
dj-electric
I have always deemed Intel's YOLO behavior with boosts since 12th gen a questionable one. I'm no silicon engineer, but when ones literally behind the tech mention that tolerances are being tested, who am i to doubt anything.
When I run intel for personal use, its being done with conservative V/F values. I'm not going to gain any significant performance by torture testing these chips anyway.
The sad part of this whole story to me is the fact most users will never know about this issue, and also aren't tech savvy enough to get into voltage tuning to prevent any longer term damages.

This, despite a possible microcode update, stands quite exposed to a regulatory problem Intel will have to face in court.
Posted on Reply
#36
Zubasa
azraelSo it seems I didn't remember incorrectly. From what I do remember it was a board issue (well, manufacturers running things out of specs for that teeeny little bit of bragging power). AMD did take the blame on themselves, though, and replaced the CPUs.

As for that voltage issue Intel now seems to blame, from what I can tell, they don't as much talk about the voltage going into the chip, but how said power is distributed internally. Which apparently is in a way resulting in these defects.
Yes as said, while AMD had the responibility of keeping an eye on what the boards were doing, overall it was initiated by the board partners.
Also FYI anandtech tested different AGESA and bios versions on Asrock boards, and it seems they kept out of the Vsoc (VDDCR SOC) insanity.
AGESA 1.0.0.5c to 1.0.0.7 Firmware Testing: Temps, Voltages, Currents, and Power - Voltage Lockdown: Investigating AMD's Recent AM5 AGESA Updates on ASRock's X670E Taichi (anandtech.com)

Posted on Reply
#37
Tomorrow
Dr. DroI believe G92 was not affected (9800 GTX, GTS 250)
I remember a 9800 GT that i put in the oven a couple of times to fix it. So it defenetly had the same solder issue as my G80 based 8800 GTS 320.
Posted on Reply
#38
Assimilator
Please can we keep discussions about G80/G92 bumpgate, and AMD CPU voltage, as minimal as possible to prevent this thread from being derailed and thus locked by mods?

Thank you.
Posted on Reply
#39
Zubasa
AssimilatorPlease can we keep discussions about G80/G92 bumpgate, and AMD CPU voltage, as minimal as possible to prevent this thread from being derailed and thus locked by mods?

Thank you.
I suspect that is the goal of some of the comments with "whataboutism".
Get the discussion derailed and hopefully shield Intel from further discussion/critisim.
Posted on Reply
#40
Crackong
Intel (Malfunction) Inside ...

Posted on Reply
#41
RGAFL
fevgatosSo amd overvolted their 3d chips in order to compete turning them into handgrenades and then Intel overvolted theirs resulting in crashes. Lovely market, competition is great
Please get this right, AMD did not release overvolted or faulty CPUS. Certain motherboard companies pumped a little to much SOC voltage to it which resulted in the CPUS not working. To put the blame on AMD is a bit desperate to divert blame away from Intel to say the least.

What is not at fault is that Intel have a major design problem and have stayed radio silent until called out on it while knowing there is a fault.

To put it as simply as these are crashing is also belittling the problem. These are crashing and degrading.

You want to see the extent of the problem look here.




Posted on Reply
#42
JWNoctis
ZubasaI suspect that is the goal of some of the comments of whataboutism.
Get the discussion derailed and hopefully shield Intel from further discussion/critisim.
Seeing how that sprung from a semi-rhetorical question for previous, similar, occurrences, guess I should have known better. Sorry about how that turned out.

Still interesting how things are repeating themselves.
Posted on Reply
#43
mtosev
Intel fucked up big time.
Posted on Reply
#44
Rabit
hm... I know some guys running i9 12900k at 1,56V for years now no issue, in my humble opinion 13 gen architectures changes caused CPUs to no longer tolerate high voltages.
Posted on Reply
#45
Daven
fevgatosSo amd overvolted their 3d chips in order to compete turning them into handgrenades and then Intel overvolted theirs resulting in crashes. Lovely market, competition is great
This is pure bothersiderism bull that no one should listen to. Intel boasted that their chips were extremely stable versus the competition because reasons and blamed everyone (motherboard manufacturers especially) but themselves when their products turned out to be anything but stable.

Add statements from the CEO such as ‘geostability’ when it come to manufacturing and Intel looks like a scam company. Theranos esque comes to mind.

www.axios.com/2021/10/18/intel-semiconductor-chips-national-security

Intel should be boycotted and denied government funding until they spin off their fabs and forced to concentrate on actually making stable high quality products.
Posted on Reply
#46
RGAFL
Also reports of a major OEM that had 8 million 13th and 14th gen Intel CPUS and 35% (yes 35%) of them were faulty at initial testing. That's without the degradation that may happen in the future.

Don't worry, it's only a small problem.
Posted on Reply
#47
kondamin
Rabithm... I know some guys running i9 12900k at 1,56V for years now no issue, in my humble opinion 13 gen architectures changes caused CPUs to no longer tolerate high voltages.
The vast ocean of AVX512 mostly idle silicon acting like some sort of capacitance buffer?
Posted on Reply
#48
fevgatos
Rabithm... I know some guys running i9 12900k at 1,56V for years now no issue, in my humble opinion 13 gen architectures changes caused CPUs to no longer tolerate high voltages.
No he doesn't. He is lying to you. No way he is running 1.56 for more than 5 minutes.
DavenThis is pure bothersiderism bull that no one should listen to. Intel boasted that their chips were extremely stable versus the competition because reasons and blamed everyone (motherboard manufacturers especially) but themselves when their products turned out to be anything but stable.

Add statements from the CEO such as ‘geostability’ when it come to manufacturing and Intel looks like a scam company. Theranos esque comes to mind.

www.axios.com/2021/10/18/intel-semiconductor-chips-national-security

Intel should be boycotted and denied government funding until they spin off their fabs and forced to concentrate on actually making stable high quality products.
Can you stop talking about amds handgrenades and focus on the topic? Thanks.
Posted on Reply
#49
Assimilator
Given this is a microcode fix, it will be delivered as a Windows update - no new BIOS version or end-user action needed. That's at least a relief for Intel and its board partners.
Posted on Reply
#50
RGAFL
AssimilatorGiven this is a microcode fix, it will be delivered as a Windows update - no new BIOS version or end-user action needed. That's at least a relief for Intel and its board partners.
Pretty sure this will need to be a bios update.
Posted on Reply
Add your own comment
Jul 23rd, 2024 13:36 EDT change timezone

New Forum Posts

Popular Reviews

Controversial News Posts