The Infamous D3D Device Lost Crash

General Feedback & Requests
, ,
1

Hi Epic,

Since today I am getting D3D device lost crashes on any of my 4.15.1 projects.
Both the engine compiled from source as well as new projects through launcher.

Both log attached are from two new test projects.
thirdperson, add a landscape.
To put some pressure on the GPU I added the LAM from marketplace to it.
Up till here both projects start up fine.

when enabling depth fields under lighting section in project settings and restarting the editor, it crashes and will continue to crash any time I try to open the project.
Our code version also has depth fields activated due to dynamic lighting and also crashes on startup of the editor.

Is there a way to disable the depth fields so I can test if they are the cause at this time?

Log files project 1

Log files project 2

2

I made an mistake on what I think causes it. It’s mesh distance fields, not depth fields…

sorry bout that.

3

I found the entries within both engine.ini files and desabled mesh distance fields there. Editor loads normally again. re-enabling them crashes the engine again. So the issue for us seems to be triggered when enabling the mesh distance field in project settings. This behavior happens on both projects build from the code version of 4.15.1 as well as empty BP projects created through the Epic launcher.

4

Still receiving it while doing other actions in the editor as well. simply placing an object or opening a blueprint can crash it.

Since 4.13 has issues under the new windows 10 release with dropdown menu’s not working normally and 4.14 and 4.15 constantly give d3d device errors we have no working engine version at this time.

5

Hey ,

We have several cases causing the D3D Device being lost. We plan to incorporate Nvidia Aftermath in an upcoming patch that will assist us with gathering information.

What I may ask of you is to get the latest drivers and test this once again after we release another patch.

!

Ed

6

Hi Ed,

for the reply. I just upgraded to the newest drivers released by nvidia following the windows upgrade. Problem remains the same.

I’ll keep looking foor things which may help. .

7

Ah, sorry if I wasn’t clear. What I mean is once we release our patch and are ready to test for the d3d issue that is when we may start asking users to get the latest drivers and try to reproduce the crash in that engine version.

8

Whenever I attempt to play ‘Dead by Daylight’ I receive this crash report.
I haven’t found anyway to fix it on my end.

Fatal error: [File:D:\Jenkins\workspace\DBD_L_ND\UnrealEngine\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 176]
Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - ‘HUNG’)

KERNELBASE {0x0000000000000000} + 212056 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 7641053 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 7373802 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 7290584 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 10495121 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 10498668 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 10461038 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 11292252 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 23100711 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 11376720 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 11365521 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 6680410 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 6680653 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 11379142 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 11379288 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 7637735 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 7596428 bytes
kernel32 {0x0000000000000000} + 33636 bytes
ntdll {0x0000000000000000} + 422097 bytes

9

Hey Darkwolf2017,

This forum is for issues discovered while working in the Unreal Engine. For issues with games made using Unreal Engine 4, you’ll need to visit the developer’s forums and report the issue there.

For your convenience, here is a link to the Dead by Daylight bug reporting forums: Steam Community :: Error

Have a great day

10

Hello Guys,
I’m only keeping you updated with my specifications and workaround. I’m experiencing the same reported problem with the following specifications:

Windows 10 - 64 bits
I7 3.4 ghz
GTX 550 ti (Geforce driver 381.65)

In my case, the editor crashed everytime I tried to open an animation blueprint and I tried the following:

Disabling Real-Time Thumbnails (didn’t work)
Running the engine with -dx12 (it worked, but my editor was extremelly slow)
Running the engine with -opengl4 (same here)
Using Forward Rendering (success, it has worked)

11

So Far so good another one for “Forward Rendering” .
Windows 10 - 64 bits I5 3.4 ghz GTX 550 ti

I also had some success with running the Editor with -dxddebug although I don’t know why this would be the case?? still locks entire system but only once an hour or so. which was great compared to once ever few minutes.

I can work again, for the heads up. I see Epic says the UE-42280 error is expected to be corrected for UE4.17
hope this comes to pass.

12

I found Lost 3D Device error happens almost immediately in Soul Calibur 6 when my desktop has just be turned on, then it becomes less frequent as the PC warms up. This suggests it is due to a still-cold power supply being unable to meet the peak demand of the GPU. Some voltage may be dropping too low and hanging the GPU.

13

Hey guys,

I don’t normally post here as I very rarely have any issues that I can’t find solutions to on google, but it seems that I have hit a roadblock and will required some input from this outstanding community.

I have updated to 4.24.1 and have started a small project and have come across the infamous D3D device being lost “Internal Error” issue.

bfc9d4d6d70599deec78e806769e6
EpicAccountId:d66ba0c22f4346f8be072dc9714a966b

Fatal error: [File:D:/Build/++UE4/Sync/Engine/Source/Runtime/Windows/D3D11RHI/Private/D3D11Util.cpp] [Line: 198] Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0020 - 'INTERNAL_ERROR')

UE4Editor_D3D11RHI
UE4Editor_D3D11RHI
UE4Editor_D3D11RHI
UE4Editor_D3D11RHI
UE4Editor_D3D11RHI
UE4Editor_RHI
UE4Editor_RHI
UE4Editor_RHI
UE4Editor_RHI
UE4Editor_RHI
UE4Editor_SlateRHIRenderer
UE4Editor_SlateRHIRenderer
UE4Editor_SlateRHIRenderer
UE4Editor_Core
UE4Editor_Core
UE4Editor_RenderCore
UE4Editor_RenderCore
UE4Editor_Core
UE4Editor_Core
kernel32
ntdll

Last important lines of log file

