“We’re going to undervolt them. You’re stuck with the damage done, and you won’t have luck overclocking or getting as much performance from our chips.”
Not only that, but I don’t think stability issues like this would’ve been known around or shortly after launch, so Intel (likely unknowingly) got to mislead consumers and reviewers into thinking that their 13th/14th HEDT processors were close to competitive with AMD’s, when they were anything but. It’s never been more apparent how stagnant Intel truly has become, and that’s already been a trope for years.
Nice one Intel. My next computer certainly will not contain an Intel CPU.
I wish someone would start making desktop motherboards with socketed RISC-V and ARM CPUs.
That would be great for a server, but 1.7GHz is a bit slow for a desktop.
My first thought went to the Milk-V Pioneer since it has mATX form factor, but both products are priced way higher than your average desktop.
Up to 128 cores. Not meant for gaming, but it cranks at server tasks, compiling & coding tasks, etc.
There’s a windows dev kit (ARM) that I think is 3ghz: https://www.microsoft.com/en-us/d/windows-dev-kit-2023
But bleeding edge stuff from MS means likely driver issues, and this isn’t something you’ll throw a dedicated graphics card in.
Still, feels like the tide is changing away from Intel. I too was looking at “ARM for Desktop” options a couple weeks back.
Ampere is pretty slow compared to AMD and Intel.
https://www.phoronix.com/review/intel-xeon-6700e-ampere-altra/6
AMD stock should have gone through the roof on this news.
This is actually good for Intel, if they think that they can actually fix the problem in microcode.
“Gamers Nexus, on the other hand, thinks the issue is more deep rooted and originates from a foundry-level fault.”
- The GN piece makes it very clear that this claim is not definitely true but is a line of inquiry.
- Intel statement does not definitely exclude this hypothesis, the flawed CPU might need the lower voltage to work around the flaw.
- The obvious question this article does not address is what will be the performance hit for the patched parts?
That’s a bit annoying to see GN so grossly misquoted when Steve spends half the run time of the video explaining that they are not sure of anything at this point.
Steve does go on, and on, and on, and on… Quite challenging, if you have a tight deadline.
He’s just really thorough. They have a text-based website too if you prefer that format for reviews, but they don’t always have time to make text articles of their investigative pieces and news reports.
Intel confirmed on reddit that oxidation did impact some chips.
More than one thing can be wrong at the same time, so everybody can be right!
They admitted that there was an oxidation defect and they haven’t started a recall or even listed serial numbers?
It’s a lot cheaper to say “if you think you’re affected contact us” than it is to proactively reach out with a recall.
Go with amd for now.
