Icarus
... Dec 4, 2021 @ 9:00am
Unreal Engine is exiting due to D3D device being lost
Hey - just want to say that you should review your Unreal-Programming.

Other Unreal-Engine-Games are running fine on my rig.
(Intel I7-7700K / GTX1080ti / 32GB RAM / Win10 / New Installation of OS)


Error:
LowLevelFatalError [File:Unknown] [Line: 198] Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - 'HUNG')


(Tryed many different troubleshooting without success)
< >
Showing 1-15 of 25 comments
EXERION Dec 9, 2021 @ 12:30am 
same problem here
Eivind Dec 14, 2021 @ 5:01am 
I have the same problem...
EXERION Dec 15, 2021 @ 1:52pm 
Originally posted by Fleckser:
Hey - just want to say that you should review your Unreal-Programming.

Other Unreal-Engine-Games are running fine on my rig.
(Intel I7-7700K / GTX1080ti / 32GB RAM / Win10 / New Installation of OS)


Error:
LowLevelFatalError [File:Unknown] [Line: 198] Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - 'HUNG')


(Tryed many different troubleshooting without success)
Did you find a fix yet?
If not, then try turning Steam in-game overlay off but not from the game properties, but from Steam settings and use directx 12 instead of 11. I did this and played the game like 3+ hours and it didn't crash but somehow the in-game texture looks terrible even if I set it to epic. I haven't tried using directx 11 tho.
... Dec 15, 2021 @ 2:28pm 
Thank you for this fix-hint.
I will try this and response :-)

"my" textures are terrible too
Last edited by ...; Dec 15, 2021 @ 2:29pm
Mika Dec 15, 2021 @ 4:43pm 
I have the same problem. Also one of the other people I play with has the same issue as well.
Ancient Dec 15, 2021 @ 5:09pm 
D3D DEVICE HUNG errors mean that your GPU driver has crashed.

Sometimes, rarely, it is a genuine driver crash but most of the time it is a result of Windows TDR (Timeout Detection and Recovery), which, if the hardware at any time does not respond within the default 2 seconds, Windows will automatically kill and restart the graphics driver.

In my experience, this is often caused by an unstable GPU overclock, whether manual or handled by the Nvidia Boost 2.0/3.0 algorithm (factory OCs by AIB partners can definitely be a cause and may need to be fine tuned to eliminate the problem). Sometimes an easy fix is just to crank up your GPU's power limit to 110% or more using Afterburner or Precision XOC. That might allow it to pull a little extra voltage during peak loads and remain stable through the point where it might have previously faulted. Another option is to fine tune the boost curve to use a little less frequency for each given voltage on all the higher frequency points along the boost curve.

Yet another option is to edit your registry to increase the TDR timeout from 2 seconds to 4, 5 or even more seconds. This one is sometimes hit or miss. If the actual cause is GPU core instability causing the hardware to fault and stop responding, this is no more than a band-aid, because what needs to be addressed is the actual OC instability and the card needs to be fed more voltage per clock until it is stable.

Honestly, the very first thing I would try is to DDU your drivers in safe mode and then do a clean install of the latest driver to eliminate that as a cause. Then, if it's still happening, move on from there and troubleshoot further.
... Dec 16, 2021 @ 9:38am 
Thanks for your Help Ancient.

I got a Zotac gtx 1080ti in my rig.
As far as i know, there is no overclocking.

I am very curious because since the last new OS installation, every game crashes.
Even blizzard games (D2R) - and there was no problems before the OS installation.

I tryed an Win default graphics driver (465.10) - still crashes.

Will try your steps now and give report :-)
... Dec 16, 2021 @ 9:41am 
Update:
Checked the Eventlog.

It says "nvlddmkm not found".
..will go on searching the problem.
I got a GTX 1080ti, I7 9700K and 32gb ram. I am guessing this game wont run on gtx 1080tis?
NeVuR Dec 16, 2021 @ 3:38pm 
im getting this -

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000038
... Dec 17, 2021 @ 1:30am 
I cleared the whole system - even with new partition for windows10.
Started a new game - hung again.

