July 12th, 2024

Intel is selling defective 13-14th Gen CPUs

Intel faces criticism from Alderon Games for selling defective 13th and 14th gen CPUs causing crashes, instability, and memory corruption. Alderon Games advises against using Intel CPUs for hosting, migrating to AMD. They urge Intel to recall and refund affected consumers.

Read original articleLink Icon
Intel is selling defective 13-14th Gen CPUs

Intel is facing criticism from Alderon Games for selling defective 13th and 14th generation CPUs. The issues reported include crashes, instability, and memory corruption, affecting various aspects of game development and server hosting. Alderon Games has observed a high failure rate in these CPUs over time, leading them to migrate their servers to AMD processors. They are also advising against using the problematic Intel CPUs for hosting game servers. The company is taking steps to inform users about the issue through in-game notifications. The issue has gained attention from news outlets and other companies like Fortnite and RAD Game Tools. Alderon Games hopes Intel will recall the faulty CPUs and refund consumers. The situation highlights the importance of addressing product defects promptly to prevent further harm to users.

Related

Vulnerability in Popular PC and Server Firmware

Vulnerability in Popular PC and Server Firmware

Eclypsium found a critical vulnerability (CVE-2024-0762) in Intel Core processors' Phoenix SecureCore UEFI firmware, potentially enabling privilege escalation and persistent attacks. Lenovo issued BIOS updates, emphasizing the significance of supply chain security.

Investigating SSMEC's (State Micro) 486s with the UCA

Investigating SSMEC's (State Micro) 486s with the UCA

An investigation into State Microelectronics Co. Ltd.'s SM486 CPUs reveals they closely mimic Intel's 486 CPUs but may use more advanced processes. Questions arise about their legality and potential applications in China's vintage microprocessor market.

Ubuntu kernel update cripples graphics on AMD GPUs

Ubuntu kernel update cripples graphics on AMD GPUs

AMD GPUs with IOMMU enabled face null pointer dereference, causing black screens on boot for Picasso/Raven 2 GPUs. A fix is available by reverting a problematic patch, impacting Ubuntu users.

Intel's bad year worsens, with analyst decrying company as 'profoundly broken'

Intel's bad year worsens, with analyst decrying company as 'profoundly broken'

Intel's stock plummets by 36%, labeled one of S&P 500's worst. Analysts express concerns over disappointing earnings, foreseeing challenges ahead due to management struggles, low growth potential, and competitive threats.

AMD Ryzen 7000/8000 Series vs. 14th Gen Intel Core CPU Performance on Linux

AMD Ryzen 7000/8000 Series vs. 14th Gen Intel Core CPU Performance on Linux

The article compares AMD Ryzen 7000/8000 Series processors with 14th Gen Intel Core CPUs on Linux 6.10 using 400+ benchmarks. Testing on Ubuntu 24.04 LTS with Linux 6.10 kernel includes various models like Ryzen 9 7950X and Core i9 14900K. Systems used DDR5-6000 memory, AMD Radeon RX 7900 GRE graphics, and NVMe SSDs. Results show performance differences and include performance-per-dollar metrics.

Link Icon 19 comments
By @ComputerGuru - 4 months
This seems like deflection to me. There’s no reproducer, no technical info, no objective facts besides what is basically a meta study that lumps their code quality with intel’s hardware correctness as one metric.

If it’s as they say, switching to AMD shouldn’t lead to 100x fewer crashes, it should lead to no crashes.

Lumping both 13th and 14th gen hardware together makes it harder to take the claims as easily at face value. 13th gen have been around long enough that you’d think they’d be able to dig up a kernel mailing list bug report or some other corroboration of their accusation.

I clicked expecting basically an undocumented errata with specific, 100% reproducible instructions and a deep dive into the internal architecture changes that could have caused this. I’m tempted to flag the submission, honestly. Claims of such magnitude demand at least some baseline evidence.

By @darthShadow - 4 months
Related Videos:

Intel has a Pretty Big Problem (by Level1Techs): https://www.youtube.com/watch?v=QzHcrbT5D_Y

Intel's CPUs Are Failing, ft. Wendell of Level1 Techs (by Gamers Nexus): https://www.youtube.com/watch?v=oAE4NWoyMZk

By @trynumber9 - 4 months
Oodle, a very optimized texture compression library used by Unreal, noted some problems months ago.

It is a bit odd that after months of this being well-known problem Intel still hasn't released a root cause. Is it an instruction sequence? Is their code subtly wrong in a way that works sometimes on these chips but always on other chips? Are some processors defective?

By @jeffbee - 4 months
I have my 14900K power capped at 225W/125W using RAPL and that seems to have stabilized it. I don't game with it, but it was unstable under all-core C++ compilation workloads. With these settings it is essentially a 14900. While trying to stabilize it I wasted a lot of time, bought a new motherboard, and bought all new DIMMs. I feel that if Intel can fix it they should provide owners with working replacements, a refund, and a goodwill discount on a future Intel product.
By @more_corn - 4 months
As someone who used to spec data center hardware I assure you that AMD is going to have a series of kick ass quarters. We’ve had a slight preference for Intel for a decade but this probably is enough to flip 50% of large scale cpu purchases for the next year.
By @wolpoli - 4 months
> I clicked expecting basically an undocumented errata with specific, 100% reproducible instructions and a deep dive into the internal architecture changes that could have caused this.

That's a really high bar for a non-Intel investigation. The Pentium III 1.13GHz issue 24 years ago had 100% reproduceable instruction, but even that didn't include any deep dive into the internal architecture because that just isn't information that people have.

By @segasaturn - 4 months
This issue is specifically affecting Intel's K-series line, which are engineered to run up against the CPU's thermal limits. Basically, as long as there is load on the CPU and the CPU is running below 100°C, it keeps cranking up the frequency and voltage until it hits that barrier. I am quite sure that this behavior is what is causing CPU lifespan issues as pumping a theoretically unlimited amount of volts into a CPU can't be healthy. AMD is doing this performance hack on their newest AM5 Ryzen CPUs as well.
By @signa11 - 4 months
hmm, there seems to be this : https://www.youtube.com/watch?v=oAE4NWoyMZk piece on gamer-nexus right now...
By @KennyBlanken - 4 months
This was widely covered by the tech press back in April and was common knowledge among gaming enthusiasts much earlier. Intel has been working with motherboard suppliers to leave aggressive overclocking features turned on, and it's also pretty clear they're not correctly binning their chips. For a while now Intel hasn't been "innovating", just turning up the wick. They're clearly lagging in R&D while also trying to chase the very tippy-top of gaming benchmarks which makes no sense, even for world-class competitive FPS players.

Nvidia's been flat out telling people complaining about games crashing on 13th and 14th gen CPUs to 'talk to Intel':

https://www.techspot.com/news/102611-nvidia-advises-crash-pr...

If you overlooked Ryzen because of issues like memory latency in the early days, I encourage looking at them again. If you do your homework, you can find motherboards that support ECC ram to varying degrees (ie from "it'll run but with ECC disabled" to "error correcting but doesn't report it" to "full support, just not listed as such".) I believe AM4-socket ECC support is much more prevalent, if that's important to you.

Familiarize yourself with AMD's Precision Boost Overdrive, which can be used for overclocking and/or undervolting. Unlike AMD's graphics cards (which are space heaters, though the current 7xxx series is an improvement), Ryzen processors are fairly efficient in stock form; more so if you do even a bit of mild undervolting.

Don't waste your time with the stock coolers supplied with any of the chips. They'll keep the chip cool enough, but are noisy as hell compared to a well-performing $30 dual-fan air cooler (GamersNexus has found several in their reviews.)

Keep your BIOS up to date for AGESA (AMD microcode) improvements, and keep your AMD chipset drivers up to date as well.

By @mikaelh2 - 4 months
I've had this issue come up twice now on one server, at first i was perplexed as i simply couldn't imagine the nvme drive causing these errors. Could it be related to the 13th gen issues? https://i.imgur.com/l6vQFum.jpeg
By @NoPicklez - 4 months
Glad I bought a 13600k

I don't think I should have issues?

By @librasteve - 4 months
they are using the FPU heavily - in my experience an FPU design can be prone to gnarly and unpredictable bugs that are related to certain combinations of bit patterns (eg hammering all ‘1’s to all ‘0’s) in successive pipe stages which my be issued in an out of order sequence - it is very hard to diagnose and correct such failures and impossible to screen for them on a production tester
By @tibbydudeza - 4 months
I got a 13900 rather - not a gamer but developer so the extra bucks for K variant did not make sense to me - fortunately it seems.
By @icf80 - 4 months
This looks like general memory corruption generated by the CPU.
By @newzisforsukas - 4 months
By @swatcoder - 4 months
Wow, I would not make a public statement like this without narrowing down the issue and making a replication case.

Given what little insight they have now, the crash-triggering fault could just as likely be in the peculiarities of their own code, some flaw in their build toolchain, some flaw in a runtime library, etc

With all respect to the folks at this studio, this statement reads like a junior dev throwing up their arms and blaming others over a bug they can't wrap their head around.

Even if they have a hunch that it's a CPU bug and can't afford to prove it, a more professional approach would be to perform the hardware change to AMD and toss out a more curious and less authoritative statement -- "Anybody else seeing more crashes on these processors? Have you figured out what from?" vs "These are broken and should be recalled".