Enshrouded 1.0 has introduced several different crash patterns, including failures during shader compilation, crashes at the main menu or character creator, MiniDump errors, and seemingly random crashes after loading into a world. Because those problems do not all share the same cause, the best approach is to identify when the crash happens and work through the fixes that actually match it.

Jump To Section:
How to Fix Enshrouded 1.0 Crashing
Verify Game Files
Reset Enshrouded Settings
Crashing While Compiling Shaders
Disable Overlays and GPU Tools
Clean Install GPU Drivers
Fix MiniDump Crashes
Crashing on One Character or World
If Enshrouded Still Crashes

How to Fix Enshrouded 1.0 Crashing

Start by making sure Enshrouded is completely updated before changing anything on your PC. Hotfix 1.0.0.1 addressed multiple random crashes and crashes caused by certain peripherals, while Hotfix 1.0.0.2 added fixes for more random crashes, save migration, fast travel and glider landings in entity-heavy worlds, water simulation, Adventure Sharing, full backpacks, and several other specific situations.

If Steam has already installed the latest version and you are still crashing, restart Steam and your PC, verify the game files, then reset the game's local settings file. Those three steps deal with update corruption and incompatible settings without touching your characters or worlds.

After that, the correct next step depends on where Enshrouded is failing. Shader compilation crashes point more strongly toward drivers, system stability, or software interacting with the GPU, while crashes after reaching the menu can often be narrowed down through the configuration file and overlays.

Verify Enshrouded Game Files First

Open Steam, right-click Enshrouded, select Properties, open Installed Files, and run Verify integrity of game files.

This should be one of the first fixes after a major update because it gives Steam a chance to replace files that were damaged, interrupted, or left inconsistent during the 1.0 update process.

Once verification finishes, restart Steam before testing the game again. Do not immediately move on to several other fixes at once. Launch Enshrouded after each change so you know which step actually solved the crash.

Reset Enshrouded's Local Settings

If verification does not work, the next useful test is forcing Enshrouded to generate a fresh local configuration.

Go to your Enshrouded installation directory and find:

File: enshrouded_local.json
Typical Folder: Steam\steamapps\common\Enshrouded\

Rename the file instead of deleting it. For example, change it to enshrouded_local_backup.json, then launch the game again.

Enshrouded will no longer see the original configuration and can create a new one. This resets your in-game settings, including graphics options, but it does not delete your normal character or world saves.

This is particularly worth trying if Enshrouded reaches shader compilation successfully but then crashes at the main menu, during character creation, or shortly after loading.

Fix Crashing While Compiling Shaders

A crash during shader compilation deserves a different troubleshooting path than a random crash several hours into a world.

First, let shader compilation finish without launching into the game early. Enshrouded uses Vulkan, and shader compilation can put substantial load on the system. If the game consistently crashes at roughly the same percentage, start looking at the graphics driver and anything modifying GPU or CPU behavior.

Return any GPU or CPU overclock to stock settings while testing. The same applies to undervolts. A configuration that appears stable in other games can still fail during a heavy compilation workload, so stock settings give you a useful baseline.

If you have MSI Afterburner, RivaTuner, ASUS GPU Tweak, or similar tuning software running, close it completely before starting Enshrouded. Then restart the game and allow shader compilation to run again.

Players using 13th- or 14th-generation Intel desktop CPUs should also make sure the motherboard BIOS and Intel microcode are current. Enshrouded has previously required specific crash fixes for those processors, and shader compilation is exactly the kind of heavy CPU workload that can expose an unstable system configuration.

Disable Overlays and Background GPU Tools

If the crash persists, reduce the number of programs hooking into the game while you test it.

Turn off the Steam Overlay for Enshrouded and temporarily disable overlays from Discord and the NVIDIA app. Close OBS if you are not actively using it, along with monitoring, frame-limiting, overclocking, and performance-overlay software.

MSI Afterburner and RivaTuner deserve particular attention if the problem appeared with 1.0. Enshrouded runs through Vulkan, so eliminating programs that inject overlays or manipulate frame presentation is a useful diagnostic step.

