Unreal Engine 5.5 GPU Crash (GPU Crashed or D3D device removed.)

Hi! I installed 5.5 preview and tried to open my project in it. When rendering with any settings and even in an empty scene it throws out of the program with an error. I tried pausing in regedit according to the recommendations and updated the card drivers, but nothing helps. The scene is not heavy. The error appeared also when working in editor.
Error ONLY when DirectX 12 is enabled. If I switch to 11 version, the scene works quickly and without errors.

Video card 4090, 196GB RAM, Ryzen 9 7950X


same here.unable to open unreal engine

1 Like

UPDATE:
I still canā€™t figure out whatā€™s wrong. Tried different video card drivers and resetting the bios. Now switching to SM5 has helped. The renderer started, but as soon as I switched back to SM6 it crashes again at render startup.

Greetings @ytka88ua

Thanks for the information! Are you having this issue with any other UE version or only with 5.5?

(post deleted by author)

Hi! No, Iā€™ve never had this problem. Sometimes I would make a super heavy scene on purpose to see what the program and the comp could do and the maximum I could do was a long render. And this is a simple scene. It crashes even if there are no render settings at all. Just the default. Tried local and direct renderer. Everywhere fails. Yesterday I tried deleting the config folder completely and the renderer seems to start, but only I set the basic settings and direct 12 immediately shuts down. I am willing to give Any Desk access or a scene to investigate the error. I really want to render my scene, but I canā€™t for over a week now.

Iā€™ve saw this type of issue before with DX12 and it did not happen with 11. Sometimes thatā€™s due to the projects having so much content that it overloads the system. But, the GPU crashed/device removed Iā€™ve saw happen from a LOT of variables. Weā€™ll have to play process of elimination to try to figure out the area. Have you tried going into NVidia control panel and resetting everything to global default and testing? (Also when removing config folder remove any other folder there other than ā€˜Contentā€™ for testing) Have you installed any new components? (Specifically new RAM, Motherboard, or CPU as hardware compatibility is common culprit too)

The update for UE and for 4090 came out today. I updated both at once and launched the scene. I noticed immediately how much faster everything started working. Thatā€™s nice. On the downside, the scene still crashes, but now ONLY when Ultra Dynamic Weather is added. As soon as they release an update to 5.5 I will test again. No good news so far.

UPD:
By trial and error I came to the conclusion that the scene crashes at any settings if the ā€œstormā€ preset in UDW is set. If you change it to any other setting, everything is fine. I think it has to do with some particles or something, but itā€™s not my problem.

I found the bug and Iā€™m waiting for my Unreal Engine fun t-shirt!

1 Like

Same issue here, different (yet to be discovered) cause/trigger. Crashes quite frequently. Updated to 5.5 and v566.14 nvidia drivers (also have a 4090) and only thereafter experienced this issue. For me, simply opening a widget blueprint and leaving the event graph open for a time (several minutes) causes it. Switched back to 5.4 and thus far no issuesā€¦

UPDATE: after posting that I remembered I installed the Studio Driver and not the Game Ready Driver, so I did a clean install of that driver and have used 5.5 without issue for several hours since!

Iā€™ve also installed UE 5.5 and, guess what, been affected by a GPU crash (D3D device removed)ā€¦ Something that had never happened in previous UE versions since the 4.27.
Hereā€™s a screenshotā€¦

Tried already lots of tweaks, disabling hardware ray tracing, disabling G-Sync on nVidia settings and remove all windows 11 visual effects in performance options.
The crash occurs almost in every session of UE 5.5 in the editor and PIE :frowning:

UPDATE - SOLVED: I believe that was some nodes of a plugin that was not yet updated (or checked as active) which was on some blueprints - On my case the screen capture plugin.
Guess that is the major issue which seems solvedā€¦ Should I get the T-Shirt ? he he he

just had the same GPU Crash issue, on a project I was working on UE 5.4 and then UE5.5 Early, both without any issues. Running a 3900x and a 2080ti, and changed 2 days ago to a 3090ti.
Now on UE5.5 official release, it crashed when opening a map in Lit mode. I could open the same map in Unlit mode and it ran fine.
So I tried to change Nvidia Studio driver to Game Ready, nothing changed. Then set the TdrDelay value to 60, it stop crashing the project but i occured multiples freezes each time I would move the camera around the level.
I finally fixed it by enabling Raytraced shadows in the project settings.

I have no idea what was going on here. I didnā€™t tested it on my previous GPU but I felt like I didnā€™t had this issue on it. Driver problem? Hope this can save somebody a hour or two of fixing

Hi there @kelit! Welcome back to the forum! That is indeed an interesting find. Some of the posts above talking about earlier UE versions not having the crashes there may have been from running DX11. DX12 Iā€™ve noticed is prone to the crashing on newer UE versions much more often. Youā€™re not the first one Iā€™ve saw mentioned the ray tracing fixed their issue either. Iā€™m going to look further into that. Thank you for the information!

I think Iā€™ve found what was causing the issue, I suspect it to be linked to Nanite displacement being allowed in one of my material settings. When trying to optimize my scene, which is very low poly, I noticed in the Nanite triangle view mode that some of my meshes were insanely detailed, while the displacement strength was set to 0. The lags occurred only when I was close to theses areas. I forgot to disable the feature after trying EasyMapper displacement, thinking i would use it for the project. So maybe the hardware raytracing is handling more efficiently these high density nanite triangles and the software version is struggling?
Iā€™m glad if this can help!

Oh wow! Thank you! Iā€™m positive this will be helpful for people in the community who run into this issue and search it. We appreciate your response!

1 Like