Call of Duty: Warzone Error Codes

Warzone's named error codes (Diver, Vivacious, Marlinโ€ฆ) are mostly connection, file, or install problems layered on top of Battle.net/Steam. Here's what each one means and the fix that gets you back into a match.

Error codes

Diver Lost connection to the Warzone servers

Cause: An unstable connection, NAT type, or an Activision-server issue.

Fix:
  1. Restart the router and use a wired connection.
  2. Set an Open NAT (enable UPnP or port-forward the CoD ports).
  3. Check the Activision Online Services status page.
Vivacious Connection to the online services was interrupted

Cause: A dropped connection to Activision/Demonware, often mid-load.

Fix:
  1. Flush DNS (ipconfig /flushdns) and restart the router.
  2. Disable VPN and allow the game through the firewall.
  3. Retry โ€” it's frequently a temporary server hiccup.
Marlin Server connection failed

Cause: A network or account-services problem reaching Warzone.

Fix:
  1. Restart the game and launcher (Battle.net/Steam).
  2. Power-cycle the router; try a wired connection.
  3. Confirm your Activision account is linked to the platform.
Fuego General connection error to Warzone

Cause: Network instability or a server-side outage.

Fix:
  1. Reset the router and check for an Activision outage.
  2. Disable VPN/proxy.
  3. Set NAT to Open.
BLZBNTBGS4000... (Battle.net) Battle.net can't reach the game servers

Cause: A Battle.net connection block or region issue.

Fix:
  1. Restart Battle.net and flush DNS.
  2. In Battle.net โ€บ Settings, remove any forced region/proxy.
  3. Whitelist Battle.net and the game in the firewall.
Dev Error 6xxx / 5476 / content still installing The game crashes or won't start due to files

Cause: Corrupt game files, an incomplete texture install, or shader/driver issues.

Fix:
  1. Scan and Repair the game in Battle.net (or Verify on Steam).
  2. Let all optional/high-res packs finish installing before playing.
  3. Clear the shader cache in-game and update the GPU driver.

Fixes that work for most Call of Duty: Warzone errors

  1. Fully quit the client from the system tray (right-click โ€บ Exit), then reopen it โ€” a half-loaded client throws most generic errors.
  2. Restart your PC and router, and on Windows flush DNS (Command Prompt: ipconfig /flushdns).
  3. Update or reinstall the client to the latest version โ€” many 'connection' or 'version' errors are just an out-of-date client.
  4. Temporarily disable VPN and add the client as an exception in your antivirus/firewall, then retry.
  5. Check the service's official status page or its X/Twitter โ€” if the servers are down for maintenance there is no local fix; wait it out.

FAQ

How do I fix the Warzone 'Diver' error?

Diver is a lost connection to the Warzone servers. Restart your router and switch to a wired connection, set an Open NAT type (enable UPnP on the router or port-forward the Call of Duty ports), and check the Activision Online Services status page in case the servers are down. Disabling any VPN also helps.

What does a Warzone Dev Error mean?

Dev Errors (6xxx, 5476, and similar) are game-file or graphics problems, not connection issues. Run Scan and Repair in Battle.net (or Verify integrity on Steam), let all optional high-resolution and shader packs finish installing before you launch, clear the in-game shader cache, and update your GPU driver.

Other games