Problem: Call of Duty: Warzone “Switching games” countdown → closes, or Battle.net/Steam says “Playing Now” but nothing launches (crash/failed handoff with no clear fix)

Published: 2026-01-16 13:10 (local time)

Quick Summary

Many PC players report Warzone (via COD HQ) closes right after the “switching games” countdown, or never fully launches while the launcher stays stuck on “Playing Now.”
It often comes with multiple crash-handler processes (e.g., bootstrapper / external crash handler) and no helpful error message.
Reports spike around recent Warzone/COD HQ updates and “integration” changes, with some players saying the issue appears/disappears without local changes.
There’s no single confirmed root cause; evidence points to conflicts with overlays/peripheral software, unstable RAM/CPU boost behavior, and corrupted install/shader caches.
Workarounds exist, but many involve tradeoffs (turning off XMP/EXPO, closing accessory apps, reinstalling components).

What’s happening

PC players attempting to launch Warzone (commonly through the Call of Duty “HQ” launcher flow) report a frustrating pattern: the game reaches a “switching games” countdown (for example when selecting Warzone from the HQ menu), then the game closes to desktop with no clear error; or Battle.net/Steam displays “Playing Now” while no game window appears. In Task Manager, multiple Call of Duty crash-handler processes may remain running, and the launcher may require manual process-killing to recover.

Recent community reports describe the issue recurring even when players don’t knowingly change drivers or settings, suggesting a server-side/content-side trigger (or an update-side interaction) rather than a purely local configuration problem. At the same time, other players find that specific local changes can immediately “fix” the symptom—pointing to conflicts and stability sensitivity rather than one universal defect.

Who’s affected: primarily PC users (Battle.net and Steam have both been mentioned), across a wide range of modern hardware. The symptom is especially painful because COD HQ relies on mode-handoffs/restarts; if the Warzone handoff fails, you can’t reach the mode at all.

Likely causes (what research suggests)

Conflicts with peripheral/overlay software (especially Razer Synapse): Multiple user reports indicate Warzone launches/crashes can be resolved by exiting Razer Synapse (or closing background Synapse processes). Similar “close Synapse to stop crashes” patterns are also seen in other major games, supporting the idea of a software conflict rather than pure hardware failure.
Memory/CPU stability edge cases (XMP/EXPO, aggressive boost): Some players report the problem disappears when DDR5 EXPO/XMP is disabled (running RAM at stock). Others report reducing Intel CPU multipliers slightly stops persistent Warzone instability. This suggests Warzone/COD HQ may be unusually sensitive to borderline-stable OC/boost behavior even if other games seem fine.
Corrupted content, shaders, or partial update state: Players describe cycles of “verify files” / “scan and repair” sometimes helping, sometimes not—consistent with broken caches, mismatched files, or a launcher update agent getting stuck.
Update/integration regressions: Community threads link the start of the issue to specific “integration” periods and recent changes; Activision also maintains a rolling “Known Issues” list, implying active tracking rather than a resolved, universal fix.

Solutions & Workarounds

1) Hard-close conflicting background apps (start with Razer Synapse + overlays)

Who it helps: PC players using Razer devices/software, heavy overlay stacks (RGB suites, performance overlays, macro tools).

Close the game and launcher.
Open Task Manager → end tasks for Razer Synapse processes (and optionally Razer Chroma-related processes).
Also temporarily exit other overlays: Discord overlay, GeForce/AMD overlays, MSI Afterburner/RTSS, recording tools.
Relaunch the launcher, then start Warzone again.

Risks/tradeoffs: You may lose RGB profiles, keybinds/macros, headset features while the software is closed.

Stop & contact support when: You can reproduce a clean launch failure even after disabling all accessory/overlay apps and rebooting.

2) Disable EXPO/XMP (run RAM at stock) and test

Who it helps: DDR5 users (EXPO/XMP enabled) seeing “switching games” close-outs or unexplained crash-handlers.

Reboot into BIOS/UEFI.
Set EXPO/XMP to Disabled (or “Auto/JEDEC”).
Boot Windows and try launching Warzone.
If it works, consider re-enabling at a lower profile or manually lowering RAM frequency/timings later.

