Modern Warfare 4 Campaign Won't Launch or Keeps Crashing? Every Early-Access Fix (October 16, 2026)

Modern Warfare 4's campaign early access went live on October 16, 2026 — and within hours players were posting the same wall of problems every Call of Duty launch brings: the game refusing to launch, hard crashes to desktop the moment a mission loads, black screens in cutscenes, and the dreaded `KERNELBASE.dll` / `0x00001338` crash handler. If you paid for early access specifically to play the story a week before the October 23 full launch, "wait for a patch" is not an answer. This guide walks every confirmed early-access issue, the exact fix in the order that works, and the one PC setting that keeps the crashes from coming back.

Key Takeaways (TL;DR)

• Most early-access crashes are shader/driver-side, not your account. The campaign is single-player, so "won't launch" or "crashes on load" is almost always a local file, driver, or display-mode problem — not a server or entitlement issue.
• On PC, verify game files first. Verifying the integrity of your install on Steam or Battle.net fixes the single most common "campaign crashing / won't launch" case, because the early-access download frequently finishes with a corrupted or missing shader file.
• The `KERNELBASE.dll` / `0x00001338` crash is a known, recurring Call of Duty crash tied to a broken shader cache — delete the shader cache and let it rebuild, don't reinstall 119 GB.
• Borderless Windowed + HDR off stops most mid-mission crashes to desktop. Exclusive Fullscreen plus HDR or an overlay is the most common display-driver crash trigger on PC.
• Console players: rebuild, don't reinstall first. A PS5 database rebuild in Safe Mode and an Xbox cache clear fix most console boot failures in two minutes — a full reinstall is the last resort, not the first.
• TPM 2.0 + Secure Boot are only required for online modes. The campaign is offline-capable, but Warzone and multiplayer (live October 23) will hard-gate you without them — enable them now.

Is the Modern Warfare 4 campaign actually playable right now?

Yes. As of October 16, 2026, the Modern Warfare 4 campaign is live in early access for anyone who digitally pre-ordered any edition — a full week before the October 23 worldwide launch that adds Multiplayer and (on the Warzone side) Season 1 (support.activision.com/mw4). DMZ opens in between, on October 20. So if the campaign won't start, you are not too early and your pre-order is almost certainly eligible — the problem is on the technical side, which is exactly what this guide fixes.

One important distinction up front: the campaign is single-player and offline-capable. That means a crash or "won't launch" is rarely a server outage or a matchmaking problem the way it is in Warzone — it's a local issue with files, drivers, display mode, or shaders. That's good news, because every one of those is something you can fix yourself in minutes.

Why does the Modern Warfare 4 campaign crash or refuse to launch?

Call of Duty's engine compiles a huge set of shaders — small GPU programs that render lighting, surfaces, and effects — the first time you run a new build. As Activision puts it in its own PC guide:

"Shaders are small programs that tell your graphics card — or GPU — how to optimally render what you see on screen, from surfaces and lighting to shadows, visual effects, and more... certain shaders need to be prepared for your specific PC before they can do their job." — Call of Duty official PC blog

That's exactly why Activision ships Shader Preloading to prepare them before you hit the menu — because a bad or incomplete shader set is the number-one cause of launch crashes (callofduty.com). When an early-access download finishes with a corrupted shader or config file, the result is a game that either won't boot at all or crashes the instant the first mission loads.

The pattern is consistent across the launch reports. One PC player on an RX 7600 XT described it exactly: the CoD HQ menu loads fine and is fully navigable, but the game crashes the moment the actual mode loads — and a full 119 GB clean reinstall didn't help. That's the signature of a shader-cache or display-driver problem, not a corrupt install, which is why reinstalling alone so often fails. The fixes below target the real cause.

Fix 1 — Verify your game files (the 90-second fix that works most often)

Before anything else, verify the integrity of your install. This re-downloads only the corrupted or missing files — it does not mean redownloading the whole game.

• Steam: Right-click Call of Duty in your Library → Properties → Installed Files → Verify integrity of game files.
• Battle.net: Click Call of Duty → the gear icon next to Play → Scan and Repair.

