Why Does My Fallout 4 Keep Crashing? | Stops The Crash Loop

Fallout 4 can run for hours, then face-plant the second you step into a new cell, open the Pip-Boy, or save the game. That whiplash usually means one thing: the game tried to load an asset, setting, or script state that didn’t behave. The fix is rarely magic. It’s a short, repeatable test loop and a few targeted changes.

This article is written for PC players because PC stacks extra crash sources: mod managers, INI tweaks, overlays, driver features, and Windows permissions. If you play on console, skip to the save tips and the “one-hour plan” near the end.

What A Crash Is Telling You

A crash is Fallout 4’s blunt error message. The engine hit something it couldn’t recover from, so it bailed. That “something” is often one of these: a broken mesh, a texture call that fails, a script pileup, a driver feature the game can’t handle, or a save that grew heavy.

Right after a crash, jot down three details: where you were, what you did in the last 30 seconds, and whether a load screen just finished. That tiny note turns “random” into “repeatable.”

Why Does My Fallout 4 Keep Crashing? On PC: Common Triggers

These triggers show up across Windows 10 and 11, across old GPUs and new GPUs. Fix the base game first, then add your extras back in.

Mods That Clash Or Break Requirements

Mods can crash the game through missing requirements, bad load order, or two mods touching the same record in a way the engine can’t sort out. Script-heavy mods can crash on a delay, which makes them feel unpredictable.

If you installed a batch of mods, roll back. Disable everything optional, then re-enable in small batches. Keep the test loop the same each time.

Damaged Archives, Textures, Or Meshes

A bad texture can crash at the moment it’s called. A bad mesh can crash as an item loads into a cell. Corrupt archives can crash while streaming. These failures often repeat in the same spot, with the same weapon, enemy, or clutter piece.

Start with a repair pass in your launcher. On Steam, use its built-in file check. On other launchers, use their repair option.

Graphics Toggles That Trigger Driver Conflicts

Fallout 4’s graphics menu includes settings built for older hardware. One setting is a repeat offender on many modern Nvidia cards: Weapon Debris. Nvidia calls out that Weapon Debris can cause Fallout 4 to crash, and the recommended fix is simply turning it off: Nvidia’s Weapon Debris crash note.

If your crashes start a few minutes into a session, or spike during firefights, toggle Weapon Debris off, restart the game, and retest in the same area.

Overlays And Injectors

Steam overlay, Discord overlay, Windows Game Bar, recorders, FPS limiters, reshade tools — any of these can hook into DirectX. On a fragile setup, one hook is enough to tip the game over.

For a clean test, close them all, reboot, then run Fallout 4 with nothing riding on top. If stability returns, add overlays back one by one.

Missing Or Outdated Windows Runtimes

On some PCs, the game expects runtime files that aren’t present after a Windows refresh or drive swap. A safe baseline is installing the current Microsoft Visual C++ Redistributable package, then rebooting: Microsoft Visual C++ Redistributable latest supported downloads.

Make A Simple Repro Loop

Don’t change ten things at once. Pick one short loop and rerun it after each change. That’s how you learn what worked.

• Load the same save.
• Fast travel to the same busy area (Diamond City market works well).
• Enter a building, exit, start a short fight, loot, then quicksave.
• Play ten minutes and watch for stutter, audio glitches, or sudden exits to desktop.

If you can’t force a crash on demand, track “time to crash.” A jump from 5 minutes to 45 minutes is real progress.

Fix Order That Saves Time

This order starts with easy, reversible moves. Then it goes deeper only if it has to.

Step 1: Reset The Session

Restart Windows. Close overlays. Unplug extra controllers. Close heavy background apps. Then launch Fallout 4 and run your loop once.

Step 2: Drop To Safer Graphics

Lower your preset one notch. Turn off Weapon Debris. Turn off God Rays. If you run a high-refresh monitor, cap FPS to 60 for a test, using the driver control panel or a limiter you already trust.

Step 3: Repair The Game Files

Run your launcher’s file check. This catches missing files, partial downloads, and base files that were changed by accident. Retest right after the repair finishes.

Step 4: Run A No-Mods Test

Disable all mods and launch. If you use a mod manager, make a separate “vanilla test” profile. If the game is stable with no mods, your crash is almost certainly inside your mod stack or a mod-added asset.

Step 5: Add Mods Back In Batches

Re-enable a small group, run the loop, repeat. When the crash returns, you’ve found the group to narrow down. Now cut that group in half and retest. This “halve it” method is fast and keeps your sanity intact.

Step 6: Reset Your INI Files

INI edits can bite hard. Back up your Fallout4.ini and Fallout4Prefs.ini, delete the originals, then launch so the game regenerates fresh versions. Retest before you put any tweaks back.

Step 7: Clean Up Save Behavior

Rotate manual saves. Keep at least five. If crashes hit during saving, sleeping, or loading, try an older save and replay the last few minutes. If one save is cursed, don’t keep hammering it.

Crash Clues And First Moves

This table matches common crash patterns to the first move worth testing. It won’t catch every edge case, yet it narrows the field quickly.

Deeper Fixes When The Basics Don’t Work

If you still crash after a vanilla test and file repair, go after the next layer: clean installs, cleaner mod stacks, and Windows friction.

Do A Clean Reinstall That Leaves No Leftovers

A normal uninstall can leave modded files behind. Uninstall, then delete any remaining Fallout 4 folder in your install directory. Reinstall, launch once with no mods, and run your loop. That gives you a clean baseline.

Rebuild Mods In Layers

Add mods back in a steady order: bug fixes first, UI second, gameplay third, visuals last. Retest at each layer. If a mod needs a specific tool version like F4SE, match it to your Fallout 4 version.

Reduce VRAM And Downtown Pressure

Downtown Boston is a stress test. If crashes stack there, reduce texture resolution, lower shadow distance, and lower God Rays. If you run 1440p or 4K, try 1080p for a test. If stability returns, you were brushing into a limit.

Make Windows Stop Blocking Writes

If Windows blocks config writes, games can crash. Check that your Documents folder is writable and local. If you use OneDrive folder redirection, pause sync for a test. Also check antivirus history for quarantined game files.

Small Settings That Reduce Crash Odds

Once you’re close to stable, a few low-drama settings can keep things steady. These won’t fix a broken mod, yet they can smooth out the rough edges that trigger a crash during cell loads or quicksaves.

• Use borderless windowed mode if alt-tab crashes hit you.
• Turn autosave off if your crashes cluster around door loads, then rely on rotated manual saves.
• Keep God Rays off on midrange GPUs; it’s a common source of frame spikes in dense areas.
• Stick to one FPS limiter. Two limiters fighting each other can cause hitching.
• Avoid stacking multiple texture packs that hit the same assets. Pick one, test, then add more only if the loop stays clean.

After you change a setting, restart the game. Fallout 4 can cache behavior across a session, so a restart keeps your test honest.

One-Hour Plan You Can Run Tonight

Run this order once, without skipping steps:

1. Restart Windows, close overlays, launch once.
2. Turn off Weapon Debris, drop one preset, cap FPS to 60 for a test.
3. Repair files in your launcher.
4. Run the 10-minute loop.
5. Disable all mods and run the loop again.
6. Reset INIs and run the loop.
7. Install the latest Visual C++ runtime, reboot, run the loop.

After that hour, you’ll either be stable or you’ll have a clear suspect: a setting, an overlay, a mod group, or a messy install. That’s a win. Now you can fix the right thing instead of guessing.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback