Intel's Biggest Failure in Years: Confirmed Oxidation & Excessive Voltage

Gamers Nexus
23 Jul 202426:56

Summary

TLDRIntel has acknowledged oxidation and voltage issues with its 13th generation CPUs, leading to instability and potential CPU failure. The company initially downplayed the oxidation problem, only admitting it after public pressure. Tech outlets and users report high failure rates, and Intel's lack of transparency and delayed response have raised concerns. Consumers are advised to update BIOS and microcode, while those experiencing instability should consider RMA. The situation casts doubt on Intel's reliability and requires a clear commitment to customer support.

Takeaways

  • 😨 Intel has admitted to oxidation issues with its 13th gen CPUs, which were initially only partially disclosed in a statement focusing on voltage issues.
  • 🔍 The oxidation problem was identified during the gate formation process in the CPU manufacturing, potentially leading to corrosion and instability.
  • 💻 Intel's initial public statement did not mention oxidation, only addressing voltage and microcode changes, which was seen as misleading by some.
  • 🤔 The company's handling of the situation has been criticized for lack of transparency and slow response, raising questions about internal disorganization or calculated obfuscation.
  • 🛠️ Intel is planning microcode and BIOS updates to address the instability issues, but the exact impact on performance is yet to be determined.
  • 🚫 Intel reportedly rejected some RMAs (Return Merchandise Authorizations) for B2B and B2C CPUs during the period when they were aware of the oxidation issue, which has been deemed inexcusable.
  • 📅 The exact date range of affected CPUs has not been clearly specified by Intel, leading to confusion and a call for more transparency in identifying affected products.
  • 💡 Consumers are advised to update their BIOS and keep an eye out for Intel microcode changes, especially if experiencing system instability.
  • 🚨 There are concerns that affected CPUs might be problematic in the used market, with sellers potentially not disclosing their instability issues.
  • 🔎 Ongoing discussions and investigations are happening, with some users reporting high failure rates, indicating the severity of the issue in certain environments.

Q & A

  • What issue did Intel admit to regarding its 13th gen CPUs?

    -Intel admitted to issues with oxidation and voltage problems in its 13th gen CPUs, which could cause instability and potential chip failure.

  • What is the significance of the oxidation issue mentioned in the script?

    -The oxidation issue is significant because it's a physical hardware-level defect that occurs during the fabrication process and could lead to corrosion, instability, and eventual chip failure.

  • What is the role of microcode changes in addressing the CPU instability issues?

    -Microcode changes are part of the solution to address the instability issues caused by elevated operating voltages. These changes aim to correct the algorithm that results in incorrect voltage requests to the processor.

  • Why is there criticism regarding Intel's communication about the oxidation issue?

    -Criticism arises because Intel initially published a statement addressing only voltage issues and later appended information about the oxidation issue to a Reddit post, which seemed less transparent and potentially misleading.

  • What is the expected impact of the microcode and BIOS updates on affected CPUs?

    -The microcode and BIOS updates are expected to resolve the instability issues caused by elevated voltages. However, the long-term impact on CPUs that have been exposed to excessive voltage for a long time is uncertain and may require further evaluation.

  • What actions should consumers take if they own 13th or 14th gen Intel CPUs?

    -Consumers should update their BIOS and keep an eye out for Intel's microcode updates. If they experience any system instability, they should consider applying for an RMA.

  • What is the potential impact of the CPU issues on business customers like server providers?

    -The CPU issues can lead to server instability, which may result in significant financial damages due to players abandoning games or services, thinking the problem lies with the software rather than the hardware.

  • What is the 'Asus treatment' mentioned in the script referring to?

    -The 'Asus treatment' refers to a situation where a company must revisit and reprocess all rejected RMAs, evaluating whether customers were owed replacements based on new information or admissions about product issues.

  • What does the script suggest about the transparency and communication from Intel regarding the CPU issues?

    -The script suggests that Intel's communication has been lacking in transparency, with important information about the oxidation issue not being disclosed promptly or clearly, leading to public pressure and criticism.

  • What is the script's recommendation for consumers experiencing instability with their Intel CPUs?

    -The script recommends that consumers experiencing instability should apply for an RMA, as the potential for irreparable damage from long-term exposure to excessive voltage makes it uncertain whether updates will fully resolve issues.

  • What steps does Intel need to take to address the concerns raised in the script?

    -Intel needs to provide clear information on affected CPU date ranges, offer warranty extensions, commit to supporting customers with affected CPUs, and ensure transparency in communication about the issues and their resolution.

Outlines

00:00

😕 Intel's Oxidation and Voltage Issues Acknowledgment

Intel has admitted to oxidation and voltage issues affecting its 13th generation CPUs. Initially, the company only addressed voltage concerns in a public statement, leaving out the oxidation problem which was later mentioned in a Reddit post. This has led to speculations of disorganization or a deliberate attempt to downplay the severity. The oxidation issue is tied to the manufacturing process and cannot be resolved with a software patch, unlike the voltage issue which Intel plans to fix with a microcode update and BIOS changes from vendors. Intel's handling of the situation, including the rejection of some RMAs during the known oxidation period, has been criticized as irresponsible and lacking transparency.

05:01

😠 Lack of Transparency and Customer Support from Intel

The video script criticizes Intel for its unclear communication regarding the oxidation issue, which only came to light after significant public pressure. Intel's statements have been inconsistent, initially attributing instability solely to voltage issues, then later acknowledging a connection to oxidation in a Reddit comment. The lack of detailed support plans, such as affected CPU date ranges or warranty extensions, is highlighted as a failure to adequately address customer concerns. The community is calling for transparency, including clear communication of the extent of the issues and concrete steps to support affected customers.

10:03

😡 Contradictions and Concerns Over Intel's Oxidation Statement

Intel's statement on the oxidation issue has been criticized for its vagueness and internal contradictions. While the company confirmed a manufacturing issue with via oxidation in 2023, it failed to provide specific date codes or means to identify affected CPUs. The script points out that Intel's claim that the oxidation issue is not related to instability is directly contradicted by its own statement that a small number of instability reports are connected to the manufacturing issue. This has led to further skepticism and calls for a re-evaluation of rejected RMAs from customers who may have been unfairly denied support.

15:03

😤 High Failure Rates and the Impact on Business Customers

The script discusses the significant impact of Intel's CPU issues on business customers, such as game developers and server providers, who have reported high failure rates and instability. The potential long-term effects of the oxidation issue, which could cause permanent damage and degrade performance over time, are a major concern. The lack of awareness among users about the need for microcode updates and BIOS changes is also highlighted, emphasizing the need for active outreach from Intel to ensure all customers are informed and protected.

20:05

🚫 Recommendations and Precautions for Consumers and Intel

The script offers guidance for consumers on dealing with the Intel CPU issues, advising caution in the secondhand market and urging owners of 13th or 14th gen CPUs to update their BIOS and watch for microcode changes. For those experiencing instability, the recommendation is to apply for an RMA. The script also calls for Intel to provide clear commitments on warranty support and to avoid recommending Intel CPUs until the microcode update is released and the company provides firm assurances on customer support.

25:07

🔬 Independent Testing and Future Recommendations

The script outlines plans for independent testing of Intel CPUs under official guidance once the microcode updates are released. It states that the current stance is to avoid recommending Intel's 13th and 14th gen CPUs until the updates are verified and Intel provides clear commitments on warranty and performance. The script also hints at potential issues beyond voltage and oxidation, suggesting that motherboards and other factors may contribute to the instability, and promises to continue following the story and update the community as new information becomes available.

Mindmap

Keywords

💡Oxidation

Oxidation, in the context of the video, refers to a chemical reaction where a material loses electrons and bonds with oxygen. It is a critical manufacturing issue that Intel faced with its 13th generation CPUs, where oxidation of the vias occurred during the gate formation process. This issue is central to the video's theme as it discusses the impact of oxidation on CPU stability and the subsequent steps Intel took to address it.

💡Voltage Issues

Voltage Issues in this script denote problems related to the electrical potential supplied to the CPU, which can cause instability. The video discusses Intel's admission of these issues with its 13th and 14th generation processors, where an elevated operating voltage stemming from a microcode algorithm led to incorrect voltage requests, highlighting the significance of voltage regulation in maintaining CPU stability.

💡Microcode

Microcode is a layer of machine-level code used in CPUs that helps translate instructions into operations that the hardware can execute. The script mentions Intel's plan to deliver a microcode patch to address the root cause of exposure to elevated voltages, indicating the role of microcode in fixing hardware-related issues post-production.

💡BIOS

BIOS, or Basic Input/Output System, is firmware used to perform hardware initialization during the booting process. The video mentions that motherboard vendors will need to make BIOS changes in response to the instability problems, showing the interplay between hardware and software in addressing technical issues.

💡Instability

Instability, in the context of this video, refers to the unreliable or unpredictable behavior of Intel's 13th and 14th generation CPUs due to various issues, including voltage and oxidation problems. The script discusses how these instabilities can lead to system crashes and the steps needed to mitigate them.

💡RMA (Return Merchandise Authorization)

RMA is a process allowing customers to return defective products for repair, replacement, or refund. The script criticizes Intel for rejecting some RMAs during the period when they knew oxidation was a problem, emphasizing the importance of fair customer support policies in maintaining brand trust.

💡Transparency

Transparency in this video refers to the openness and communication from Intel regarding the issues with its CPUs. The script argues for the need for clear and honest communication from companies about product defects and the steps being taken to resolve them, which is crucial for consumer confidence.

💡Manufacturing Defect

A manufacturing defect is an error or flaw that occurs during the production process of a product. The script discusses the oxidation issue as a manufacturing defect that affected some early Intel Core 13th gen desktop processors, illustrating the impact of such defects on product quality and consumer experience.

💡Overclocking

Overclocking is the practice of increasing the clock rate of a computer's CPU beyond what the manufacturer specifies for operations. The video mentions the potential long-term damage caused by excessive voltage, which is particularly relevant to overclocking, as it may lead to hardware instability or failure.

💡Warranty

Warranty is a guarantee provided by manufacturers to cover repairs or replacements for defective products within a specified period. The script calls for Intel to extend warranties for affected users and to clearly define its commitment to customer support, highlighting the importance of warranty in consumer protection.

💡CPU (Central Processing Unit)

A CPU, or Central Processing Unit, is the primary component of a computer that performs most of the processing. The script revolves around issues with Intel's 13th and 14th generation CPUs, emphasizing the significance of CPU stability and reliability in computing.

Highlights

Intel admitted to oxidation issues with its 13th gen CPUs, affecting stability.

Initial Intel statement only addressed voltage issues, not oxidation.

Oxidation issue was later confirmed in a Reddit post, indicating a lack of transparency.

Oxidation occurred during the gate formation process in CPU manufacturing.

Microcode changes and motherboard BIOS updates are part of the solution to instability issues.

Intel rejected some RMAs during the period they knew about oxidation issues.

Intel's largest business customers were not made aware of the oxidation issue until 2023.

Thermaltake's Frozen Prism 360 liquid cooler is highlighted for its affordability and performance.

Intel's statement on voltage and microcode changes was criticized for omitting oxidation.

Intel's contradictory statements on oxidation's relation to instability raise concerns.

Intel failed to provide specific date codes or means to identify affected CPUs.

Users are advised to update BIOS and microcode for 13th and 14th gen CPUs.

Consumers are warned about the potential toxicity of affected CPUs in the used market.

Intel's commitment to customer support is questioned due to lack of clarity and action.

The oxidation issue is resolvable at the fabrication level, but the extent of the problem is unknown.

Long-term exposure to excessive voltage can cause irreparable damage to CPUs.

Microcode and BIOS updates may resolve voltage-related instability issues.

Intel's handling of the situation is described as irresponsible and lacking transparency.

Recommendations include applying for an RMA if experiencing instability, and avoiding 13th and 14th gen CPUs until further notice.

Transcripts

play00:00

questions about manufacturing or via

play00:01

oxidation as reported by Tech Outlets

play00:05

thanks

play00:07

Steve Intel just admitted oxidation

play00:09

issues with its 13th gen CPUs but this

play00:13

only comes after first publishing a half

play00:15

complete statement addressing only the

play00:17

voltage issues that means the media gets

play00:20

to run with the voltage story while

play00:22

Intel could then append the oxidation

play00:24

issue to a Reddit post after people

play00:26

already went depressed with the voltage

play00:28

issues options for this strange series

play00:31

of choices might include things like

play00:33

General disorganization within the

play00:36

company of how to deal with this Panic

play00:38

uh General incompetence or and we can't

play00:41

speak to the motive but maybe something

play00:44

more calculated in my opinion now if

play00:46

you're not familiar with that latest

play00:48

revelation of oxidation we broke the

play00:50

story on possible oxidation of the vas

play00:52

within the CPU occurring during gate

play00:53

formation process and began talks with

play00:56

the failure analysis lab inel has now

play00:58

officially confirmed that oxid was at

play01:00

one point a problem but it's not the

play01:02

only one this comes alongside a

play01:03

notification from Intel of micro code

play01:05

changes and this uh will also bear with

play01:08

it some Motherboard BIOS changes from

play01:10

the motherboard vendors and so the two

play01:13

of these in combination are part of the

play01:16

instability problem so speaking with

play01:17

Wendell uh it's possible there's other

play01:19

aspects of the instability of Intel CPUs

play01:21

as well but it seems like these are the

play01:23

two that at least Intel's addressing

play01:25

right now uh now somewhat disgustingly

play01:29

uh from my viewpoint Intel rejected at

play01:31

least some rmas for B2B and some B Toc

play01:35

CPUs During the period at which they

play01:38

knew oxidation was a problem but from

play01:41

everything we've uh heard from our

play01:44

contacts before the contacts the

play01:47

business partners were aware of the

play01:50

oxidation problem so this period is

play01:51

critical because if there's any rejected

play01:54

rmas when Intel knows about it but the

play01:56

partners don't it's it's really just

play01:59

inexcusable it's the Asus treatment

play02:01

where the company must revisit all the

play02:04

rejected rmas and it needs to reprocess

play02:07

them to evaluate whether those customers

play02:09

were actually owed Replacements with

play02:11

everything that Intel knows today that

play02:13

includes the voltage problems and that

play02:15

includes the oxidation issues and this

play02:17

is just Frankly Speaking this is int's

play02:20

biggest up that I have personally

play02:23

reported on uh in the 16 years or so

play02:25

that we've been doing this and the

play02:28

company is it's behaving

play02:30

irresponsibly it is slow for an issue

play02:33

that's important and requires confidence

play02:36

in what support is being provided to

play02:38

customers not just a blanket statement

play02:40

of we're committed to supporting our

play02:41

customers whatever that means but

play02:43

something actually firm written down to

play02:46

what those commitments are and that

play02:48

includes business customers as well but

play02:50

speaking to the business customers so

play02:52

Intel's largest ones like big oems were

play02:55

not made aware of the oxidation issue

play02:57

until just this year and this something

play03:00

that Intel said was in 2023 that it was

play03:01

happening so if that's the case

play03:05

then just I don't I don't really it just

play03:08

looks bad to be the most charitable

play03:12

possible with that uh or like a coverup

play03:15

but let's get into it before that this

play03:17

video is brought to you by thermal R and

play03:19

the Frozen prism 360 liquid cooler

play03:21

thermal W's Frozen prism is one of the

play03:23

most affordable liquid coolers on the

play03:24

market and is able to achieve

play03:26

competitive results with a high cold

play03:28

blate convexity that applies pressure

play03:29

potentially to the Silicon area based on

play03:31

our testing this works on both AMD and

play03:33

Intel we previously benchmarked the

play03:36

Frozen prism and found that it's overall

play03:38

competitive for its price point the

play03:39

cooler comes in a few color variations

play03:42

it has a blackout option and an RGB

play03:44

option and it's the cheapest liquid

play03:46

cooler we've tested anytime recently

play03:47

that still hits performance markers

play03:49

learn more at the link in the

play03:50

description below this is pretty simple

play03:52

