Call of Duty Error 0xE06D7363 (KERNELBASE.dll) Crash on Startup? Every Working Fix for Black Ops 7 & Warzone (2026)

Quick answer (TLDR): Error 0xE06D7363 with a KERNELBASE.dll fault is a Windows C++ exception crash — the game throws an unhandled error at launch and closes instantly, usually before you reach the menu. It hits Black Ops 7, Warzone and Black Ops 6 because they share the same engine and `cod.exe`. The single fix landing for the most people right now is adding an Exploit Protection exception for `cod.exe` and turning OFF Control Flow Guard (CFG) — a Windows 11 memory-protection feature that blocks the game even on high-end rigs. If you're on the Xbox App / Game Pass build and get "Access Denied" adding the file, use the "Add program by name" trick (type `cod.exe`) below. Then run Scan and Repair, update your GPU driver with a clean install, and repair Visual C++. Work the checklist top to bottom.

If Call of Duty flashes on screen for a second and dies to error `0xE06D7363` — often naming `KERNELBASE.dll` as the faulting module in Event Viewer — you're looking at one of the most common PC crashes in the franchise, and it's almost never your hardware failing. Fresh reports are stacking up across r/CODWarzone, r/blackops7 and r/CallOfDuty this week, with players describing the exact same behaviour: click Play, the game opens for one second, then closes with no menu, no error box, or a bare `0xE06D7363` code.

Here's the important part: `0xE06D7363` is a generic Windows code, not a Call of Duty-specific one. That's why the same crash shows up in Excel, VEGAS and dozens of other apps. Decoded, it means a C++ EH (exception handling) exception was raised through `KERNELBASE.dll` — the Windows system library that hosts `RaiseException`. In plain terms: the game tried to do something Windows wasn't willing to allow, and instead of handling it, the whole process died. Below is the exact order to fix it on PC, fact-checked against Activision's own Crashes or Game Freezes in Black Ops 7 guidance and the fixes players are confirming right now.

What is error 0xE06D7363 / KERNELBASE.dll in Call of Duty?

`0xE06D7363` is the hexadecimal Windows code for a C++ exception (`E06D7363` even spells out "msc" — the Microsoft C++ compiler signature — in ASCII). When you see it paired with KERNELBASE.dll in Windows Event Viewer, it means the crash was funnelled through the OS's core kernel API, which is where `RaiseException` lives. It is a symptom, not a root cause — so the goal is to work out which thing on your PC is tripping the exception.

For Call of Duty specifically, three culprits cause the overwhelming majority of `0xE06D7363` / KERNELBASE crashes:

• Windows 11 "Control Flow Guard" (CFG) blocking the game's memory access. This is the #1 fix right now, and it's why brand-new, high-end PCs crash while older ones don't.
• Corrupted or mismatched game files after an update — a partial patch, a bad shader cache, or a file the launcher never finished writing.
• A broken graphics-driver or Visual C++ runtime state — an old, beta, or overclock-unstable GPU driver, or a damaged VC++ redistributable the game depends on.

The crash spans titles because Black Ops 7, Warzone and Black Ops 6 all launch through the shared `cod.exe` and the same engine layer. If one throws `0xE06D7363`, the others usually do too on the same machine. Fix it once and all three stop. If your crash instead names a different fault — like a DirectX Unrecoverable Error or "All Graphics Adapters Failed to Initialize" — those have their own dedicated fixes.

Fix 1: Add a Control Flow Guard (CFG) exception for cod.exe

This is the fix landing for the most people, and it targets the exact cause the community traced: Windows 11's Exploit Protection ("Control Flow Guard") blocks the game's memory calls, which throws the C++ exception. A widely-upvoted fix thread on the Steam Call of Duty forums put it plainly:

"The problem often seems to be caused by a Windows 11 security feature that blocks the game's access to memory ('Control Flow Guard'). Even on high-end systems, this leads to random crashes."

Here's how to whitelist the game:

• Press the Windows key, type Exploit Protection, and open it.
• Click the Program settings tab at the top.
• Click + Add program to customize → Choose exact file path.
• Navigate to your CoD install folder (often under `Call of Duty` on Steam/Battle.net, or `XboxGames` on Game Pass), select `cod.exe`, and click Open.
• Scroll down to Control Flow Guard (CFG), tick Override system settings, and switch it OFF.
• Click Apply, then restart your PC and launch the game.

Xbox App / Game Pass "Access Denied" workaround: the Microsoft Store build stores the game in a locked folder, so Windows often won't let you select `cod.exe` directly — even as admin. Instead:

• In Exploit Protection → Program settings, click + Add program to customize.
• Choose Add program by name (not by file path).
• Type exactly `cod.exe` and click Add.
• Now open its settings, override and turn CFG OFF, Apply, and reboot.

That name-based method sidesteps the permission block entirely and is why so many Game Pass players were stuck until they found it.

Fix 2: Scan and Repair (or Verify Integrity) your game files

A partial or corrupted update is the second most common trigger, and Activision's own troubleshooting leads with a file repair. This rebuilds any file the exception is choking on:

• Battle.net: open the launcher, go to the Call of Duty tab, click the cogwheel next to Play, choose Scan and Repair → Begin Scan, and let it finish.
• Steam: right-click Call of Duty in your Library → Properties → Installed Files → Verify integrity of game files.

If the scan reports a `0x1`, `0xfffffffe` or similar `0x` error partway through, Activision recommends running the Windows app Repair: open Settings → Apps → Installed Apps → Call of Duty → Advanced Options → Terminate, then Repair. Reinstall only if the error survives the repair.

Fix 3: Clean-install your graphics driver

An outdated, beta, or corrupt GPU driver is a classic `0xE06D7363` cause because the game raises the exception the moment it hands work to a bad driver.

• Download the latest stable driver — NVIDIA or AMD — for your exact card.
• Choose the Custom (Advanced) install and tick Perform a clean installation (NVIDIA) so it wipes the old state. For a deeper reset, run DDU (Display Driver Uninstaller) in Safe Mode first, then install fresh.
• Reboot and relaunch.

Avoid brand-new "Game Ready" drivers that released in the last day or two if your crash started right after a driver update — roll back one version, since a bad driver day can itself throw KERNELBASE crashes.

Fix 4: Repair Visual C++ and update DirectX

Call of Duty depends on the Microsoft Visual C++ Redistributables and DirectX. A damaged VC++ runtime is a direct path to a C++ exception like `0xE06D7363`.

• Open Settings → Apps → Installed Apps, find every Microsoft Visual C++ Redistributable (2015–2022, x64 and x86), choose Modify → Repair on each. If Repair fails, download the latest VC++ redistributable from Microsoft and reinstall.
• Make sure Windows is fully updated (Settings → Windows Update), which also refreshes DirectX components.

Fix 5: Run SFC and DISM to repair Windows

Because the fault module is `KERNELBASE.dll` — a Windows system file — corrupted OS files can be the real cause. Repair them:

• Open Command Prompt as Administrator.
• Run `sfc /scannow` and let it complete.
• Then run `DISM /Online /Cleanup-Image /RestoreHealth`.
• Reboot and test.

Multiple support threads report SFC finding and fixing corrupt files that were behind the crash.

Fix 6: Disable overclocks and close overlays

If your RAM or GPU is even slightly unstable, the game is the first thing to expose it as a crash:

• Turn off GPU overclocks (MSI Afterburner) and set memory to defaults. Some players fix it by underclocking VRAM slightly (−100 to −200 MHz).
• Disable XMP/EXPO in BIOS temporarily to test whether an aggressive RAM profile is the trigger.
• Close overlays — Discord, GeForce Experience/NVIDIA App, Steam, Xbox Game Bar, MSI Afterburner/RivaTuner, and any FPS counter. Overlay hooks are a frequent KERNELBASE offender.
• Run the launcher as Administrator and add exclusions for `cod.exe` in your antivirus/Windows Defender.

Fix 7: Swap platforms or reinstall as a last resort

If nothing above works, the file state itself is likely broken:

• Try the other platform. Several players who couldn't launch on Battle.net installed Warzone free from Steam (or vice versa) and the crash vanished. It's free, so it's a fast test.
• Reinstall clean. Fully uninstall, delete any leftover `Call of Duty` folder, and reinstall. This is the nuclear option Activision suggests only after Windows Repair fails.

Is 0xE06D7363 an Activision-side bug or my PC?

Sometimes it's on Activision's end. After a bad patch, players have seen the crash clear on its own once a small hotfix (one report noted a ~10 MB update) went live. Before spending an hour troubleshooting, check the official Known Issues in Black Ops 7 page and the @CallofDuty / @CODUpdates feeds — if a launch-day crash is server-side, a fix is usually deployed within a day. If your friends crash too, wait for the hotfix; if it's only you, work the checklist.

If your game doesn't hard-crash but instead shows a black screen on launch, gets kicked by Memory Error 968053563-0, or runs but lags and stutters mid-match, those are separate issues with their own step-by-step guides.

The fastest way back into the grind

Fixing the crash is step one — but if `0xE06D7363` cost you days of playtime while everyone else levelled up, the gap is real. Whether it's weapon levels, camo challenges, or a Warzone rank you've fallen behind on, you don't have to grind it all back solo.

Skip the catch-up grind once your game is stable again:

- CoD Account & Weapon Leveling — max your guns and account level fast, done by pro players.

- CoD Camo Unlocks (BO7) — mastery camos unlocked for you, fast and secure.

- CoD Warzone Bot Lobbies — easy lobbies to farm XP and challenges without the sweat.

- All Call of Duty services →

FAQ

What does error 0xE06D7363 mean in Call of Duty? It's the Windows hex code for a C++ exception (the code literally spells "msc", Microsoft's C++ signature). Paired with KERNELBASE.dll, it means the game raised an unhandled error through Windows' core system library and the process crashed. It's a symptom that can be caused by Control Flow Guard, corrupted files, a bad GPU driver, or a broken Visual C++ runtime — not a single specific bug.

Why does 0xE06D7363 crash Black Ops 7, Warzone and BO6 at the same time? All three launch through the shared `cod.exe` and the same engine, so a machine-level cause — like Windows 11's Control Flow Guard blocking `cod.exe` — trips the identical crash across every Call of Duty title on your account. Fixing it once (usually the CFG exception in Fix 1) stops all of them.

What's the number-one fix for the KERNELBASE.dll crash? Add an Exploit Protection exception for `cod.exe` and turn Control Flow Guard (CFG) OFF (Fix 1). It's the community's most-confirmed solution, especially on Windows 11 and high-end PCs. On the Xbox App/Game Pass build, use the "Add program by name" method to get around the "Access Denied" message.

I'm on Game Pass and get "Access Denied" when adding cod.exe — what do I do? The Microsoft Store folder is locked, so don't browse to the file. In Exploit Protection → Program settings, choose Add program by name, type `cod.exe` exactly, add it, then override and disable CFG. That bypasses the permission block completely.

Is 0xE06D7363 caused by my hardware? Rarely. It's almost always a software conflict — Control Flow Guard, a corrupt update, driver or Visual C++ state. The only hardware angle is instability from overclocking (GPU or an aggressive XMP/EXPO RAM profile); reset those to stock to rule it out (Fix 6). If a hotfix later clears it with no changes on your side, it was server-side all along.