A number of code changes have gone into 4.17 to potentially resolve or significantly reduce the frequency of these crashes. If you still experience this crash, please submit your crash reports along with detailed information. Please keep in mind that this is still expected and natural to occur on low spec GPUs, but should not be an issue on recommended hardware.
This JIRA has been made to consolidate all "D3D device being lost. (Error: 0x887A0006 - 'HUNG')" crashes into one. Previous Jira tickets include:
Most of these JIRAs link to different CrashGroups in CrashReporter which all have slightly different Callstacks.
These crashes gained widespread frequency starting with the 4.14 Preview (a regression from 4.13) and have consistently remained as the #1 crash based on submitted crash data. One fix was made in 4.14.2 for a specific repro case (CL 3237597) but that did not resolve the overall issue.
Affected GPUs are varied, including:
Some affected users claim that the following workarounds have helped them:
Some specific crashes have been reproduced internally by Engine Support, but in other cases the repro steps are currently unknown. The crashes seems dependent on hardware and load placed on the GPU, without a single specific repro case. Please reach out to the Engine Support Technician team for more details, or review repro steps on the additional linked Jiras.
Fatal error: [Link Removed] [Line: 176] Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - 'HUNG')
OTHER CALLSTACKS ALSO INCLUDE LINES:
There's no existing public thread on this issue, so head over toAnswerHub just mention UE-42280 in the post.