Call of Duty: Warzone crashing on startup is distinct from the mid-match stutters and random desktop returns that plague most competitive shooters. When this game dies before you ever see the loading screen or the main menu, it almost always points to one of a narrow set of culprits: a shader cache conflict between the IW engine’s compilation step and your GPU driver, an overlay hook that the Ricochet anti-cheat cannot tolerate, or a corrupt config file carrying over from a previous session that the launcher fails to clear. The engine is unforgiving about initialization order. If anything interrupts the handshake between cod.exe, the Ricochet kernel driver, and DirectX, the process simply terminates—often without a visible error dialog. What follows is a structured set of checks ordered by likelihood and least invasiveness.
- Likely Causes
- Fix 1: Disable all overlay and hooking software
- Fix 2: Clear the shader cache and reinstall GPU drivers cleanly
- Fix 3: Verify game files through your launcher
- Fix 4: Remove or rename the config and players2 folders
- Fix 5: Repair or reinstall the Ricochet anti-cheat driver
- Fix 6: Disable fullscreen optimizations and adjust compatibility settings
- Fix 7: Add exclusions for Warzone in Windows Defender and third-party antivirus
- Fix 8: Test with XMP disabled and RAM at JEDEC defaults
- If Nothing Works
- FAQ
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Overlay software hooking into the render thread (RTSS, MSI Afterburner, Discord, GeForce Experience) | Disable all overlays, launch again. Crashes that occur within 2-5 seconds of the splash screen are typical. | Low |
| Corrupt or conflicting GPU shader cache after a driver update | Crash log in Documents/Call of Duty/logs/ mentions shader compilation failure or device lost. |
Low |
| Missing or mismatched game files after a launcher update | Launcher “repair” or “verify integrity” reports errors or downloads hundreds of MB. | Low |
Corrupt config.cfg or players2/ folder with invalid video settings |
Renaming the folder and relaunching allows entry into the game. | Medium |
| Ricochet anti-cheat initialization failure (kernel driver blocked or outdated) | Error string “Ricochet initialization failed” or the game closes silently after the Activision logo. | Medium |
| Windows compatibility layer conflict (fullscreen optimizations, DPI scaling, VBS/hypervisor) | Launching in borderless window or toggling Memory Integrity resolves it. | Medium |
| Antivirus or Windows Defender flagging Ricochet kernel driver or cod.exe | Quarantine logs show blocked items; disabling real-time protection allows startup. | High |
| Unstable RAM or XMP profile causing engine initialization failure | Crash is inconsistent and occurs at different points; lowering or disabling XMP stabilizes it. | High |
Fix 1: Disable all overlay and hooking software
This is the single most common reason Warzone fails to start in 2026. The IW engine’s render thread initialization conflicts with any software that injects into Direct3D or Vulkan pipelines via DLL hooks. Ricochet’s integrity checks compound this by treating unknown module loads as tampering.
How to check
Open Task Manager (Ctrl+Shift+Esc) and look under the “Startup” and “Background processes” tabs for RivaTuner Statistics Server (RTSS), MSI Afterburner, Discord, GeForce Experience, or any third-party FPS counter. Kill them all, then launch the game.
What to do
Fully exit each overlay application from its system tray, not just close the window. If the game launches successfully, re-enable them one at a time to isolate the culprit. RTSS and MSI Afterburner are the most frequent offenders. If you need an FPS counter, enable the built-in telemetry in the in-game settings instead of a third-party overlay.
How to undo it
Relaunch the overlay applications normally. If you must use RTSS, set its “Application-specific” entry for cod.exe to disable the OSD hook rather than turning off RTSS globally.
Fix 2: Clear the shader cache and reinstall GPU drivers cleanly
The IW engine pre-compiles and stores shader binaries. A driver update can invalidate these, causing an immediate “device lost” failure during initialization. NVIDIA stores them in C:\Users\[you]\AppData\Local\NVIDIA\NV_Cache\ and %LOCALAPPDATA%\D3DSCache\. AMD uses C:\Users\[you]\AppData\Local\AMD\DxCache\.
How to check
Open the crash log at Documents/Call of Duty/logs/crash/. If you see “D3D device removed” or “Shader compilation timeout,” this is your issue.
What to do
Delete all contents of the D3DSCache folder (safe to do; Windows and drivers regenerate it). Then use DDU (Display Driver Uninstaller) in Safe Mode to fully remove your current GPU driver, and install the latest stable release fresh. Avoid hotfix drivers for this step.
How to undo it
No undo needed. Shader caches rebuild automatically. Your driver reinstall simply replaced what was already there.
Fix 3: Verify game files through your launcher
Partial downloads, interrupted patches, and launcher sync errors are common after season updates. A single missing or mismatched asset can crash cod.exe before it reaches the menu.
How to check
On Steam, right-click Call of Duty > Properties > Installed Files > “Verify integrity of game files.” On Battle.net, click the gear icon next to the Play button and select “Scan and Repair.” The process will flag corrupt or missing files and re-download them.
What to do
Run the verify/repair tool. If it downloads a very large amount of data (multiple GB), something was significantly corrupt. After it finishes, launch the game once more. If it still crashes, proceed to the next fix.
How to undo it
No undo needed. Verification only replaces files that are already expected to exist.
Fix 4: Remove or rename the config and players2 folders
Corrupt settings files are a well-known cause of immediate startup crashes. If a previous session wrote invalid video settings—particularly resolution, refresh rate, or ray tracing toggles—the engine can fail during display initialization.
How to check
Navigate to Documents/Call of Duty/players2/. Inside, the config.cfg file stores your settings. Rename the entire players2 folder to players2.bak and attempt to launch. If you reach the main menu, a corrupt setting file was the cause.
What to do
With the folder renamed, launch the game and let it generate a fresh configuration. Re-enter your keybinds and preferences. You can selectively copy back individual files from the backup if you want to preserve something specific.
How to undo it
Close the game, delete the newly created players2 folder, and rename players2.bak back to players2.
Fix 5: Repair or reinstall the Ricochet anti-cheat driver
Ricochet installs a kernel-mode driver (RiotK.dll and associated service). If this driver fails to load—due to a Windows Update, a conflicting security product, or a corrupted installation—the game will not pass its initialization gate and closes silently or with “Ricochet initialization failed.”
How to check
Open an elevated Command Prompt and run sc query WsddDrv and sc query riotk. If either service reports “not started” or is missing entirely, the anti-cheat layer is broken.
What to do
Uninstall the game completely through the launcher, delete the remaining folder, then reinstall. This forces the launcher to re-register and re-extract the Ricochet driver. Alternatively, some players report that reinstalling the Visual C++ Redistributables (2015-2022 x64) and rebooting resolves the driver load failure without a full reinstall.
How to undo it
Not applicable in a meaningful sense. The driver is designed to be present. If the system is working, no reversal is needed.
Fix 6: Disable fullscreen optimizations and adjust compatibility settings
Windows applies its own compositing layer when it detects fullscreen-exclusive applications. For Warzone, this can interfere with the engine’s swap chain creation. High DPI scaling set to something other than 100% on the system display also triggers this.
How to check
Right-click cod.exe in the game install folder, open Properties, and look at the Compatibility tab. If “Disable fullscreen optimizations” is unchecked, Windows may be interfering.
What to do
Check “Disable fullscreen optimizations” and click “Change high DPI settings” to override the scaling behavior to “Application” mode. Apply and test. In your graphics settings, select “Borderless” window mode rather than “Fullscreen” to sidestep the issue entirely.
How to undo it
Uncheck the boxes and restore the original DPI override. Revert the in-game display mode back to Fullscreen if desired.
Fix 7: Add exclusions for Warzone in Windows Defender and third-party antivirus
Security software sometimes quarantines Ricochet’s kernel driver or blocks cod.exe from loading unsigned modules during initialization. This has been observed with Bitdefender, ESET, and even Windows Defender after certain definition updates.
How to check
Open Windows Security > Virus & threat protection > Protection history. Look for any blocked items referencing cod.exe, RiotK, or the Call of Duty installation path.
What to do
Add an exclusion for the entire Call of Duty install folder and, separately, for C:\Windows\System32\drivers\Riotk.sys (path may vary). If using a third-party suite, add the same exclusions there. Restart the system after adding exclusions, since kernel-level drivers may not re-register without a reboot.
How to undo it
Remove the exclusions from the antivirus settings. Only do this if you are certain the software was not the cause, as leaving it in place while the AV continues to block the driver will keep the game unplayable.
Fix 8: Test with XMP disabled and RAM at JEDEC defaults
Warzone’s IW engine allocates and initializes large memory buffers during startup. Unstable XMP profiles—particularly on DDR5 platforms with aggressive timings—can cause the process to crash before the menu appears. This is more common on 4-stick DDR5 configurations.
How to check
Enter your BIOS/UEFI and temporarily set memory to “Auto” or the JEDEC default (4800 MT/s for DDR5, 2133/2400 MT/s for DDR4). Disable XMP/EXPO entirely. Attempt to launch the game. If it starts without crashing, your memory overclock is the root cause.
What to do
If the game works at JEDEC, you have options: tighten one variable at a time (tCLK or tRCD) to find the instability threshold, increase DRAM voltage slightly (for DDR5, 1.4V from the default 1.35V), or run a memory stability test like TestMem5 with the anta777 Extreme profile to confirm whether XMP is genuinely unstable. The game crashing at startup is one of the more visible symptoms of subtle RAM errors.
How to undo it
Re-enable XMP or restore your previous memory profile in BIOS. If instability persists, the hardware is at fault and no software fix will reliably solve it.
If Nothing Works
At this point the problem is almost certainly hardware-level. Test with a single RAM stick in the primary slot to rule out a dead channel or DIMM. Try a different GPU if available to eliminate a failing VRAM or GPU core. Check your Event Viewer under “Windows Logs > Application” for a specific faulting module name in the crash report—if it consistently points to ntdll.dll or ntoskrnl.exe, the issue is in the Windows kernel or a driver, not the game itself. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an elevated prompt to rule out OS file corruption. If the game crashes on a fresh Windows install with only drivers present, the hardware is your answer.
FAQ
Does Warzone need DirectX 12 specifically, and can switching to DX11 help?
The game defaults to DirectX 12. You can force DirectX 11 by adding -d3d11 to the launch options in Steam (right-click game > Properties > Launch Options) or by editing the shortcut target on Battle.net. Some users report that DX11 bypasses a shader compilation bug that triggers the startup crash, but it comes with a minor performance cost and is not a permanent fix.
Why does it crash only after a season update?
Season updates rebuild the shader cache and sometimes change the Ricochet driver version. If your system was stable before, the new cache or driver is incompatible with whatever overlays, config remnants, or security exclusions you had tuned for the previous build. Start with Fix 2 and Fix 3 after any major patch.
Is the “Failed to initialize graphics” error the same problem?
Usually yes. That string specifically means the IW engine’s device creation call to DirectX returned a failure. Overlays, corrupt shader caches, and GPU driver mismatches all produce this message. Follow the same checks above.
Can a second monitor with a different refresh rate cause startup crashes?
It has been reported. The engine sometimes attempts to query the primary display’s timing during initialization and fails if the secondary display introduces a conflicting EDID. Unplug the secondary monitor and test. If it resolves, ensure both displays report compatible refresh rates in Windows Display Settings, and set the primary monitor to the highest available rate.
