If it's not crashing then it's not damaged. Or if you want to look at it this way absolutely all things are damaged.Obviously it could be damaged and not to the point of crashing yet. Obviously it takes a while for it to get to that point.
If it's not crashing then it's not damaged. Or if you want to look at it this way absolutely all things are damaged.Obviously it could be damaged and not to the point of crashing yet. Obviously it takes a while for it to get to that point.
That actually makes sense. But it's hard to tell what's true. Too bad we have to rely on leakersIntel cooking the Ring Bus on dying 13th and 14th Gen Core CPUs, says leaker
Intel 13th Gen and 14th Gen Core CPU issues: the ring bus is getting cooked because it's fed the same rail as the P-Cores and E-Cores, says leaker.www.tweaktown.com
Ring bus cooked?
This statement is not true. Damage can absolutely occur without operating system failures as an immediate indicator. Electomigration and dielectric breakdown does not instantaneously result in crashes, but can absolutely precipitate them in the future. Despite what people think, solid state electronics do eventually wear out given enough time. The damage we're talking about here is accelerated wear caused by excessive voltage. It's reasonable to conclude essentially all 13th and 14th gen chips which are eligible for the new microcode have been exposed to some modicum of this accelerated wear and hence are "damaged"; the challenge is understanding if the part fail within the extant warranty period.If it's not crashing then it's not damaged. Or if you want to look at it this way absolutely all things are damaged.
As I've said if you want to look at things this way then ALL things around you are inherently "damaged". The question is will this lead to any sort of issues with them over the time you will be using them? And since nobody knows the answer to that for the 13th/14th gen Intel CPUs right now calling them all "damaged" is nothing but pointless FUD at this point.Damage can absolutely occur without operating system failures as an immediate indicator. Electomigration and dielectric breakdown does not instantaneously result in crashes, but can absolutely precipitate them in the future. Despite what people think, solid state electronics do eventually wear out given enough time.
Does ring bus even run at variable clocks? Why would it need variable voltages?That actually makes sense.
By Intel's own definition and admission, these chips are damaged, therefore I rank their opinon above yours. Let's not try to trivialize this with esoteric handwaving "oh the entire world is moving towards entropy" nonsense.As I've said if you want to look at things this way then ALL things around you are inherently "damaged". The question is will this lead to any sort of issues with them over the time you will be using them? And since nobody knows the answer to that for the 13th/14th gen Intel CPUs right now calling them all "damaged" is nothing but pointless FUD at this point.
If your CPU works fine then it's not "damaged".
Does ring bus even run at variable clocks? Why would it need variable voltages?
Could you point me to Intel's statement which says that ALL 13/14th gen CPU are "damaged" please?By Intel's own definition and admission, these chips are damaged -- their opinon outweighs yours.
Intel has now divulged that the crashing issue affecting 13th and 14th-gen processors impacts all 65W and higher CPUs, meaning even more mainstream un-overclockable models are impacted. Intel announced Monday that, even though it still continues to investigate, it had finally gotten to the bottom of crashing issues plaguing its chips. As we reported on Monday, the microcode update is coming in mid-August, but if the bug has already damaged your CPU, you’re out of luck — the damage is irreversible, and the chip will need to be replaced. Intel has no plans to do a recall, but it is replacing impacted processors.
The reality is that the quote you've posted is basically saying what I'm saying:The reality is, the bugged target / request voltage microcode is irrespective of motherboard or related firmware, and as such any and every 13th and 14th gen processor at or above 65W has been affected.
Means that not ALL CPUs affected by the bug are damaged and those which are stable and don't crash are NOT damaged as per this Intel statement despite being "affected" by the m/c bug.but if the bug has already damaged your CPU
No, it can't. If a CPU works without issues then it's not "damaged", period.And what I'm telling you is a CPU can absolutely be damaged and not (yet) causing OS failures. And this is 100% absolutely correct, despite your claims to the contrary.
This is a semantic argument. In absolute terms, yes, they are damaged. Like getting some imperceptible micro-scratches on your phone screen. If the damage isn't affecting the experience, it can be ignored, but it's still damaged.No, it can't. If a CPU works without issues then it's not "damaged", period.
Precisely.What you seem to suggest is that the bug has affected the longevity of CPUs which are working fine now but has worked with improper voltages long enough to be further in their silicon quality degradation than some other CPU which doesn't have the bug (i.e. a 12th series one).
Not FUD but a different use of the word. Replace Albuquerque's use of 'damage' with 'further in their silicon quality degradation' and you'll get their point. With guaranteed accelerated wear and tear, all these processors should be expected to have a reduced life expectancy versus 1) the standard for similar processors and 2) the life expectancy of new 13/14 series that have been patched.However at this moment you, me, Intel or anyone really don't know anything about that. There are no data suggesting that these CPUs will be affected to any measurable degree yet, so just saying that they are "damaged" as if that's a fact is pure FUD.
No, it's not. A damaged CPU would not be able to work as intended while a CPU which is "affected by the bug" but not damaged would work fine. Since no one knows the extent of degradation the bug has caused to each particular CPU which is affected you CANNOT call them all "damaged" even from the point of them possibly having lower longevity now (i.e. failing sooner than expected; you need to have a time machine to say that this will definitely happen).This is a semantic argument.
Homerdog was asking if he could expect a patched CPU to be fine for the rest of its life. It's reasonable to reply that even after the patch, the CPU may fail earlier than it otherwise would have, due to the issue. And I don't think observing such effects requires any mysterious godlike powers. You just need to compare the failure rate (after the patch rollout) vs. prior generations and CPU models not vulnerable to the issue.No, it's not. A damaged CPU would not be able to work as intended while a CPU which is "affected by the bug" but not damaged would work fine. Since no one knows the extent of degradation the bug has caused to each particular CPU which is affected you CANNOT call them all "damaged" even from the point of them possibly having lower longevity now (i.e. failing sooner than expected; you need to have a time machine to say that this will definitely happen).
I'll stop at that because it's honestly tiresome to argue things which are clear as day.
Sure. Any CPU may fail earlier than you would expect, even those which don't have the issue. It is impossible to say that it definitely would though. And this applies to the affected CPUs too.Homerdog was asking if he could expect a patched CPU to be fine for the rest of its life. It's reasonable to reply that even after the patch, the CPU may fail earlier than it otherwise would have, due to the issue.
Yes, it is. It's not about who's right or wrong - maybe your definition is the correct one. The point here is the intent of the term and what people are trying to communicate. The discussion shouldn't be trying to determine if someone is right or wrong in using the word 'damaged', but if their idea of the impact of the fault is correct or not, regardless of the word or phrase used to describe that.No, it's not.
Higher voltages than what? Every processor which is operating on any voltages experience degradation and will eventually fail. The question whether this will happen to 13/14th gen CPUs earlier than you would expect doesn't have an answer since we don't know the future. Also "earlier than expected" is actually completely subjective and may be different to you, me and everyone in this thread. So just stating "yes, it is" in nothing but FUD.Move on from that - will every processor that has been operating with higher voltages have experienced accelerated wear or not?