Post 4.13 Upgrade "Device Lost" Crashes

mechotron_ue4.log
dxdiag
crash report

I’m getting a “D3D device lost” crash fairly frequently as of the upgrade to 4.13; not really sure what to even identify as a good repro case as it seems to happen frequently enough that I can’t narrow anything in particular down.

Using exclusively dynamic (movable) lights (skylight, two directional lights of which only one is active at any given time), heightfield GI, distance field AO, and LPVs.

Hey -

Looking at the log files, this is a known issue that you can follow here:

Something you can try would be to update video drivers for your graphics card if available.

Cheers

Hello ,

I’d like to ask a few questions to help us narrow down the cause of this crash:

  1. Were you able to update your drivers / was there any affect after doing so?
  2. Can you provide an estimate of how often this crash occurs for you (3/4 times, 5/9 times, 10/10 times, etc)?
  3. Does the crash occur if you create a new blank project or new project from a template?
  4. If you create a copy of the project, are you able to disable/remove features and still get the crash to occur?

Another test would be to disable the Global Illumination.It’s possible that it’s using too much video memory and causing the driver crash to happen. If the crash does still occur, you can try disabling Ambient Occlusion as well by using the command r.DistanceFieldAO 0.

Additionally, according to your logs there are a number of plugins being used (Truesky, Easy Ballistics, Quixel Substance, Unreal Fast Noise). Can you try disabling the plugins in use (one at a time) and see if the crash still occurs?

Yeah, the plugin disabling didn’t really affect anything.

The most common crash seems to be a result of using the static mesh viewer, actually.

Could you explain what you mean by “using the static mesh viewer”? What are you doing with the mesh editor when the crash occurs? Does the crash occur when a specific mesh is open in the editor or with different meshes? Does the crash occur if you open a mesh from the starter content? If the plugins did not have an affect on if the crash was occurring, can you also try disabling DFGI and DIAO separately, as well as provide information for the other questions asked?

Ah, yeah, sorry.

  1. Latest drivers installed after running DDU for a clean install.
  2. Once I open the static mesh viewer, it’s about 90%
  3. Will find out.
  4. Project is fairly enormous, so probably won’t do this.

I’ve tried disabling distance field AO and it may be helping, but I shouldn’t be running out of vram either. So that’s confusing.

Does the crash occur as soon as you open the static mesh editor or after making a change inside the editor? If the crash occurs after an edit, is it after a specific edit or after any change is made? Does the crash occur when a specific mesh is open in the editor or with different meshes? Does the crash occur if you open a mesh from the starter content?

I can look into that last question a bit later, but I can answer the remaining:

  1. Crash occurs shortly after starting the static mesh editor; I grabbed gpushark to monitor my VRAM usage and, while high, there are about 400mb free, so I wouldn’t think that would be the issue.
  2. No specific mesh seems to be the issue.

Hey -

Thank you for the provided information and assistance. We have reproduced the crash internally to give a reproduction case to work from.

not sure if this is relevant, but with my crash log, I see a lot of render errors trying to write to the D:\ drive. I do not have a D:\ drive. Maybe that is what’s happening to me??? Also, the crash for me does not specifically happen in the mesh viewer. Most of the time for me has to do with simply editing in the Level Editor. Meaning it can happen when I add a static mesh, move a static mesh, or even editing tools for the BSP brushes.

<3 <3 <3 <3