Unreal Editor Crashes After Startup

Development Platform & Builds
, , , , ,
1

Hello,

Up until about a week ago, I was having no trouble at all with the Unreal Editor. The program had been working fine and I was in the process of learning how to use the engine.

Now I keep running into a problem. Every time I open the editor and select a project, the editor itself boots up fine. But as soon as I go into any of the menus, the program crashes without fail. I’ve tried uninstalling and reinstalling but that did not solve the problem. Unfortunately I am not as tech savvy as I would like to be, so I’ll just post as much information as I can. Any and all help would be greatly appreciated, thank you!

I am using Unreal version 4.20.1
I have an Intel Core i5-8300H CPU @ 2.30 GHz
8 GB of RAM, Nvidia GeForce GX GPU
Crash Log [1]: 250302-myproject2.log (28.1 KB)

2

Do you see a ue4 has crashed window? Does it show details of what made it crash in the bottom black square? If not, do the following:
In epic games launcher, click on the little triangle next to your engine version and download the “debugging symbols”. This will show some information the next time it crashes.

3

Thank you for the swift reply DarkWave0!

Here is what I got from the crash log after I downloaded the debugging symbols (thanks for that too btw):

Fatal error: [File:D:\Build++UE4\Sync\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp] [Line: 826]
Rendering thread exception:
Fatal error: [File:D:\Build++UE4\Sync\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 200]
Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - ‘HUNG’)

4

I have the same problem. For me all my games are affected so it seems like it’s not related to unreal. I’ve been trying things to solve this problem:

  • changed filepaths that are too long
  • Removed 3 folders from the project folder and having editor rebuild it(forgot which)
  • reinstalled windows10
  • used DDU to clean display drivers and reinstalling nvidia drivers
  • installed older GPU drivers
  • removed geforce experience
  • removed anything related to unreal engine and epic games launcher and reinstalling
  • changed blueprints with errors in them
  • changed the startup map for my project
  • disabled “realtime thumbnails” in the asset browser
  • ran ue4 in DX12 by adding -DX12 to the editor’s shortcut
  • ran ue4 in openGL4 by adding -opengl4 to the editor’s shortcut
  • enabling nvidia aftermath by using these instructions:
    NVIDIA Aftermath | Unreal Engine Documentation
  • Set power profile in windows to maximum performance
  • Restored backups of my project multiple times
  • Packaged my project to see what errors it gives and solve them
  • Checked my hardware temperatures and activity
  • Installed chipset drivers for my motherboard
  • Checked BIOS for any settings that might influence GPU
  • Tested other unreal games (same error)
  • Tested other games (they also crash with a similar “DXGI has stopped” kind of error
  • Tested if opengl works using tessmark
  • Disabled discord, steam, xbox gaming overlays
  • Added some regedit thing that makes windows wait longer when GPU crashes
  • Checked solutions from other games that have similar crashes

Other things you can try:

  • if you’re using a laptop; plug in the power supply

Info I’ve gathered:

  • Making a new project seems to make crashes happen less often but they still happen. This crash happens more often with heavier load
  • It doesn’t happen in the first 10 minutes after rebooting mostly
  • There’s a ticket for this problem: UE-51650
5

For me it turned out that it was one of my RAM sticks that was broken. Weird how that causes a GPU crash. How is your search going OP?

6

Thanks for all the information, I really appreciate it!

So far haven’t found the source of the problem, although I am going to look into the ticket number you posted. I just disabled my Steam and Discord overlays and updated my Nvidia drivers. I’m running through some of the other stuff you tried to see if it yields any results for me. Fingers crossed.

That is weird though, I hope I’m not experiencing the same problem…