[Dylan16807]

Well they didn't notice it for a good while, so it's really hard to say how much impact it had.

And at a certain point if you barely believe anything they say, then you shouldn't be using their statement to get mad about. The complaint you're making depends on very particular parts of their statement being true but other very particular parts being not true. I don't think we have the evidence to do that right now.

[hsbauauvhabzb]

> Well they didn't notice it for a good while, so it's really hard to say how much impact it had.

That negates any arguments you had related to failure rates.

> The complaint you're making depends on very particular parts of their statement being true but other very particular parts being not true

Er, I’m not even sure how to respond to this. GamersNexus has indicated they know about the oxidisation issue, intel *subsequently* confirm it was known internally but no public statement was made until now. I’m not unreasonably cherry picking parts of their statement and then drawing unreasonable conclusions. Intel have very clearly demonstrated they would have preferred to not disclose an issue in fabrication processes which very probably caused defective CPUs, they have demonstrated untrustworthy behaviour related to this entire thing (L1techs and GN are breaking the defective cpu story following leaks from major intel clients who have indicated that intel is basically refusing to cooperate).

Intel has known about these issues for some time and said nothing. They have cost organisations and individuals time and money. Nothing they say now can be trusted unless it involves them admitting fault.

[Dylan16807]

> That negates any arguments you had related to failure rates.

I mean it's hard for us to say, without sufficient data. But Intel might have that much data.

Also what argument about failure rates? The one where I said "if" about failure rates?

> Er, I’m not even sure how to respond to this. GamersNexus has indicated they know about the oxidisation issue, intel subsequently confirm it was known internally but no public statement was made until now.

GamersNexus thinks the oxidation might be the cause of the instability everyone is having. Intel claims otherwise.

Intel has no reason to lie about this detail. It doesn't matter if the issue is oxidation versus something else.

Also the issue Intel admits to can't be the problem with 14th gen, because it only happened to 13th gen chips.

> Intel has known about these issues for some time and said nothing. Nothing they say now can be trusted unless it involves them admitting fault.

If you don't trust what Intel said today at all, then you can't make good claims about what they knew or didn't know. You're picking and choosing what you believe to an extent I can't support.

[hsbauauvhabzb]

GN called out the lack of further details relating to oxidisation, fyi.