Crashes

[EUMOK1]

Oblivion Remastered Crashes: A Deep Dive Into a Cross-Platform Engine-Level Bug

TL;DR:
This post summarizes a major crash issue in Oblivion Remastered that appears across all platforms (PC + Xbox), all GPU vendors, and multiple player scenarios. After debugging across hours of play, I believe the root cause lies in the way legacy Oblivion scripting and object calls interact with Unreal Engine 5’s asynchronous streaming and memory systems.


---

Crash Pattern Observed:

Happens when transitioning from interior to exterior areas, or fast traveling

Can trigger during save/load, continue from menu, or exiting dialogue scenes

Affected systems include:

AMD & Nvidia GPUs

Intel CPUs

Xbox Series X/S consoles



> This crash is not isolated to one hardware or driver set. It is engine-level and manifests inconsistently, often after 1–3 hours of play.




---

What the Logs Show:

The crash descends into:

OblivionRemastered_Win64_Shipping

kernel32.dll

ntdll.dll


On PC, this presents as a GPU crash dump followed by the Unreal Engine crash reporter.

On console, it causes an app crash to the dashboard.



---

Likely Root Cause (Based on Technical Analysis):

The legacy Oblivion scripts are attempting to access or maintain references to objects (e.g., items, terrain meshes, or triggers) that have already been flushed or unloaded by UE5’s streaming system. This results in:

A GPU memory call attempting to render or resolve an asset that no longer exists

A mismatch between a shader/material and its referenced mesh or transform data

A crash when the system can’t resolve or recover that invalid state


This behavior is consistent with a streaming pool overflow, invalid render thread call, or dangling object reference passed to the GPU too early or too late.


---

Why This Affects Everyone:

Consoles cannot modify .ini files or driver behavior—yet they crash too.

The PC version, even with tuning, still crashes under heavy zone transitions.

This indicates a systemic issue in the packaged build—not something the player can permanently fix.



---

Temporary Mitigations (PC only):

For PC users, I’ve had limited success reducing crash frequency by:

Disabling AMD Adrenalin overrides

Disabling Steam Overlay

Launch flags:

-useallavailablecores -NoTextureStreaming -windowed

Modifying Engine.ini:

[SystemSettings]
r.Streaming.PoolSize=6144
r.Streaming.LimitPoolSizeToVRAM=1
r.Lumen.Reflections=0
r.Lumen.GlobalIllumination=0


> However, this does not eliminate the problem, and console users have no such options.




---

Request to Devs:

This crash behavior cannot be resolved by the community alone. It is likely caused by a mismatch between legacy asset logic (or wrapper calls) and UE5's async loading pipeline. I believe it warrants:

A formal investigation and memory validation patch

A review of how objects are held or released between world transitions

A user-configurable memory/streaming setting or fallback toggle in the options menu



---

If You've Experienced This Too:

Please comment with:

System specs or console model

What you were doing when the crash occurred

Whether you’re using mods or launch flags


Let’s help gather more data and push for visibility.


---

This game is beautiful, and I want to keep playing it. But we shouldn’t be the QA department for a shipping product.
The bug is real. It’s replicable. And it needs a fix.

— A concerned and capable player (aka @Eumok)

[Prokjohnny]

rx6700xt, ryzen 7 3800, 32gb ram, opening a door from a crypt to the forest. Game is fantastic just makes me irate this wasn't fixed before launch cause aint no way they didnt know about it. Literally fantastic game i dont even want to play anymore because its so ♥♥♥♥♥♥♥ annoying.

[Girth Worm Jim]

RTX2060 12gb, Ryzen 5 5600X, 32gb memory.
I've been encountering that crash somewhat consistently but also encountering major black screen freezes when going into a load zone (transitions into cyrodiil, cities, or interior cells) that force me to either restart my pc or log out of windows that had started happening around 50 hours in.
I do genuinely enjoy this game, but as it stands right now, it's ♥♥♥♥♥♥ bad enough to be unplayable.

[Steven Silverheart]

Same issue here.

[Mightylink]

I've been watching users pass all sorts of blame to each other for the past 2 weeks but this is certainly a bug in the games coding, it seems to happen much more often when your inventory has much more weight in it and when an autosave is triggering. I've particularly noticed it happening much more often when I use feather and have over 700 weight in my inventory and it happens often when changing cells.

There is also a separate crash that is triggered when an enemy is paralyzed and is hit a certain way.

People need to stop telling users to "upgrade their potatoes" or "lower your graphics settings" because these crashes aren't related to that.

The only fix is to wait for the developers to fix it.

[foxglov]

I play on PC AMD 9950x 96gig ddr5 6000 mts memory on crucial T705 PCIE gen 5 SSD. GPU is a 5070ti. Windows 11 latest maintenance. The game crashes randomly and my save files appear to be corrupted. Great game but this is seriously annoying! Thank you for the analysis in your original post.

[★REM★]

almost 50 hours. ZERO crashes. take your math. It's your system.

[Weird Potato]

Not a single crash here. Wait, one singular " fatal error" crash attributed to gpu memory overclock, not one since.

[Wille84FIN]

30 hours in, no crashes. Clearly not everyone.

[Xurxo]

Saliendo al mundo abierto.
Si no carga, cambio la configuración de gráficos y funciona un rato.
i9-13900KF 4090 32 GB DDR5

[Torsion]

Ryzen 9 5900X, Radeon RX6750XT, 32GB Corsair Vengeance @3200. Running at 3440x1440, all ultra but with quality FSR and frame gen on. Generally speaking fps is fine (50-60 outside, 80-100 inside). But sometimes the game just slows down for no reason to 18-20fps, only solved by restarting. Often crashes on area change, usually to the overworld.

It's strange because I've had like 10 hours without these issues, but the first 5 and last 5 hours I constantly have it. I'm guessing there is some item you can carry that does something to mitigate the problem.

I'm bummed because I love the game and I would very much just like to play uninterrupted. Often times I just give up now after a few crashes, annoying as hell.

[MrBones]

I've had this issue since launch. Nobody cares.
People have a compulsive need to shill. This is a very poorly designed, poorly optimized game for the vast majority of players. There's a reason it was surprised dropped the way it was.

[MrBones]

İlk olarak Mightylink tarafından gönderildi:

I've been watching users pass all sorts of blame to each other for the past 2 weeks but this is certainly a bug in the games coding, it seems to happen much more often when your inventory has much more weight in it and when an autosave is triggering. I've particularly noticed it happening much more often when I use feather and have over 700 weight in my inventory and it happens often when changing cells.

There is also a separate crash that is triggered when an enemy is paralyzed and is hit a certain way.

People need to stop telling users to "upgrade their potatoes" or "lower your graphics settings" because these crashes aren't related to that.

The only fix is to wait for the developers to fix it.

İlk olarak Mightylink tarafından gönderildi:

I've been watching users pass all sorts of blame to each other for the past 2 weeks but this is certainly a bug in the games coding, it seems to happen much more often when your inventory has much more weight in it and when an autosave is triggering. I've particularly noticed it happening much more often when I use feather and have over 700 weight in my inventory and it happens often when changing cells.

There is also a separate crash that is triggered when an enemy is paralyzed and is hit a certain way.

People need to stop telling users to "upgrade their potatoes" or "lower your graphics settings" because these crashes aren't related to that.

The only fix is to wait for the developers to fix it.

I'm not holding my breath for a patch. They basically released this and then ghosted.

[xXDrEvil212Xx]

ryzen 9 9900x3d, 7900xtx, 64gb ddr5 @6000mt. I have only managed to get as far as character creation after intro video. I have tired every fix, and change graphic settings from 4k to 1080p, high to low settings.
I have ran any other game with no hang-ups, I have ran stress tests, and memtest. All with no errors.

[Torsion]

@EUMOK1 Another observation that might help:

In my post I noted that I had a certain amount of hours playing without much issues. I just noticed, after some troubleshooting, that I did a chipset driver update. That disabled XMP in BIOS. Memory was set to 2666Mhz, with XMP enabled it runs at 3600. That seemed to have fixed it largely again. Don't know what it means, but it seemed worth noting

[ebolaconundrum]

OK I have yet to experience any crashes personally. But that seems a very credible cause of some crashes people are experiencing.

Bridging between the Gambryo engine and Unreal in the way they do has a lot of room for technical issues of that kind.