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

General Feedback & Requests
, ,
1

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

Screenshot 2024-11-07 145958
Screenshot 2024-11-07 1459581920Ɨ1013 110 KB

Screenshot 2024-11-07 150011
Screenshot 2024-11-07 1500111115Ɨ885 118 KB

2

same here.unable to open unreal engine

1 Like
3

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.

4

Greetings @ytka88ua

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

6

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.

7

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)

8

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
9

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!

10

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ā€¦

Screenshot UE55 error
Screenshot UE55 error1920Ɨ1080 405 KB

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

11

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

12

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!

13

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!

1 Like
14

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
15

Unreal engine 5.5 closes after enabling mega light and it is not possible to open it again.
LoginId:9a6bbc12425d311aaffc8190d4d9bf76
EpicAccountId:2b3f513183a14cff82d9d68cd6941c47

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000008

UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_Renderer
UnrealEditor_RenderCore
UnrealEditor_RenderCore
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_Core
UnrealEditor_RenderCore
UnrealEditor_RenderCore
UnrealEditor_Core
UnrealEditor_Core
kernel32
ntdll

Final log:
[2024.11.26-16.23.50:654][358]LogWindows: Error: === Critical error: ===
[2024.11.26-16.23.50:654][358]LogWindows: Error:
[2024.11.26-16.23.50:654][358]LogWindows: Error: Fatal error!
[2024.11.26-16.23.50:654][358]LogWindows: Error:
[2024.11.26-16.23.50:654][358]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000008
[2024.11.26-16.23.50:654][358]LogWindows: Error:
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffc16538080 UnrealEditor-Renderer.dll!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffc1682ad77 UnrealEditor-Renderer.dll!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffc1616ccb9 UnrealEditor-Renderer.dll!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffc16f44b26 UnrealEditor-Renderer.dll!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffc16efbb8a UnrealEditor-Renderer.dll!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffc7fb7b7c5 UnrealEditor-RenderCore.dll!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffc7fba94cf UnrealEditor-RenderCore.dll!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffc6b912722 UnrealEditor-Core.dll!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffc6b907d4a UnrealEditor-Core.dll!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffc6b9081ee UnrealEditor-Core.dll!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffc7fbd7e1c UnrealEditor-RenderCore.dll!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffc7fbdceb4 UnrealEditor-RenderCore.dll!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffc6bf3c0ad UnrealEditor-Core.dll!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffc6bf335cf UnrealEditor-Core.dll!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error: [Callstack] 0x00007ffcc108e8d7 KERNEL32.DLL!UnknownFunction
[2024.11.26-16.23.50:654][358]LogWindows: Error:

16

I find GPU Crashed when enable Ray Traced Shadows.

1 Like
17

My outages are still continuing. For myself, I found a problem with rain in UDS. If the rain value is greater than 6, the scene crashes.

18

never had a gpu related crash with 5.4 but 5.5 crashes , mostly when iā€™ve been afk for a few minutes , 5.5 got some unresolved issues

19

5.5 megalights crashing like crazy. Guess its really is experemental, should be only used inside some small test levels

20

I tested by creating a new, completely empty project. As I suspected that Unrealā€™s own water bodies system could be causing the crash, I set up a new project with the following steps:

1 - I created a project with the GAMES" > ā€œBlankā€ template.

2 - I created a level empty.

3 - I enabled the plugins: Water, Chaos Vahicles and Day Sequence.

4 - I added to the empty level: the lendscape (default size), the ocean water body and the Day sequence.

5 - I enabled Mega Lights and Shadows Ray Tracing.

6 - I placed only one point light in the scene.

7 - I started play, and at the same time the crash occurred:

LoginId:9a6bbc12425d311aaffc8190d4d9bf76.

EpicAccountId:2b3f513183a14cff82d9d68cd6941c47

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000008

UnrealEditor_Renderer

UnrealEditor_Renderer

UnrealEditor_Renderer

UnrealEditor_Renderer

UnrealEditor_Renderer

UnrealEditor_RenderCore

UnrealEditor_RenderCore

UnrealEditor_Core

UnrealEditor_Core

UnrealEditor_Core

UnrealEditor_RenderCore

UnrealEditor_RenderCore

UnrealEditor_Core

UnrealEditor_Core

kernel32

ntdll

I repeated this entire procedure using bodies of water from rivers and lakes, and the same crash also occurred with just one point light in the scene.

So, I believe that the body of water ocean, rivers and lakes could be responsible for this crash, because without a body of water the MegaLight works perfectly.

I would like the Unreal community to redo these tests and confirm the suspicion that the water bodies system is causing these crashes, reporting this problem to Unreal Engine. My intention is to contribute to the growth and improvement of the Unreal graphics engine, which is incredible.

1 Like
21

I migrated a level over from a 5.4 project and was getting this crash instantly after loading the level, I deleted the particle effects from the project folder and reloaded, no crashes so far