NVIDIA GeForce RTX 4070 Intel Core i9-13900KF. Still Crashing every time I try and Exit Sewer.

[jhoncoolidge]

I got the RTX 4070. Not the Super. Just the normal RTX 4070. My Game always crashes when I try and leave the sewers. Updated Drivers and uninstalled and reinstalled the game.

Everything before Sewer exit runs super smooth and fine. Nor complaints. But when I get to the sewer exit I get a crash every time, all the time.

Is this game going to get patched soon? I don't know what to do.

[zaku49]

Try turning off XMP to see if it fixes the issue and update your bios. Your CPU is also part of the intel 13/14 gen issue which means it could be failing.

[The Mud Wizard]

I have an overcocked 4070-ti super and intel 12700, I get about 30 min of play. I accept oblivion might melt my rig. NVIDIA NEEDS TO OPTIMIZE THE DRIVERS HELP!!!!

[Photonboy]

RTX4070 owner here...
You might try the 3rd step here:
https://www.pcguide.com/software/how-to/fix-the-elder-scrolls-iv-oblivion-remastered-crashing/

apparently the game will still crash (and drop FPS) due to a memory leak at some point as well.

[Photonboy]

Originally posted by The Mud Wizard:

I have an overcocked 4070-ti super and intel 12700, I get about 30 min of play. I accept oblivion might melt my rig. NVIDIA NEEDS TO OPTIMIZE THE DRIVERS HELP!!!!

I don't think the crashing has much to do with NVidia's drivers. I played for three hours straight with no crashing on:

RTX4070 (driver 576.28)
R7-5700X3D
32GB DDR4
W11

Oh, in addition to what I wrote in my above post I also rebuilt the shader cache and am running a mod that I think helps with stuttering:

Rebuild shader cache:
Delete "Save_settings" file. Mine was in my OLD Documents folder here->
C:\Users\(yourusernamehere)\Documents\My Games\Oblivion Remastered\Saved\SaveGames

That rebuilt my shader cache AND reset my game settings.

MOD:
https://www.nexusmods.com/oblivionremastered/mods/79?tab=description

Don't use a mod manager. Follow the Installation instructions including to create the "~mod" folder. Yes with the tilde sign.

(I also set an FPS cap of 120FPS for indoors. And I was using Frame Gen which I normally don't use so I got "80FPS" or so outdoors and sometimes hit "120FPS" cap indoors. To me Frame Gen was ideal because anything below 80FPS I get noticeable persistance blur, and the latency seemed acceptable.

I was using a 4K monitor, DLSS Performance, HIGH preset and Lumen HW Ultra)

[eniohideカルロス]

Thankyou for share, I was thinking this issue is because I am using an obsolete RTX 3080 Ti

[Sgt. Flaw]

Turn off all overlays! Even without an overclock MSI afterburner will crash the game...discord ruins performance sometimes as well

Also, make sure your MoBo bios is current to the CPU you're using.

[Morgian]

Turn down the RT. A 3080 is fine for this game.

[bluewaffles4ever]

https://www.quodsoler.com/blog/how-to-fix-crashes-in-unreal-engine5-games-on-intel-i7-13700k-and-i9-13900k-series

This may be the fix you need, and there is an additional link about the issue zaku49 mentioned. Beware of this

[bluewaffles4ever]

"There is a confirmed hardware problem affecting 13th and 14th generation Intel Core processors (13xxx and 14xxx series) that manifests as general system instability and causes, among other things, Oodle Data decompression failures and crashes in games built with Unreal.

When starting an Unreal Engine-based game, the most common failure is of this type:

DecompressShader(): Could not decompress shader (GetShaderCompressionFormat=Oodle)
However, this problem does not only affect Oodle, and machines that suffer from this instability will also exhibit failures in standard benchmark and stress test programs. Any programs which heavily use the processor on many threads may cause crashes or unpredictable behavior. There have been crashes seen in Adobe Premiere, RealBench, CineBench, Prime95, Handbrake, Visual Studio, and more. This problem can also show up as a GPU error message, such as spurious "out of video memory" errors, even though it is caused by the CPU.

