[Updated] Call of Duty: Modern Warfare "Dev error 6034" hinders multiplayer as game keeps crashing on Xbox and PS4 (workarounds inside)

Here’s the crux of the article in video form:

New updates are being added to the bottom of the story…

Original story (from April 10, 2021) follows:

Call of Duty Modern Warfare is easily one of the most popular FPS games and is a reboot of the Modern Warfare sub-series which by itself was a starting point for many gamers.

COD: Modern Warfare is available on Windows, Xbox One, Xbox Series X/S, PlayStation 4, and PlayStation 5. And the multiplayer experience is what keeps players coming back to the game.

But it seems that several Call of Duty: Modern Warfare players on the Xbox and PS4 are unable to play most multiplayer maps as a “Dev error 6034” message pops up.

This error pops up when the system detects unreadable or corrupted game data. It explains why many users were left scratching their heads over the error after they updated the game.

Same Issue Here. I have uninstalled and reinstalled Clean, and it did not resolve The Issue. Activision needs to say something about This. (Source)

Fix the game please. I can’t even play a fu***** game with out this happing. Bc of this DEV ERROR 6034 bull shit. Please just fix the damn game. (Source)

@ATVIAssist ever since last week’s update I get DEV error 6034 on multiplayer every time I get loaded into a match on the Hardhat multiplayer map. I have to reboot my game every time. Pls fix soon. (Source)

Here’s an image that was taken by a user of the error screen when trying to play a multiplayer match on Piccadilly.

Activision is yet to release an official statement regarding the pestering dev error 6034 on Call of Duty: Modern Warfare for Xbox and PS4 players.

That said, there are a few workarounds that you can try out in order to fix the issue. Check them out below.

It seems that the error is a result of the 22 GB update not removing the previous files that it was supposed to replace. So a Redditor has shared a step-by-step guide for Xbox and PlayStation users to fix the issue.

1. Uninstall all the older multiplayer data packs, except the first one (6.0 GB Multiplayer pack). This includes the Data Packs 1 & 2, uninstall those.

2. Then, install the new “pack 2” (just listed as multiplayer pack (22GB) and the new Spec Ops and Mutilplayer compat pack.

3. For multiplayer, final install should look like this (image below) with nothing else installed when scrolled down.
(Source)

Another Xbox user has also shared some more useful details in case the above-mentioned steps don’t fix it.

Edit 2: This does work for Xbox one! The “multiplayer pack” that is required was named “multiplayer pack 2” for me. In the game screen it should look exactly like what OP posted. In the Xbox manage add-ons screen things are named differently for some reason.

Edit 3: on Xbox one the packs that I had to install in order for my add one to match OP are the following:

Multiplayer pack 6.0Gb Multiplayer and spec ops pack 6.7Gb Multiplayer pack 2 22.1Gb
(Source)

Feel free to drop a comment below to let us know if the workaround shared above works for you. We also welcome alternate workarounds in case you’ve found one that works for you.

In the meantime, we’ll keep tabs on the situation and will post an update once new details emerge. So stay tuned to PiunikaWeb.

IST 16:00 – Check out the following video which explains how to fix this issue. Many complainants have confirmed the issue got fixed for them after they followed the steps mentioned in this video.

So, check it out and share your thoughts (if any) with us in the comments section at the bottom of this page.

https://www.youtube.com/watch?v=Y9gIkB4chJM

IST 11:20 – Here’s a user-shared description of what exactly could be causing the dev error (and it makes sense).

What’s happened is they’ve merged map packs, there used to be 3 map packs but they were condensed into two. So now when your game is searching for specific maps it’s looking in the wrong place and you eventually get timed out for the dev error.

IST 11:20 – While Dev error 6034 is yet to be officially acknowledged, the developers have removed 2 newly added maps ‘Drainage’ and ‘Al-Raab Airbase,’ stating they need to be refined.

Here’s what Infinity Ward shared on Twitter:

We recently released two new maps to Modern Warfare, ‘Drainage’ and ‘Al-Raab Airbase’ which were available in private match. We temporarily removed them as they aren’t quite ready and need a bit more love before returning. We’ll update soon on when they’ll be back!

IST 10:30 – Another workaround that may help console users is head to Settings> Select Network> Advanced Settings> Select Alternate MAC address> Clear. Following this, the console will reboot and the game should work.

IST 10:45 – Keeping quiet on social media platforms, Activision has officially acknowledged the error 6034 along with multiple other issues. The “Known Issues in Call of Duty: Warzone” page says:

Issue: I got a Dev Error when I launched Warzone.
– PC
Description: We’re investigating multiple PC Dev Errors, including 6034, 6036, 6070, 6066, and 6065.
Be sure to check out Call of Duty: Modern Warfare PC Troubleshooting for additional help.

Other problems that have been recognized are:

Issue: I didn’t get the items from the Call of Duty: Black Ops Cold War Starter Pack.
– Xbox One
Description: We’re investigating an issue where players who do not have Call of Duty: Black Ops Cold War installed are not receiving their content in Warzone after purchasing the Black Ops Cold War Starter Pack.

– Fixed now (Check update section 14 below for details)

Issue: My game crashes and gives Dev Error 6634.

– All platforms
Description: We’re investigating an issue where the game is crashing for some players and leading to Dev Error 6634 “Unified Geometry Buffer has reached the max surface allocation limit!”

Issue: My Intel Missions aren’t tracking in Warzone.

– All platforms
Description: We’re currently investigating reports that some Intel Mission steps are not tracking.

Issue: I didn’t get credit for winning a Warzone match.

– All platforms
Description: We’re investigating an issue where wins in Warzone are not counting.

Issue:I keep getting a message that says “Update requires restart”.

– PlayStation 4 and Xbox One
Description:We’re working to fix an issue causing players to get caught in an update loop.

In the meantime, some players have found that clearing cache on their consoles ends this update loop. Follow the steps in this article to clear your console’s cache. In some cases, clearing cache may need to be done multiple times between attempts to load the game.

IST 10:45 – While the team addresses the issue, here’s another workaround you can try, if you’re not interested in reinstalling the entire game.

Head to the folder where the game is installed on your PC, and delete these files – .patch.result, .product, vivoxsdk_x64.dll, Launcher.db, Modern Warfare Launcher.exe. Now run Battle.net and select the game from the list that you can see on the left-hand side.

Select the options button under the title, then choose scan and repair, and wait for the process to complete. Run the game now. This process will basically check the game for the missing files, and redownload them.

IST 11:15 – Here’s another (slightly different) user shared workaround that you can give a shot.

Delete: -Multiplayer pack 2 (9.1 gb) -Multiplayer pack 3 (3.4 gb) -Compatibility Pack 2 renamed Data Pack 2 (8 gb) Then restart your Xbox DO NOT DELETE MP2 (22.1 gb) PACK These file sizes may differ slightly from different versions of Xbox, I’m on a Series X

IST 11:35 – While Dev error 6034 continues to persist, Raven Software is currently looking into the Stat Tracking glitch wherein players report of stats not tracking correctly across different game modes.

Additionally, the devs have updated the game to exclude the Most Wanted Contract in the Verdansk BR Playlist.

IST 16:35 – For some reason, some users have to uninstall and re-install the game followed by uninstalling the multiplayer pack (2 & 3), for the issue to be resolved.

IST 13:45 – Microsoft agents/moderators on the community have shared a few troubleshooting steps that the affected users can try.

I would like you to go through the following steps to clear the Mac address and then perform a quick power cycle on your console:

Settings > Network Settings > Advanced Settings > Alternate Mac Address > Clear it and the console should restart. It would definitely help if you could restart the internet router while the console is restarting.

After going through the troubleshooting steps mentioned, I invite you to perform a quick power cycle by turning off the console and then unplugging all the cables. After 2 to 3 minutes, re-plug them back again, then restart your console.

They further add:

In case the issue still persists, the next step would be to perform a reset on the console. To do so you will need to follow the steps below to perform a reset on the Xbox:

Settings > System > Console Info > Reset This Xbox > Reset and Keep my Games and Apps.

Note =>The “Reset and Keep my Games and Apps” option will not cause losing your games, but please be aware that you need to be completely aware of the email address as well as the password of your account before going for it because it will require you to sign in to the account.

Apart from the above-mentioned, another agent suggests:

Another thing you should check is your NAT type. I would like you to check your NAT type if open because that could sometimes interfere. to check for the NAT type you can follow the steps below:

Settings > Network Settings > NAT type => It should be open.

If the NAT type is not open, you will need to open some ports with your internet provider. These ports must be open for Xbox Live to work: Port 88 (UDP) Port 3074 (UDP and TCP) Port 53 (UDP and TCP) Port 80 (TCP) Port 500 (UDP) Port 3544 (UDP) Port 4500 (UDP).

In case the issue still persists after the previous steps have been performed here is the official link to all the network troubleshooting steps that can help sort this out for you.

IST 11:15 – A new update is now live for Modern Warfare, but sadly, the changelog says nothing about the Dev error 6034.

GENERAL

The RC-XD has been removed from Buy Stations and is now only available via Containment Monitors.
Fixed an issue causing players to be unable to equip Armor Plates after activating certain Killstreaks or Field Upgrades.
The Containment Protocol missiles will no longer land in the Play Area.
The Containment Protocol missiles have had their sound effects volume reduced.
Fixed a bug causing Loadout Drops to block movement and projectiles after the crate collapses.
King Slayer Trios – The Gas Circle will no longer move completely outside of the Play Area.

BLUEPRINTS

The Swatt Master Blueprint now correctly displays the Electric Dismemberment icon.

ATTACHMENTS

Fixed a bug with the Modern Warfare Sniper Scope and Variable Zoom Scope where they were not displaying glint.
Fixed a bug with Modern Warfare weapon perks where they were not having their intended effects.
Fixed a bug with the Bullseye Reticle where it would sometimes cause frame rate issues or the disappearance of UI elements.
Sorokin 140mm Auto (Sykov)
Hip spread increased
Akimbo (Sykov)
Movement speed reduced by 5%
80 Round Drums (Sykov)
Movement speed reduced by 5%
ADS movement speed reduced by 7%
When equipping the Sykov with the Sorokin 140mm Auto and the Akimbo* attachment, damage is reduced by 25% and capped at a minimum of 19.

IST 01:15 – While deleting the corrupted files (as stated in this article) is a workaround to fix this issue, it’s worth stressing that keeping the GPU drivers updated is yet another way to avoid issues on COD Modern Warfare.

As a basic troubleshooting step, you may also scan and repair game files by:

Heading to Battle.net or Blizzard client> Selecting the game you wish to repair> In the middle of the screen, click on drop-down arrow near Options> Click on Scan and Repair> Begin Scan.

IST 02:15 – Changing the Wifi router’s DNS settings may also help to resolve the issue being discussed.

OpenDNS

PRIMARY: 208.67.222.222
SECONDARY: 208.67.220.220

Google DNS

PRIMARY: 8.8.8.8
SECONDARY: 8.8.4.4

IST 11:15 am – As if Dev error 6034 wasn’t enough, those who were earlier encountering this problem say the error has now changed to a “Transmission error” (as can be seen in the image below).

@ATVIAssist
hello, I messaged in the past for assistance with maps not working and had no reply (I had dev error 6034 when playing certain maps)
Updates game today and checked. It now says “disconnected via transmission error” can I get any support with this please? Many thanks
Source

So dev error 6034 is changed to transmission error? Got it. Why can’t you fix this
Source

So goes from dev error 6034 to transmission error. Wow
Source

Apart from the above, Activation has updated the known issues page fixing the following issue:

Black Ops Cold War Starter Pack

We fixed an issue where players who did not have Call of Duty: Black Ops Cold War installed were not receiving their content in Warzone after purchasing the Black Ops Cold War Starter Pack.

NOTE: We’re conducting a poll to know if game players would like to see Battle pass again. So share your opinion with us.

P.S. Many COD Mobile users are troubled with “Authorization error 5 1200.” For details and workaround, head here.

Microsoft agent/moderator at the community are directing the affected users to troubleshoot NAT errors and multiplayer game issues by heading here for a step-by-step troubleshoot guide.

IST 11:55 am Call of Duty has once again thrown an error and this time it is the “Dev error 5573” which kicks gamers out of the lobby and won’t let them play the game. Workarounds here.

IST 01:55 pm Multiplayer is not working for many, the problems joining multiplayer games, or finding other players has been officially acknowledged by Xbox support.

We are aware that some users may be experiencing issues connecting to multiplayer activities in Call of Duty: Black Ops Cold War. Stay tuned here and on our status page for updates. http://xbox.com/status

IST 07:35 pm Going by the reports doing rounds on Twitter, apart from dev error 6034, dev error 6068 is also troubling some users.

IST 05:48 pm It appears that Dev errors have become a lot more frequent in COD: Warzone after every patch or update. Do you agree or have you not come across any such issues? Let us know by voting in our poll here.

IST 12:15 pm While the game is getting a new update, sadly, dev error 6034’s addressal is still not mentioned in the patchnotes.

IST 12:15 pm For Warfare Dev error 6065/6066/6068, here’s what the official ‘Known Issues in Call of Duty: Modern Warfare’ page says:

We’ve identified an issue that is causing hang crashes on the GPU, particularly during Campaign cutscenes. These crashes will be addressed in an upcoming patch.

Workaround: Try running VRAM under maximum and/or run the game with the default settings.

IST 06:05 pm It now seems that many Warzone players are reporting that they’re seeing a ‘Dev error 6661’ message while playing which results in the game crashing.

What is Dev error 6661? Constantly crashing with that error message… Getting pretty annoyed… (Source)

Dev error 6661 and game freezing? 5950x, 3090 fe, 32gb 3600mhz ram and crosshair Vlll hero wifi are all up to date (Source)

Dev error 6661 on pc has been going on for weeks. How about some help with that (Source)

The problem appears to have been around for weeks but there’s no official confirmation.

IST 11:15 am There are a few generic workarounds that you could try out to fix the Dev error 6661 issue in Warzone. The most common of which is to reboot your PC or console.

This usually fixes most bugs and issues, hence the reason why it’s the first thing most support teams recommend doing.

Alternatively, you could do a complete power cycle on your PC or console by turning it off and disconnecting it from the power source. Then wait for 30 seconds and plug it back and turn it on.

Next, you can repair the game via the Battle.net launcher (Blizzard). Simply select the game from the left panel and then click the gear icon (settings icon) and select ‘Scan and Repair’.

You may also want to try updating the game to the latest available version in case you’re facing a problem. This should fix most problems that pop up as a result of the game being played on an older version.

IST 13:15 pm In order to fix the “disconnected due to transmission error” here’s what you need to do apart from the usual troubleshooting steps of rebooting and re-installing the game:

Change the NAT type to open on your router, now go to UPnP in the router settings, and enable the option, save the settings, and restart the router. This should help.

IST 16:15 pm A new update recently went live for COD Warzone. Unfortunately, it too does not bring any fixes for the issues discussed here. Hence, users may have to wait a bit longer for the bugs and errors to be ironed out.

Well, well, while so far the problem appeared to be at the game’s end, now things have taken a bad turn as the hackers are reportedly able to send the Dev errors to other players, ruining their experience. For more details, head here.

PiunikaWeb started as purely an investigative tech journalism website with main focus on ‘breaking’ or ‘exclusive’ news. In no time, our stories got picked up by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and many others. Want to know more about us? Head here.