#Constant Crashing on AMD GPU

1 messages · Page 1 of 1 (latest)

quartz fulcrum
#

Greetings! I'm having an issue where my game keeps crashing. Usually every 5 minutes after entering the world, everything, including my dekstop, simply freezes and the crash occurs. AMD Drivers seem to completely crash along with it and I get a UE5 fatal error. Sometimes if I play around with the settings it can last up to 30 minutes, but after that, it crashes and the situation begins anew. I've tried DDU, I've tried changing voltage and power levels on the GPU, minimal graphics, turned all AMD related settings off (FSR, Anti Lag etc.) but it still keeps crashing. Any known fixes?
If any other infos are needed let me know. Not quite sure where to find the exact error logs.

Specs:
Ryzen 7 5800x
Nitro+ Sapphire 9070 XT
32GB 3600Mhz RAM

velvet briar
#

Hello!

AMD Radeon RX 9070 XT is currently known to have issues with the newest AMD Adrenaline Driver (26.3.1) and its creating much UE5 Crashes with reason:

EXCEPTION_ACCESS_VIOLATION
Crashes inside amdxc64.dll
Crashes inside D3D12Core.dll
UE5 closing before the project even loads
Shader compilation freezes
Random GPU hangs during Nanite or Lumen initialization
These issues are caused by:
Broken DX12 pipeline state handling
Faulty shader compiler behavior on RDNA4
Invalid descriptor heap access
Aggressive shader caching that corrupts UE5’s PSO cache

In short:
UE5 + AMD 26.3.1 = unstable on RDNA4 GPUs.

Some players reported that previous Stable Version does much better:
AMD Adrenalin 26.1.1 WHQL

quartz fulcrum
quartz fulcrum
#

@velvet briar Nope. Just tried it with 26.1.1 is installed and it's still doing the same. Took around 10 minutes this time but game still ran into fatal crash :(. Is there a place where I can check the logs to see exactly what comes up?

#

I'll try and roll back even further, 25.8, and see if that works better

quartz fulcrum
#

Ok well, to anyone that may come across this: After (a lot) of digging, the issue was the RAM. It was running at 3600MHz, which the CPU is more than capable of handling. The issue was, the RAM was not correctly set in dual channel mode. So either decrease RAM clocks, or check if dual channel mode is correctly set up on the motherboard.

tall summit
#

Could you play other games, though?

mild sleet
quartz fulcrum
ocean escarp
#

I wonder what i'm doing differently that i'm not getting crashes
i'm on epic quality, i've got fsr on balanced, frame gen on, HAGS on, 26.3.1 driver

velvet briar
#

hardware magic I suppose 🙁

ocean escarp
#

could try shader cache setting in registry. although mine's at the default "31" when you edit the binary value, so that's probably not it but 31 is "amd optimised", 32 would be "always on". could try that along with clearing shader cache in adrenalin

#

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\ then you ctrl f to search "ShaderCache"

velvet briar
#

this is beyond my understanding I'm sorry 🙂

but perhaps @random forum could hind a minute to review thi 🙂

ocean escarp
#

oh he's solved it by fixing an unstable ram overclock, I didn't notice that, that explains why i'm not crashing

worldly reef
#

just posting this if it means anything, you can see where i crashed

image.png
velvet briar
#

AMD Radeon cards are currently known to have issues with the newest AMD Adrenaline Driver (26.3.1) and its creating much UE5 Crashes. Some players reported that previous Stable Version does much better:AMD Adrenalin 26.1.1 WHQL. We are also investigating if there is something we can do to run better on AMD cards.

quartz fulcrum