I would agree if....it was an issue in many games. Is there any other game having this issue that you know of? If not then isn't the issue simply that the game is doing something odd and over pushing a cpu, or at least doing something that no other game does that runs into a weird issue?
Right now the uniqueness of the issue seems to be a this game issue, not a hardware issue to me.
You're coming in late to this story. I haven't even tried Outpost: Infinity Siege. That it's exhibiting problems for some Core i9 users isn't even remotely surprising to me, because many games had problems over the past year or so. Here's a
Steam forum thread on the subject.
Horizon Zero Dawn would fail during shader compilation about 80% of the time — or rather, it would probably get something like 10–30 percent finished each time I restarted and tried again, so after five times it would finally have all of the shaders compiled and would then run fine.
The Last of Us, Part 1 crashed to desktop about 90% of the time. Hogwarts Legacy was so bad that I was convinced the game was unplayable and left it alone for a couple of months. Metro Exodus: Enhanced crashed maybe 60% of the time (until shader compilation was finished). Immortals of Aveum was another impacted game. There have been at least half a dozen games that I personally tried where they would crash, and by no means have I sampled every game out there, not even close.
About nine months back, I had figured out a workaround: I would set the game processor affinity to just eight of the P-cores (none of the E-cores). This would get the affected games to finish shader compilation probably 80–90 percent of the time. I had also noticed that my CPU was hitting 98–100C before crashing, which is why I even tried messing with affinity.
So then a few months back, I was having a conversation in the forums regarding another game or something. That led to the writing of this article:
https://www.tomshardware.com/pc-com...blame-other-high-end-intel-cpus-also-affected
In other words, yes, this happens in quite a lot of games for impacted CPUs / motherboards / whatever. It definitely doesn't affect all Core i9-13900K or 14900K processors. In fact, it's probably a very small percentage, like 5% at most. If it was a bigger problem, it would have been all over the internet right when the 13900K launched. But if you have a CPU that's right near the limit of stability at "stock" settings, then it seems a lot of motherboards push beyond safe levels and that causes the problem.
Does that make it Intel's fault? Well, not if the CPUs are fully stable at stock settings. Just because 12900K, 11900K, 10900K and 9900K were all fine being pushed higher than the official specs doesn't mean every future CPU needs to have the same margins. And that's the crux of the issue. We need proof of CPUs that can't even run safely at stock settings to prove this is a problem... and they need to be new CPUs that weren't potentially run at "auto overclock" settings for a year or more, because that could cause degradation.
In my book, what we really need is for the motherboard makers to stop using auto-overclocks as the default behavior in their BIOS / firmware. I'm not against having those settings, but they should clearly be a case of users saying, "Yes, please, try to give my system a modest performance boost by increasing the power levels, core clocks, and memory speeds." If I tell the BIOS to load optimized defaults, that doesn't even turn on XMP, so why should it turn on higher power and current limits that spec?
Facebook
Twitter
Instagram