Posting what seemingly stopped my game ue5 crashing all the time after hours of failed potential fixes, hope it helps you!

[bluewaffles4ever]

So, I'll start with my specs as this is pretty imperative to this fix working for you since everybody has different builds and different fixes will or won't work based on that. But from what I gathered this is more common on high end systems, which I can personally verify since my friend who has my 8 year old GTX 1080, has only crashed TWICE in his 30 hour play through thus far, despite him running well below recommended specs. My ue5 crashes were usually runtime\rendercore\private\shadercodearchive or rarely exception access violation causing crashes every 10-30 min, or sometimes upon main menu screen or loading a save (these 2 instances were most frequent)

-i9 149000kf
-GeForce RTX 4090 24gb vram dx12
-MSI MPG Z790 Carbon Wifi DDR5 Motherboard
-2x RAM sticks G.SKILL Trident Z5 DDR5 32gb (64gb total)
-C1500 Platinum ATX 3.1 power supply
-Windows 11

In terms of actual game play performance, runs mostly great for me which I know is not the case for many so I haven't tried to majorly adjust anything as I'm satisfied in that area. 4k ~120 fps on medium to ultra settings with dlss on quality. No dlss and I can still pull ~60 fps in cities and interiors, ~50fps in open world traversing. CPU usage 20%-40%, gpu useage 50%-90% both based on area and what I'm doing

Now I'll show what fixes I tried that didn't work for me and other poor souls, but may work for you. I'll then show what may have finally fixed it for me, at least so far. Played about 2.5 hours with no crashing after many combat encounters, loading screens, fast travel, open world traversing, inventory management and a few quests along with now 13 minor mods. I will update as I play more to confirm stability

