Fallout 4 — Common Errors & How to Fix Them
When a Fallout 4 error is fixable and when it is grounds for a refund.
Last updated 2026-09-25 · evergreen reference
Most Fallout 4 errors are fixable in under an hour. This page tells you which ones are, and which ones mean you should stop troubleshooting and ask the store for a refund instead.
Errors, causes and fixes
Start from the symptom that matches yours.
Crashes on modern NVIDIA cards (weapon debris)
What is happening: Weapon Debris uses NVIDIA PhysX-based particle simulation and is associated with crashes on many modern GeForce systems.
Fix: Turn Weapon Debris off. It is the single highest-value stability change in the graphics menu.
Crashes in downtown Boston
What is happening: The area is the densest worldspace in the game; broken PreVis/PreCombine data from mods makes it worse. Symptoms include flickering objects, buildings disappearing and the world blinking.
Fix: Confirm a PreVis problem by setting bPreCulledObjectsEnabled=0 and bUseCombinedObjects=0 in Fallout4.ini — if the flickering stops, a mod is breaking PreCombine data. Boston FPS Fix or PRP must load after the Unofficial Patch but before worldspace mods.
Crash at the main menu
What is happening: A mod’s load order, a missing master file, or a corrupted texture.
Fix: Disable all mods and test. The Unofficial Fallout 4 Patch should sit near the top of the load order.
Everything broke after the next-gen update
What is happening: The next-gen update invalidated a large number of previously stable mods; not all have been patched.
Fix: Either wait for compatibility patches or downgrade to 1.10.163 with a downgrade patcher, which remains the stable baseline most modding guides target.
Launch crash before the menu
What is happening: Missing Visual C++ or legacy DirectX components.
Fix: Install Visual C++ 2015-2022 (x64 and x86) and the DirectX End-User Runtime, then restart.
The order to work in
Cheapest and most reversible first.
1. Rule out the universal causes
Verify game files, update the GPU driver with a clean install, and close overlays, recorders and RGB utilities. Across every engine, these three resolve the largest share of crashes before you touch anything game-specific.
2. Match the fix to the symptom
A crash that happens in the same place every time in Fallout 4 is usually asset or configuration damage — a cache, a config file or a mod. A crash that happens at random intervals is far more often a driver, an overlay, thermals or unstable memory tuning.
3. Change one thing, then retest
Load the same save, visit the same area and repeat the same action. If you change five settings at once you will never learn which one mattered, and you will end up reinstalling a game that did not need it.
When to stop fixing and ask for a refund
Troubleshooting has a deadline.
Store windows are short
Steam refunds within 14 days of purchase and under 2 hours of playtime, though documented technical faults can sometimes be accepted past that. Microsoft Store and Epic follow similar 14-day or 2-hour rules with their own exception paths.
Evidence changes the outcome
A denied refund can sometimes be overturned if you attach crash logs, a DxDiag and the steps you already tried. Contact store support with the evidence rather than filing a bare request.
Account actions are not refundable
If the failure is a ban from online cheating or a modified client, no store will refund it. That category is separate from a game that simply will not run.
Related pages
This is an independent player reference and is not official documentation for Fallout 4. GameFixPro does not host or link to copyrighted assets. Modding guidance is for single-player use only — never use mods in online multiplayer. Verify current requirements, prices and policies with the publisher before acting.