So no matter what I do, whenever I try to render my scene it gives me this error and crashes immediately after. Any help is appreciated.
Hello there @Realih!
That type of error is usually related to hardware conflicts, either due GPU overheating, or driver issues. Rendering with Lumen tends to take the video card to its limits. The viewport can handle it in real-time, but MRQ will push for higher quality.
In order to resolve this, the first step would be to refresh your drivers. Make a clean install, and pick the Developer drivers, as those are better suited for engine work.
Next, we can try to setup Lumen to hit less hard on your system. Using the following console commands for MRQ, you can lower its impact:
r.Lumen.Reflections.HardwareRayTracing 0
r.Lumen.Reflections.ScreenTraces 0
r.Lumen.TranslucencyReflections 0
Also, test switching between DX11 and DX12, and rendering without HRT, via going to Project Settings > Rendering > Lumen > disable Hardware Ray Tracing
As a last step, pick your choice of GPU monitoring tool (GPU-Z, Afterburner, etc), and look at your VRAM and temps during rendering. If any or both are hitting the red, then the video card might need a bit of maintenance. Hope this helps!
Happen to me too. It is really weird. Happen after upgrading to 5.6. There is no specific trigger that causes the crash. Just to select and play around with the level in editor. It might crashes randomly, but very often
We’re most likely experiencing the same issue.
In UE5.5.4, the packaged build worked perfectly fine, and as a released game, it has been running stably on the recommended hardware specs.
However, after upgrading to UE5.6.1 to support a new platform, this problem started to occur.
Of course, we’ve tried updating and downgrading the graphics drivers, but nothing has improved the situation.
The tricky part of this issue is that the crash timing is highly inconsistent.
In our environment, crashes occur most often during asynchronous level streaming.
They can also happen even when the loaded actors are not visible in the scene.
After checking the logs with -gpucrashdebugging and -d3ddebug, it seems almost certain that Lumen is the cause.
Currently, the only workaround is to disable Lumen,
but since the project uses both Lumen and Nanite, it needs to run on DX12.
So disabling Lumen or switching to DX11 isn’t really an option.
In our case, the crash never happens in the Editor — it only occurs in packaged builds.
Because the issue is difficult to reproduce consistently, it’s hard to file a solid bug report,
and at this point, debugging low-level rendering code seems to be the only thing left to try.
Hopefully someone from the RHI development team will notice this thread and take a look.
The related bug ticket was updated yesterday.
It appears that the crash I’m encountering is the same as the known issue listed here: