Unreal Engine is exiting due to D3D device being lost for no real reason

Game mode: Single-player
Type of issue: Crash
Server type: PvP


Fatal error: [File:C:\REPO\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp] [Line: 805]
Rendering thread exception:
Fatal error: [File:C:\REPO\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 181]
Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - ‘HUNG’)

!0x0000000000000000

I have done everything in my power from changing settings all the way up to reinstalling windows and nothing has fixed this error. can anyone please help! Everything is up to date and there is no reason that I can find that causes this issue.


Please provide a step-by-step process of how the bug can be reproduced. The more details you provide us with the easier it will be for us to find and fix the bug:

  1. Launch game
  2. Enter saved game
  3. Wait for about ten seconds
  4. Game crash with text box pop up

My Specs:
Windows 10 Home 64-bit
AMD Ryzen 5 3600
MSI A320M GAMING PRO (MS-7A39) (AM4)
XFX Radeon RX 5500 XT
Samsung SSD 860 EVO 500GB
931GB Western Digital

Two suggestions for you that often resolve crashes on start-up:

  1. If you have an integrated video card other than the main one you are using, try disabling it.
  2. Install or re-install Microsoft Visual C++ 2015 Redistributable

Thank you for the help but I installed C++ Redistributable 2015 and I am still getting the same error. For the integrated graphics I have had that disabled before I had Conan.

Ok, a few more things to try in order to narrow down the issue:

  1. Launch the game without BattleEye.
  2. Launch the game with the Anti-Virus Software disabled/turned off.

Since you are also an AMD user, you may want to check this thread as well:

Are you running dual monitors?

I had a similar issue, I tried everything I could think of just as you did.

The only thing I found that seemed to reduce frequency of occurrence was to physically disconnect one of my monitors.

That’s odd, granted I am using different hardware but I have been using dual monitors for years with this game and haven’t had any issues. Thanks for sharing though. I wouldn’t have thought that it might be related to the use of a second monitor.

Hey I tried everything in the thread you recommended and disabled windows defender but I still get the same error.

I have unplugged one of my monitors but the issue still remains thank you though.

Do you have access to the settings? Try capping your FPS to 60 and use Fullscreen Windowed instead of Fullscreen.

In addition, start the game on low settings.

To me it seems it does not matter what settings I use. This error will happen no matter what because when this first started I ran the game on low end laptop mode and that worked for about an hour then the error came back.

I assume you’ve gone through the “dumb steps” already:

Updated Windows fully via Windows Update, rebooting as necessary
Updated video drivers to latest
Updated Directx (Win10 incorporates these automatically and updates via Windows Update)
Verify files for Conan through Steam

In addition, you may want to:
Run Disk Cleanup or CCleaner to clean up registry entries and unused files
Run Defragmenter or Defraggler to Optimize SSD drives and Defragment non-SSD drives

See [1] to see if there is any further advice that may be helpful - although it looks like most of the points have already been touched on by previous posters.

Speaking personally, when I get a UE4 D3D error similar to the one you mentioned, it’s after an extended gaming session where the game client has been open for hours and a memory leak has finally taken its toll.

[1] https://appuals.com/how-to-fix-the-error-unreal-engine-is-exiting-due-to-d3d-device-being-lost/#:~:text=How%20To's%2FGames-,How%20to%20Fix%20the%20Error%20'Unreal%20Engine%20is%20exiting,to%20D3D%20device%20being%20lost'&text=According%20to%20Unreal%20Engine%20developers,work%20properly%20with%20D3D%20device.

@ZaDuuu
I run a home made system with a liquid cooled AMD 9590 CPU and the same dedicated graphics card as yours. (Radeon RX 5500/8GB).
Prior to purchasing the newer graphics card, I was using an RX 580 and was occasionally getting a near identical error, but for the life of me never could quite pinpoint what caused the error.
Here’s the catch, I was getting that same error on other apps.
But, here’s a side note that may or may not be relevant to what you’re experiencing.
At the time, I was running an OEM version of Windows 10 Pro (because I built this system myself and bought/installed the OEM W10 pro version to save a few bucks).
Get this: Updates were consistently failing no matter what I tried, until I got a pretty clear indication of the nature of the Windows 10 updates by stumbling upon some notes about it. I found out that windows updates only work on the full retail version of Windows 10 (this is no joke).
Once I purchased and installed the full retail version, the Windows updates installed flawlessly.
Since the install of the full retail version of W10 (pro), I’ve not had any more of the “D3D device being lost” issues which I partly attributed to installing the new dedicated card. I realize in hind sight that I might not have needed to get a newer card.

Maybe this is just coincidence, but check your version of Windows 10. Especially if it was a manufactured PC with Windows 10 already installed.
I highly suspect the issue is associated with Windows 10.

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.