Call of Duty DEV ERROR 6068

DEV ERROR 6068 means your GPU ran out of VRAM or the driver crashed mid-match. If you're in Warzone or MW3 and just lost a ranked game to this, here's the fastest fix: lower Texture Resolution to Normal, turn off On-Demand Texture Streaming, disable Ray Tracing, and make sure your GPU driver is updated. That combination fixes it for most people. If you're still crashing, there's a deeper issue and this guide covers all of them.

What's actually happening

DEV ERROR 6068 is Call of Duty's internal code for "DirectX fatal error." When the game sends rendering commands to your GPU and the GPU either runs out of VRAM, crashes, or takes too long to respond, Windows' TDR (Timeout Detection and Recovery) kills the GPU driver. Call of Duty catches this and shows DEV ERROR 6068 instead of a generic Windows crash.

The "6068" number is specific to DirectX device removal — it's the same underlying issue as DXGI_ERROR_DEVICE_REMOVED, but wrapped in CoD's error reporting. What makes this one special is that Call of Duty is one of the most VRAM-hungry games on the market. Warzone with high textures and On-Demand Texture Streaming enabled can eat 10-12GB of VRAM. If you have an 8GB card (like an RTX 4060 or RX 7600), you're operating right at the edge.

The most common causes (in order of likelihood)

VRAM exhaustion. This is the #1 cause by a wide margin. Call of Duty's texture streaming system aggressively fills your VRAM, and when it overflows, the GPU crashes. The game's VRAM usage meter in the graphics settings is optimistic — real-world usage is often 1-2GB higher than what it reports, especially in Warzone where you're loading textures for an entire battle royale map. Chrome running in the background with hardware acceleration can steal 500MB-1GB of VRAM on top of that.

Outdated or buggy GPU driver. NVIDIA and AMD release Call of Duty-specific driver optimizations with almost every major update. Running a driver even 2-3 months old can mean you're missing critical stability fixes for the latest CoD season. The driver version matters more for CoD than almost any other game because the engine pushes GPU hardware so aggressively.

GPU overclock instability. Call of Duty's renderer is extremely sensitive to unstable GPU clocks. An overclock that passes FurMark and Unigine benchmarks can still crash in Warzone because the game hammers the GPU in patterns that synthetic benchmarks don't replicate — rapid shader compilation spikes, massive VRAM transfers during loadouts, etc.

On-Demand Texture Streaming issues. This feature downloads high-res textures in real-time from Activision's servers and loads them into VRAM. When your internet hiccups, the streaming system can corrupt texture data in VRAM, which crashes the GPU. It also uses more VRAM than the game's UI suggests.

Insufficient virtual memory (pagefile). When VRAM overflows, the GPU driver spills texture data into system RAM via the Windows pagefile. If your pagefile is too small, the spill fails and you get DEV ERROR
6068.
How to fix it

