> Intel® reaffirms that both Intel® Core™ 13th and 14th Gen mobile processors and future client product families – including the codename Lunar Lake and Arrow Lake families - are unaffected by the Vmin Shift Instability issue.
It's an expensive component that's meant to last 4-5 years at least.
AFAIK AMD had a similar issue with elevated voltage burning 7000 series CPUs and also didn't recall them. Is there something I'm missing?
The fact that AMD has responded in three days [0] with an update, and stopped the problem in its tracks?
Original article is on 20230424, "We're investigating" update is on 20230425, the firmware update and "yes we screwed, this the cause, here's the fix" update is in 20230427, and case is closed.
[0]: https://www.tomshardware.com/news/amd-ryzen-7000-burning-out...
My read is they know all the chips are screwed and should do a recall but literally do not have enough stock for replacements and obviously don't want to take the hit. That's why they're giving people trying to RMA a runaround as well, they likely are prioritizing their big OEM customers over retail purchasers.
Maybe you'd be better assuaged if they also sent every confirmed purchaser of an affected CPU a $10 DoorDash coupon?
That is not a solution. That is a mitigation.
What if you bought a car with 65mpg that has an undisclosed engineering flaw where the engine will explode every 15,000 miles. The "solution" proposed by the manufacturer is to bring the car in for "repair" that reduces it to 40mpg, but the car will last a normal lifespan.
Did you not lose a considerable amount of value on your purchase?
wild anecdotes are fun to use on the internet, but provide nothing substantive to the discussion. but if you want to continue to memify everything, then have a nice day
Sneaky wording. Aren't they supposed to be testing the version before 0x125, considering it is the first one that may have potentially negative effect on performance?
> eTVB Microcode algorithm which was allowing Intel® Core™ 13th and 14th Gen i9 desktop processors to operate at higher performance states even at high temperatures. a. Mitigation: microcode 0x125 (June 2024) addresses eTVB algorithm issue.
emphasis mine.