Hello there @aristia697!
This is an interesting scenario, what you are getting is one of the catch-all errors for graphics conflicts, but we need to reach a possible solution without access to the crash log, due the NDA in place. We do know that your project has multiple levels, and the crash is affecting a very specific one. Meaning, whatever’s causing the crash, is only contained in said level. That already gives us one possible approach.
Take one of the functioning sub-levels, (or create an empty one, if possible), and start moving assets associated to the affected level, that are NOT present in other levels. Then, try to run the test level, until you get a crash. This should allow you to pinpoint the problematic asset, isolate it from the build, then re-open the affected level. Since the crash is graphic-based, you can stick to testing anything that renders on screen, or blueprints that generate certain effects.
Next, we got the usual suspects for graphic issue. From an open scene, you can disable taxing feaures like Nanite and Lumen from Project settings, or via console commands. Then, open the affected level again. You can also test by forcing the engine into DirectX11 with the -dx11 tag.
Another approach, would be to give your setup more time to process what’s going on, since this type of GPU crash is due the card not being able to fully render the screen before timeout. If you can touch the registry in your station, a TDR Delay should be useful here.
- Open the Registry Editor, and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
- Create two DWORD (32-bit) values: “TdrDelay” and “TdrDdiDelay”
- Set them both to 60 (Decimal), then restart your PC.
This will give your GPU about an extra minute to process during level load, which should prevent the crash alltogether.
If the issue persists even then, the remaining action would be to check the full log with someone inside your project, to avoid breaking NDA. Try looking for entries related to “Crash”, “Error”, “Unable to…”, or “Missing…”. Since the crash occurs on load, the line should be early in the log, during map setup. Hope this helps, and good luck!
