非UE5的游戏根本不会大面积Trigger这个BUG，只有基于UE5的游戏才会这样高频引起稳定性问题，别的游戏的稳定性问题只能说是个例。
Epic旗下RAD的官方statement:
RAD has become aware of a problem that can cause Oodle Data decompression failures, or crashes in games built with Unreal. We believe that this is a hardware problem which affects primarily Intel 13900K and 14900K processors, less likely 13700, 14700 and other related processors as well.
https://www.radgametools.com/oodleintel.htm
Nightingale(UE5游戏）的Steam社区讨论：
To everyone experiencing shader compilation "Out of video memory trying to allocate a rendering resource" errors
Your CPU is faulty and has Core errors. It's not your GPU, its your CPU
Crashing with this sort error message (and others, including straight up CTDs) when performing shader compilation is famously caused by broken CPUs, namely the Intel 13x and 14x series, and more specifically (but not solely) the 13900k and 14900k variants.
Anyone affected by shader comp crashing on the aforementioned CPUs just needs to open Event Viewer and do a parse for 'WHEA-Logger' warnings. Inside those entries, look for 'Translation Look Aside Buffer' and 'Internal Parity Error'. There will be lots. That's a bad CPU.
Furthermore, the CPU core errors, which are PCore-based can be surfaced by running OCCT whilst applying a very slight OC via BIOS, with SVID=Typical and LLC=4. OCCT will out Core errors almost immediately and then throughout the rest of the run. You may even get OCCT to report Core errors without these BIOS tweaks, depending on how bad the CPU has gotten. Attempt any this at your own risk. I'm simply reiterating how I was able to isolate down.
https://steamcommunity.com/app/1 ... 221029098493967556/
REMNANT 2 （UE5游戏）的官方答复：
--Out Of Memory when Loading (Intel 13th generation CPU’s)--
We have identified an issue on some Intel 13th generation CPU’s where upon startup the game will display a message about being out of video memory or the crash reporter will pop up referencing an issue with decompressing a shader. If you experience this problem, you will likely also see it in other DX12 games.
https://www.remnantgame.com/en/news/article/11551423
还有很多UE5游戏关于intel稳定性问题的社区讨论和官方答复，我就不全贴了，你想找我可以给你找十来个出来。
现在是intel这边的最新答复：
Intel analysis has determined a confirmed contributing factor to the instability reports on Intel Core 13th and 14th Gen (K/KF/KS) desktop processors is elevated voltage input to the processor due to previous BIOS settings which allow the processor to operate at turbo frequencies and voltages even while the processor is at a high temperature.
However, in investigating this instability issue Intel did discover a bug in the Enhanced Thermal Velocity Boost (eTVB) algorithm which can impact operating conditions for Intel Core 13th and 14th Gen (K/KF/KS) desktop processors. We have developed a patch for the eTVB bug and are working with our OEM/ODM motherboard partners to roll out the patch as part of BIOS updates ahead of July 19th, 2024. While this eTVB bug is potentially contributing to instability, it is not the root cause of the instability issue.
As Intel and its partners continue working towards a conclusion to the investigation, we want to make sure that all users are clear on the recommended power delivery profile settings for Intel Core 13th and 14th Gen (K/KF/KS) desktop processors. Intel also recommends users check their motherboard vendor’s website for the latest relevant BIOS updates:
Next Steps
As we noted earlier, this investigation is not an easy one to conduct and we’re grateful for both the support of our partners in conducting the analysis as well as the patience of the Intel community.
In the interim, please reach out to Intel Customer Support if you have questions or concerns regarding your Intel Core 13th or 14th Gen (K/KF/KS) desktop processor.
https://community.intel.com/t5/P ... /m-p/1607807#M73544
意思是问题还没有解决，顺便把13600K/KF, 14600K/KF也加到了问题影响的列表里。目前intel还是在通过售后换新来处理。
顺便，这不是很多人理解的降频锁功耗降压就能简单处理的，因为参照前期intel处理这个问题是严格锁功耗，但是现在有部分放开功耗的情况来看，功耗不是影响稳定性问题的关键。现在intel自己也不清楚到底问题出在哪里，所以很多坛友理解的降压降频保平安并不是解决问题的办法。目前最靠谱的方法还是更新最新的BIOS+售后换新。
|
310112100042806
发表于 2024-6-22 15:25
