An Unreal Process Has Crashed UE4 | Fixes That Stick

Guide / By

This UE4 crash usually comes from drivers, overlays, corrupted files, or a bad project load, and logs tell you which.

If you’re staring at a crash window, it can feel like Unreal pulled the plug without warning. Most of the time the trigger is repeatable once you know where to look. A graphics driver can fail during shader compilation, a monitoring app can hook into DirectX, or a damaged file can break the load sequence.

This guide is built for the real-world situation where you want a fix without random tweaking. You’ll start with checks that are safe, then read the crash report, then apply targeted repairs based on what the log shows.

What This Crash Message Is Telling You

The crash dialog is a wrapper around a fatal error. UE4 exits because something it needs is missing, unstable, or rejected by the system. That can be hardware-related, software-related, or project-related.

Think of it as a breadcrumb. Your job is to turn that breadcrumb into a concrete cause by matching the crash to a pattern.

  • It Crashes During Launch – The issue is often drivers, DirectX, overlays, missing runtimes, or a corrupted install.
  • It Crashes When Loading A Level – The issue is often a specific asset, a plugin, or a save/config file that got corrupted.
  • It Crashes In One Project Only – The issue is usually inside the project folders, plugins, or config.
  • It Crashes In Every UE4 App – The issue is usually system-level, like drivers, overlays, clocks, or storage errors.

You’ll see people call it the “an unreal process has crashed ue4” error. Treat that phrase as a label, not a diagnosis. The log is where the diagnosis lives.

An Unreal Process Has Crashed UE4 After An Update

When the crash starts right after an update, think in two directions: what changed on your PC, and what changed in the app. Updates can flip graphics defaults, swap runtime files, or invalidate cached shader data. Start with fast checks that do not touch your project files.

  1. Reboot And Retry Once – A half-finished driver install or a stuck overlay can survive a normal close. A reboot clears that state.
  2. Undo Recent GPU Driver Changes – If you updated your GPU driver and the crash started right after, roll back or install a different recent driver version.
  3. Disable Overlays Before Launch – Close Discord overlay, GeForce Experience overlay, Steam overlay, Xbox Game Bar, and any frame counters.
  4. Verify The Install – Let the launcher re-check files so missing or corrupted content is restored.
  5. Switch Rendering Mode If The Game Offers It – If there is a DirectX 11 option, try it first. DX11 is often more forgiving on older drivers.

After each step, do one launch test. If it stops crashing, you found the change that mattered.

Find The Crash Report And Read The Right Lines

The fastest way to fix a UE4 crash is to stop guessing and read what the crash reporter saved. Even if the crash window does not show a call stack, the report still creates files that point to the failing module.

Start with these locations on Windows. Pick the newest log.

  • Game Log Folder – Look under the game’s install or documents path for a Saved\\Logs folder.
  • Project Log Folder – In your UE4 project, check ProjectName\\Saved\\Logs.
  • Crash Folder – Check ProjectName\\Saved\\Crashes for the latest crash report bundle.
  • Crash Reporter Log – On Windows, CrashReportClient logs are commonly saved under AppData\\Local\\CrashReportClient\\Saved\\Logs.

Open the newest .log file and search for the last block before the crash. You’re looking for a module name, a missing file message, a GPU error, or a plugin reference.

Clue In The Log Likely Cause Try This First
GPU crashed / device removed Driver issue, overlay hook, unstable clocks Disable overlays, revert clocks, swap driver
Missing pak / file not found Corrupted install or mod conflict Verify files, remove mods, reinstall clean
Access denied / cannot write Permissions or security tool block Run as admin, whitelist folders, check disk

If the crash happens after a specific action, match that action to the last log entries. A crash right after “Initializing D3D” points to graphics. A crash right after loading a named asset points to content.

Fix Graphics And Overlay Triggers First

Many UE4 crashes on Windows tie back to the graphics stack. That stack includes the driver, DirectX, and any app that injects itself into frames. Fixing that layer first can remove a large set of crash types in one pass.

Reset Overclocks And Tuning

UE4 can be sensitive to borderline GPU or CPU settings. A clock that seems fine in one game can still crash a different render workload. If you use MSI Afterburner, Radeon tuning, Intel XTU, or BIOS OC, test once at stock values.

  • Return GPU To Stock – Reset core and memory clocks, then close tuning apps during the test.
  • Return CPU And RAM To Stock – Disable CPU OC and any aggressive memory profiles for one controlled test.

Do A Clean Driver Change

Driver installs can pile layers on top of old components. A clean driver change is worth doing when logs point to GPU issues or when the crash started after a driver update.

  1. Download One Known-Stable Driver – Use the GPU vendor’s official site and grab a standard release driver.
  2. Perform A Clean Install – Use the installer’s clean option if available, then reboot after install.
  3. Test With Default Driver Settings – Reset control panel overrides like forced AA, forced AF, and frame caps.

Turn Off Overlays And Injectors

Overlays and performance tools hook into the render path. When that hook misbehaves, UE4 can crash even if the game itself is fine.

  • Disable Game Overlays – Turn off Steam overlay, Discord overlay, GeForce Experience overlay, and Xbox Game Bar.
  • Close Frame Counters – Exit MSI Afterburner, RivaTuner, and any FPS limiters while testing.

Prefer DirectX 11 When You Have A Choice

