Unreal Engine is exiting due to D3D device being lost Unreal 4.27 and 5.1.1

[Roadified]

Hi,
no need to mention this error, but it is still here in Unreal 5.1.1
9999 people asked for the fix.

Unreal Engine is exiting due to D3D device being lost

It is marked as fixed in UE4, but it is not. I have this crash in 5.1.1 and 4.27.2 in two different PCs.

Did anyone ever found a fix?

I tried everything that is in Unreal forums and all relevant things that I found:

1 Disable battery boost in Nvidia - nope, I use stationary PCs
2 Added registry entries of tdrddidelay and tdrdelay
3 Update, reinstall, roll back Nvidia drivers
4 Studio vs game ready drivers
5 Disable raytracing
6 Running editor in “windowed” mode
7 Disabled antivirus
8 I have no integrated GPU, so disabling it is not an option
9 Running in DirectX 11 and 12
10 [FIXED] Fatal error: Unreal Engine is exiting due to D3D device being lost
11 Reinstalled to Windows 11 from 10 (clean install)
12 Changed GPU. Went from 3070ti to 3060
13 crashes in new project, new level and default-engine-assets
14 not related to single or multi screen setup
15 not overclocking of the hardware - everything is default

I experience this crash ~50 times a day, and it takes at least 1 hour of time, to recover from crash or reimport whatever I was trying to import. I do not need to do anything, and Unreal just crashes randomly, I can just look at the screen, without any computation in, or interaction and I know 100% that it will crash at some point.

System specs:
CPU - AMD Ryzen 9 3950X 16-Core Processor, 3500 Mhz, 16 Core(s), 32 Logical Processor(s)
GPU - Nvidia GeForce RTX 3070 Ti 8gb
Ram ~64gb

Edit: tried 9th option.
Edit: not related to DirectX, crashes on both 11 and 12.
Edit: tried 10th option, adding another registry key, still crashes
Edit: 11th step reinstalled to Windows 11
Edit: 12th step new GPU
Edit: 13th, not project related
Edit: wrote system specs
Edit: 14th option, original setup is 3 screens, tried with one, still crashes
Edit: 15th added picture

[ClockworkOcean]

What is your GPU?

[Roadified]

Nvidia’s 3070 TI 8gb on the first PC and 1070 6gb on another PC.

[ClockworkOcean]

One more thing. In the Nvidia control panel, 3D section, reset everything to defaults.

Apart from that I’d look at the level you’re loading.

If it’s just tinkering about with the first person example level, then, yeah, you’ve got a problem.

If it’s a massive landscape with grass all the way to the horizon, trees and stones everywhere, then I’d start to wonder if you’re just driving the system into the ground.

[Roadified]

I reinstalled, upgraded and downgraded drivers multiple times on both PCs.
It crashes in different projects, levels and computers, and as I mentioned in initial post, it crashes without interacting with PC, just when Unreal is open.

[ClockworkOcean]

Strange, yes…

Did you try the control panel fix?

[Roadified]

What is Control Panel fix?

[ClockworkOcean]

[Roadified]

Yes of course. They also get reset with a clean install, and maybe the default install too.

[Roadified]

Solved!!!

It took close to half a year to find a solution. Constant crashes and lost work, so much time wasted…

I changed the processor and motherboard. The old, which I am sure was the problem for Unreal, was AMD Ryzen 9 3950X 16-Core.
I am assuming it was the processor, as I found some people on the internet also having problems with Unreal, while using this processor. It was very misleading as it is GPU crash, and it does not have internal GPU, so it is not related to switching to internal.

Maybe someone in the field can explain why this could be the cause?

Changed to 12th Intel i7-12700F. No crashes in ~4 days.

[guillemsrr (Guillem Serra)]

No way… I have an AMD Ryzen 9 5950X… Are you telling me I need to buy another Intel CPU? There has to be another solution!

[Roadified]

I have no idea how it is for you, do you also experience GPU crashes? Some people report, that doing some of the steps I did - solve their problem, but non worked for me.

Changing to Intel, was only solution that worked for me, and I tried everything else as you see in the original post. There is a small chance that it was the motherboard, but I doubt it as some users also had crashes with this CPU.