today so Intel posted a statement

play03:54

claiming only the voltage and micro code

play03:56

changes initially this is what it said

play03:58

based on extensive analys of Intel Core

play04:00

13th and 14th gen desktop processors

play04:03

returned to us due to instability issues

play04:04

we have determined that elevated

play04:06

operating voltage is causing instability

play04:08

issues in some 13th and 14th gen desktop

play04:11

Parts our analysis of returned

play04:13

processors confirms that the elevated

play04:15

operating voltage is stemming from a

play04:16

micr code algorithm resulting in

play04:18

incorrect voltage request to the

play04:20

processor Intel is delivering a micro

play04:22

code patch which addresses the root

play04:24

cause of exposure to elevated voltages

play04:26

We are continuing validation to ensure

play04:28

that scenarios of inst stability

play04:30

reported to Intel regarding core 13th

play04:32

and 14th gen desktop processors are

play04:34

addressed Intel is currently targeting

play04:36

mid August for patch release to Partners

play04:39

following full validation the statement

play04:40

concludes with this quote Intel is

play04:42

committed to making this right with our

play04:44

customers and we continue asking any

play04:46

customers currently experiencing

play04:48

instability issues on their core 13th

play04:50

and 14th gen desktop processors to reach

play04:52

out to Intel customer support for

play04:54

further assistance now this statement

play04:56

said nothing of oxidation it was fully

play04:58

focused on micro code and access voltage

play05:00

uh oxidation is a physical Hardware

play05:03

level defect it would not be fixable in

play05:06

micro code it's something that happens

play05:08

during the fabrication process so any

play05:10

chips that were affected by oxidation of

play05:13

the veds are likely going to be uh

play05:17

subject to corrosion and potentially

play05:19

instability as a result of that

play05:21

corrosion and maybe eventual chip

play05:23

failure because it's not something you

play05:24

can just patch out the lack of a comet

play05:27

on oxidation combined with the clear

play05:29

language where they said they root

play05:32

caused it to voltage it makes it sound

play05:34

like oxidation was not part of the story

play05:37

and that it was fully voltage which is

play05:40

unintentionally at best misleading or uh

play05:45

again deliberately misleading and

play05:47

manipulative so we're not sure what it

play05:50

is I I can't speak to their motive but

play05:53

certainly I have some opinions and it

play05:56

again just does not look good it is not

play05:58

congruent with a company that uh wants

play06:02

the transparency of these issues Intel

play06:04

statement also completely fails to say

play06:07

how exactly they are going to support

play06:09

customers dropping the ball on every

play06:11

single possible level the community

play06:13

needs the transparency on what quote

play06:16

committed to making this right with our

play06:18

customers actually means because that

play06:21

means all at this point and there's

play06:24

a problem where these companies like to

play06:27

put out statements about we're going to

play06:29

support and make it right and whatever

play06:32

but without a hard commitment of what

play06:34

that means active Outreach to people uh

play06:37

actually have a list for Intel so we'll

play06:39

make this easy Intel here's the road map

play06:41

that I'd like to see uh first of all the

play06:44

affected date range of the CPUs has to

play06:46

be out there and if it's not fully known

play06:49

with certainty what's affected at least

play06:51

a suspected date range where if it's in

play06:53

this date that you bought it or it was

play06:55

manufactured via the manufacturer code

play06:57

then possibly it is affected so for the

play06:59

voltage and the micro code problem that

play07:01

might mean effectively all of them we

play07:03

don't know for the oxidation problem

play07:05

there is a specific window before Intel

play07:08

fixed it and I will talk about this

play07:11

later but the good thing with the

play07:12

oxidation problem is any manufacturing

play07:14

level defect is something that once it's

play07:16

fixed it should just be fixed and

play07:18

permanently so for everything made after

play07:20

that so it's in a it's a really bad

play07:22

problem in the sense that it's a

play07:23

hardware level defect it'll affect

play07:25

everything potentially um and there may

play07:28

be uncertain certainty as to which ones

play07:31

got through without that problem and

play07:33

which ones got through with it but it's

play07:34

a good thing in the sense that once it's

play07:36

resolved it's resolved so they need to

play07:38

have an effective date range of CPUs for

play07:40

both of these they need to have a serial

play07:42

number range or lookup tool inel has

play07:44

tools on its website for warranty

play07:46

services you can type in some characters

play07:48

on the CPU lid and get information about

play07:51

the warranty they should apply that to

play07:52

this and make it that you could type it

play07:54

in and it spits out a you might be

play07:56

affected or you are not affected and

play07:59

maybe that simple maybe they can't

play08:00

confirm it's affected but at least

play08:02

saying maybe and no would help a lot and

play08:05

ease some anxiety for customers uh we'd

play08:07

also like to see a commitment to

play08:08

warranty extensions offered to users of

play08:11

CPS affected and a commitment to

play08:12

warranty extensions for users who

play08:14

experience degradation likewise if the

play08:17

micro code changes affect performance in

play08:19

any capacity we would expect an offer of

play08:23

a full refund because if you're buying

play08:26

something that doesn't perform as it was

play08:27

reviewed and advertised then that's just

play08:30

fair at this time however I really want

play08:32

to emphasize this we don't know if

play08:34

there's going to be a performance change

play08:37

uh it's possible that can affect the

play08:39

voltage tables without changing anything

play08:41

for the actual CPU performance but we'll

play08:44

really need to to see and independently

play08:46

validate that one of the concerns I have

