Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0020 - 'INTERNAL_ERROR')

Development Platform & Builds
, ,
1

I’m not sure if this is the right place to post this, so I apologize if it isn’t.

I’ve recently come across this bug while trying to play Sea of Thieves. I had a different crash message, but when I tried to launch another UE4 game (PUBG in this case), I had a crash like this. This error message is from Dead by Daylight, of course, but it hasn’t worked in Deep Rock Galactic or Insurgency: Sandstorm either. What really perplexes me is the fact that Tower Unite works, despite the game being on UE4.

I am running an underclocked (for the sake of trying to fix this) EVGA GTX 1080ti and an i7 8700k (OC to 4.7GHz)

I’ve tried uninstalling and reinstalling my graphics drivers (both manually and through GeForce Experience), uninstalling each game in question, doing registry edits (TdlDelay to 10), and virtually every solution I’ve found on the internet.

Any assistance would be appreciated. I am really going insane trying to find a solution.

Assertion failed: [File:Unknown] [Line: 198] Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0020 - 'INTERNAL_ERROR')

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 25327097 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 25073690 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 24830071 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 24829816 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 29637364 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 29642646 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 29643743 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 29600907 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 35190731 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 35181399 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 40378236 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 40386633 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 24136899 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 35475826 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 35478984 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 25361339 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 25350204 bytes
kernel32 {0x0000000000000000} + 97236 bytes
ntdll {0x0000000000000000} + 446161 bytes
2

Contact game developer, it’s there responsibility to give you support of published game. D3D Internal Error suggest there something with either DirectX or Driver, that all that can be deduced from this. D3D simply tells UE4 that internal error happened and UE4 just say “ok bye bye” and simply aborts. Call stack you posted is useless without debug symbols which game developer has.

You may try to download Ue4 editor with debug symbols (it’s in installation options) run some demos and see if crashes too, it will give more readable call stack and we may able to deduce something more out of it.

If you run on laptop common D3D crash cause with UE4 is automatic GPU switching between CPU-integrated GPU and seperate GPU.

If you OC CPU you may want to try to run it in normal stack clock and see what happens.

3

Hey friend. I appreciate the comment. I think this error is more sided towards DirectX, since Tower Unite runs on DX11 and not 12. I just don’t know where to go from here, since it seems like I’ve kinda narrowed down the culprit.

As of what you said about running UE4 Editor, I tried to yesterday and UE4 just crashed on startup too.

Not on a laptop, but I might try the CPU standard clock if I continue to have problems.

Again, thank you so much for a lengthy response. It really means a lot, since I don’t really know much about UE4 and error codes.

4

It’s possible that your CPU is running DirectX 12. It is possible to have directx 11 and 12 on your CPU. I was running into this error and downloaded DirectX 11 and have not had the error since. I also did a clean driver install before downloading DirectX 11 so it’s possible that’s what fixed it but since my error was directly related to DirectX 11 I do not think that is the case. Hopefully this helps anyway, should be moot soon as I’m sure UE5 will be running on DX12.