Intel 13th and 14th Gen confirmed defective

[SpyderTracks]

So there's been a lot of upset gathering steam on the inter webs with intermittent games crashes on Intel 13th and 14th gen.

Workarounds range from underclocking to disabling ecores.

BUT, there are a lot of people finding that simply disabling hyperthreading is a proper solution.

The findings so far is that crashes are far more frequent on games developed on Unreal Engine 4 and 5, and I've certainly had a few examples of this where disabling hyper threading immediately corrected the issue.

Affected titles include Hogwarts Legacy, Fortnite, Remnant 2, Nightingale, and more.

No word from Intel as yet, but it does seem there may be a correlation as Intel have confirmed they're removing hyper threading from CPU's from now on

Intel CPU gaming crashes are causing an uproar

Many users are reporting issues with crashes in games on Intel's top CPUs, including the Core i9-14900k.

www.digitaltrends.com

MSI Global English Forum

...

forum-en.msi.com

PSA: Try turning off E-Cores if crashing with Intel CPU :: Cities: Skylines II General Discussions

I was getting crashes every 10 minutes while trying to play, and turning off E-cores with Process Lasso fixed them entirely. I have played for 8 hours straight without a single crash after having a 10 crashes in 2 hours before the change. My PC specs: i9-13900k RTX 3090 32GB RAM I am running at...

steamcommunity.com

Solved - All games having crashing issues suddenly

Hi everyone, im hoping to get some insight on what the problem with my pc could be. Here are my pc specs: CPU: 13700kf GPU: PNY XLR8 4090 RAM: G.Skill ddr5 6400mhz cl32 Mobo: MSI Z790 Tomahawk PSU: Corsair RM1200 SHIFT AIO: Arctic Liquid freezer II 360 SSD: Kingston kc2500 2tb, firecuda 2tb...

pchelpforum.net

Intel 15th-Generation Arrow Lake-S: A Shift Away from Hyper-Threading Technology?

Recent leaks have revealed insights into Intel's 15th-Generation Arrow Lake-S platform, particularly focusing on its CPU architecture and potential shift in multi-threading approach.

www.guru3d.com

 

[TonyCarter]

Sucks to be Intel or Intel fanboi

 

[Tron1982]

Sometime, you don't really have the choice ^^"
Specially in the laptop space ^^"

 

[ubuysa]

I've been helping a user on another forum with BSODs and freezes whilst gaming. The user is running an i9-13900K and an RTX4080 on an Asus Z790 Gaming A board. We'd managed to highlight the CPU as a likely cause and the user brilliantly came back with the solution. It's apparently a known issue with i9-13900K and i9-14900K CPUs. The solution (or workaround) is from Intel's own forum here...

Please try the following steps:
-Install XTU, run AVX2 test, and check if the processor passed that test, if it fails, please change the next BIOS settings:
Advanced (F7)
AI Tweaker
SVID Behavior: Change to “Intel’s Fail Safe”
-Reboot the OS and run XTU test again in order to confirm if the unit passed the AVX2 test
-Run the games as well and see if the issue happens again

Responses from this thread on the Intel forum are positive and the user I was helping also reports that this SVID change eliminated the BSODs and freezing.

 

[SpyderTracks]

I've been helping a user on another forum with BSODs and freezes whilst gaming. The user is running an i9-13900K and an RTX4080 on an Asus Z790 Gaming A board. We'd managed to highlight the CPU as a likely cause and the user brilliantly came back with the solution. It's apparently a known issue with i9-13900K and i9-14900K CPUs. The solution (or workaround) is from Intel's own forum here...

Responses from this thread on the Intel forum are positive and the user I was helping also reports that this SVID change eliminated the BSODs and freezing.

Looks like @ubuysa is entirely on to something here.

Turns out returns of Intel 13th and 14th Gen are so frequent in Korea that Intel have warranted opening an investigation into finding out the cause.

Intel reportedly "investigating" 13th/14th crashing issues in games - OC3D

Intel have reportedly opened an investigation into 13th/14th generation Raptor Lake CPU crashing issues in popular games.

overclock3d.net

Gamers are reportedly returning Intel Core i9 CPUs in droves

An increasing number of customers are reporting issues with Intel's latest Core i9 CPUs, and the company is finally looking into the problem.

www.digitaltrends.com

Intel's 13th & 14th Gen CPU "Gaming Stability" Is Being Investigated As 10+ Chips Being Returned In Korea Each Day

Intel has started investigating issues currently facing its 13th & 14th Gen CPUs such as gaming stability which affects thousands of gamers.

wccftech.com

For Intel to open an investigation shows that they acknowledge there's a problem, Intel almost never do that, since the 12th Gen with the enormous heat causing warping, they've denied any kind of issue that's affected each platform since, but looks like there's just too much evidence now not to raise an official investigation.

Early reports are that due to the ridiculously high temperatures, the silicon is actually starting to degrade after around 3 months of use literally leading to core meltdown! Nothing has been said officially though so take everything with a pinch of salt at this stage.

If you are facing any kind of instability with your Intel chip and don’t have any luck with @ubuysa thread above, undervolting should be the first step to see if you can find some stability, IMHO, under clocking is totally rediculous and if you're finding that's the only way to get it stable, I'd seek an RMA rather than settling with nerfed performance on a very expensive CPU!

 

[SpyderTracks]

 

[SpyderTracks]

Jayz input

 

[Scott]

Should just point everyone looking at a 14900k build to watch the last 5 minutes of that vid. It sums it up for me. Amps & Temp pushed way further than the silicone can handle in order to beat AMD at metrics. No consideration whatsoever to the consumer for the £600 paperweight they could end up with.

Added bonus of a CPU that can potentially be held inside 100C with an AIO too.

Curious if Puget are running Intel governed limits on their testing benchmarks etc.

 

[SpyderTracks]

Should just point everyone looking at a 14900k build to watch the last 5 minutes of that vid. It sums it up for me. Amps & Temp pushed way further than the silicone can handle in order to beat AMD at metrics. No consideration whatsoever to the consumer for the £600 paperweight they could end up with.

Added bonus of a CPU that can potentially be held inside 100C with an AIO too.

Curious if Puget are running Intel governed limits on their testing benchmarks etc.

The other question is so far, this seems to only have been reported in the gaming community, but judging by the findings so far, I think it’s likely that professional users may have stronger cooling setups that are perhaps delaying the degradation, if not preventing it with hardcore coolers.

But I suspect this will become more widespread outside of gaming within 3 months.

 

[SpyderTracks]

Unofficial update from Intel to board partners made public by Igor of Igors Labs, they blame board manufacturers out of the gate, but admit the root cause hasn't been identified.

Bear in mind a lot of these issues occur with brand new CPU's out of the packaging. The over voltage settings set by some board manufacturers could certainly contribute to deterioration over a period of time, but the issue isn't limited to that.

This will reduce performance slightly putting in proper limits.

Intel issues statement about CPU crashes, blames motherboard makers — BIOSes disable thermal and power protection, causing issues

Intel points out motherboard profiles with disabled protections while exceeding recommended voltages to gain high overclocks.

www.tomshardware.com

The other thing I don't understand about this is that a lot of people have said that disabling hyperthreading has stopped the issue from occuring, but without applying the proper limits on the board power profile. I don't understand enough about the workings of CPU's at this level, but don't really understand the correlation between hyperthreading and ramping up excess voltages. Intel have been pushing to do away with Hyperthreading since 9th Gen, and only haven't due to public backlash, but it's been loosely confirmed that 15th Gen onwards won't have hyperthreading.

 

[SpyderTracks]

Update from Hardware Unboxed calling out Intel for blaming board partners.

I edited my initial previous post because I’d put a line in the first line saying “great way to annoy your partners” because I suspected Intel had been pushing partners to eek out as much performance as possible so they could remain competitive in reviews.

What’s even weirder is that ASUS and Gigabytes newly released BIOS updates that apply “Intel Baseline Profiles” are different with gigabytes being more aggressive, which is extra weird

But performance wise in multithreaded, you’re looking at anywhere from 9% on Asus to 25%!!! On gigabyte performance drop with the new limits. Gaming is less affected as it’s usually only a few cores peaking in short bursts rather than a sustained all core load, here it’s up to around 5% on Asus and sometimes 12% on gigabyte.

Now currently both the gigabyte and asus new BIOS are beta so don’t expect this to be the final result. We don’t know why gigabytes cuts are so much heavier, weather that’s a mistake or for another reason.

HUB are calling them out saying it’s intels responsibility and that they have evidence to prove it

 

[SpyderTracks]

Now, this isn’t limited to Intel, AMD had exactly the same issue with the SoC voltage running too high on boards on the new AM5 boards.

The difference in handling it though are entirely different. AMD are very connected to the community and use their forums to track feedback and respond to user issues. They took ownership and rolled out a FEW Agesa updates before they got it right. Board partners in the main were quick to roll out BIOS updates. Asus seemed to struggle more than other partners in getting their boards stable with the new agesa limits and initially they even said anyone applying these BIOS fixes would void their warranty until GamersNexus called them out about it.

Here is also a direct quote from one of the early users affected who worked with AMD and their experience

AMD Ryzen 7 7800X3D CPU Burns Up, Kills Itself & The ASUS X670 Motherboard

There are reports of AMD's Ryzen 7 7800X3D CPUs burning up and killing the ASUS X670 motherboard with it from the AMD subreddit.

wccftech.com

But with AMD, the release was October reports started hitting in around April, fixes started flowing in April after AMD liaised directly with people affected and people like GN and buildzoid who were investigating, and after a few mis hits, the final agesa update was pushed out to all board partners by beginning of May

AMD Issues Official Statement on Reported Ryzen 7000 Burnout Issues

www.anandtech.com

With Intel, the officially responded to consumer complaints in February

Regarding Reports of 13th/14th Gen Unlocked Desktop Users Experiencing Stability Issues

*9/25/24 - Please go to the following link for the latest updates: Intel Core 13th and 14th Gen Desktop Processor Vmin Instability Issue Root Cause* Intel is aware of reports regarding Intel Core 13th and 14th Gen unlocked desktop processors experiencing issues with certain workloads. We’re...

community.intel.com

Yesterday was intels first official response almost 2 months later and that was to try to deny it was anything to do with them and blame their partners which it’s been proven by HUB that they’ve always said these parameters were still considered in spec. And the fixes so far have been done by board manufacturers, not Intel

AMD are not faultless, and this highlights the need for both of them to clearly define what is to be in spec going forwards

But there is a big difference in the attitude of both companies in respect to listening to the community feedback, and their respect for partners.

 

[Scott]

Really great info, thanks for the summaries as well. Incredibly helpful, especially for anyone without their finger fully on these pulses.

As you have highlighted, everyone makes mistake. It's the reaction that matters more than the issue.

 

[SpyderTracks]

 

[Scott]

Didn't watch all of it, had a little nosey through it though and caught some snip discussions. Pretty fair from what I could see. They're much more polite with the fanboi contingent than I would be. Imagine criticising an outlet for bringing news of an issue to you purely because you feel the need to justify your choice!

 

[SpyderTracks]

Didn't watch all of it, had a little nosey through it though and caught some snip discussions. Pretty fair from what I could see. They're much more polite with the fanboi contingent than I would be. Imagine criticising an outlet for bringing news of an issue to you purely because you feel the need to justify your choice!

I got in a twitter argument with a couple of fanboi's who were adamant that as long as intel were offering to fix them, then any voltage values were within spec.

And one of them went on to tell me how it was important that board manufacturers allowed you to adjust the TDP of the CPU????

I called them a few names and exited the conversation.

The very real consideration is that if intel double down on blaming board partners, it squarely forces the responsibility onto them, and Intel can claim that it's not covered by their warranty and people have to go to board partners. That would be suicide for Intel, but I wouldn't put it past them.

 

[SpyderTracks]

Sometime, you don't really have the choice ^^"
Specially in the laptop space ^^"

Oh, apologies, should have stated this previously, so far, this is only reported on desktop CPU's, laptops are not affected.

 

[Tron1982]

Oh, apologies, should have stated this previously, so far, this is only reported on desktop CPU's, laptops are not affected.

"a few moment later" XD

Anyway, thank you for this information, it's good to know !

 

[ubuysa]

FWIW this issue is indeed universal. As a BSOD analyst on many forums it's got so bad now that before I even look at the dumps I check the CPU type. There's no point in looking at the dumps for the affected Intel CPUs, it just leads down pointless rabbit holes...!

 

[SpyderTracks]

FWIW this issue is indeed universal. As a BSOD analyst on many forums it's got so bad now that before I even look at the dumps I check the CPU type. There's no point in looking at the dumps for the affected Intel CPUs, it just leads down pointless rabbit holes...!

When you're analysing the logs, is there anything repetitive amongst them or is it general errors that just seem random between cases?