play08:48

here is if users are unaware of these

play08:49

micro code changes and unaware of the

play08:51

need to update BIOS you know most users

play08:54

they kind of buy or build their system

play08:56

and then ignore all of this stuff and go

play08:59

on on with their lives and that's

play09:00

probably a good way to do things but

play09:03

those people will not be informed on

play09:05

this issue which is uh unfortunate

play09:08

because this is something where if

play09:09

they're being their CP is being exposed

play09:11

to excessive voltage uh it will over

play09:13

time potentially exhibit this

play09:15

instability and maybe just stop working

play09:17

at the the spec that it's set for so

play09:20

what we'd like to see is some kind of

play09:21

active Outreach uh and options for that

play09:25

might include going through motherboard

play09:26

Partners going through Retail Partners

play09:28

posting on social media making sure the

play09:30

Press is aware of this which includes

play09:32

transparency and all these other things

play09:33

we talk about to make sure everyone's

play09:35

aware of it so that Intel can minimize

play09:38

its liability and minimize its legal

play09:41

exposure to the extent possible long

play09:43

term by trying to get in front of these

play09:44

failures by notifying everyone back to

play09:47

the statement though like we said it

play09:48

said nothing of oxidation in fact it

play09:50

said that it had identified the root

play09:52

cause of stability as being excessive

play09:54

voltage related to it but it did update

play09:56

its statement on Reddit where it's

play09:58

common are more likely to go under the

play10:00

radar for investors and media I didn't

play10:02

see it until someone sent it to me

play10:04

here's what it said quote so that you

play10:05

don't have to hunt down the answer

play10:08

questions about manufacturing or via

play10:09

oxidation as reported by Tech Outlets

play10:13

thanks Steve quote short answer we can

play10:15

confirm there was a via oxidation

play10:17

manufacturing issue addressed back in

play10:19

2023 but it is not related to the

play10:21

instability issue first this is just

play10:23

more unclear language from Intel back in

play10:27

2023 is an incredible ly wide range uh

play10:31

in fact you might say it's almost about

play10:34

a year and that's a that's a huge amount

play10:36

of time be nice to actually know what

play10:38

that range was Intel failed to provide

play10:40

any date codes any means to identify

play10:43

potentially affected CPUs again it might

play10:45

not have affected all of them that went

play10:46

through it but we don't know and that's

play10:48

the point of the transparency so while

play10:50

it's good that they've confirmed this

play10:51

publicly for the first time and really

play10:53

just within days of it becoming a public

play10:55

pressure issue it's unfortunate that it

play10:57

took a year to do so and they also once

play10:59

again failed to provide any means to

play11:01

actually do something with this

play11:03

information as a consumer so uh Intel

play11:05

continued with this quote lawn answer we

play11:08

can confirm that the Via oxidation

play11:10

manufacturing issues affected some early

play11:12

Intel Core 13th gen desktop processors

play11:15

however the issue was root caused and

play11:17

addressed with manufacturing

play11:19

improvements and screens in 2023 we've

play11:21

also looked at it from the instability

play11:23

reports on Intel Core 13th gen desktop

play11:26

processors and the analysis to date has

play11:28

determined that only a small number of

play11:30

instability reports can be connected to

play11:32

the manufacturing issue for the

play11:34

instability issue we are delivering a

play11:36

micro code patch which addresses

play11:37

exposure to elevated voltages which is a

play11:40

key element of the instability issue we

play11:42

are currently validating the biker code

play11:44

patch to ensure the instability issues

play11:46

for the 13th and 14th gen are addressed

play11:48

so if you didn't catch it Intel is

play11:50

contradicting itself in these statements

play11:52

with some slippery phrasing uh in

play11:55

Intel's first statement it attributed

play11:58

the root cause only to voltage and it

play12:00

pointed to a solution as a micro code

play12:02

update in Intel's short answer version

play12:05

of that Reddit comment it said quote it

play12:07

is not related to the instability issue

play12:10

referring to oxidation uh but its lawn

play12:14

answer which was in the same comment

play12:16

said quote only a small number of

play12:18

instability reports can be connected to

play12:20

the manufacturing issue again relating

play12:23

to oxidation so these are in congruent

play12:25

with each other because they are

play12:26

absolute statements it is not connected

play12:29

and then only some of them are connected

play12:31

the only Su wipes out that it is not

play12:33

obviously so that means it is at least

play12:35

somewhat related to the instability

play12:37

issue uh and then of course the

play12:39

excessive voltage is one that that path

play12:41

everyone's kind of been on for months

play12:43

now at this point alongside the power

play12:45

behav pl1 pl2 actually were before the

play12:47

voltage discussion uh so the power side

play12:49

of things was kind of the one that

play12:51

seemed like the really it's likely

play12:53

there's a problem here because Intel has

play12:54

been pushing the power so high and

play12:56

running too close to the limit uh but

play12:58

the oxid a separate issue that appears

play13:00

to have at least affected some of them

play13:02

for instability according to Intel again

play13:04

we don't know how many the contact we

play13:06

had in our previous PS assumed that they

play13:08

would have a range of 10 to 25% uh

play13:11

affected by instability that they

play13:13

thought might be attributable to the

play13:15

oxidation issue and a company that size

play13:18

the scale is in the hundreds of

play13:20

thousands to potentially millions of

play13:22

processors so we're not sure how big a

play13:24

small number is it's possible whatever

play13:26

they had going on with instability

play13:27

issues was related to oxid

play13:30

at a a lower percentage and the voltage

play13:32

on the other problems but either way uh

play13:36

Intel immediately faced some pressure in

play13:39

the Reddit post Matt of Aldon games

play13:41

asked this quote any ideas on why we had

play13:45

server providers who ran into faulty

play13:46

CPUs in 2023 get rejected around the

play13:50

time you mentioned the oxidation

play13:51

manufacturing issue after 2 years of

play13:53

being handed rejected rmas contacting

play13:57

customer support again and H to not get

play13:59

rejected again is getting quite annoying

play14:02

and this is really bad this is why Intel

play14:03

has to go back in time and re-evaluate

play14:07

all the rmas from this period uh kind of

play14:09

like Asus just did and start rectifying

play14:13

those situations especially now that

play14:14

they've admitted they knew there were

play14:16

problems uh back then they knew the

play14:18

oxidation was a thing in 2023 just wrote

play14:20

it and then voltage they at least

play14:22

publicly say they know about as of a

play14:25

couple days ago so this is something

play14:27

that has to be rectified for customers

play14:29

who were unfairly rejected for claims

play14:32

and that is not something Intel has uh

play14:34

put in its commitment to support

play14:36

customers additionally Dylan Brown

play14:38

Unreal Engine supervisor at model Farm

play14:40

wrote this quote for anyone curious at

play14:42

work our failure rate for our 13900 K

play14:45

and 14900 K machines is about 50% so far

play14:48

any new machine builds going to be uh

play14:51

9950 X's production environments need

play14:53

reliability end quote Wendell asked

play14:56

Dylan Brown for more information on

play14:58

things like motherboards effected to

play14:59

which Brown responded with this quote

play15:01

fairly sure most are Rog ones they

play15:03

haven't fully failed but exhibit the

play15:05

instability even when lowering power

play15:07

limits haven't tested new bioses yet we

play15:09

first noticed the instability crashes

play15:11

that appeared to be GPU related but

play15:13

swapping gpus didn't seem to help

play15:15

finally clicked when the news started

play15:16

coming out about this issue and made

play15:18

much more sense at the time we tried

play15:20

reducing the power limits and such which

play15:22

didn't really help we have many

play15:24

identical machine builds and some were

play15:26

completely fine While others were

play15:27

extremely unstable so that's another

play15:29

note for this approximately 50%

play15:31

instability issue uh that pops up now

play15:35

there's a lot of sampling bias here it's

play15:37

possible that there are other problems

play15:38

at play too which I only soften because

play15:40

50% is such an enormous percentage that

play15:44

it it seems unfathomable but that is now

play15:47

multiple groups that have said a number

play15:50

like that are close to it Wendell when

play15:52

he presented his uh one server client

play15:54

who had a claimed approximate 50%

play15:57

instability failure rate softened it by

play16:00

saying that he thought maybe half of

play16:01

those would be recoverable that might be

play16:02

with something like micro code and so

play16:04

that would bring it down to say 25%

play16:06

either way very large numbers I mean

play16:08

even really anything over one is an

play16:10

enormous percentage for failure rate of

play16:13

something like a CPU uh so we would

play16:15

believe that a lot of the instability is

play16:17

recoverable with the micro code update

play16:19

and with the BIOS updates the concerns I

play16:21

have are more longterm like for ones

play16:23

that have been running for a while it

play16:24

may have some kind of permanent damage

play16:26

uh and just obviously you for these B2B

play16:29

customers especially game developers and

play16:33

Publishers where you have server

play16:35

providers who have difficulty with

play16:37

server stability players get pissed off

play16:40

you have maybe hundreds of thousands of

play16:41

dollars in Damages from players

play16:43

abandoning the game uh thinking that

play16:45

it's the game's fault the programmer uh

play16:47

who built the net code whatever it is

play16:49

these are Big costs that are thanks to

play16:51

Intel back to you Steve all right back

play16:54

to the statement so also note Intel did

play16:56

not name the 14th gen for CPUs that

play16:58

thinks were affected by oxidation and in

play17:00

that Reddit post the Intel employee who

play17:03

was commenting seemed to effectively

play17:05

explicitly state that it was a 13th gen

play17:08

issue that was resolved there now our

play17:09

source for the oxidation story gave us a

play17:12

list of only 13th gen CPUs if you're put

play17:15

that back up on the screen uh from the

play17:17

last one the source was as we said at

play17:19

the time concerned it might affect 14th

play17:20

gen but the list that they had was 133

play17:23

only I think it was 11 CPUs so seems

play17:25

like 14th gen is at least affected by

play17:28

micro code and voltage issues but may be

play17:30

clear of the oxidation issues this is a

play17:32

huge problem for Intel we appreciate

play17:35

that they finally disclosed what's going

play17:36

on at some level it's not enough but

play17:39

it's better than complete silence it did

play17:41

take immense public pressure to finally

play17:42

get them to an answer it was bad enough

play17:45

that large customers of Intel were

play17:49

starting to leak to us information about

play17:51

how bad it was because they didn't feel

play17:53

like they were getting the support they

play17:54

needed if you think about that really

play17:57

how big of a statement that is for for

play17:59

these huge customers and I say huge I

play18:01

mean like not Asus and MSI but bigger

play18:03

than those if they start contacting

play18:05

media uh there's really only a few

play18:08

reasons that'll happen of course you've

play18:10

always got the one where someone might

play18:12

just want to be involved in some big

play18:13

