And who can blame them after the disgusting way Intel handled that whole situation. It'd be different if they said "we fucked up" and did some kind of recall. But just calling it a "regular support issue" when the hardware is legitimately fucked beyond repair is a whole other ball of wax.
Honestly if it weren't for laptop OEMs propping them up they would have already gone under. If AMD could get the fab time to really crank out their APUs en mass for OEMs they could put Intel to bed permanently.
And who can blame after the disgusting way Intel handled that whole situation. It'd be different if they said "we fucked up" and did some kind of recall. But just calling it a "regular support issue" when the hardware is legitimately fucked beyond repair is a whole other ball of wax.
Yep.
And to make matters worse I read they don't always fail right away. So yours could be working fine and then fail after it is out of warranty.
Or an unassuming user blaming their OEM or some other part of their build. I guarantee they did a CBA on the whole thing to see what would be the cheapest thing to do, and it looks like just ignoring it won out.
Ha yes, but clearly they didn't put long term damage to their reputation in that equation.
Let's be fair here, this only happens once every 0.999999999999999999999999999998 times out of a million or so.
The voltage thing or the bad soldering? The bad solder was responsible for over 50% of all reported application crashes in a few games. That's just want we know about so far.
The microcode update isn't going to fix a hardware level defect like that.
I was more being sarcastic using the pentium floating point bug.