Intel processors crashing Unreal engine games (and others)

[Ranulf]

Tom 'TAP' Petersen, the face of Intel Graphics. Ryan Shrout was dead weight.

Funny how things turn out over say 10 years. That Tom is at Intel now (formerly Nvidia) and talking a lot with GN is certainly a thing I wouldn't have expected. I used to be a fan of Shrout at PCPer and AMDmb before that.

 

[Saylick]

Seems like it was a microcode issue:
https://www.igorslab.de/en/intel-co...hensive-update-of-its-own-investigation-leak/

Root Cause Root cause is an incorrect value in a microcode algorithm associated with the eTVB feature.
Implication Increased frequency and corresponding voltage at high temperature may reduce processor reliability.
Observed Found internally.
Impacted platforms Raptor Lake S, Raptor Lake Refresh S (CPUID 0xB0671)

 

[KompuKare]

"may reduce processor reliability."
Is that temporary here-and-now reliability, or long term we-have-degraded-your-CPU reliability?

And, are they actually going to release and official statement including RMA and warranty info?

 

[Hitman928]

"may reduce processor reliability."
Is that temporary here-and-now reliability, or long term we-have-degraded-your-CPU reliability?

Yes.

 

[igor_kavinski]

Goody. Now I can look forward to a future where I might be able to buy a cheap used delidded 14900KS.

 

[DAPUNISHER]

100% Intel's screwup. All of those that were blaming the users are looking really bad right now.

 

[Kepler_L2]

Seems like it was a microcode issue:
https://www.igorslab.de/en/intel-co...hensive-update-of-its-own-investigation-leak/

I wonder how TVB is causing crashes when non-TVB CPUs like 13700K/14700K also had issues.

 

[Kepler_L2]

The saga continues: https://www.tomshardware.com/pc-com...re-i9-crashing-issues-investigation-continues

 

[Saylick]

The saga continues: https://www.tomshardware.com/pc-com...re-i9-crashing-issues-investigation-continues

Just sad. I don’t see how this isn’t anyone but Intel’s fault. If the CPU vendor can’t identify the root cause with all the resources at their disposal, how can we blame mobo vendors or reviewers who have only a fraction of those same resources?

My cynicism tells me Intel likely will just sweep this under the rug since they’ve moved onto MTL and soon enough LNL and ARL.

 

[Thunder 57]

LoL at Tom's for simping for Intel.

eTVB technology is an exclusive feature for Intel's Raptor Lake chips, specifically the Core i9 SKUs, so the ongoing instability issues don't affect the rest of Intel's processor population. eTVB is a great asset for Core i9 processors since it gives them a burst of performance in games and applications that prize high clock speeds.

Yup, let's not focus on them crashing and still not identifying a root cause. eTVB is awesome, trust us, just buy it. /s

I have a feeling Intel knows the root cause. They are just trying to figure out a way of saying they overclocked their chips too far without actually saying that.

 

[adroc_thurston]

The saga continues: https://www.tomshardware.com/pc-com...re-i9-crashing-issues-investigation-continues

"We failed at binning but not as hard as Qualcomm with 4.3G Hamoa" definitely takes the 2024 failure crown so far.

 

[branch_suggestion]

When you have a good part and a good node you can settle for a very comfy stock part and have everything you need.
Intel meanwhile has leaned desperately hard into the 'gamer stable' crowd which is just a paradise of grifters, not to mention the lack of oversight on OEM BIOS settings.
Why? Because the thing at reasonable clocks has no competitive edge at all.

 

[igor_kavinski]

Because the thing at reasonable clocks has no competitive edge at all.

Intel just refuses to learn from their mistakes. They ignore that Broadwell was still decent for gaming even in 2020. They ignored the performance advantage of 5800X3D. Heck, when AMD demoed their V-cache prototype, Intel should've embarked on a competing solution that very same day. Then they would've had something to show maybe three years later. But no. These dumb idiots running the show at Intel (Pat's underlings) think that brute force frequency ramping is the solution to everything. It's like they don't understand anything about the importance of latency masking. And the engineers there must be real chickens**ts for not speaking up against stupid marketing decisions.

 

[DAPUNISHER]

TLDW = Why did you buy Raptor Lake high end for gaming again? LMAO

Note: I don't think Steve knew about the TVB bug at time of filming, which may contribute to the issues even if not the primary cause. Consequently, his conclusion to use the XTREME!!1! profile may be inaccurate due to that lack of updated info?

Regardless, if you bought the K SKU and did not plan to manually overclock or tweak it (as numerous responses on r/Intel, reddit, and youtube have asserted) you did not get the performance you paid for. I'd suggest the performance profile as the power savings outweigh the performance regression IMO.

 

[igor_kavinski]

Atrocious!

This is worse than AMD's Bulldozer!

 

[KompuKare]

Intel just refuses to learn from their mistakes. They ignore that Broadwell was still decent for gaming even in 2020. They ignored the performance advantage of 5800X3D. Heck, when AMD demoed their V-cache prototype, Intel should've embarked on a competing solution that very same day. Then they would've had something to show maybe three years later. But no. These dumb idiots running the show at Intel (Pat's underlings) think that brute force frequency ramping is the solution to everything. It's like they don't understand anything about the importance of latency masking. And the engineers there must be real chickens**ts for not speaking up against stupid marketing decisions.

Demoed? The 3D vials were there in Zen3 for ages before AMD said anything and I cannot see how a corporation the size of Intel had not taken an Xray images of Zen3 by then.

As for Broadwell - well that was one of the most interesting Intel CPUs in years but was so largely ignored.

 

[coercitiv]

Stay tuned for Season 2!

Intel releases eTVB microcode fix and new Default Settings for 13/14th Gen Core i5/i7 CPUs, instability investigation still ongoing - VideoCardz.com

New Default Settings for Core i5/i7 SKUs, eTVB microcode update, but no final solution to instability issues Intel has released a new statement on the instability issue observed in some 13th and 14th Gen Core “Raptor Lake” processors. The good news is that Intel is actively working on the...

videocardz.com

TL;DR - New Default Settings for Core i5/i7 SKUs, eTVB microcode update, but no final solution to instability issues.

 

[KompuKare]

Stay tuned for Season 2!

Intel releases eTVB microcode fix and new Default Settings for 13/14th Gen Core i5/i7 CPUs, instability investigation still ongoing - VideoCardz.com

New Default Settings for Core i5/i7 SKUs, eTVB microcode update, but no final solution to instability issues Intel has released a new statement on the instability issue observed in some 13th and 14th Gen Core “Raptor Lake” processors. The good news is that Intel is actively working on the...

videocardz.com

TL;DR - New Default Settings for Core i5/i7 SKUs, eTVB microcode update, but no final solution to instability issues.

i5 and i7? So much for "it only affects some i9 SKUs" then!

 

[igor_kavinski]

View attachment 99259

Will check again after 31st May for a newer BIOS version and see if ASROCK has "fixed" the IccMax value.

Updated to the 11th June BIOS. IccMax is still Unlimited at default settings. However, Turbo Boost Power Max is now 241W by default, instead of 125W.

I'm guessing the BIOS may be applying safe default settings for only 13th/14th gen K CPUs.