Risks/tradeoffs: Performance can drop (sometimes noticeably in CPU-bound scenes). It’s a diagnostic step and a temporary workaround.

Stop & contact support when: You are uncomfortable changing BIOS settings, or your PC becomes unstable in other ways.

3) Reduce CPU boost aggressiveness (Intel 13th/14th gen especially) / remove OCs

Who it helps: Players who are stable in other games but crash repeatedly in Warzone/COD HQ.

Undo manual CPU overclocks first (BIOS “Load Optimized Defaults” is a simple test approach).
If you used tuning tools, try lowering the max multiplier by 1 step (example: 53x → 52x) and retest.
Re-test Warzone launch and a full match to confirm stability.

Risks/tradeoffs: Slight performance loss; changing CPU behavior can affect other workloads. Proceed cautiously.

Stop & contact support when: You don’t know your CPU settings, or you suspect a true hardware fault (unexpected reboots, WHEA errors, etc.).

4) Force a “clean-ish” repair: verify files + clear caches (without full Windows reinstall)

Who it helps: Players whose issue started after an update and who see inconsistent behavior between launches.

Reboot PC first (to clear stuck update agents and lingering crash handlers).
Battle.net: run “Scan and Repair.” Steam: “Verify integrity of game files.”
Let shader compilation complete once in-game; avoid alt-tabbing and overlays during the first rebuild.

Risks/tradeoffs: Time-consuming; sometimes does nothing if the conflict is external (Synapse/OC).

Stop & contact support when: Verify/repair repeatedly re-downloads large chunks or you cannot complete the process.

5) If Battle.net is stuck on “Playing Now,” kill the right processes and relaunch cleanly

Who it helps: Battle.net users stuck in a state where the launcher thinks COD is still running.

Open Task Manager → end “Call of Duty,” “bootstrapper.exe,” and crash-handler processes tied to COD.
Close Battle.net completely.
Reboot (best), then reopen Battle.net and try again.

Risks/tradeoffs: Ending tasks can interrupt updates or file operations; do not do this mid-patch if you can avoid it.

Stop & contact support when: The launcher re-enters the stuck state every time, even after reboots.

6) Check official “Known Issues” + open a ticket with reproducible details

Who it helps: Everyone—especially if your scenario matches a tracked item.

Review the current Warzone “Known Issues” list.
If matched, follow any official guidance and wait for updates.
If not matched, submit a support ticket including: launcher (Steam/Battle.net), exact symptoms, whether Synapse is installed, whether XMP/EXPO is enabled, and whether you see crash-handler processes.

Risks/tradeoffs: Support responses can be slow; you may be asked to do standard steps you’ve already tried.

Prevention (so it doesn’t come back)

Keep a “clean launch” profile: minimal startup apps, overlays off, accessory suites closed when playing competitive titles.
Avoid stacking multiple overlays at once (recording + performance overlay + RGB + chat overlay).
If you rely on EXPO/XMP, validate stability with memory testing and consider a slightly lower RAM frequency if Warzone remains sensitive.
After major updates, do one first launch without background utilities so shaders/content can settle.

FAQ

Q: Is this definitely a Warzone bug?
A: Not conclusively. Reports suggest update-related triggers, but many fixes involve local software conflicts (Synapse/overlays) or stability margins (EXPO/XMP, CPU boost), so it’s likely a mix.

Q: Why does Battle.net say “Playing Now” if nothing is open?
A: Crash/exit handoff can leave background COD processes running (bootstrapper/crash handlers). The launcher sees a process and assumes the game is still active.

Q: I shouldn’t have to disable EXPO/XMP—why does it help?
A: Some games are more sensitive to borderline memory stability than others. Disabling EXPO/XMP is a strong diagnostic step to confirm whether that sensitivity is involved.

Q: Do I need to reinstall Windows?
A: Usually no. Some players report it works, but it’s a last resort after testing conflicts (Synapse/overlays) and stability (EXPO/XMP/OC removal) first.

Q: If closing Synapse works, what should I do long-term?
A: Keep Synapse closed while playing, or consider switching to a lighter device configuration (onboard profiles) until the conflict is resolved via updates.

Q: Where can I see what Activision is tracking right now?
A: Activision Support maintains a “Known Issues” page for Warzone that is periodically updated.