You do not need to uninstall everything on the PC. Close the likely candidates, test the game, and re-enable them individually once Enshrouded is stable. That makes it possible to identify an actual conflict rather than permanently disabling unrelated software.

Clean Install Your GPU Driver

If Enshrouded still crashes after verifying files and resetting its configuration, move to the graphics driver.

A normal driver update does not always remove damaged or conflicting parts of the previous installation. A clean installation is more useful when diagnosing Vulkan crashes, especially when the problem begins during shader compilation or the crash log reports a lost graphics device.

Install the current stable driver for your NVIDIA, AMD, or Intel GPU. If you recently updated the driver and Enshrouded only started crashing afterward, testing the previous stable driver is also reasonable.

For persistent MiniDump or shader crashes, a full driver cleanup with DDU followed by a fresh driver installation is the more thorough option. Restart Windows after the installation before launching Enshrouded again.

Do not waste time adding -dx11 or -dx12 to the Steam launch options. Enshrouded uses Vulkan, so generic troubleshooting advice about forcing DirectX does not address the renderer the game is actually using.

How to Fix Enshrouded MiniDump Crashes

A MiniDump message does not identify one specific failure. It is a crash report, which means two players seeing the same MiniDump message can still have completely different underlying problems.

The most useful MiniDump troubleshooting order is therefore:

1. Update Enshrouded to the latest hotfix.
2. Verify the game files through Steam.
3. Rename enshrouded_local.json and test with fresh settings.
4. Close overlays, tuning software, and overclocking tools.
5. Clean reinstall the GPU driver.
6. Test again before changing anything else.

There is also a community-developed Enshrouded Tool Fix that has been used specifically for recurring MiniDump and startup problems. It is better treated as a targeted troubleshooting option after the basic Steam and configuration fixes rather than the first thing you run.

If a MiniDump continues after the entire sequence, check temperatures and system stability as well. A GPU, CPU, or memory problem can surface under Enshrouded even when lighter workloads appear normal.

If Enshrouded Crashes on One Character or World

If the game reaches the menu normally but crashes only when loading a particular character or world, do not immediately delete or rename your entire save directory.

Hotfix 1.0.0.2 specifically addressed a crash during save migration when Enshrouded attempted to load a corrupted character save. The current version can avoid migrating those damaged characters while the developers work on recovering them, which means a character temporarily disappearing from the list can be part of that issue rather than evidence that you should delete the save manually.

The same hotfix also addressed crashes connected to worlds containing large numbers of entities, including crashes while fast traveling or landing with the glider. Water simulation and Adventure Sharing received additional crash fixes as well.

For that reason, update the game before troubleshooting a world-specific crash and preserve a backup of your save data before making any manual changes.

What to Do If Enshrouded 1.0 Still Crashes

If none of the earlier fixes work, strip the PC down to a diagnostic baseline. Disconnect unnecessary USB devices, controllers, wheels, adapters, and other peripherals, close nonessential background programs, return all overclocks and undervolts to default, and test again.

This is particularly relevant to 1.0 because the first post-launch hotfix specifically fixed crashes caused by certain peripherals. If removing one device suddenly stops the crashing, reconnect devices individually until the trigger is identified.

Only after those tests should you consider heavier steps such as reinstalling Enshrouded to another SSD, updating motherboard firmware, or performing deeper Windows troubleshooting.

Avoid deleting your entire Steam userdata or Enshrouded save folder as an early fix. That creates far more risk than verifying files or regenerating enshrouded_local.json and tells you much less about the actual cause of the crash.

The useful dividing line is where Enshrouded fails. Crashes during shader compilation should push you toward drivers, stock clock settings, and GPU-related background software. Crashes at the menu or character creation make the local configuration worth resetting. Crashes tied to one character or world should be treated as save-specific until proven otherwise. Working from the crash stage instead of applying every generic Windows fix is the fastest way to narrow down what 1.0 is actually having trouble with.

Guides