🔧 Call of Duty Error Fix · 8 Proven Fixes

How to Fix Call of Duty Dev Error 6036: Stop the Crash

By GameAddaUpdated October 17, 20268 min read

You hit Play on Warzone or Modern Warfare, the game loads for a few seconds — and then it happens: DEV ERROR 6036 [reason: 2]. The game closes, you're staring at your desktop, and the error gives you absolutely nothing useful to work with. If this keeps happening every time you launch (or mid-match, which is even worse), this guide is for you.

Dev Error 6036 is one of the most reported Call of Duty errors on PC, and it has been around across multiple CoD titles. The good news is that it is almost never a server issue and almost never something wrong with your account. It is a PC-side crash, and in the vast majority of cases it comes down to one of a handful of causes — starting with the single biggest one: an unstable graphics card overclock. Work through the fixes below in order and you'll likely be dropping back into matches the same evening.

What does Dev Error 6036 actually mean?

In plain English, Dev Error 6036 means Call of Duty's engine crashed because something went wrong between your graphics card, its driver, and the game's files or shaders. The "dev" in the name is a giveaway: this error comes from the game's own engine code catching a failure it doesn't know how to recover from, not from the network, not from Activision's servers, and not from your account.

Concretely, the engine crashed while trying to render the game — compiling shaders, loading textures, or talking to the GPU through the driver. That points to a small set of suspects: a GPU running slightly too fast to be stable, a corrupted graphics driver, corrupted game files, a broken shader cache, or a third-party app injecting itself into the rendering pipeline (looking at you, overlays).

What causes Dev Error 6036?

After years of community reports across Modern Warfare, Warzone, and later titles, the usual suspects are well mapped:

Try this first — it fixes most 6036 crashes: If your graphics card is overclocked in any way (you did it yourself in MSI Afterburner, or the card shipped "OC" from the factory), drop the Core Clock by −100 MHz in Afterburner and apply it. This single change resolves more Dev Error 6036 cases than every other fix combined. If you don't use Afterburner, the full steps are in Fix 1 below.

1Remove the GPU overclock

This is the fix the Call of Duty community swears by, because 6036 is overwhelmingly an instability crash. Download MSI Afterburner (free) if you don't have it, and enter −100 in the Core Clock field, then click the checkmark to apply. You can also drop the Power Limit slider slightly as a second stabilizer. This doesn't noticeably change your frame rate — you're trading about 2–3% of performance for stability — but it returns a borderline-unstable card to safe territory.

If you never overclocked anything yourself, check whether your card is a factory-OC model (the box or product name usually says "OC", "Gaming X", "ROG Strix", or similar). Those cards ship with a mild overclock applied by the manufacturer, and the same −100 MHz step works. You don't even need to keep Afterburner running forever: if 6036 stops, you've found your cause, and you can experiment with smaller offsets later.

2Clean-install your graphics drivers

A driver that is merely "up to date" can still be the problem — bad installs corrupt driver files in ways that only certain games trip over. A clean install wipes the slate:

Don't skip DDU: the standard installer leaves old files and registry entries in place, and 6036 has a habit of surviving those. A full clean install is what resets whatever the engine is tripping over.

3Repair the game files

Corrupted game data is the next most likely culprit, and it's quick to check. On Battle.net: select the game, click the gear icon next to the Play button, and choose Scan and Repair. On Steam: right-click the game in your library, open Properties → Installed Files, and click Verify integrity of game files. Both tools scan the installation and re-download anything damaged or missing. Run the game immediately after the scan finishes and see whether 6036 is gone.

Don't disable your anti-cheat or run "fix" tools from random forums: 6036 has nothing to do with Ricochet, and community "patcher" utilities claiming to fix it are a common way to get malware — or to trigger an actual ban by modifying game files. Stick to the legitimate fixes here: downclocking, clean drivers, file repair, and cache rebuilds are all safe and reversible.

4Rebuild the shader cache

