DayZ crashing after the server queue in 1.30: what helps

You wait in the queue for a Nasdara server, the counter reaches zero, the 15-second countdown runs out, and DayZ closes. There’s no error, or a crash report that says Access violation. Start the game again and you’re back at the end of the queue.

Since DayZ Badlands and Update 1.30 came out on 15 October, this has been one of the most common complaints from players. It’s also confusing for server owners, who get the messages and can’t tell whether the problem is theirs. This guide covers what Bohemia has confirmed as of 25 October, the workarounds players have had the most luck with, and what server owners should check so a broken mod isn’t mistaken for the same bug.

What the crash looks like

Reports on Reddit, on Steam and in Bohemia’s bug tracker describe the same pattern:

• You get through the queue, and the usual 15-second countdown starts.
• When it ends, the loading bar never fills, and the game closes to the desktop. Sometimes there’s no message at all, and sometimes there’s a crash report with Exception: Access violation.
• Some players then get a data verification error when they try to reconnect.

Most reports come from Nasdara servers, official and community alike.

Crash or kick?

Not every failed join is this bug. A crash closes the game. A kick sends you back to the menu with a message, and the message usually points somewhere else:

What Bohemia has said

Bohemia has acknowledged the crash. Shortly after launch, the official DayZ account listed the game crashing when joining a server after the queue among its known issues. It said the team was investigating several causes, one of which may be related to the Smooth Motion feature in the NVIDIA app, and recommended turning Smooth Motion off as a temporary workaround.

Since then:

• 21 October: Update 1.30.164200 came out on PC and console. Its server notes mention a fix for a specific server crash, but say nothing about queues or joining, so don’t assume it fixed this one.
• 23 October: A player’s report of the crash on Bohemia’s feedback tracker (DZG-1330) was marked as a known issue.

So at the time of writing, the crash is known, it’s being worked on, and there’s no date for a fix. Bohemia hasn’t said what causes it, and Smooth Motion is one lead among several, so treat any single fix with some caution, including the ones below.

Workarounds for players

None of these is a guaranteed fix, and some players still crash after trying all of them. They’re in order of effort, so start at the top, and try joining again after each one.

1. Turn off NVIDIA Smooth Motion

This is the workaround Bohemia recommends. Smooth Motion is the NVIDIA app’s frame generation, applied by the driver rather than the game. Open the NVIDIA app, go to Graphics, and make sure Smooth Motion is off both in Global Settings and in DayZ’s entry under Program Settings. Only recent GeForce RTX cards have the option, so if you can’t find it, it isn’t the cause for you.

2. Drop the graphics preset to Medium

During 1.30’s Experimental phase, one player reported on Bohemia’s tracker that the game crashed on the Extreme preset and loaded normally on Medium, then crashed again as soon as they switched back. A player on Steam has reported the same since launch. Nobody knows yet which setting matters, so take a screenshot of your current settings before you change anything, set the overall preset to Medium, and join from there. Once you’re in, leave it on Medium: switching back is what brought the crash back in that report.

3. Verify your game files

In Steam, right-click DayZ in your library and choose Properties, then Installed Files, then Verify integrity of game files. It only takes a few minutes. It has helped some players and not others, but it rules out a damaged install.

4. Reset your profile files

DayZ keeps your profile and settings in Documents\DayZ. One player on Bohemia’s tracker got past the crash some of the time by deleting their .DayZProfile files, although it came back on later joins, so this is one to try when nothing above has worked. Copy the whole folder somewhere safe first, then delete the files ending in .DayZProfile. The game creates new ones with default settings, so you’ll need to set your graphics and keys again, or copy your old files back once there’s a fix.

5. If it’s a BattlEye kick, reinstall BattlEye

If you’re kicked with a BattlEye message rather than crashing, reinstalling its service is the usual fix after a big update. Close DayZ, and in Steam, right-click DayZ and choose Manage, then Browse local files. Open the BattlEye folder, and run Uninstall_BattlEye.bat, then Install_BattlEye.bat, each as an administrator. This won’t stop the queue crash, but it rules BattlEye out.

Until there’s a fix, pick shorter queues

