You're in the lobby, squad's ready, drop's about to start. The map starts loading—Al Mazrah's buildings, the sand, the cranes—and then boom, desktop. No error message, no warning, just a hard crash. Check the logs and you see Dev Error 6036. Had a client last month whose entire ranked squad hit this three games in a row. He was about to reformat his PC before we found the real culprit.
What Is Dev Error 6036?
This error is a memory allocation failure. The game is trying to load the map—specifically the geometry and textures—but the system runs out of memory. Not physically, but virtually. Warzone 2.0 has a known memory leak that eats up RAM as you play. By the time you hit the loading screen for the next match, the game can't allocate enough memory to load the map, so it crashes.
You'll see it most often after a few matches. First game loads fine. Second game might load. Third or fourth, boom. The longer you play, the more likely it is. Also happens when you've got a browser open with 40 tabs, Discord, and a streaming overlay running. The leak gets pushed over the edge and the game can't find enough free memory.
The Root Cause
It's not your GPU, not your CPU, not your hard drive. It's a memory leak in the game engine that never fully releases VRAM/RAM after each match. On some PC setups, especially with certain graphics drivers, the leak accelerates. The game's memory footprint grows and grows until it exceeds what Windows will let it use, then it crashes. Blizzard and Infinity Ward have patched it multiple times, but it still sneaks back with each update.
You can't fix the leak yourself, but you can work around it. The trick is to force the game to use less memory overall, and clear the memory between matches. The most reliable fix is to lower the video memory scale and set a custom framerate cap. That stops the leak from ballooning out of control.
The Fix That Actually Works
Skip the reinstall, skip the driver rollback. Here's what to do, in order.
Step 1: Lower the Video Memory Scale
This is the big one. Go to Settings > Quality > Video Memory Scale. Slide it down to 70 or even 60. What this does is tells the game to only use up to 70% of your VRAM, leaving headroom for the leak. Default is 90, which is too close to the edge. I've seen this single change fix the error for 9 out of 10 people.
Step 2: Cap Your Framerate
Back out to Settings > Graphics, find Custom Framerate Limit, and set it to your monitor's refresh rate—or better, one frame below. If your monitor is 144Hz, set it to 141. Uncap the framerate in the menu and the game will try to push as many frames as possible, which uses more CPU and memory. Capping it removes that stress and stops the leak from filling up the memory pool as fast.
Step 3: Turn Off On-Demand Texture Streaming
In the same settings page, look for On-Demand Texture Streaming. Turn it off. This is a feature that streams textures as you play, which adds a constant memory load. Had a client with a 16GB RAM system, and this was the difference between crashing every other game and playing all night. Yes, the game might look slightly less sharp in the first second of a match, but you'll actually finish a match.
Step 4: Close Memory Hogs
Before you launch Warzone, close Chrome, Discord (you can use the web version on your phone), and any other overlay like MSI Afterburner or RivaTuner. Those tools are great, but they eat VRAM. If you're on 16GB of RAM, you need every MB free. I know it's a pain, but it's the difference between crashing and not.
Step 5: Clear the Game Cache
If the above doesn't stop the crashes, clear the game's cache. This resets the shader cache that can get corrupted after crashes.
Battle.net: Options > Game Settings > Reset In-Game OptionsOr in Steam, right-click the game, properties, local files, verify integrity of game files. That won't wipe your settings but will re-download any corrupted data.
What If It Still Crashes?
If you've done all that and you still get 6036, you're dealing with a different problem. Check your RAM stability. Download MemTest86 and run it—had a client whose PC passed everything else but had a faulty stick of RAM. The memory leak just exposed it. Also make sure Windows and your GPU drivers are fully updated. If you're on Windows 10, update to the latest 22H2.
Finally, if you're on a 16GB RAM system, consider closing every background app and using the task manager to see if anything's eating memory. Warzone 2.0 can use up to 10GB alone after a few matches. The real long-term fix is adding more RAM—I upgraded mine to 32GB and the error completely disappeared. But that's an expensive fix. The steps above should get you playing now.
You might also need to switch from Fullscreen Borderless to Fullscreen Exclusive. That gives the game direct control over the display, which can improve memory allocation. Go to settings, display mode, change it, apply, and test. Sometimes that's enough to stop the leak from being the thing that kills the game.
Dev Error 6036 isn't the end of the world. It's annoying, but it's fixable. I've got a client who runs a small gaming cafe, and we applied these settings to all 20 machines. They haven't seen 6036 since. Start with the video memory scale, cap the frames, and you'll be back on the drop in no time.