Subj : Intel: Once mighty, now f
To : ARELOR
From : Cougar428
Date : Mon May 19 2025 08:41 am
-=> Quoting Arelor to Cougar428 <=-
Ar> Re: Intel: Once mighty, now f
Ar> By: Cougar428 to ARELOR on Thu May 15 2025 02:19 pm
> It wasn't actually bad hardware.
>
> Primarily the 13th and 14th generation CPU's using the Raptor Lake
> platform, and the issues were software related not actual hardware
> issues. The problem stemmed from a microcode algorithm that caused
> elevated operating voltages leading to CPU degradation and crashes.
> Once they patched the code the problems went away.
Ar> That is semantics.
Ar> If a regular consumer bought a PolyStation 23 and it caught fire
Ar> during a normal operation, the regular consumer would think it is a
Ar> hardware problem, even if it was caused by some BIOS bug. Low level
Ar> software, firmware and the like are so tightly tied to the hardware
Ar> that you may as well say it is an integral part of the hardware
Ar> appliance you bought (and got toasted).
Ar> While technically correct, saying it is not a hardware problem and
Ar> that it can be fixed by patching comes across as telling people they
Ar> can fix a motherboard issue by unsoldering some EPROM and soldering an
Ar> updated replacement, and therefore their motherboard is perfectly fine
Ar> and faultless.
I think the fix was to download the update and reboot the system. Of
course I may be wrong about how it was done, but you update drivers for
different hardware all the time. At every OS update.
You can explain it any way you like, but the hardware was not the
fault. If you're minds made up, then you're mind is made up. People
'think' alot of things. Doesn't actually make them true. I think you're
original post was about the defective 13th and 14th gen Intel CPU's. So
it is 'technically correct' - It wasn't a hardware problem, it was a
software problem. Had nothing to do with removing and replacing
components, just a flash update.
Ar> I don't buy it. We are already giving the IT industry too much leeway
Ar> to produce crappy products. Let them own their failures.
I would be happy to let them own their failure, like I said AMD chips
operated at such a high frequency to one up the competition that they
did actually catch fire. I guess if you never had it happen to you, you
would not appreciate the chaos.
As usual - just my opinion. Thanks for your reply.
Have a great day Arelor!
... I was on a roll till I slipped on the butter.
___ Blue Wave/QWK v2.20
---
� Synchronet � CJ's Place, Orange City, FL - cjsplace.thruhere.net