Fix Call of Duty Modern Warfare Warzone Dev Error 6345July 17, 2020
With Modern Warfare and Warzone Season 5 set to release sometime during the next month if the release is not delayed due to COVID-19 users are still encountering the old error since the release day. One of them is the Call of Duty Modern Warfare Warzone dev error 6345. Like most dev errors, there is not much information in the error message. If you have been battling with dev errors, you would know there is no one fix that works for everyone. Hence, you must try a bunch of fixes to get the game running. Thankfully, we have certain fixes you can try.
The most effective fix for this problem is to reinstall the game, but the error will still occur if you have bad sectors on your hard drive or a third-party software is interfering with the game. The huge size off the game makes this fix cumbersome, but users across platforms have reported that reinstalling was the only fix that worked. So, before you proceed with the reinstall, try these other fixes and if nothing works to resolve the dev error 6345, you can proceed to reinstall the game.
Fix 1: Underclock the GPU
If you have overclocked the GPU or are using an overclocking software, revert the changes and try playing the game. Also disable all third-party software by pressing Windows Key + R, type msconfig. Go to the Services tab, click on Hide all Microsoft services. Now, click on Disable all. Save the changes and check if the dev error 6345 still occurs.
Fix 2: Force the Game to Run on DirectX 11
Switching back to DirectX 11 to play the game has worked for a lot of users. DirectX 11 is more stable version, but you will have to sacrifice some features which DirectX 12 brings; however, not extreme. So, let’s force the game to run in DirectX 11 mode. Here are the steps.
- Open Battle.Net Client on the PC.
- Open the game COD Modern Warfare
- Go to Options
- Check Additional Command Line Arguments and type -d3d11
- Exit and try playing the game.
Fix 3: Clear Console Cache
The cache on the console are temporary files that enhance the performance of the game, but sometimes the files can get corrupted or overwritten leading to game loading errors, freezes, connectivity problems, and in this case the dev error 6345. Clearing the cache can help you fix the problem. Here are the steps to follow.
Clear Cache in PS4
- Turn-off the Console normally.
- Remove all the power-cords after the console has completely powered down.
- Press and hold the power button for 10 seconds or let the console rest for 30 seconds.
- Reconnect the power cords and restart the PS4.
- Hold the L1 + R1 buttons while the PS4 is booting.
This will not only clear the PS4 cache but also reset the brightness and language.
Clear Cache in Xbox One
- Press and hold the power button on Xbox One to turn it off.
- Dethatch the power brick and press and hold the power button for a few seconds. Do it a few times to reinitialize and clear cache from the device.
- Connect the power brick back to the console
- Wait for the light to turn orange in the power brick.
- Turn on the Xbox One normally.
Once you have done this, restart the console to check if the dev error 6345 still appears.
Fix 4: Delete Saved Game Data from Console
Several users were able to fix the dev error 6345 error in Call of Duty Warzone by deleting the saved game files. Once you have deleted the files, the console would request an update after which the error gets resolved. Do create a backup of the saved game files as once it’s deleted from the console you cannot retrieve it.
Fix 5: Uninstall and Reinstalling the Game
Uninstalling and reinstalling the game has resolved the error for quite a number of users. As a method of troubleshooting, you probably have already tried uninstalling and reinstalling the game. However, some users were able to resolve the error after multiple attempts and uninstall and reinstall. Hence, I suggest you try this a few times. I know the game size is large and it can take up considerable time depending on your internet speed, it’s worth the shot.
Hope you dev error 6345 is resolved with the above fixes.