The root cause is now confirmed by Intel to be rapid aging of clock signal circuitry in the chip due to a confluence of several other issues. This is actual physical wear of the chip itself, and once this deterioration has occurred, it is sadly irreversible. Affected parts need to be replaced; the process is outlined here.

As of this writing (Oct 1, 2024), new BIOS updates are just being released that avoid the operating conditions causing damage to the circuitry. If you are using a pre-built laptop or desktop PC, the vendors are (or at least will be shortly) distributing BIOS updates containing this workaround. It is important to install these updates ASAP before symptoms manifest. Once the crashes start, it's too late for a software solution! If you built your machine yourself, check your motherboard vendor's web site for an updated BIOS image" from the link

[welltooth]

any time i see one of these posts on any game and then see intel, i automatically assume its the lemon products they have put on the market.

[FaTaLDN]

Originally posted by bluewaffles4ever:

"There is a confirmed hardware problem affecting 13th and 14th generation Intel Core processors (13xxx and 14xxx series) that manifests as general system instability and causes, among other things, Oodle Data decompression failures and crashes in games built with Unreal.

When starting an Unreal Engine-based game, the most common failure is of this type:

DecompressShader(): Could not decompress shader (GetShaderCompressionFormat=Oodle)
However, this problem does not only affect Oodle, and machines that suffer from this instability will also exhibit failures in standard benchmark and stress test programs. Any programs which heavily use the processor on many threads may cause crashes or unpredictable behavior. There have been crashes seen in Adobe Premiere, RealBench, CineBench, Prime95, Handbrake, Visual Studio, and more. This problem can also show up as a GPU error message, such as spurious "out of video memory" errors, even though it is caused by the CPU.

The root cause is now confirmed by Intel to be rapid aging of clock signal circuitry in the chip due to a confluence of several other issues. This is actual physical wear of the chip itself, and once this deterioration has occurred, it is sadly irreversible. Affected parts need to be replaced; the process is outlined here.

As of this writing (Oct 1, 2024), new BIOS updates are just being released that avoid the operating conditions causing damage to the circuitry. If you are using a pre-built laptop or desktop PC, the vendors are (or at least will be shortly) distributing BIOS updates containing this workaround. It is important to install these updates ASAP before symptoms manifest. Once the crashes start, it's too late for a software solution! If you built your machine yourself, check your motherboard vendor's web site for an updated BIOS image" from the link

My game keeps crashing too.
I haven't updated the BIOS yet. Do you think it's too late?

[bluewaffles4ever]

Originally posted by FaTaLDN:

Originally posted by bluewaffles4ever:

"There is a confirmed hardware problem affecting 13th and 14th generation Intel Core processors (13xxx and 14xxx series) that manifests as general system instability and causes, among other things, Oodle Data decompression failures and crashes in games built with Unreal.

When starting an Unreal Engine-based game, the most common failure is of this type:

DecompressShader(): Could not decompress shader (GetShaderCompressionFormat=Oodle)
However, this problem does not only affect Oodle, and machines that suffer from this instability will also exhibit failures in standard benchmark and stress test programs. Any programs which heavily use the processor on many threads may cause crashes or unpredictable behavior. There have been crashes seen in Adobe Premiere, RealBench, CineBench, Prime95, Handbrake, Visual Studio, and more. This problem can also show up as a GPU error message, such as spurious "out of video memory" errors, even though it is caused by the CPU.

The root cause is now confirmed by Intel to be rapid aging of clock signal circuitry in the chip due to a confluence of several other issues. This is actual physical wear of the chip itself, and once this deterioration has occurred, it is sadly irreversible. Affected parts need to be replaced; the process is outlined here.

As of this writing (Oct 1, 2024), new BIOS updates are just being released that avoid the operating conditions causing damage to the circuitry. If you are using a pre-built laptop or desktop PC, the vendors are (or at least will be shortly) distributing BIOS updates containing this workaround. It is important to install these updates ASAP before symptoms manifest. Once the crashes start, it's too late for a software solution! If you built your machine yourself, check your motherboard vendor's web site for an updated BIOS image" from the link

My game keeps crashing too.
I haven't updated the BIOS yet. Do you think it's too late?

I hope not, this is a worse case scenario but it's something to keep in mind