[2019.12.30-02.52.52:283][621]LogSlate: InvalidateAllWidgets triggered.  All widgets were invalidated
[2019.12.30-02.52.52:319][621]LogAudioMixer: Display: No commands were queued while flushing the source manager.
[2019.12.30-02.52.52:324][621]LogSlate: Updating window title bar state: overlay mode, drag disabled, window buttons hidden, title bar hidden
[2019.12.30-02.52.52:327][621]LogUObjectHash: Compacting FUObjectHashTables data took   2.93ms
[2019.12.30-02.52.52:454][622]LogPlayLevel: Display: Destroying online subsystem :Context_8
[2019.12.30-02.52.55:681][917]LogSlate: Window 'Message Log' being destroyed
[2019.12.30-02.52.55:687][917]LogSlate: Window 'Message Log' being destroyed
[2019.12.30-02.53.30:564][279]LogRHI: Error: SyncInterval 0
[2019.12.30-02.53.30:564][279]LogRHI: Error: SwapChainDesc.BufferDesc.Width 152
[2019.12.30-02.53.30:565][279]LogRHI: Error: SwapChainDesc.BufferDesc.Height 26
[2019.12.30-02.53.30:565][279]LogRHI: Error: SwapChainDesc.BufferDesc.RefreshRate.Numerator 0
[2019.12.30-02.53.30:565][279]LogRHI: Error: SwapChainDesc.BufferDesc.RefreshRate.Denominator 0
[2019.12.30-02.53.30:565][279]LogRHI: Error: SwapChainDesc.BufferDesc.Format 24
[2019.12.30-02.53.30:565][279]LogRHI: Error: SwapChainDesc.BufferDesc.ScanlineOrdering 0
[2019.12.30-02.53.30:565][279]LogRHI: Error: SwapChainDesc.BufferDesc.Scaling 0
[2019.12.30-02.53.30:565][279]LogRHI: Error: SwapChainDesc.SampleDesc.Count 1
[2019.12.30-02.53.30:565][279]LogRHI: Error: SwapChainDesc.SampleDesc.Quality 0
[2019.12.30-02.53.30:565][279]LogRHI: Error: SwapChainDesc.BufferUsage 48
[2019.12.30-02.53.30:565][279]LogRHI: Error: SwapChainDesc.BufferCount 2
[2019.12.30-02.53.30:565][279]LogRHI: Error: SwapChainDesc.OutputWindow 0000000001240832
[2019.12.30-02.53.30:565][279]LogRHI: Error: SwapChainDesc.Windowed true
[2019.12.30-02.53.30:565][279]LogRHI: Error: SwapChainDesc.SwapEffect 4
[2019.12.30-02.53.30:565][279]LogRHI: Error: SwapChainDesc.Flags 2050
[2019.12.30-02.53.30:565][279]LogD3D11RHI: Error: Result failed 
 at D:/Build/++UE4/Sync/Engine/Source/Runtime/Windows/D3D11RHI/Private/D3D11Viewport.cpp:389 
 with error DXGI_ERROR_DEVICE_REMOVED DXGI_ERROR_DRIVER_INTERNAL_ERROR
[2019.12.30-02.53.30:565][279]LogD3D11RHI: [Aftermath] GDynamicRHI=000002F66F53C0C0, GDX11NVAfterMathEnabled=0, Result=0xFFFFFFFF, bDeviceActive=0
[2019.12.30-02.53.30:565][279]LogWindows: Windows GetLastError: The operation completed successfully. (0)

I have tried changing my Tdr Values in RegEdit(Was required for Substance Painter) as seen below:

294580-unrealerror1regedit.png
294580-unrealerror1regedit.png3600×1090 241 KB

I have also tried underclocking my gpu as mentioned in this answerhub topic: [Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - 'HUNG') - Pipeline & Plugins - Unreal Engine Forums][2]

I have also updated windows 10 and installed my latest graphics drivers as well.

Also, I have turned off “Real Time Thumbnails”

Thank you for your time,

Aaron

14

Is it a laptop?

15

After crashing every 5 minutes using UE 4.24 and having NO problems with 4.23 I finally found a fix for myself.

I no longer crash due to D3D Device being lost for any reason after switching from Nvidia’s game drivers to Nvidia’s Studio Drivers in Geforce Experience.

I have been able to use 4.24 for hours without crashing due to D3D Device Lost. Haven’t crashed once since switching to the Studio Drivers.

I don’t know what they changed, but I did a clean installation and had no problems afterwards. For those of you having the D3D crash, can you see if this also fixes your D3D crashes?

UE-74575

16

How do I switch? On the web it says its not possible.

Thank you. This bug is driving me crazy.

17

Another unanswered question, nearly a year old. Superb.

18

I’m just beginning my first tutorial for UE and keep getting this crash. After searching the forum and the web, I still haven’t found a fix that works. I’d appreciate any help from a more experienced user.

The issue:

Listed here as “fixed” - but, as far as I can determine, it doesn’t indicate what the fix is.

My rig:
UE 4.26 (also crashed in 4.25)
Win 10
Nvidia Studio driver 460.89
Ryzen 3950X
EVGA FTW3 RTX 2070 Super

Steps tried:
-uninstalled and reinstalled the Epic Launcher and the UE editor
-updated to the latest NVidia Studio driver
-changed display resolution to and from 4k
-changed display color depth between 8bit and 10bit
-confirmed that D3D is activated
-searched the UE forum
-whined and felt sorry for myself

The Editor will open and stay open on its own, but it always crashes within a few minutes after I start moving objects around in the viewport.

UE did run successfully one time before on this machine, when I followed a tutorial to connect my Oculus Quest to VR Preview. It worked beautifully that one time, then never ran without crashing again.

.

19

Same issue here

20

A common issue.
You can find various links on this forum that suggest help.
Gathered several of these together for the Technical Support section of our games steam forum.
Hopefully you’ll find something there that works.

See Unreal Engine is exiting due to D3D device being lost.