Some UE4 titles offer a DirectX 11 toggle. If your crash happens during launch or right after loading shaders, DX11 can be a steadier test path.

  1. Use The In-Game Graphics Option – If there is a DX11 option in settings, select it and restart the game.
  2. Use Launcher Launch Options – Some launchers allow launch arguments. If the title documents a DX11 flag, use the documented flag only.

Repair Files, Caches, And Permissions

If graphics fixes did not change anything, treat the crash as a file or write problem. UE4 reads and writes a lot of small files during start, shader compile, and asset load. One blocked write can crash a session.

Verify And Rebuild What You Can

Verification fixes silent corruption and restores stock files.

  • Verify UE4 Game Files – In Epic Games Launcher, open Library, click the three dots next to the game, choose Manage, then click Verify.
  • Verify Unreal Engine Files – In the Unreal Engine section, open Library, use the engine tile dropdown, then select Verify.

Clear Derived Data Cache And Shader Caches

A bad cache can crash on startup. Clearing the cache forces a rebuild on the next launch.

  1. Close Unreal And The Launcher – Exit the app fully so files are not locked.
  2. Open The Local Cache Folder – On Windows, check C:\Users\[YourUser]\AppData\Local\UnrealEngine\Common\DerivedDataCache.
  3. Rename The Cache Folder – Rename it so you can restore it if needed.
  4. Launch And Wait For Rebuild – The first start may take longer while shaders rebuild.

Remove Permission Blocks

If the log shows access denied, the app is failing while writing config, cache, or save files. This can happen when the install folder is protected, or a security tool blocks writes.

  • Run As Administrator – Right-click the game or UE4Editor.exe and choose Run as administrator for a test session.
  • Whitelist The Install And Saved Folders – Add the game folder and Documents\\My Games folder to your security tool’s allowed list.
  • Move The Install To A Simple Path – Install to a short path like C:\Games\Title to avoid odd permission edge cases.

Trim Background Apps

Some tools interfere with UE4 even when they are not made for games. Audio enhancers, RGB control suites, macro tools, and third-party network tools can inject DLLs or filter device calls.

  • Close Extra Apps – Close background tools, then retry the launch with a clean desktop.
  • Test With A Minimal Startup – If the crash disappears, add apps back one by one until you find the conflict.

Project-Level Fixes When The Editor Dies

If the UE4 editor crashes while opening one project, treat it as project data or settings. If it crashes on every project, treat it as engine install, driver, or system. This section assumes only one project fails.

Protect Your Work First

Before you delete folders, make a safe copy. That way you can reverse a step if you learn you removed a file you needed.

  • Duplicate The Project Folder – Copy the entire project to a new location and work on the copy.
  • Note The Last Change – Write down the last asset you imported, plugin you enabled, or setting you changed.

Clear Project Generated Folders

UE4 regenerates a lot of files automatically. If one of those files is corrupted, deleting it forces a clean rebuild and can stop the crash.

  1. Delete Saved – Remove ProjectName\\Saved to clear local config, autosaves, and logs.
  2. Delete Intermediate – Remove ProjectName\\Intermediate to clear generated build and cache files.
  3. Delete Project Derived Data – If your project has a DerivedDataCache folder, remove it as well.

Disable Plugins That Crash On Startup

If the call stack points to a plugin module, the editor may crash before the UI loads. Disabling that plugin can get you back into the project so you can repair or update it.

  • Edit The .uproject File – Open the .uproject in a text editor and set the plugin’s Enabled value to false.
  • Temporarily Remove The Plugin Folder – Move the plugin folder out of ProjectName\\Plugins, then try opening the project again.

Isolate A Bad Asset

If the crash happens at the same percentage each time, or right after loading a named package, the issue can be one asset. Move suspect assets out in small batches to find the one that triggers the crash.

  1. Start With Recent Imports – Move the last imported folder out of Content, then test load.
  2. Repeat In Small Batches – Keep splitting until you find the specific file that breaks the load.

When The Crash Still Wins

If you’ve worked through graphics, files, and project caches and the crash still shows up, don’t keep changing random settings. Switch to gathering clean evidence and testing one controlled variable at a time. That approach ends the loop of reinstalling and hoping.

Try A Fresh Windows User Profile

User profiles can carry broken permissions and corrupted app data that survive reinstalls. A new Windows user profile is a quick way to test whether the crash is tied to your profile.

  • Create A New Local User – Sign into the new user and launch the game or editor once.
  • Compare Results – If it works there, the issue is likely in your AppData or Documents UE4 folders.

Reinstall With A Clean Folder

Reinstalling helps only when you remove the pieces that the installer would otherwise reuse. If you reinstall, also rename leftover folders in AppData so the next start builds fresh config and cache files.

  1. Uninstall The App – Uninstall the game or engine from Epic Games Launcher or Windows.
  2. Remove Leftover Folders – Rename any remaining game folder and the related folders under AppData\\Local.
  3. Install Fresh – Install again, then launch once before adding mods, plugins, overlays, or custom configs.

Send A Crash Package To The Publisher

When you reach the point where logs point to a game-specific module, the publisher may need the crash bundle to confirm a known bug. Provide clean details so you don’t go back and forth for days.

  • Include The Log And Crash Folder – Attach the newest .log and the latest folder from Saved\\Crashes.
  • List What You Tried – Mention driver change, overlay disable, verify, and cache clear so they can skip repeats.

If you see the crash again after fixes, capture the newest log right away. A new crash signature can appear after the first one is removed. If your crash message is still the same, the line that changes is the one that matters. You may still call it the \”an unreal process has crashed ue4\” error, yet your next move should be based on the new log.