Story Rex Bose we try to filter that as

play18:16

best we can but typically what it comes

play18:18

down to is uh it is best for every

play18:21

business in the relationship so that'd

play18:23

be in telling their Partners to just

play18:24

stay quiet and fix it quietly so that

play18:26

neither one of them affects the

play18:28

confidence and the product that's being

play18:29

sold whether that's the customer using

play18:30

an Intel product or Intel itself and so

play18:32

if it eventually does get out to Media

play18:34

uh that is indicative of maybe how big

play18:36

the problem is so uh the oxidation issue

play18:41

to come back to that one is good in the

play18:43

sense that it is resolvable in kind of

play18:45

one swoop where uh it is a Fab level

play18:48

change as far as I understand it's kind

play18:51

of binary it's either fixed or it's

play18:53

problematic and Intel says it's fixed

play18:55

it's concerning of course we don't know

play18:56

how wide reaching it is but at least

play18:58

that one's probably resulted uh our

play19:00

failure analysis lab sources have

play19:02

indicated it's possible for oxidation of

play19:04

the vas to cause additional problems

play19:07

with time or worsen the stability with

play19:08

time and create longer term failures

play19:11

we'll have to keep an eye out for that

play19:12

as for the lab we have at least one CPU

play19:14

where we've pinpointed the region of the

play19:15

CPU that is problematic uh we're not

play19:18

sure if it's a voltage thing or if it's

play19:19

an oxidation thing we're going to send

play19:21

that out to them I have not fully locked

play19:23

in that contract yet uh so it's not

play19:25

guaranteed we're going to have an fa

play19:27

report they're going to need to get me a

play19:28

cost C estimate but we're going to still

play19:30

try and do one at this point though

play19:31

would just be academic and to learn

play19:33

because Intel's already confirmed the

play19:35

problem so it's not a mystery anymore

play19:36

but it still be cool just to try to

play19:38

understand understand the scope of it

play19:39

and get some educational material for us

play19:41

and for you all right what's next so uh

play19:44

here are the immediate items for

play19:46

consumers to know this is the part that

play19:47

you should care about these CPUs might

play19:49

be toxic on the used Market it's kind of

play19:51

an interesting point but you should be

play19:52

careful to check with sellers that they

play19:54

are stable and not being sold because

play19:56

they're unstable and remember that

play19:58

seller might lie to you especially ones

play20:01

on the internet you don't know so that's

play20:03

a great accidental way to reduce

play20:05

secondhand competition for new chips for

play20:07

Intel and AMD but if you're a buyer of

play20:10

secondhand you need to be careful uh two

play20:12

if you own any 13th or 14th gen CPUs you

play20:15

should immediately update the BIOS and

play20:17

you should keep an eye out for Intel

play20:18

micro code changes Intel said that this

play20:20

will be in August so these can be pushed

play20:23

a few different ways but a bios update

play20:26

let's say late August should effectively

play20:28

guarantee been applied and you can check

play20:30

your motherboard manufacturers bios

play20:32

notes to see if they explicitly address

play20:34

it to give you some confidence uh three

play20:37

If you experience any system instability

play20:39

at all and you have been using the CPU

play20:41

for a little while and you have no

play20:42

reason to suspect it's some other

play20:44

problem like malware or whatever then

play20:47

our guidance gn's guidance would be to

play20:49

immediately apply for an RMA even if you

play20:51

think it might be Windows you really

play20:53

don't want to be caught with a degraded

play20:55

chip uh and Intel should be responsible

play20:57

for its mess anyway so if they replace

play20:59

excessive CPUs then that's their own

play21:01

fault as a recap of the problems here's

play21:03

kind of an FAQ based on some of the

play21:05

comments we've seen on the internet the

play21:06

last few days so uh one oxidation that

play21:09

is a physical issue it can't be fixed

play21:11

with micro code two the oxidation can

play21:12

lead to instability and failure three

play21:14

CPU should no longer have this problem

play21:17

as it would have been resolved at the

play21:18

Fab level and it would not persist once

play21:21

fixed four Intel indicates that the 14th

play21:23

series is unaffected by this and then

play21:25

some FAQ for the voltage issues so first

play21:27

of all long-term excessive can cause

play21:29

irreparable damage typically this would

play21:31

manifest as the inability to maintain

play21:33

the same clocks at the same voltages so

play21:35

uh overclocking is my best example of

play21:36

this is the only real area I've seen

play21:38

this applicable but in the OC world the

play21:41

fix would be to reduce the clocks uh or

play21:45

you'd have to pump the voltage more to

play21:46

maintain the same clocks and this is

play21:48

just one type of that kind of failure

play21:49

I'm sure there can be other types but in

play21:51

that manifestation of it it ends up

play21:54

being sort of a self-fulfilling prophecy

play21:55

of degradation so the better move would

play21:57

be to reduce both uh for new CPUs or

play22:00

those which have not been exposed to

play22:02

excessive voltage for long periods micro

play22:04

code and a bios update should

play22:07

theoretically resolve all of these

play22:08

concerns and if you haven't used your

play22:10

CPU much and you don't see any

play22:12

instability we'd recommend just applying

play22:15

the BIOS and the micro code updates uh

play22:17

mid August to let's say late August

play22:19

maybe do it again just in case they make

play22:20

a change and then move on because if you

play22:23

don't think you're affected because you

play22:24

don't see instability It's relatively

play22:26

new hasn't had a lot of uptime then just

play22:30

you know my I I don't want people like