The crash costs you the whole wait, so the length of the queue decides how much time you lose. Until there’s a fix, a less busy server, or a Nasdara server outside peak hours, means a failed attempt costs you minutes rather than an evening. Bohemia has been adding official Nasdara servers in Europe and North America since launch, with Asia and South America to follow.

Report it

If you still crash, a detailed report on Bohemia’s feedback tracker is more use than another comment on a forum thread. Say which server you were joining, how long you’d queued, your GPU and graphics preset, and whether Smooth Motion was on, and attach the newest crash files from %LOCALAPPDATA%\DayZ.

For server owners: rule out your own server

When players crash on the way into your server, they’ll tell you, and from their side the queue crash looks a lot like a broken server. It’s not one you can fix. But 1.30 also broke a lot of mods, and those problems are yours. These checks make sure the only thing your players are hitting is Bohemia’s bug.

Update the server, CF and every mod

Make sure the server is on the latest 1.30 build: 1.30.164200 at the time of writing. With forceSameBuild = 1, the default, players on a different build can’t join.

Community Framework 1.5.9, released on 13 October, is CF’s 1.30 compatibility release, so update @CF first, then every other mod. A new CF doesn’t fix the mods built on it, though. Each mod with its own 1.30 problems needs an update from its author, so check every mod’s Workshop change notes for a 1.30 build.

Read the script log from the top

A mod that fails to compile under 1.30 usually stops the server starting at all, rather than crashing players one at a time. Open the newest script_<date>_<time>.log in the server’s profile folder and search for (E). Read the first error, not the last: one failure tends to set off dozens more below it, ending in Can't compile "World" script module!. The path after the @ in that first error names the mod.

Remove that mod, along with any mods that depend on it, restart, and repeat until the server starts cleanly. Then add each one back once its author ships a 1.30 update.

The CombinationLock rename

The most common break is a rename in the vanilla scripts. 1.30 replaced CombinationLock.UnlockServer with UnlockOnServer, which takes an extra argument:

// 1.29
UnlockServer(EntityAI player, EntityAI parent)

// 1.30
UnlockOnServer(EntityAI player, EntityAI parent, bool isInsideLock = false)

Any mod that still calls the old name fails with Undefined function 'CombinationLock.UnlockServer', and takes its whole 4_World script module down with it. Base building, admin, raiding and lockpicking mods are the usual suspects. The fix is an update from the mod’s author. Be wary of unofficial “1.30 fix” mods that patch someone else’s mod, since they can clash with the real update when it arrives.

If you’re rebuilding a long mod list for 1.30, Adding 50+ DayZ Workshop mods without corrupting your loot table covers a layout that makes mod updates much easier to manage, and DayZ Nasdara server setup has a checklist for a new Nasdara server’s first week.

Tell your players

Pin a short message in your Discord: a crash as the queue ends is a known 1.30 bug, not your server, and turning off Smooth Motion or dropping to the Medium preset has helped some players. It saves you answering the same question all evening, and it gives players a reason to try again rather than move on to another server.

Until Bohemia ships a fix, turn off Smooth Motion, try the Medium preset, and choose your queues carefully. And if you run a server, get your mods clean, so the only crash your players can hit is the one nobody can fix yet.

Questions

Why does DayZ crash after the server queue?

Since Update 1.30, many players' games close as the countdown at the end of a server queue runs out, mostly when joining Nasdara servers. Bohemia lists it as a known issue and is investigating several causes, one of which may be the Smooth Motion feature in the NVIDIA app. It hasn't said what the cause is.

Has Bohemia fixed the crash after the queue?

Not as of 25 October 2026. The 21 October update (1.30.164200) fixed a server crash, but its notes say nothing about queues or joining, and Bohemia's bug tracker still lists the queue crash as a known issue.

How do I stop DayZ crashing after the queue?

Turn off Smooth Motion in the NVIDIA app, which is Bohemia's recommended workaround, then try the Medium graphics preset and verify your game files in Steam. None of these is guaranteed to work, and some players still crash after trying all of them.

Does the crash only happen after five minutes in the queue?

There's no evidence of a time limit. Bohemia hasn't mentioned one, and players report the crash at the end of the queue however long the wait was.

Can a server owner fix the crash after the queue?

No. It's a crash in the game itself, not in the server. Server owners should still update the server, Community Framework and every mod for 1.30 and check the script log, so a broken mod isn't mistaken for the same bug.