Im finally done with this unfinished piece of coding.


searched the relevant file.

Fault ID: 13
nvddmkm.sys missing


ehm yes....after a clean installation the file is missing?
searched for it - no file there.

Got anyone an idea where to get this file?
(Newest Nvidia driverpack is installed - very strange)
Last edited by ...; Dec 17, 2021 @ 1:46am
EXERION Dec 17, 2021 @ 3:06am 
If you still get the D3D device being lost (Error: 0x887A0006 - 'HUNG'), for me it definitely the game running with Directx 11 is the problem. I run the game using Directx 12 by modifying the Launch Option adding "-dx12" line fix the crashing issue but the game looks terrible even on high to epic preset and become a bit stutter-y which doesn't happen on Directx 11. Increasing the TDR on registry editor don't help at all.
... Dec 17, 2021 @ 3:13am 
thanks for help so far.

tryed the 3dmark - even here there are errors.
i really have no idea what is wrong.

nvlddmkm is causing the trouble and i dont know how to fix this.
there are so many different points what it could be.

this is gonna be a looong weekend :steamfacepalm:
Ancient Dec 18, 2021 @ 1:20am 
Originally posted by EXERION:
If you still get the D3D device being lost (Error: 0x887A0006 - 'HUNG'), for me it definitely the game running with Directx 11 is the problem. I run the game using Directx 12 by modifying the Launch Option adding "-dx12" line fix the crashing issue but the game looks terrible even on high to epic preset and become a bit stutter-y which doesn't happen on Directx 11. Increasing the TDR on registry editor don't help at all.

That really should not be a fix, IMO. Every GPU we have in circulation today should run DX11 especially, but also DX12 without issues. This ability should go back to GTX 900 desktop and all GTX 1000 GPUs. There are certain GTX 900 mobile GPUs that are not actually DX12 capable. That's real ♥♥♥♥. They are Maxwell Gen 1 GPUs that are only DX_11_1 capable and the GTX 960M is probably the most popular example of this. It is not a DX12 GPU and never will be.

Meanwhile, the GTX 960 Desktop or better were hardware capable of DX12 and should have no issues with DX12 beyond the fact that a GTX 960 or a 1050 Ti (it's hardware counterpart) are very weak when it comes to memory bandwidth and might struggle with newer games due to that alone, not due to the fact that they can't handle rendering operations. They can, they just suck at it so the FPS witnessed will be bad.

OP's 1080 Ti is fully capable of both DX11 and DX12.

I almost want to repeat after hearing they are seeing errors to do a full driver reinstall.

OP, if you haven't yet. Download DDU from wagnardsoft and run it in safe mode.

That means holding your shift key while clicking Start > Power > Restart in normal windows. That should, on reboot, bring up the Windows Power user menu and let you pick the option to go through a lot of power user options, one of which is a safe mode boot. From there, run the DDU package you already got and pick the nvidia options to clear all Nvidia drivers and software from the system.

When it's done it will reboot the PC and then you should go ahead and get the newest Nvidia Drivers as you normally would from Nvidia.com/drivers/

Install those and reboot even if the software doesn't tell you that you have to.

From there, try everything again. Test your games and try to replicate any issues you've had.

If they still persist, that sucks because it may be a genuine hardware issue.
Last edited by Ancient; Dec 18, 2021 @ 1:39am
... Dec 18, 2021 @ 1:53am 
Thank you Ancient,

yesterday i made exactly this steps you've written down :-)
Also i renewed manually the new "nvlddmkm"Driver-File.
After 5 head-crackin' hours of searching the internet and trying lots of things, it seems to work.
(The final solution is the new "nvlddmkm"-File, so far)

I will keep you updated :-)


Important Note:
The nvlddmkm-File was not installed in the System32-Direction by the installer!
Last edited by ...; Dec 18, 2021 @ 1:54am
< >
Showing 1-15 of 25 comments
Per page: 1530 50

Date Posted: Dec 4, 2021 @ 9:00am
Posts: 25