CoD pre-compiles shaders so the game doesn't stutter while playing. When that cache corrupts, the engine crashes on load with 6036. Two ways to clear it:

The first launch after clearing will take longer (the game is recompiling everything), which is normal. If 6036 stops after the rebuild, the old cache was the problem.

5Turn off every overlay

Overlays inject themselves into the game's rendering — exactly the pipeline that 6036 complains about. Disable all of these before testing:

Test the game with everything off. If it launches cleanly, re-enable overlays one at a time to find the troublemaker — but honestly, most competitive players leave them all off anyway.

6Run your RAM at stock speed

If your system uses XMP (Intel) or DOCP/EXPO (AMD) memory profiles, those are overclocks too — and marginal memory instability corrupts the exact data the engine fails on. Enter your BIOS/UEFI, find the memory profile setting, and switch it back to the stock speed temporarily. If 6036 disappears, your RAM overclock was unstable under CoD's workload (you can then try a slower XMP profile or slightly looser timings, but stock is the test). Also worth running: Windows Memory Diagnostic — type it into the Start menu, run the extended test, and check for failing memory sticks.

7Update Windows and clear antivirus blocks

Install every pending update in Settings → Windows Update: newer Windows builds include DirectX and runtime fixes the CoD engine depends on. Then open your antivirus (Windows Security counts) and add the entire game folder to the exclusions list — security software sometimes locks or quarantines game files at launch, and the engine reports that as 6036. Finally, try launching the game as administrator once: right-click the launcher and choose Run as administrator, in case a permission problem is blocking file access.

8Reinstall the game as a last resort

If nothing above worked, the installation is likely damaged in a way the repair tool can't see. Uninstall the game, restart your PC, then reinstall fresh from Battle.net or Steam. Yes, it's a big download — but community experience says 6036 is fixed by the downclock, clean drivers, or repair in the large majority of cases, so this step is genuinely rare. After reinstalling, keep the downclock and the disabled overlays in place from the start.

Quick checklist to keep Dev Error 6036 away

Frequently asked questions

What does Dev Error 6036 mean in plain English?

It means the Call of Duty engine crashed because something went wrong between your graphics card, its driver, and the game's data — usually an unstable overclock, a corrupted driver, or a broken shader cache. It's a PC-side crash: your account, rank, and inventory are completely safe.

Is Dev Error 6036 caused by my GPU being too weak?

No — it's a stability error, not a performance error. It hits high-end cards just as often, and it's actually most common on overclocked and factory-overclocked cards, which are the opposite of weak.

Why does 6036 only happen in Warzone and not my other games?

Call of Duty's engine is unusually sensitive to GPU instability and shader cache corruption. An overclock or driver issue that's perfectly stable in other games can still crash CoD — which is why the game-specific fixes here matter even when everything else runs fine.

Does Dev Error 6036 mean I'll get banned?

No. This is a client crash error, not a cheating detection. Ricochet anti-cheat flags are a completely separate system. Your Activision account is safe, and the error clears as soon as the hardware or file issue is fixed.

Can I fix Dev Error 6036 without downclocking?

Sometimes — a clean driver install with DDU or a game file repair can fix it if the cause was corruption rather than instability. But if those don't work, a modest −100 MHz core clock drop is the single most successful community fix and costs almost no performance.

Should I reinstall the game first?

No — reinstalling first wastes hours in most cases. Downclocking, a clean driver install, and file repair fix 6036 far more often than a reinstall does. Keep the full reinstall as your last resort (Fix 8).

For most players, Dev Error 6036 ends at Fix 1 or 2 — the overclock drop or the clean driver install fixes what the engine was choking on, and you're back in the lobby in under an hour. The frustrating part of this error is how little it tells you, but the pattern is remarkably consistent: unstable GPU, bad driver, or corrupted files, in roughly that order. Fix the stability, verify the files, and 6036 stays gone. And if you'd rather skip launchers, patches, and driver drama for a while, the free browser games here on GameAdda start with a single click. 🎮