[Photonboy]

13/14th gen Voltage etc issues discussed at length on Gamers Nexus (in addition to above) quite well but I couldn't find the link again. And it's not necessary really as long as you know what to do about it->

Basically:
1) update to the most recent BIOS (read what the BIOS updates say. It should say something like "microcode update to fix..."

2) may need to seek advice for your exact motherboard on settings. Not sure. If unsure, go for defaults. Including XMP for system memory.

3) Stress testing.
Tricky. Because oddly LIGHT usage could actually trigger the issue worse. The reason being that heavy usage tended to manage to throttle down the voltage in the CPU that was problematic. And light usage let more voltage be applied since you didn't need to limit the power draw of the entire CPU.

*Long story short, no matter what your situation you should update your motherboard's BIOS if you have a 13th/14th gen and the microcode BIOS update hasn't been applied.

That doesn't mean Oblivion Remastered crashes are related. If NOTHING ELSE is crashing then it's probably not the issue since good systems are crashing due to the game running out of memory and other reasons.

Basically:
a) update the BIOS
b) probably not a CPU issue if everything ELSE works
c) investigate some of the above fixes (that don't fix all crashes. Nothing does yet.)
d) make a backup SYSTEM IMAGE of c-drive prior to BIOS updates. And make sure you have your Microsoft LOGIN information handy. I had to put that in one time. Another time I didn't.

(and some of your BIOS settings may get changed that you want to change back. Such as you may want "CSM" (compatibility support module) disabled. May have Virtual (intel name?) enabled, Secure Boot etc. Maybe go look at the BIOS before updating.)

**Are you fine for the CPU?
Well, it's just wait and see after that. Again, if only one game is crashing assume it's the GAME that is the problem not your CPU. If several months go by without crashing you may be okay.

You may want to consider running MEMTEST86 as well. Free version.

[SuPRn0A]

If you happen to equip a silver bow or a silver dagger. Sometimes the game crashes because of the silver gears, i did not encounter other crashes than when i equiped silver stuff. Unequip any silver gear fixed the crashes here. Just saying.

[bluewaffles4ever]

Originally posted by Photonboy:

13/14th gen Voltage etc issues discussed at length on Gamers Nexus (in addition to above) quite well but I couldn't find the link again. And it's not necessary really as long as you know what to do about it->

Basically:
1) update to the most recent BIOS (read what the BIOS updates say. It should say something like "microcode update to fix..."

2) may need to seek advice for your exact motherboard on settings. Not sure. If unsure, go for defaults. Including XMP for system memory.

3) Stress testing.
Tricky. Because oddly LIGHT usage could actually trigger the issue worse. The reason being that heavy usage tended to manage to throttle down the voltage in the CPU that was problematic. And light usage let more voltage be applied since you didn't need to limit the power draw of the entire CPU.

*Long story short, no matter what your situation you should update your motherboard's BIOS if you have a 13th/14th gen and the microcode BIOS update hasn't been applied.

That doesn't mean Oblivion Remastered crashes are related. If NOTHING ELSE is crashing then it's probably not the issue since good systems are crashing due to the game running out of memory and other reasons.

Basically:
a) update the BIOS
b) probably not a CPU issue if everything ELSE works
c) investigate some of the above fixes (that don't fix all crashes. Nothing does yet.)
d) make a backup SYSTEM IMAGE of c-drive prior to BIOS updates. And make sure you have your Microsoft LOGIN information handy. I had to put that in one time. Another time I didn't.

(and some of your BIOS settings may get changed that you want to change back. Such as you may want "CSM" (compatibility support module) disabled. May have Virtual (intel name?) enabled, Secure Boot etc. Maybe go look at the BIOS before updating.)

**Are you fine for the CPU?
Well, it's just wait and see after that. Again, if only one game is crashing assume it's the GAME that is the problem not your CPU.

For me it's only this game that I was having these issues with, so I'm thinking my cpu is probably fine, but yeah just a wait and see situation. Of course Oblivion of all games would do something like this. Already updated my bios and have default settings and I have my cpu under warranty but hopefully I won't need to use it. Done all the memory tests and processor diagnostic stuff, everything came back fine so fingers crossed