The Elder Scrolls IV: Oblivion Remastered

The Elder Scrolls IV: Oblivion Remastered

View Stats:
it keeps crushing
LowLevelFatalError [File:W:\Altar\Engine\Source\Runtime\RenderCore\Private\ShaderCodeArchive.cpp] [Line: 385] DecompressShaderWithOodleAndExtraLogging(): Could not decompress shader group with Oodle. Group Index: 1090 Group IoStoreHash:db58b03a260791e7ec0c4209 Group NumShaders: 12 Shader Index: 15357 Shader In-group Index: 1090 Shader Hash: 7F3F31DF3EB988339812C2946B6D63C3E2C213F0

Can you make sense from it? I can't even open a game now.

My specs:
Intel(R) Core(TM) i9-14900KF
96 Gb RAM, RTX 4090
Win 11 Pro, updated
< >
Showing 1-12 of 12 comments
Have you tried deleting the shader cache?
That's a dying 14900 issue. If you see errors in compression/ decompression you have a 14900 with the oxidizing inside, RMA with Intel

Edit: the official announcement by Oodle https://www.radgametools.com/oodleintel.htm
Last edited by L O F T Y; Apr 23 @ 4:19am
Originally posted by SoNotJames:
Have you tried deleting the shader cache?
Yes, it's still crushing.
Viper Apr 23 @ 8:39am 
Did you upgrade your BIOS which was required for that CPU.
zerrg1234 Apr 23 @ 10:50am 
I FIXED IT

This is what I ended up doing in my BIOS (Motherboard Gigabyte Z790 UD AX) and again, my CPU i9-14900KF (adjust values to your own and your choice):

Package Power Limit1 - TDP (Watts) > 253 (Holy grail, page 98, table 17, 8P+16E Core 125W Extreme Config)

Package Power Limit1 Time > 56 (Holy grail, page 98, table 17, 8P+16E Core 125W Extreme Config)

Package Power Limit2 - (Watts) > 253 (Holy grail, page 98, table 17, 8P+16E Core 125W Extreme Config)

Core Current Limit(Amps) > 307 (Holy grail, page 184, table 77, S-Processor Line (125W) 8P+16E)

Enhanced Multi-Core Performance > Disabled (OP recommendation)

Performance CPU Clock Ratio > 57 (I mentioned I changed this to 56x using XTU, but OP told me to go back to 57 when doing the changes above)

Extreme Memory Profile(X.M.P.) > XMP 1

And ♥♥♥♥♥♥♥♥♥♥ worked flawlessly. :steamhappy:
Restart PC, Windows is famous for memory fragmentation. Restart your PC at least every 7 days. A COLD boot.
Last edited by Pixelfetish; Apr 23 @ 11:03am
The game not even enter just show this msg from Ureal Engine 5:
LowLevelFatalError [File:W:\Altar\Engine\Source\Runtime\RenderCore\Private\ShaderCodeArchive.cpp] [Line: 385] DecompressShaderWithOodleAndExtraLogging(): Could not decompress shader group with Oodle. Group Index: 482 Group IoStoreHash:b7377ab8e7c4713efcfff109 Group NumShaders: 4 Shader Index: 6143 Shader In-group Index: 482 Shader Hash: 217F4BBCC3C92A60209CDC80E9C9C28A98347E08
Last edited by flasilver; Apr 28 @ 5:49pm
ThotsBContagious (Banned) Apr 28 @ 6:01pm 
Originally posted by Pixelfetish:
Restart PC, Windows is famous for memory fragmentation. Restart your PC at least every 7 days. A COLD boot.
He literally stated above he already fixed it lol
Last edited by ThotsBContagious; Apr 28 @ 6:01pm
Now update your motherboard BIOS so your CPU doesn't die.
just deleting the shaders folder helped me
null Apr 29 @ 9:29am 
BIOS has updated the Intel 0x12B microcode, but it still continues to crash. If the power plan of Win11 is changed to energy-saving, it can prevent crashes and ensure stable operation. Does anyone know the reason
Arc Apr 29 @ 11:00am 
Originally posted by null:
BIOS has updated the Intel 0x12B microcode, but it still continues to crash. If the power plan of Win11 is changed to energy-saving, it can prevent crashes and ensure stable operation. Does anyone know the reason
Assuming you didn't undo the stability fixes from those BIOS updates by overclocking the CPU manually and you cool the power hog of a CPU adequately, it means it is unstable even under proper in-spec settings under nominal load.

Which means you should RMA the unit since it is defective. Intel had to cover up these cases with extended warranty for almost all desktop Raptor Lake and Raptor Lake Refresh SKUs:
https://community.intel.com/t5/Processors/Additional-Warranty-Updates-on-Intel-Core-13th-14th-Gen-Desktop/m-p/1620853

You can use number of workarounds to lower the chances to trigger instabilities (underclock, lower power state, etc.) but at that point you wasted a lot of money on a product that you can't even fully utilize anymore.
< >
Showing 1-12 of 12 comments
Per page: 1530 50

Date Posted: Apr 23 @ 3:55am
Posts: 12