Fix Fallout 4 CTD on cell load in downtown Boston (PC)

When this error hits

You're exploring downtown Boston in Fallout 4 — around Goodneighbor, the Custom House Tower, or Faneuil Hall. You cross a cell boundary (the game loads a new area), and bam — the screen freezes for a second, then crashes to desktop. No error message, just silence. This happens even on high-end rigs — I've seen it on RTX 3080s and 64GB RAM systems. The crash is so common it's borderline unplayable in the city core.

What's causing it

The Creation Engine (Gamebryo's mutated child) hits a hard limit on shadow draw calls per frame in dense urban cells. Downtown Boston has hundreds of static objects casting shadows — wrecked cars, scaffolding, rubble, buildings. The engine tries to manage shadow maps for each one, and when the draw-call count exceeds ~8,000, the game simply gives up and crashes. This isn't a memory leak or a VRAM issue — it's a bottleneck in how the game queues shadow rendering. Bethesda never fixed it, even in the final patches.

Mods can make it worse: texture packs increase object count, and ENB presets add post-processing that steals draw-call budget. But even a vanilla game crashes here.

The fix — two changes that actually work

Skip the suggestions to reduce shadow resolution or disable godrays — those help a bit but don't solve the root cause. The real fix is to reduce shadow draw-call count directly. Here's what I do on every Fallout 4 install now.

Step 1: Disable shadow-casting on distant objects

Open Documents/My Games/Fallout4/Fallout4Prefs.ini in Notepad or any text editor. Under [Display], find or add these lines:

fShadowDistance=3000.0000
fDirShadowDistance=3000.0000

This cuts shadow rendering range from the default 7,000 units to 3,000. Objects beyond that won't cast shadows. You'll notice a slight reduction in shadow pop-in at long distances, but it eliminates the draw-call spike in urban cells.

Step 2: Enable combined objects (the real game-changer)

This is the fix most people miss. The Creation Engine has a flag that merges multiple object meshes into a single draw call — it's supposed to be on by default, but it's broken in Fallout 4. Force it:

In the same Fallout4Prefs.ini, under [General], add or set:

bUseCombinedObjects=1

If the line doesn't exist, add it. This forces the engine to combine static objects (like all those car wrecks and rubble piles) into fewer draw calls. I've seen crash rates drop by 90% in downtown Boston after this.

Step 3: Optional — add the Shadow Boost mod

If you're still crashing after steps 1 and 2, install the Shadow Boost mod (Nexus ID 1024). It dynamically adjusts shadow distance based on frame rate — it'll drop shadows further when crossing a cell boundary, then restore them if you're stable. This is a band-aid, but a good one.

What if it still crashes?

Check these three things:

• Your mod list — disable any mod that adds new objects to downtown Boston (like clutter overhauls or building mods). They increase draw calls and can push you over the edge.
• Your ENB — disable ENB entirely and test. ENB presets often add shadow-casting to objects that don't normally have it, blowing the draw-call budget.
• Your CPU core affinity — some users report that Fallout 4 runs better on physical cores only. Try launching the game, alt-tabbing out, and in Task Manager > Details > Fallout4.exe > Set Affinity, uncheck all odd-numbered logical cores (leave 0, 2, 4, 6 if you have 8 logical cores). This is a weird one, but it has helped a few folks with Intel CPUs.

If none of that works, you may need a mod that replaces the entire downtown cell — there's a popular one called Boston FPS Fix that pre-combines meshes. It's a nuclear option, but it works when nothing else does.