Is This Game Down
Browse games
You can fix thisReported

DayZ crashes after the server queue (Badlands, 1.30)

DayZ server status →

Written by

IsThisGameDown

Last checked

October 16, 2026

Steam Discussions: Game is Crashing After 1.3 Update BADlands ↗

DayZ closes with no error message, or shows a crash report such as "Exception: Access violation", right when the server queue reaches 0 and the loading finishes. Players report it mostly on Badlands (Nasdara) servers since Update 1.30 on October 15, 2026.

Also appears as: dayz crashes after queue, dayz crash when joining server, dayz crashing with nvidia filters, dayz crashing after queue no error, Data Verification Error, Data Error, dayz badlands crash, dayz nasdara crash, Exception: Access violation, ExceptionCode c0000005, game closes when queue reaches 0

This looks like a bug in the 1.30 game client that some players can get around on their own PC. The crash report players post shows Access violation and ExceptionCode c0000005, which only says the game touched memory it shouldn't. Bohemia Interactive hasn't acknowledged it in anything we found.

The best-supported workaround is turning off NVIDIA's "Smooth Motion" (posters wrote "smooth movement"). Three players in two Steam threads said it got them in, and a fourth recommended it. Other tips split the thread, and some players still crash on community servers.

Bohemia's October 15 post says a first 1.30 patch for Steam experimental was aimed at October 16 and a stable patch will follow "at a later date". Neither is said to fix this crash. Check the live status page for news.

Fix it, step by step

  1. Turn off NVIDIA Smooth Motion in the NVIDIA app

    In a Steam thread titled "Game is Crashing After 1.3 Update BADlands", one player advised that if "smooth movement mode" is enabled in NVIDIA you should turn it off, and another said that after turning it off they were able to get in. In a Russian-language thread, a player with an RTX 5070 Ti said disabling "smooth motion" in the NVIDIA app let them play and join servers again, adding that the crashes began after the experimental update. A second poster there said it fixed their crash too. That is three players who say it worked, plus the one who suggested it, all player reports.

  2. Start DayZ from the DZSA launcher instead (one report)

    In the Russian-language "Crash after queue" thread, one player said trying the DZSA launcher worked after reinstalling and changing network settings did not. We saw no second player confirm it, and the original poster there said the game still closed on both of their computers.

  3. Close DayZ and rename or delete Documents\DayZ (one report)

    One player in the main thread posted this as "the solution": close the game, rename the DayZ folder inside your Documents folder (for example to DayZ_Old) or delete it, then launch the game so it recreates the folder. Nobody replied to say it worked. Renaming keeps a copy of your settings, so prefer it to deleting.

  4. Join a community server instead of an official Nasdara server

    One player said "Community servers work..." and another said they got into a community server before a restart stopped them. Players on the Russian thread said US servers let them in but with very high ping. A player in the main thread said the crash also happened on official and community servers. Modded servers may be down or missing after 1.30; see the DayZ status page FAQ.

  5. Delete and reinstall the BattlEye anti-cheat (one report)

    On Reddit, a player stuck at "battleye is starting.." after the queue said deleting and reinstalling the BattlEye anti-cheat fixed Nasdara for them. A reply said it did not work for them. In the Steam thread, one player who deleted the BattlEye folder and reinstalled still crashed.

  6. Retry or join an official Nasdara server straight away (one report each)

    On Reddit, a player who saw "Data Error" or "Data Verification Error" when reconnecting after the crash said joining an official Nasdara server immediately worked, and another got in after retrying repeatedly. Neither is a tested fix; some reconnects dropped players back into a long queue.

  7. Note

    One player in the main Steam thread said setting video options to medium and verifying the game files worked. At least three others said verifying files, with or without medium settings, changed nothing, and one said the crash came back after an hour. A Reddit moderator suggested verifying files; people in the Reddit threads said it did not help. Reinstalling and restarting also did not help the players who tried them.

    Unconfirmed
  8. Note

    We found no acknowledgement of this crash from Bohemia and no confirmed fix. Bohemia's October 15, 2026 post says a first 1.30 patch for Steam experimental was aimed at October 16 to address "issues that affect modders on Steam", and the stable patch on all platforms "will follow at a later date". That post does not mention this crash, so we can't say a patch will fix it.

    Unconfirmed

Hit this error? Leave a comment

Say where you are, what you see on screen, and whether any fix worked for you.

No links. Anonymous, no account. Keep it about the game.

What people are saying

Notes from players who've hit this one — no time limit, an answer from months ago is still an answer.

  • Nothing reported here yet.
← 0x00010001BATTLEYE-SERVICE-FAILED-TO-INITIALIZE →

Other DayZ error codes

Recently added