#Crash on startup
12 messages · Page 1 of 1 (latest)
Things we've tried:
- launching as admin
-deleting the sl.pcl.dll (a few times then reset)
-launching from file as admin
-launching steam as admin
-manually allocating increased VRAM (Reset after)
One attempt resulted in Blue Screen with the error " ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY "
Most of the time the game attempts to launch I get either Black Screen or Logo and then the game just stops and i go back to steam library.
Sometimes crashes my discord call as well
Update:
Managed to get into the menu before crashing? I'm not sure what I changed if anything to make that happen.
Just started it randomly and it go there
From one of the crash reports, the error is fairly descriptive:
Fatal error: [File:F:\GitEngine\UnrealEngine\Engine\Source\Runtime\RenderCore\Private\ShaderCodeArchive.cpp] [Line: 440]
DecompressShaderWithOodleAndExtraLogging(): Could not decompress shader group with Oodle. Group Index: 27 Group IoStoreHash:0a637398e39802f182106e09 Group NumShaders: 40 Shader Index: 559 Shader In-group Index: 27 Shader Hash: AFAD0857340D4C5F34569230B4CF97F028E4AE32. The CPU (Intel(R) Core(TM) i7-14700KF) may be unstable; for details see http://www.radgametools.com/oodleintel.htm
RAD Game Tools' web page. RAD makes Bink
Video, the Telemetry Performance Visualization System, and Oodle Data Compression - all popular video game middleware.
Finally awake:
Fatal error: [File:F:\GitEngine\UnrealEngine\Engine\Source\Runtime\RHI\Private\Windows\WindowsDynamicRHI.cpp] [Line: 824]
Unable to launch with RHI 'D3D11' since the project is not configured to support it.
That was caused by you trying to troubleshoot, so you can disregard this and generally stop using DX11 toggle in UE5 games that do not have the option for it by default, it's 99% not supported.
In most DX12 titles that have shader compilation on boot screen, you can resume it just fine in an instance the title crashes. In that way you can bruteforce your way through it on unstable CPU like that, up until that CPU fails to run at base clock that is.
If neither of your fixes were "updating BIOS" then you have to go through that process on Raptor Lake CPUs, since it's a broken product by default.
So basically this is just a matter of update bios like a few others Thank you
Updating the bios works. Thank you for helping!