Dev Error 6036 is a common crash that occurs in Call of Duty: Modern Warfare (2019) and Warzone on Windows 10, often right after the game loads or during a match. This guide provides step-by-step fixes that address the most frequent causes: corrupted shader cache, outdated graphics drivers, and conflicting background software. Follow the steps in order, and you will likely resolve the error without reinstalling the game.
What You’ll Need
- Windows 10 PC with administrator access
- Stable internet connection (for driver updates and game file verification)
- Your game installation path (default: C:\Program Files\Call of Duty Modern Warfare)
Step-by-Step
- Restart your PC and launch the game again. Sometimes the error is a one-time glitch. If it persists, continue.
- Update your graphics drivers. Outdated drivers are the #1 cause of Dev Error 6036. Go to the official website of your GPU manufacturer (NVIDIA, AMD, or Intel) and download the latest driver for your specific model. Use the “Clean Installation” option if available. After installing, restart your PC.
- Clear the DirectX shader cache. In Windows, type “Disk Cleanup” in the search bar and open it. Select the drive where Windows is installed (usually C:). Click “Clean up system files.” Check “DirectX Shader Cache” and click OK. Confirm deletion.
- Delete the game’s shader cache folder. Navigate to
Documents\Call of Duty Modern Warfare\players. Delete the folder namedshadercache(or files likeshader.pak). The game will rebuild these files on next launch. - Scan and repair game files. Open Battle.net, go to your game library, select Call of Duty: Modern Warfare, click the gear icon, and choose “Scan and Repair.” Wait for the process to complete, then try launching.
- Disable overclocking. If you have overclocked your CPU or GPU, revert to stock settings. Use tools like MSI Afterburner or your BIOS to reset to default clocks. Overclocks can cause instability that triggers Dev Error 6036.
- Close background applications. Press Ctrl+Shift+Esc to open Task Manager. End tasks for programs like Discord, Chrome, RGB software (e.g., iCUE, Razer Synapse), and any recording software (OBS, ShadowPlay). Then relaunch the game.
- Set the game to run as administrator. Right-click the Modern Warfare executable (found in your installation folder) and select Properties. Go to the Compatibility tab, check “Run this program as an administrator,” and click Apply. Do the same for the Battle.net launcher.
- Disable fullscreen optimizations. In the same Compatibility tab, check “Disable fullscreen optimizations.” This is a known fix for many DirectX errors.
- Lower your graphics settings. Launch the game (if it opens). Go to Options > Graphics. Set “Shader Cache” to ON (if available), and reduce “Texture Resolution” and “Shadow Quality” to Normal. Also set “Render Resolution” to 100%.
- Reinstall the game (last resort). If nothing works, uninstall the game completely from Battle.net, then reinstall. This ensures no corrupted files remain.
Common Mistakes
- Only updating drivers without a clean install. A regular update may leave old files that still cause conflicts. Always use the “Clean Installation” option.
- Deleting the wrong folder. Ensure you delete the shader cache folder in
Documents\Call of Duty Modern Warfare\players, not the entire “players” folder. - Skipping the DirectX cache cleanup. Many users only delete the in-game shader folder, but the Windows-level DirectX cache can also be corrupted.
- Ignoring background overlays. Discord overlay and GeForce Experience overlay are known to cause this error. Disable them fully.
- Not restarting after each step. Some changes require a reboot to take effect. Restart after driver updates and cache deletions.
Tips
- Keep Windows 10 updated to the latest version. Go to Settings > Update & Security > Windows Update and check for updates.
- If you use an NVIDIA GPU, open the NVIDIA Control Panel and set “Power Management Mode” to “Prefer Maximum Performance” for the game.
- Set your in-game FPS limit to match your monitor’s refresh rate. Uncapped FPS can cause memory spikes.
- If you have multiple monitors, try disconnecting the secondary one and run the game on the primary.
- Disable any VPN or proxy software before launching the game.
Troubleshooting
If the error continues after all steps, try the following advanced checks:
- Check for Windows corruption. Open Command Prompt as administrator and run
sfc /scannow. Then runDISM /Online /Cleanup-Image /RestoreHealth. Restart after. - Test your RAM. Use Windows Memory Diagnostic (search “Windows Memory Diagnostic” in the start menu). Faulty RAM can cause random crashes.
- Monitor your temperatures. Use a tool like HWMonitor. If your CPU/GPU exceeds 90°C, clean your PC’s fans or improve airflow.
- Try a different account. Create a new Windows user account and run the game from there. This isolates profile corruption.
- Check your page file. Go to System Properties > Advanced > Performance Settings > Advanced > Virtual Memory. Ensure it is set to “System managed size.”
Frequently Asked Questions
What exactly causes Dev Error 6036?
The error is most often linked to corrupted shader cache files or outdated graphics drivers. It can also occur due to overclocking or conflicting background software.
Will reinstalling the game definitely fix it?
Reinstalling is a reliable last resort because it removes all corrupted files, but it’s time-consuming. Try the other steps first.
Does this error happen on consoles?
Dev Error 6036 is primarily reported on Windows 10. Console versions rarely show this specific code.
Can I ignore this error and keep playing?
No. The error crashes the game, so you cannot play until it is resolved. Ignoring it will only lead to repeated crashes.
Is there a permanent fix?
There is no official permanent fix, but keeping drivers updated and regularly clearing the shader cache will prevent most occurrences.
Do I need to disable antivirus software?
Sometimes third-party antivirus can interfere. Temporarily disabling it (not uninstalling) may help, but be sure to re-enable it after testing.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Disable Autocorrect on iPhone or iPad: Quick Guide
- Custom Keyboard Shortcuts on Windows 11 & macOS
- Restore Windows 11 Display Scaling to Recommended
- Semiconductor Cycle: How Investors Track It0.0
- Microsoft Store Error 0x80073d12: Fixes That Work
- View Notification Count on iPhone: Full Guide