We have a problem where players crash in Oodle decompressing shaders. This results in the error message:
FCompression::UncompressMemory - Failed to uncompress memory (41621/88635) from address 0000020FB80A0000 using format Oodle, this may indicate the asset is corrupt!
appError called: Fatal error: [File:C:\HordeAgent\RideGameMainInc-main\Sync\Engine\Source\Runtime\RenderCore\Private\ShaderCodeArchive.cpp] [Line: 491]
DecompressShaderWithOodleAndExtraLogging(): Could not decompress shader group with Oodle. Group Index: 103 Group IoStoreHash:134231c3a960eec178b32009 Group NumShaders: 9 Shader Index: 2237 Shader In-group Index: 103 Shader Hash: 1D402B96549B398AD654A87F5F2AB0BEA997BED3. The CPU (Intel(R) Core(TM) i9-14900K) may be unstable; for details see http://www.radgametools.com/oodleintel.htm
One player we are talking to don’t experience any issues with other UE5 titles, for instance Satisfactory. Their CPU reports all green with the Intel Processor Diagnostic Tool. And capping the framerate solves the issue.
His computer is a beast (i9-14900K and NVidia RTX 5800). Non Intel users has reported this also. To me this suggests that the CPU gets unstable when overheated due to uncapped FPS.
What can we do more than include a FPS limiter to solve this kind of issue?
Sorry to reply even if I’m not Epic but seeing that CPU and the headaches it has brought us I must reply ( feel free to ignore this if it does not help )
I would recommend taking a look at this, to at least discard this posibility:
The case of the user with an Intel i9-14900K would be the hardware failure described in the Oodle post. This means that the chip is permanently damaged and must be replaced. The post refers to Intel resources regarding RMAs. The workaround in Quod Soler’s blog is known to work but not in all cases. As you suspect, the problem is related to overloading the CPU cores while aggressively overclocking. Intel released a microcode update at the end of 2024. When installed, it will prevent the bug from happening.
We have not seen that problem happen with non-Intel CPUs. It would be interesting to get more details on those cases. Is the problem deterministic or random? If deterministic, it would likely be corruption of the data at the disc level or memory corruption cause by race conditions.
Thanks for the information. I have tried to gather more information, but I haven’t gotten much more from the users.
What makes me confused is that the users computer doesn’t crash on other games that use OODLE. Might it be random? Is there any test that can be done just to 100% verify that that’s the issue from the user side, to just show them, “If something here is red, please RMA you CPU”. Or might other reasons trigger the OODLE crash?
I’m not aware of a test to identify the problem. The link to the Rad Game Tools site in the error message does contain some resources that can help the consumers.
Thanks for the reply. The more information I get, the better, so thanks! It was when other users of non Intel cards started to replying that they have the same errors I reacted to it, but they might have misread their logs, and it’s another similar issue.