If you are close to the available memory limit, it is most likely the problem causing the crash. With your project open and running, you can see how much GPU memory is being consumed versus what is availble. Windows Tasks Manager displaying the current stats for the GPU that include its available memory and current amount consumed.

d3ddebug provides information about the D3D pipeline. gpucrashdebugging collects GPU progress and tracks the current GPU state when debugging GPU crashes. There are two debugging command line arguments that you can use to output logs with useful information. Therefore, it provides no actionable information.

However, when a GPU crash happens, the CPU callstack does not really point to the real cause of the crash but just indicates what the CPU was doing when the GPU crash happened. When a crash occurs in Unreal Engine, you may want to start by looking at the callstack generated by Crash Reporter and log files that contain information to help in understanding what is happening. The sections below provide you with some debugging options to help identify the root cause and some preventative measures you can take. Times out while doing an expensive operation (TDR event)įor these reasons, in an application like Unreal Engine, it is not possible to always know why a crash occurs and may be impossible to avoid a crash at the application level. GPU crashes can occur for various reasons, such as: When you get a GPU crash, the callstack and logs may have messaging such as 'GPUCrash - exiting due to D3D device being lost - D3D Hung' and 'DXGI_ERROR_DEVICE_REMOVED with Reason: DXGI_ERROR_DEVICE_HUNG.' In these situations, Windows will kill the GPU driver, resulting in an application crash. Windows has implemented a safeguard to prevent applications from locking up by using too much memory, when processes take too long to complete, and various other reasons.

Nvidia automatic driver detection tool