Error when running almost ANY Unity Engine game.

Why are you running it with "-force-vulkan"? That's a really bad idea.

 

Can you upload the .dmp file from the crash?

 

Did this crash happen right after launch? Can you show the log file corresponding to the dump? It for whatever reason fails to allocate a back buffer... You are not low on memory when this happens, are you?

 

The error is DXGI_ERROR_DEVICE_REMOVED which is basically "something in the graphics driver went very wrong, but there isn't a good way to find out what".

Are you changing the game resolution or any other settings when this happens? I noticed it's failing right as the back buffer is getting recreated.

While this is not guaranteed to work, you could try switching to DirectX 12 with the "-force-d3d12" option (this is similar to the Vulkan advice, except that the Vulkan backend is unlikely to work on Windows games as it requites the game to opt-in to support it whereas D3D12 shares shaders with D3D11).

If this is happening with multiple games, it's likely the issue with the system (either software or hardware). It might be worth trying to reinstall Windows cleanly from scratch.

 

No need to spam the forum, I see your replies.

Can you elaborate? Did it crash your machine?

Unity is by far the most popular engine in the world, so it's only natural it gets blamed for many hardware/software instabilities. It runs on billions of devices worldwide and in vast majority of cases it doesn't have any issues. Again, just because your computer runs other engines without problems doesn't necessarily mean the problem is within Unity. So far, the evidence doesn't point to it being Unity's fault.

Are any of your computer components overclocked (CPU, RAM, GPU)? Did you try disabling XMP memory profile? Lots of these issues happen due to unstable overclocks.

I could make you an instrumented build of a sample made with Unity that may contain some clues of what goes wrong IF the problem is with Unity. However, that will not be helpful if the problem is somewhere else. Let me know if you're interested in this.

 

That sounds more and more like a software or a hardware issue. But I'll get you an instrumented build. In the mean time, please check if XMP profile is enabled in BIOS.

 

It's a form of automatic memory overclocking. It's known to cause stability issues in certain cases. The setting is called "XMP" and it's in BIOS.

 

It's something you can change when your computer is starting up.
https://www.wikihow.com/Change-Computer-BIOS-Settings

 

Okay I have something to share. Here are the builds: https://share.unity.com/receive/?th...e=WPKkTAKMMECjlkkL1VTAu65XSm31vfjC1GmiBsLa4P0

Instructions:

1. Extract the 7z archive;
2. Run TroubleshootingCrashes-normal\ToubleshootingCrashes.exe, reproduce a crash. Once it crashes, save off the player.log (Found in %LOCALAPPDATA%\..\LocalLow\DefaultCompany\ToubleshootingCrashes) and the .dmp file (player log will say where it saved the dump).
3. Enable the "Graphics Tools" optional feature in Windows. Go to the Settings panel, under System, Apps & features, Manage optional Features, Add a feature, and then look for "Graphics Tools". Once installed, reboot.
4. Run ToubleshootingCrashes-instrumented\ToubleshootingCrashes-Instrumented.exe. Reproduce a crash. Once it crashes, save off the player.log (Found in %LOCALAPPDATA%\..\LocalLow\DefaultCompany\ToubleshootingCrashes-Instrumented) and the .dmp file (player log will say where it saved the dump).
5. Send me the log and dmp files from steps 2 & 4.

 

Well that's at shame, but at least it eliminates there being some fundamental issue with Unity that causes this.

Unfortunately, doing such debugging with live games is not really possible - they need to built it as "development build". I suggest contacting some of the developers that made these games to see if they were willing to make you development builds of the game so you could run it with "-force-d3d11-debug" command line arg and see why the game crashes.