We’ve all seen it. You’re mid-scramble through Norway, 1st place in the wet, and suddenly—freeze, stutter, black screen, then the desktop. No error message? No. Just the silent killer: a .dmp file dumped into your %LOCALAPPDATA%\Dirt5\Crash_Client folder.
The car hit the ramp. It sailed through the air, suspended in a glorious arc of mud and motion. The engine roared clear and true.
The is a critical software crash that completely halts the game, forcing it to generate a diagnostic .dmp file before abruptly exiting to the desktop. This specific error typically strikes right at the initial splash screen or immediately after the "Press A to Start" prompt, preventing players from ever reaching the main menu.
If you encounter this error on PS5:
The "Failed to create dump file" error in DIRT 5, often caused by DirectX 12 instability or permission issues, can be resolved by switching to DirectX 11 via launch options, updating GPU drivers, or running the game as an administrator. Other solutions include verifying game file integrity, disabling overlays, and clearing temporary files. For more details, visit Driver Easy
Download the GeForce Experience app and ensure you have the latest Game Ready Driver.
If the issue persists, check the official Codemasters/EA support forums, as it may be a wider server-side or patch-specific issue. dirt 5 dump file error top
Work through this section in order. Many users report success after applying the first few methods alone.
The error 0xE06D7363 (Microsoft C++ Exception) or ACCESS_VIOLATION (0xC0000005) you see in the dump summary? That’s not the root cause. That’s Dirt 5’s engine (EGO 4.0) throwing its hands up.
Go to User Settings → Game Overlay → Turn off "Enable in-game overlay". We’ve all seen it
Dirt 5 is VRAM and RAM intensive, especially with high-resolution textures and weather effects. The error often appears when:
The loading bar filled up. The screen faded to white, then to the dusty, sun-drenched track. The countdown timer appeared in the corner.
For crashes on Xbox: