ThisCalculator

Everyday

The Outer Worlds Crashing? Fixes for PC & Console

Updated · Standard formula, shown below

If The Outer Worlds is crashing on your PC or console, you are not alone, and most crashes can be fixed by updating drivers, verifying game files, or adjusting a few in-game settings. This guide covers the most common crash causes and the step-by-step fixes that resolve them, from launch failures to mid-game freezes.

Why The Outer Worlds Crashes

The Outer Worlds is a demanding open-world RPG built on Unreal Engine 4. Crashes typically stem from one of four sources: outdated graphics drivers, corrupted game files, overheating hardware, or a conflict with overlays and background apps. On consoles, crashes are rarer but can occur due to a full cache or a corrupted save file.

Before You Start: Basic Checks

Run through these quick checks first, as they resolve a large percentage of crashes:

  • Restart your PC or console completely.
  • Make sure your system meets the minimum requirements (Windows 10 64-bit, 8 GB RAM, GTX 660 or better).
  • Close background programs like Chrome, Discord, or RGB software that can eat memory.
  • Check for Windows updates and install them.

Fix 1: Update Your Graphics Drivers

Outdated GPU drivers are the #1 cause of crashes in The Outer Worlds. Both NVIDIA and AMD release game-ready drivers specifically for major titles. Go to the NVIDIA or AMD website, download the latest driver for your card, and install it. After installing, restart your PC. If you have an older card, consider doing a clean install (using the “Custom” option in NVIDIA’s installer) to remove any leftover driver files.

Fix 2: Verify Game Files

Corrupted or incomplete game files will cause crashes at launch or during play. The verification process checks every file and re-downloads any that are broken.

  1. Open your game launcher (Steam, Epic, or Xbox app).
  2. Go to your Library.
  3. Right-click The Outer Worlds and select Properties.
  4. Go to the Local Files tab and click “Verify Integrity of Game Files.”
  5. Wait for the process to finish, then launch the game.

On Epic, the option is under Settings > Manage Games > Verify. On the Xbox app, it’s under the game’s “…” menu > Manage > Files.

Fix 3: Disable Overlays and Background Apps

Overlays from Discord, GeForce Experience, and even Steam can conflict with the game’s rendering and cause crashes. Disable them temporarily:

  • Discord: Settings > Overlay > Disable.
  • GeForce Experience: Settings > General > In-Game Overlay > Off.
  • Steam: Settings > In-Game > Disable Steam Overlay.

Also close any hardware-monitoring tools like MSI Afterburner or RivaTuner, as they can trigger anti-cheat or crash the engine.

Fix 4: Adjust In-Game Settings

If crashes happen during gameplay, especially in combat or when loading new areas, your settings may be too high for your hardware. Lower these in the game’s Options:

  • Set Shadow Quality to Medium or Low.
  • Disable Motion Blur and Depth of Field.
  • Turn Anti-Aliasing to FXAA or off.
  • Reduce View Distance to Medium.

Also try running the game in Windowed Fullscreen mode instead of Fullscreen—this fixes many alt-tab related crashes.

Fix 5: Clear Console Cache and Reinstall (for Xbox/PlayStation)

On consoles, crashes are less common but can happen. Try these steps:

  1. Clear the cache: Power off the console, unplug it for 30 seconds, then plug it back in and restart.
  2. Reinstall the game: Delete the game and re-download it. Your saves are stored in the cloud, so you won’t lose progress.
  3. Check for system updates: Go to Settings > System > Updates.

Fix 6: Check Overheating and Power Supply

If your PC crashes after 20-30 minutes of play, overheating is likely. Use a free tool like HWMonitor to check your GPU and CPU temperatures. If they exceed 85°C, clean your fans, improve airflow, or consider replacing thermal paste. Also ensure your power supply has enough wattage for your GPU—a failing PSU can cause random crashes under load.

Fix 7: Use the “-dx11” Launch Option (PC)

The Outer Worlds runs on DirectX 11 by default, but some players have found that forcing DirectX 11 explicitly fixes crashes on certain hardware. In Steam, right-click the game > Properties > Launch Options, and type -dx11. On Epic, you can add it to the game’s command line arguments in Settings. This is a known workaround for some AMD GPUs.

Frequently Asked Questions

Why does The Outer Worlds crash on startup?

Startup crashes are usually caused by outdated drivers, corrupted files, or a conflict with overlays. Update your GPU driver, verify game files, and disable Discord/Steam overlays. If it still crashes, try the -dx11 launch option.

Will lowering graphics settings stop the crashes?

Yes, lowering graphics settings can prevent crashes if your system is running out of VRAM or overheating. Focus on shadows, anti-aliasing, and view distance. If crashes persist, the issue may be elsewhere.

Does The Outer Worlds crash on Xbox Series X?

Some players report crashes on Xbox Series X, particularly on the “next-gen” update. Clearing the cache and reinstalling usually fixes it. If not, try playing the Xbox One version via backward compatibility, which is more stable.

Can a corrupted save file cause crashes?

Yes, a corrupted save can cause crashes when loading or saving. If you suspect this, back up your save files and try loading an earlier save. On PC, saves are in Documents\My Games\The Outer Worlds.

Is there a known fix for the “Out of Memory” crash?

This crash happens when the game runs out of RAM or VRAM. Close background apps, lower texture quality, and ensure your page file is set to “System Managed.” Adding more RAM may be necessary if you have only 8 GB.

How do I stop crashes when alt-tabbing?

Alt-tabbing can crash the game due to a fullscreen exclusive mode issue. Switch to Windowed Fullscreen in the game’s display settings. Also disable the Steam overlay, as it can interfere.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.