UE5 crashes on launch every time such as games that are built on UE5 like the Finals, Fortnite, Marvel Rivals, etc. It has been extremely frustrating so I’m hoping you guys can help me fix it once and for all because I felt like I’ve done everything I can. This has been happening for over a year, ever since I played a game that uses UE5.
Troubleshooting steps I took so far:
I felt like I tried everything…
-reinstalling
-steam launch like -d3d11 (worked on the Finals before but now doesn’t)
-updating graphic drivers
-using DDU to do a clean driver installation
-undervolted cpu
-disabled xmp (unsure if I did that since its very different on a laptop)
-verified game files
-turned on core isolation
-removing msi afterburner/rivatuner
-checked for dirextx drivers
-updated bios
Hey there @ChuckleGamer! I’m certain you’d already checked my previous post on a slightly different Nvidia dll issue since your original post layout almost matches. Your issue is a bit different in that it’s an error based on Nvidia’s CUDA functionality. So my first question is if your CUDA version is reflecting correctly. Open a command prompt and enter: nvidia-smi
Interesting. Could you open the Nvidia control panel, and restore the defaults? If that doesn’t work I’d adjust the CUDA Sysmem fallback policy and see if either works and verify the CUDA - GPUs setting recognizes your GPU:
Sadly didn’t work @SupportiveEntity , checked the CUDA - GPUs if it recognized my GPU and messed around with the CUDA sysmem fallback by checking if the other two options worked. Also restored to default like said. No luck
Also @SupportiveEntity do you know what the other parts of the errors are?
nvdxgdmal64 and nvwgf2umx. I find it odd that its repeated. Man I really want to fix this but this crash looks very complex. I just want to play UE5 games…
Oh that complicates things. I was expecting to find a hint with the firmware or hardware possibly being the issue, but since the benchmarks are great, it points to a specific interaction with Unreal itself.
This portion is reaching, but do you have windows “Game Mode” on? How about local Hardware Acceleration?
Yeah, man I’m not sure what else to do besides maybe rolling back the drivers and see which ones work. I want to fix this issue badly but its looking grim. I do have windows Game Mode on. I think local hardware acceleration is on. Is called the hardware accelerated GPU scheduling?
I usually recommend (on laptops) to disable Game Mode as it has caused similar issues in the past, but I had believed that bug had been fixed so this was unlikely related. Yes local hardware acceleration is called GPU scheduling in Win10/11, and it is hit or miss in some instances.
Just to rule out DirectX core altogether, can you swap out the RHI to Vulcan and see if the engine runs? This would only be a workaround but might give more information.