If verification replaces even one file, launch again before trying anything else. A clean early-access download that finishes with a single bad shader or pak file is the most common "campaign won't launch" case, per the live launch-day reports (sportskeeda.com).

Fix 2 — Fix the KERNELBASE.dll / 0x00001338 crash (shader cache, backend, or CPU)

If you're getting a crash handler with error code `0x00001338` and a reference to `KERNELBASE.dll`, do not reinstall first — it almost never helps. This is a memory/file-execution exception with three documented causes, so work through them in order of how often they land:

A. Corrupted shader cache (most common). Clear it and let the game rebuild:

• Fully close the game and the launcher.
• Open Documents → Call of Duty → players.
• Delete the shader-cache files (the `s.1.0.*` cache set). You can safely delete the whole folder's cache contents; the game recreates them.
• Relaunch, let shader preloading rebuild (this can take a few minutes — that's expected), then re-apply your settings.

Players who hit this crash during "Connecting to Online Services" and on mode load have reported the game booting normally once the shaders rebuilt from scratch — especially if it only started after an update.

B. Backend / region routing. If the shader rebuild doesn't fix it — and particularly if you also see codes like `0x723AC2A5` — several players have traced the same crash to a backend or CDN routing issue on their region rather than their PC. In those reports, connecting through a VPN to a different region (or simply waiting out a server-side fix) resolved it when no hardware or Windows change did.

C. CPU instability (overclock / high-core-count chips). On some high-end CPUs (e.g. 13th/14th-gen Intel), the crash tracked back to an unstable boost clock. Lowering the P-core ratio by 1–2 multipliers in BIOS, or disabling an aggressive overclock, stopped it. A small game patch has also resolved it for some users with no change on their end — so update first if a new build is out.

Fix 3 — Switch to Borderless Windowed and turn off HDR (stops mid-mission crashes)

If the campaign launches but crashes to desktop mid-mission — often during a cutscene, an alt-tab, or a Windows notification — the culprit is usually Exclusive Fullscreen fighting the game's DirectX 12 implementation.

• In the game's graphics settings, set Display Mode: Borderless Windowed (not Exclusive Fullscreen).
• In Windows → System → Display, turn HDR off while you diagnose — HDR plus overlays is a well-known crash trigger on PC.
• Disable VRR tech (NVIDIA G-Sync / AMD FreeSync) temporarily; these can cause black-screen boots and cutscene crashes.

These three together resolve the majority of "it launches but keeps crashing" reports.

Fix 4 — Update (or clean-install) your GPU drivers

MW4 requires a DirectX 12-compatible system, and Activision publishes specific recommended driver builds. Match or beat these:

GPU vendor	Recommended driver
NVIDIA	610.47
AMD	26.7.1
Intel Arc	32.0.101.8861

Source: callofduty.com PC specs blog. If you're still crashing after a normal driver update, do a clean install — use the vendor installer's "clean install" option (or DDU in Safe Mode) to wipe leftover driver state that routinely causes launch crashes.

Fix 5 — Disable overlays and background apps

Steam overlay, AMD Adrenalin overlay, Discord overlay, RivaTuner/MSI Afterburner, and recording tools all hook the game and can cause instant crashes on load. Turn them all off, close background capture tools, and launch clean. Add them back one at a time only once the game is stable.

How do I fix the campaign not working on PS5 or Xbox?

Console early-access boot failures almost always clear without a reinstall. Start with the quick steps:

PlayStation 5:

• Fully close the game (don't just rest-mode it) and restart the PS5.
• Check for a console software update (Settings → System → System Software).
• If it still won't boot, rebuild the database in Safe Mode: power off the PS5 fully, hold the power button until you hear the second beep, connect your controller by USB, press the PS button, then select Rebuild Database.
• Only as a last resort, delete and reinstall the game (sportskeeda.com).

**Xbox Series X	S:**

• Restart the console and confirm both the game and the system firmware are fully updated (Settings → System).
• Clear the console cache (a full power cycle: hold the Xbox button 10 seconds, unplug for 30).
• Reinstall only if the above fails.

Avoid Rest Mode / Quick Resume for the first few sessions — resuming a half-loaded early-access build is a common cause of corrupted saves and boot hangs.

Do I need TPM 2.0 and Secure Boot for the campaign?

Not for the offline campaign — but yes for everything that comes next. Activision requires TPM 2.0 and Secure Boot enabled on PC to play MW4's online modes, because they anchor RICOCHET Anti-Cheat (callofduty.com). Multiplayer launches October 23 and Warzone's Season 1 lands the same day, so if either of those is disabled you'll be locked out even though the campaign ran fine. Enable them now so you're not scrambling on launch night — we have a full walkthrough in our Secure Boot / TPM error fix guide. You can also run Activision's Secure Attestation Wizard to confirm your PC passes before the 23rd.

Once it's running: skip the grind and jump straight into the action

Fixing the crash is step one — the next wall is the grind. MW4 gates camos, attachments, and ranks behind a long XP climb, and the launch-day lobbies are brutal while everyone resets. If you'd rather spend early access playing than grinding (or getting stomped by sweats on day one), our MW4 services get you there fast:

Done crashing and ready to actually play? Skip the slow climb and the launch-day sweat-fest with MW4 services built for day one:

• MW4 Bot Lobbies — private easy lobbies from $5.90, the fastest safe way to grind levels and camos without SBMM hell
• MW4 Weapon Leveling — max any gun and unlock every attachment, done for you
• MW4 Account Leveling — skip the rank grind with pro players
• All MW4 services — the full launch-ready lineup

Still stuck? Check these before you panic

If none of the above works, confirm it's not a wider outage or a known day-one bug rather than your PC:

• Check server/status — even though the campaign is offline-capable, the launcher and entitlement check can hang during a surge. See our MW4 server status guide.
• Compare against the full launch-day error list — if your error isn't a campaign crash specifically, our launch-day errors & fixes roundup covers connection and multiplayer codes too.
• Stutter, not crashing? That's a different problem with a different fix — see MW4 stutter & FPS drops fixes.
• Not sure you even have early access? Confirm eligibility in our how to play the campaign early guide.

FAQ

Why won't the Modern Warfare 4 campaign launch even though I pre-ordered? A valid early-access pre-order rarely causes a launch failure on its own — the campaign is single-player, so "won't launch" is almost always a local file or driver issue. Verify your game files first (Steam: Properties → Installed Files → Verify; Battle.net: Scan and Repair), then update your GPU drivers. If the launcher itself hangs during the entitlement check, that's a surge issue, not an eligibility one — wait a few minutes and retry.

How do I fix the KERNELBASE.dll / 0x00001338 crash in Modern Warfare 4? This is a corrupted shader cache, not a broken install. Close the game, go to Documents → Call of Duty → players, delete the shader-cache files, then relaunch and let shader preloading rebuild them. A full reinstall usually doesn't fix this crash, so try the shader-cache delete first.

The campaign crashes to desktop mid-mission — what causes that? Mid-mission crashes to desktop are usually Exclusive Fullscreen conflicting with DirectX 12, often combined with HDR or an overlay. Switch Display Mode to Borderless Windowed, turn HDR off in Windows, disable G-Sync/FreeSync, and close Steam/Discord/AMD overlays. That combination resolves most of them.

How do I fix the campaign not working on PS5? Fully close the game and restart the PS5, then check for a system software update. If it still won't boot, rebuild the database in Safe Mode (hold power until the second beep, connect the controller by USB, choose Rebuild Database). Reinstalling the game is the last resort, not the first step.

Do I need Secure Boot and TPM 2.0 to play the campaign? Not for the offline campaign, but yes for online play. Activision requires TPM 2.0 and Secure Boot for MW4's online modes to support RICOCHET Anti-Cheat, so Multiplayer (October 23) and Warzone will lock you out without them. Enable both now so you're ready for the full launch.

Will my campaign crashes also affect multiplayer on October 23? Not necessarily — a shader-cache or display-mode fix carries over and helps, but multiplayer and Warzone add online requirements the campaign doesn't have (TPM 2.0, Secure Boot, server connectivity). Prep those before launch day so you load in clean.