play22:32

feeling this constant anxiety about it

play22:33

so make a decision move on and apply the

play22:36

updates move on hopefully it doesn't

play22:37

affect you or I guess dump the part

play22:40

return it if you can if that's how you

play22:41

feel uh But whichever one it is if it's

play22:45

a new part and it hasn't seen a lot of

play22:46

use I would say just either apply the

play22:48

updates and move on and forget about it

play22:50

or get rid of it uh for CPUs which are

play22:53

already experiencing instability micro

play22:55

code and bios updates May resolve it or

play22:57

they may at least

play22:59

help uh if they resolve it I still you

play23:02

know we we have a certain level of

play23:04

responsibility a lot of people watch

play23:05

these videos a lot of people buy parts

play23:07

make decisions based on what we say and

play23:09

for that reason I have to air on the

play23:11

side of caution with this where uh I I

play23:14

don't feel confident or comfortable

play23:17

saying that it would stop any future

play23:19

instability if you have already had

play23:22

signs of some level of degradation or

play23:24

instability it's possible you just have

play23:26

instability without degradation but I

play23:29

can't know that realistically you can't

play23:31

either and so my blanket recommendation

play23:34

there would be an RMA and just get a new

play23:37

one and uh and apply them if they're not

play23:40

you know apply the BIOS update and then

play23:43

move forward from there that way you

play23:45

just it's kind of out of your mind

play23:46

that's how I would operate because I'd

play23:49

want to just have the confidence that

play23:50

okay this is this should be about as

play23:52

resulted as it can reasonably be

play23:53

resolved I am moving on with my life

play23:56

that's how I'd approach it so that's all

play23:57

I can really recommend

play23:59

um you know I don't want to appear like

play24:00

I'm being uh overly concerned about it

play24:03

but again if you're experiencing any

play24:06

instability that appears maybe CP

play24:07

related that's just that's my personal

play24:09

approach to it so take that for what you

play24:11

want all right for testing our plan is

play24:13

to Benchmark them under the still the

play24:15

same Intel official guidance for pl1 and

play24:18

pl2 Intel is indicating August for the

play24:20

micro code updates unfortunately this is

play24:22

after the Zen 5 reviews that means that

play24:25

I I don't really care what Intel says I

play24:26

don't care if they say there's no impact

play24:28

performance we still need to

play24:29

independently verify it so uh and to be

play24:33

clear at this time we're filming they

play24:34

haven't made a commitment as to if it

play24:36

affects performance or not so we're

play24:38

going to test them with the official

play24:41

guidance but we can't evaluate the micro

play24:44

code until it ships so we're going to

play24:46

have to revisit it in August and see how

play24:48

it is then because of all of that our

play24:50

blanket statement right now is an

play24:52

avoidance of recommending any intel 13th

play24:55

and 14th gen

play24:57

CPUs once the micro code update goes out

play25:00

we can retest for differences and we'll

play25:02

also need to see some firm commitments

play25:04

from Intel as to what specifically

play25:06

committed to supporting their customers

play25:08

means when we get those things uh

play25:11

hopefully a lack of performance changes

play25:13

and then hopefully some firm commitments

play25:15

on the warranty we will reconsider The

play25:17

Stance of whether or not we can

play25:19

comfortably recommend Intel CPUs uh and

play25:22

we'll let you all know as soon as that

play25:24

stance changes it' be the first thing I

play25:26

say in a hardware news episode or

play25:27

something so finally this voltage issue

play25:30

does not describe all instability we

play25:32

think there's more to it likely that

play25:33

comes with uh motherboards as well doing

play25:35

some of their own screwy things there's

play25:37

probably a lot of things in this problem

play25:39

and uh some chips that Wendell has have

play25:42

not been he thinks exposed to excessive

play25:44

voltage but are still uh unstable so

play25:49

it's possible it's the oxidation issue

play25:51

for some of those 13th gen ones uh but

play25:54

it could be something else entirely so

play25:56

we'll continue to follow the story think

play25:57

that's kind of it for now it's a mess

play26:00

it's a big mess for inal it's a huge

play26:02

problem you know the Fab level defect is

play26:04

both good and bad it's bad because it

play26:05

happened it's good because it's fixable

play26:08

relatively uh in a relatively binary way

play26:10

as far as I understand I don't know

play26:12

anything about manufacturing but that's

play26:13

my understanding of it and um I'd say

play26:16

that's that's about it so Zen 5 reviews

play26:19

coming soon Intel will be on the charts

play26:22

but uh we'll revisit this in August with

play26:25

micro code and that's it for this one

play26:26

thanks for watching support us direct ly

play26:28

on store. Gamers nexus.net you grab one

play26:30

of our PC Building anti-static mod mats

play26:33

with screw tracking grids cable pinouts

play26:36

two scale memory diagrams uh CPU

play26:39

dication just for some educational

play26:41

material and more or you can grab one of

play26:43

our t-shirts our commemorative pint

play26:45

glasses with the GM 3D emblem and our 3D

play26:49

coasters all of that supports our

play26:51

reporting directly and our independent

play26:53

work so thank you for watching we'll see

play26:55

you all next time

Rate This

5.0 / 5 (0 votes)

Etiquetas Relacionadas
Intel CPUsOxidation IssueVoltage ProblemCustomer SupportManufacturing DefectMicrocode UpdateBIOS ChangesHardware StabilityTech NewsConsumer Advice
¿Necesitas un resumen en inglés?