-Failed fixes (for me)
Turning off/on v sync, g sync, reflex, turning off ray tracing and lumen, switching from borderless windowed to full screen and vice versa, lowering graphical settings, turning off low latency, capping fps to 60, disable full screen optimizations, running as admin, running in compatibility mode, allowing through firewall, changing power mode to low or high, full delete and clean install of game, various nexus performance mods, no dlss, using fsr, using xxess, updating dlss using dlss updater, most recent windows and graphic driver updates, fresh install of graphics driver, deleting shader caches, deleting sl.pcl.dll file and related sl files and nvngx_dlss.dll, checking that plugins.tx is in correct order (I manually installed mods so vortex/nexus didn't screw up plugin orders for me, experienced crashes before and after mods until now)

Those are all the fixes I can remember trying, but I definitely forgot a few but on to what seemingly actually worked

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

From what I gathered, ue5 can crash on alot of modern games with modern hardware, specifically this site states

i7-13700K, i7-13700KF
i9-13900K, i9-13900KS, i9-13900KF
i7-14700K, i7-14700KF
i9-14900K, i9-14900KF

You can check the site and follow the instructions there, but basically

Use extreme tuning utility (xtu)
-Download and install version 7.14.2.14
- Run it and reduce "Performance Core Ratio" to 52x and click apply (mine was originally at 56x)
- click "Advanced View" on bottom left
- check in "Performance Active-core Tuning" and make sure all cores are at 52x, for me 1 and 2 were still at 56x, so I changed them to 52x, click apply below
- the site mentions that if this still doesn't work, try 51x, and further if that doesn't work, to "further tweak your settings or voltage settings, or your BIOS may be overriding your config", in this case there is another link on the site that may help you or not, for me 52x on all cores has worked thus far
- I'm no pc savant so I'm not sure how this may affect other games performance, but if so you may need to change it back in those cases

And that's that! I really hope it lasts for me lol I'll be testing more as the days roll by. At this point, I'd accept the occasional crash every couple hours or so, I've modded games a bunch over the years so my patience is practiced but ideally this fixes it for several hours on end. After all, it's still Oblivion so you never know. Hopefully one or many of the fixes I listed worked for you, and maybe xtu was your savior like it was for me!

After another 9 hours, I have only crashed once when creating potions in the alchemy menu since this fix. I have been doing alchemy frequently during this play through so it seems to be a rare occurrence for me as it only crashed twice in 30 hours when doing alchemy

[môrgondír]

Thank you for sharing this - I look forward to giving it a go and experiencing fewer crashes.

[bluewaffles4ever]

Originally posted by môrgondír:

Thank you for sharing this - I look forward to giving it a go and experiencing fewer crashes.

I really hope it helps, too many of us banging our head against the wall trying to find fixes. Good luck!

[Doomvora]

As you've already figured out, UE5 is really temperamental on 13th and 14th gen intel systems. XTU (intel extreme tuning) can alleviate this by ramping the performance cores to x53 or lower. It's likely due to the aggressive overclocking 13th and 14th gen intel chips do.

Games like Marvel Rivals also have this issue, it's a well known UE5 issue with these chips.

[catch22atplay]

That's a fairly old way of doing it. And it still may be needed for some. The 0x12B cpu microcode should be a part of your latest bios. So update the bios. Then select Load Intel defaults. Although you actually need to select performance mode for your cpu according to Intel. Double check PL1 and PL2 and unlimited amps bit is off and that amps aren't set to some crazy number. My watts were set to 4,095 instead of 253 or whatever it's supposed to be for my 13600kf. Look up the correct numbers. Now if that fails then downclock as needed or get better cooling. And yes even water cooling didn't help many.

Due note also the nvidia driver 576.02 puts cpu usage at 100% and will cause these insane issues. Downgrading it to 572.83 and cpu behavior is normal ie never hits 100%. cpu temps should drop 20c or so.

[bluewaffles4ever]

Originally posted by Doomvora:

As you've already figured out, UE5 is really temperamental on 13th and 14th gen intel systems. XTU (intel extreme tuning) can alleviate this by ramping the performance cores to x53 or lower. It's likely due to the aggressive overclocking 13th and 14th gen intel chips do.

Games like Marvel Rivals also have this issue, it's a well known UE5 issue with these chips.

Yeah, searching for fixes finally led me to discovering this kind of issue, which I have never experienced before. Up until now, no other modern games have had issues like this for me, but something new to learn about I suppose

[bluewaffles4ever]

Originally posted by catch22atplay:

That's a fairly old way of doing it. And it still may be needed for some. The 0x12B cpu microcode should be a part of your latest bios. So update the bios. Then select Load Intel defaults. Although you actually need to select performance mode for your cpu according to Intel. Double check PL1 and PL2 and unlimited amps bit is off and that amps aren't set to some crazy number. My watts were set to 4,095 instead of 253 or whatever it's supposed to be for my 13600kf. Look up the correct numbers. Now if that fails then downclock as needed or get better cooling. And yes even water cooling didn't help many.

Due note also the nvidia driver 576.02 puts cpu usage at 100% and will cause these insane issues. Downgrading it to 572.83 and cpu behavior is normal ie never hits 100%. cpu temps should drop 20c or so.

Lol like I said I'm not super experienced in pc tech stuff, this sounds like a bunch of BIOS stuff I need to figure out and adjust, correct? I did try to downgrade my gpu drivers a couple times as some fixes said, but it wouldn't let me for some reason. Not like I was trying that hard to I was just racing from fix to fix seeing what might work. Something else I need to learn about I guess. As far as my cpu, it never spike past 60% usage besides shader compiling, unless it hit 100% and crashed when I wasn't monitoring it at that moment, suppose I would have to check the graph in task manager to confirm that. My cooler is a Kraken Elite 280 if that has any bearing

[môrgondír]

I just finished about a five-hour session without a single crash.

Per the suggestion, I used XTU to set all active cores to identical ratio values (they were previously dynamically determined) - in my case, on an i7-8700, I set the ratio for each active core to 44x (the original dynamic settings had a mean value of 44.83 [HVal: 47, LVal: 43]) - I closed XTU, fired up the game, and subsequently lost all track of time.

Thank you again for your suggestion, bluewaffles!

[Arc]

Originally posted by bluewaffles4ever:

...
-i9 149000kf
-GeForce RTX 4090 24gb vram dx12
...

That's like the worst possible config to have these days in terms of amount of issues it brings to the table.

First the Intel CPU instability debacle and then Nvidia Blackwell (RTX5000) brought in buggy drivers that Nvidia had to fix with numerous hotfix drivers, and with them also made RTX4000 unstable. There's literally a hotfix for a hotfix now (576.26).


Glad you got your issue resolved !

Originally posted by Doomvora:

...UE5...

It is not and never was a "UE5" thing (at all, ever), i really wish people would stop making any sort of blame-shifting attempts when in reality it's a massive screwup from Intel.

For one you had out of the box unsafe overclock on some motherboards (not to be blamed on AIB's, since the spec given to them by Intel wasn't really rulling that out), then a manufacturing defect of early units and finally a hardware/microcode bug with voltage controller.


The only part UE5 brings in terms of people's PC crashing, is that it uses modern heavily multi-threaded tech that will reveal pre-existing instabilities of the PC configs, but this goes beyond Raptor Lake.

[Yourname942]

Do I need to use that if I have an Intel i9-9900k CPU?

[bluewaffles4ever]

Originally posted by Arc:

Originally posted by bluewaffles4ever:

...
-i9 149000kf
-GeForce RTX 4090 24gb vram dx12
...

That's like the worst possible config to have these days in terms of amount of issues it brings to the table.

First the Intel CPU instability debacle and then Nvidia Blackwell (RTX5000) brought in buggy drivers that Nvidia had to fix with numerous hotfix drivers, and with them also made RTX4000 unstable. There's literally a hotfix for a hotfix now (576.26).


Glad you got your issue resolved !

Originally posted by Doomvora:

...UE5...

It is not and never was a "UE5" thing (at all, ever), i really wish people would stop making any sort of blame-shifting attempts when in reality it's a massive screwup from Intel.

For one you had out of the box unsafe overclock on some motherboards (not to be blamed on AIB's, since the spec given to them by Intel wasn't really rulling that out), then a manufacturing defect of early units and finally a hardware/microcode bug with voltage controller.


The only part UE5 brings in terms of people's PC crashing, is that it uses modern heavily multi-threaded tech that will reveal pre-existing instabilities of the PC configs, but this goes beyond Raptor Lake.

Man I had no idea I was setup for such issues lol, thankfully I've only had problems like this with Oblvion Remastered thus far. I've had this pc for about 7 months and it has ran everything else great

[bluewaffles4ever]

Originally posted by Yourname942:

Do I need to use that if I have an Intel i9-9900k CPU?

It's worth a try I think. As Morgondir posted earlier, he set his to 44 to match his original dynamic setting mean of 44.83 despite having a i7-8700 and it seemed to have fixed his issues as well. Not sure if this applies to you in the same way but worth poking around if all these other fixes haven't worked for you. Best of luck!

[Doomvora]

Originally posted by Arc:

It is not and never was a "UE5" thing (at all, ever), i really wish people would stop making any sort of blame-shifting attempts when in reality it's a massive screwup from Intel.

Ironic

[bluewaffles4ever]

Update: As of 4/29, I have logged another 9 hours with only 1 crash after this fix