Sorry, but you must definitely choose what word to use : labtob, labtop or laptopINTEL SAY LIE , all gen11-14 cpu super hot , give bluescreen even in labtobs with low setting , newly i seen 3 intel labtop burn cpu even motherboard
Sorry, but you must definitely choose what word to use : labtob, labtop or laptopINTEL SAY LIE , all gen11-14 cpu super hot , give bluescreen even in labtobs with low setting , newly i seen 3 intel labtop burn cpu even motherboard
The fact that your CPU was stable does not demostrate anything, may be your workload or simply a bit of luck. So the only factual demonstration is that Intel said that only 13th and 14th gen are affected.I've used a 12700K for sometime, and did not experience any instability issues. So I believe it is factual that the issue may only be limited to Raptor Lake chips.
It is NOT oxidation. This statement has been released a while ago and was reported on ina couple of tech channels, there is no way to not having seen it. It's too high voltage requests. Not oxidation. Different things.[...]The oxidation degradation is only on 13-14 gen with CPUs 65w and higher. The mobile platform CPUs? Nope, mobile is just fine. 3 new laptops failing is alarming.
But so far there's he hardly and reports of Intel based laptops dying because of oxidation degradation.
As someone who is NOT a fanboy of Intel, even I can see that.
Also what is this 1.3v thing you're going on about? Should you be telling Intel and d engineers instead of us laypeople in the internet.? Lol... Please don't be part of the problem. You're spreading misinformation and people who don't know better might believe what you're saying and continue spreading in accurate information and people can be hurt financially because of false and inaccurate information being spread.
There are literally no reports anywhere of 12th gen suffering the issue, and 12th gen apparently has very low failure rates in general. So it stands to reason that it is, indeed, unaffected.The fact that your CPU was stable does not demostrate anything, may be your workload or simply a bit of luck. So the only factual demonstration is that Intel said that only 13th and 14th gen are affected.
Maybe it is not technically possible to release this update with the O.S. or that in this first phase, Intel prefers to maintain the situation restricted to have more control and easily fix possible issues.What does Intel mean by saying that aren't releasing the BIOS update via Windows Update? Isn't it purely up to OEM/ODM's, e.g. HP and others to release their own BIOS updates? Intel is making yet another mistake and continuing to crush confidence if they are purposely limiting distribution of the fix; surely, after a month or two of testing, it'd be safe to release to WU.
Also I understand so.Also, so they're saying that new chips are modified such that they don't exhibit this defect, regardless of microcode? Would this simply be part of CPU stepping?
Agree, it could be very useful. Nice to have some warning in the O.S.And what about the tool to help identify the problem children?
From Intel themselves "The Via Oxidation issue currently reported in the press is a minor one that was addressed with manufacturing improvements and screens in early 2023.It is NOT oxidation. This statement has been released a while ago and was reported on ina couple of tech channels, there is no way to not having seen it. It's too high voltage requests. Not oxidation. Different things.
https://community.intel.com/t5/Proc...ty-Reports-on-Intel-Core-13th-and/m-p/1617113
It's funny how you complain about misinformation, yet do the same, even though I agree with you that the guy you replied to did spread it, too.
The point is you're conflating two different issues.So as you can see you're incorrect. Intel knows that CPUs with the oxidation issue made it out into the marketplace.
Conflating?The point is you're conflating two different issues.
The oxidation problems were due to manufacturing and have been resolved as far as production is concerned and is its own problem. This is an issue Intel undoubtedly has batch identification for and they've still fumbled the response badly.
The voltage issue is universal for RPL SKUs using RC cores with 65W base TDP and higher (the only exception seems to be RC cores configured to match GC). This affects every single processor and the ones obviously damaged by it would appear to be worse binned parts, but it's entirely possible there's damage to others as well.
And one more thing, I went back to what my original comment was in response to. It was in response to someone saying all Intel does is liy and that all CPUs should be running around 1.3v. And I called that person out with some facts to back up my comment. I wasn't yelling at the top of my lungs how Intel bad!!! I was taking up for Intel.The point is you're conflating two different issues.
The oxidation problems were due to manufacturing and have been resolved as far as production is concerned and is its own problem. This is an issue Intel undoubtedly has batch identification for and they've still fumbled the response badly.
The voltage issue is universal for RPL SKUs using RC cores with 65W base TDP and higher (the only exception seems to be RC cores configured to match GC). This affects every single processor and the ones obviously damaged by it would appear to be worse binned parts, but it's entirely possible there's damage to others as well.
Whether intentional or not the way you wrote both of your posts makes them sound like they're part of the same problem rather than being two separate issues. It may not seem like an important distinction to someone like yourself who knows better it is important to be accurate.Conflating?
All I'm saying is that if oxidation damage is done, there's nothing that can be done even with the microcode.
Right on. I def didn't mean to come across as they're the same. If I did, I messed up. I personally do know those are two separate issues but that one can contribute to the other. As in, heigher voltage can lead to higher oxidation degradation. And it leads to degradation in general also. I just assumed people would make the distinction. Sometimes I have a hard time getting thoughts from my brain to the screen. (Part of the ADHD... I'm still learning how to cope with it better with my psych team). So I sometimes need someone to bluntly call it out when I make Generalized statements that aren't clear to others.Whether intentional or not the way you wrote both of your posts makes them sound like they're part of the same problem rather than being two separate issues. It may not seem like an important distinction to someone like yourself who knows better it is important to be accurate.
As for the two problems oxidation is seemingly the worse of the two as that's typically a guaranteed early death situation. It's also the one that Intel should have the easiest time identifying problem parts. In the case of the elevated voltage that seems dependent on the CPU binning more than anything else.
From what I know, Intel never said that the "oxidation" problem was responsible for any malfunction or hang. Intel only stated that the problem existed, was fixed and some CPU (only 13th gen from what I know) can be in the wild.Conflating?
All I'm saying is that if oxidation damage is done, there's nothing that can be done even with the microcode.
I wasn't saying they're the same issue. But Intel has admitted they don't know how many CPUs went to market with the oxidation issue. I hope I didn't make it sound like I was saying the vtage is the same as the oxidation. The Stryker pointed that out to me. Check out that comment and you'll see what happened.From what I know, Intel never said that the "oxidation" problem was responsible for any malfunction or hang. Intel only stated that the problem existed, was fixed and some CPU (only 13th gen from what I know) can be in the wild.
This is the reason because talking of the "oxidation" problem means disinformation, and it should never be take into account referring to the actual instability issue.
And Intel also said only a relatively small (by total volume) number of 13th gen, and 13th gen only, CPUs have that issue. So claiming that all failing CPUs have the oxidation issue, and making a blanket statement about it, is equally, if not more, incorrect.From Intel themselves "The Via Oxidation issue currently reported in the press is a minor one that was addressed with manufacturing improvements and screens in early 2023.
The issue was identified in late 2022, and with the manufacturing improvements and additional screens implemented Intel was able to confirm full removal of impacted processors in our supply chain by early 2024. However, on-shelf inventory may have persisted into early 2024 as a result.
Minor manufacturing issues are an inescapable fact with all silicon products. Intel continuously works with customers to troubleshoot and remediate product failure reports and provides public communications on product issues when the customer risk exceeds Intel quality control thresholds.
Lex H, Intel Community Manger & Tech Evangelist."
So as you can see you're incorrect. Intel knows that CPUs with the oxidation issue made it out into the marketplace.
Also, it's been proven true by lab tests.
It is both. Voltage issues and oxidation.
If you think otherwise then refer to Intel's other statement claiming if CPUs are already failing there's no fix. That is from BOTH oxidation and voltage. The voltage causes the oxidation and degradation to happen faster. But the microcode fix won't help those CPUs. They will continue to degrade faster.
So yeah, I'm not spreading misinformation. I'm actually going by what Intel, and others, have said and proven.
Before you start downing someone, maybe have the FULL story. Not just one thing found on a forum. That's what's great about the Internet!!! You can verify things for yourself.
Idc about which company to go with. I've had both AMD and Intel and they're both amazing tech! Sometimes things don't go right and there's issues. Which happened to Intel. And I have learned enough about the issues to know I won't be getting 13-14 gen CPUs. (Or Ryzen 9000 for that matter). I'm waiting to see what next gen Intel CPUs bring to the table before making any upgrade.
Wasnt there one "source" for Wendell and GamerNexus that said that the Arizona fab had the oxidation issues and it was more serious than intel wants to make it believe? (aka it went for longer than what intel claims)?From Intel themselves "The Via Oxidation issue currently reported in the press is a minor one that was addressed with manufacturing improvements and screens in early 2023.
The issue was identified in late 2022, and with the manufacturing improvements and additional screens implemented Intel was able to confirm full removal of impacted processors in our supply chain by early 2024. However, on-shelf inventory may have persisted into early 2024 as a result.
Minor manufacturing issues are an inescapable fact with all silicon products. Intel continuously works with customers to troubleshoot and remediate product failure reports and provides public communications on product issues when the customer risk exceeds Intel quality control thresholds.
Lex H, Intel Community Manger & Tech Evangelist."
So as you can see you're incorrect. Intel knows that CPUs with the oxidation issue made it out into the marketplace.
Also, it's been proven true by lab tests.
It is both. Voltage issues and oxidation.
If you think otherwise then refer to Intel's other statement claiming if CPUs are already failing there's no fix. That is from BOTH oxidation and voltage. The voltage causes the oxidation and degradation to happen faster. But the microcode fix won't help those CPUs. They will continue to degrade faster.
So yeah, I'm not spreading misinformation. I'm actually going by what Intel, and others, have said and proven.
Before you start downing someone, maybe have the FULL story. Not just one thing found on a forum. That's what's great about the Internet!!! You can verify things for yourself.
Idc about which company to go with. I've had both AMD and Intel and they're both amazing tech! Sometimes things don't go right and there's issues. Which happened to Intel. And I have learned enough about the issues to know I won't be getting 13-14 gen CPUs. (Or Ryzen 9000 for that matter). I'm waiting to see what next gen Intel CPUs bring to the table before making any upgrade.
And Intel also said only a relatively small (by total volume) number of 13th gen, and 13th gen only, CPUs have that issue. So claiming that all failing CPUs have the oxidation issue, and making a blanket statement about it, is equally, if not more, incorrect.
Also, I watched the GN report on it a week or two ago, thank you very much. That's where the statement came from, because it is not, in all or even just most cases, via oxidation.
And Intel also said only a relatively small (by total volume) number of 13th gen, and 13th gen only, CPUs have that issue. So claiming that all failing CPUs have the oxidation issue, and making a blanket statement about it, is equally, if not more, incorrect.
Also, I watched the GN report on it a week or two ago, thank you very much. That's where the statement came from, because it is not, in all or even just most cases, via oxidation.
I never implied or said anything about how many. Just that Intel themselves admitted it was a problem. So if it's a problem shouldn't the customers know that their PC could be affected and to keep an eye on it just in case? Why do you keep arguing a point I never made? What, do you think it shouldn't be talked about and it should just be swept under a rug in hopes that no one will notice? Why do you try to argue against something that's been admitted to by Intel and proven by labs?And Intel also said only a relatively small (by total volume) number of 13th gen, and 13th gen only, CPUs have that issue. So claiming that all failing CPUs have the oxidation issue, and making a blanket statement about it, is equally, if not more, incorrect.
Also, I watched the GN report on it a week or two ago, thank you very much. That's where the statement came from, because it is not, in all or even just most cases, via oxidation.
I'm not sure. I'll have to check into that. I'm just tired of people trying to to say it isn't that much of an issue so we shouldn't talk about it at all.Wasnt there one "source" for Wendell and GamerNexus that said that the Arizona fab had the oxidation issues and it was more serious than intel wants to make it believe? (aka it went for longer than what intel claims)?
Nobody said there is no issue, holy cow. But the oxidation is not as large of an issue as you made it out in your fiest post by implying that all failing CPUs have it. Because, yest, you actually did do that. And stop accusing me of sweeping the peoblem under the rug. I have been on record in multiple topics the past few weeks explicitly stating it is, indeed, an issue. You, on the other hand, are conflating two separate issues that happen to express similarly, which is something that needs correction. Got it already?I never implied or said anything about how many. Just that Intel themselves admitted it was a problem. So if it's a problem shouldn't the customers know that their PC could be affected and to keep an eye on it just in case? Why do you keep arguing a point I never made? What, do you think it shouldn't be talked about and it should just be swept under a rug in hopes that no one will notice? Why do you try to argue against something that's been admitted to by Intel and proven by labs?
Stop with this hiding and saying nah huh... It is out there and needs to be addressed. Not ignored because you don't think it's not a big deal.
It's high voltage not the overall power consumption that has been killing CPUs. Intel still recommends the extreme profile for boards that are good enough to support it as far as I'm aware.I'm surprised that, with all the concerns around these stability issues, that the default for the V2505 BIOS update was 'Extreme' vs "Performance'.
Would be interested to know if anyone else is seeing this.