1. Lower the settings that eat VRAM. Open the game's Graphics settings and change these specifically: Texture Resolution to Normal (not High or Very High), Texture Filter Anisotropic to Normal, disable Ray Tracing entirely (all RT options off), Shadow Quality to Normal, Screen Space Reflections to Normal, Tessellation to Off or Near. Check the VRAM usage bar at the top of the settings — keep it under 80% of your GPU's total VRAM. For an 8GB card, that means staying under 6.5GB in the settings menu.
2. Turn off On-Demand Texture Streaming. Go to Graphics > Quality > scroll down to On-Demand Texture Streaming and disable it. Yes, the textures will look slightly worse. But this feature is the single biggest cause of DEV ERROR 6068 because it unpredictably fills VRAM with high-res textures that the VRAM meter doesn't account for. You can always turn it back on after fixing the crashing.
3. Update your GPU driver with a DDU clean install. Download DDU (Display Driver Uninstaller) from guru3d.com. Boot into Safe Mode (hold Shift while clicking Restart > Troubleshoot > Startup Settings > Safe Mode). Run DDU, select "Clean and restart." After reboot, immediately install the latest Game Ready driver from nvidia.com or the latest Adrenalin driver from amd.com. For NVIDIA, make sure you're on the latest Game Ready driver, not a Studio driver.
4. Remove any GPU overclock. Open MSI Afterburner and click the reset button to return to stock clocks. This includes memory overclock — unstable VRAM clocks are a major cause of texture-related crashes, and DEV ERROR 6068 is a texture-related crash. Test at stock for a few sessions before re-overclocking.
5. Increase your Windows pagefile. Right-click This PC > Properties > Advanced System Settings > Performance > Settings > Advanced tab > Virtual Memory > Change. Uncheck "Automatically manage paging file." Select your SSD (NOT an HDD if you can avoid it), click Custom Size, set Initial Size to 16384 and Maximum Size to 32768 (that's 16-32GB). Click Set, then OK, and restart. This gives your GPU driver room to spill VRAM overflow into system memory instead of crashing.
6. Close VRAM-hungry background apps. Chrome uses GPU VRAM even when minimized. Close it entirely (check Task Manager — it runs background processes). In Discord: Settings > Advanced > turn off Hardware Acceleration. Also close wallpaper engines and streaming software.
7. Disable overlays. Turn off GeForce Experience overlay (Settings > In-Game Overlay > Off). Turn off Discord overlay (User Settings > Game Overlay > Off). Turn off the Steam overlay for CoD specifically. Turn off the Xbox Game Bar (Settings > Gaming > Xbox Game Bar > Off). CoD is notorious for crashing when overlays are fighting over DirectX hooks.
8. Scan and repair game files. In Battle.net: click the gear icon next to the game > Scan and Repair. On Steam: right-click > Properties > Installed Files > Verify Integrity. Corrupted shader caches cause DEV ERROR
9. Set NVIDIA Power Management to Maximum Performance. Open NVIDIA Control Panel > Manage 3D Settings > Program Settings > add your CoD executable. Set Power Management Mode to "Prefer Maximum Performance."

Is this a hardware problem?

Almost never. DEV ERROR 6068 is overwhelmingly a VRAM/driver issue, not a sign your GPU is dying. If you ONLY get this crash in Call of Duty and no other games crash, it's a CoD-specific settings or driver problem. If other games are also crashing with GPU errors, then look into GPU hardware health (run OCCT VRAM test, check temperatures with HWiNFO64).

If you suspect hardware, run OCCT's VRAM test — it can detect failing VRAM modules. But this is rare.

CoD-specific settings that make a huge difference

Spot Shadows and Spot Shadow Cache: Both to Low. They eat VRAM with minimal visual benefit. Particle Quality: Normal. High particle quality during explosions is a common crash trigger. Cache Sun Shadows: Off if you're VRAM-limited. World Motion Blur and Weapon Motion Blur: Off. They add GPU load for an effect most competitive players hate anyway.

Frequently asked questions

Q: I have a 12GB or 16GB GPU and still get DEV ERROR
6068. How?
A: On-Demand Texture Streaming can push past 12GB in Warzone. Also check if Chrome, Discord, or other apps are eating 1-2GB of your VRAM in the background. Open Task Manager > Performance > GPU to see total VRAM usage across all apps.

Q: Does switching to DirectX 11 help?
A: MW2 and MW3 removed the DX11 option — you're stuck on DX12. For older MW/Warzone (2019-2021), switching to DX11 in the game's advanced settings or config file can help because DX11 has lower VRAM overhead. Edit the "adv_options.ini" file in Documents > Call of Duty Modern Warfare > players and change RendererWorkerCount.

Q: The crash only happens when I open my loadout screen. Why?
A: The loadout screen loads weapon models, camos, and operator skins all at once. Animated camos spike VRAM usage. Lower texture quality or disable On-Demand Texture Streaming.

Q: I just updated my driver and NOW I'm getting this error. What gives?
A: New GPU drivers sometimes introduce regressions for specific games. Roll back to the previous driver version: Device Manager > Display Adapters > right-click your GPU > Properties > Driver > Roll Back Driver. Or download the previous version from NVIDIA/AMD's driver archive and DDU install it.