Unreal Editor crashes on level load on recent GeForce Drivers

Development Platform & Builds
, ,
1

Bump. Anyone?

2

I’ve found that recent NVidia GeForce Game Ready Drivers have a tendency to cause the Unreal Editor to crash when certain levels are loaded (or immediately on launch if such a level is the level that is opened by default in a project).

If a level load causes a crash immediately when project is launched, the crash does not provide any kind of stack trace. However, I was able to obtain a stack trace by setting another level as default level for the project and switching levels afterwards to one of the problematic levels, or by simply launching the editor with Visual Studio attached. The stack trace was similar to the one that can be found here: Unreal Engine Issues and Bug Tracker (UE-42280) , in that ends by complaining about a D3D device being lost (‘HUNG’).

I personally did not have this problem when I was on an earlier version of the NVidia GeForce Game Ready Drivers, though I do not remember exactly which version I was previously on. I recently updated to version 382.33 (release date: 22 May 2017). With that version of the graphics drivers, the issue occurs on Unreal Engine 4.14.3 as well as Unreal Engine 4.16.1 (did not test other versions in between). I have a GTX 1070, and run on Windows 10. Another member of my team confirmed to have the same issue in Unreal Engine 4.16.1, with even more recent drivers (382.53, release date 9 June 2017). He was also able to confirm that the issue disappears again by reverting to version 382.05 of the graphics drivers. He has 2x GTX 660 with SLI bridge, and in his case he’d also crash on a significantly simpler level where I was able to load without crashing. So, it appears like the more recent GTX 1070 is able to still handle very simple levels without crashing, whereas 2x GTX 660 even already crashes on an incredibly simple level (the levels I was crashing on also weren’t particularly complex, but a bit more complex than the ones I didn’t crash on).

So, to summarize:

  • UE4.16.1 + GeForce Game Ready Driver 382.05 → No crashes
  • UE4.14.3 or UE4.16.1 + GeForce Game Ready Driver 382.33 or newer → Crash on level load (may at least have to be somewhat complex depending on hardware, but nothing impressive)

I was able to get around the crash (even with the new drivers) by launching UE4Editor.exe with the -opengl4 argument, but this did result in some graphical artifacts (colored lines/rectangles). So, obviously that’s not an ideal solution.

3

Bump, I hope this gets fixed.

4

Any news on this? I haven’t seen any new versions of either UE4 or of the graphics drivers, so I’m still experiencing this issue. If on the same PC someone wants to have the more recent graphics drivers for improvements in performance in other games, it is basically impossible to use the Unreal Editor for anything on that PC.

5

same here with amd though

6

Same here, UE 4.15.3, with GTX 1060, Windows 10 Pro x64. nVidia drivers version 385.28. My project loads once i delete the famous Water Planes folder… Tried to redownload it and recopy it. Still crashing at the opening of my map…

LogD3D11RHI:Error: Direct3DDevice->CreateComputeShader( (void*)CodePtr, CodeSize, NULL, Shader->Resource.GetInitReference() ) failed at D:\Build++UE4+Release-4.15+Compile\Sync\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Shaders.cpp:197 with error DXGI_ERROR_DEVICE_REMOVED DXGI_ERROR_DEVICE_HUNG

7

Hi everyone.

Updates have been made in the 4.17 release that resolve some cases of the ‘D3D device lost’ crashes. I recommend testing out 4.17 (currently 4.17.1) to see if it resolves the issue for you, and if it may be worth updating your project to develop on the new version.

Cheers

8

In my case it actually appeared to be fixed in 4.16.2 already (4.16.1 was the latest at the time of posting my question). It looks like other people posting here are experiencing a similar issue with 4.17.1 though… I don’t know when I’ll be able to upgrade our project to 4.17 and check whether it’s still fixed on my end there or if the issue is re-introduced.

9

Hi! Wow, thanks for your fast answer.
I tested it today with UE 4.17.1. It’s still crashing.
I tried this move with UE 4.15.3 :

1- delete the Water Plane folder from the Content folder.

2- reload the project/map : works fine. Clode the project.

3- add the Water Plane ressources from the launcher to my project. Reload te project.

4- select the Translucent Blueprint and drop it in my scene. Eveything works fine. The shader is working perfectly. I can set the colors i want, move the sliders as much as i want, …

5- I save everthing and close the project.

6- relaod the project/map => CRASH ! and same problem related to D3D11, same crashlog.

I did the same workaround with a 4.17.1 copy of my project. Same error.
I tried to recompile the blueprint at the beginning of step 4. Same problem in the end (step 6)…
I’m trying to find a good material or BP to replace my pool water planes, but it’s not as good…

Oh by the way, i rolled back my drivers to nVidia 384.94. Same problem. I tried a cleaned reinstall of the drivers, no success.

All i can say is that the crash happened after setting the Post Process Screen Percentage to 200. (for high quality sequencer rendering batch). Everything worked fine before that. Strange isn’t it ? (i rolled back to ScreenPercentage 100, no success)

10

Yes, we’ve incrementally made updates across a few releases, and 4.16.2 included some which have definitely shown a reduction in the number of these crashes. The fixes from 4.16.2 are also included in 4.17, but if 4.16.2 is working well for you, then you should stick with it (although you may want to consider at least taking the latest 4.16.3 hotfix).

Cheers

11

Thank you for the information. I’m sorry to hear that you are still experiencing these crashes in 4.17. While a number of cases have been resolved, we are aware that other cases continue, and we will continue to look into them.

Cheers