DayZ error 0x00040031: WaitAuthPlayerLoginState (fix)
Written by
Last checked
October 15, 2026
DayZ kicks you while joining a server with "Warning (0x00040031) You were kicked off the game. Login error: Login time out. (WaitAuthPlayerLoginState)".
Also appears as: Warning (0x00040031), You were kicked off the game. Login error: Login time out., WaitAuthPlayerLoginState, AuthPlayerLoginState, 0x00040031, dayz login time out, dayz kicked login timeout
0x00040031 is PLAYER_STATE_TIMEOUT in Bohemia's DayZ error-code wiki: the player spent too much time in one state of the login process. The server log quoted in Bohemia's tracker shows the kick happening in WaitAuthPlayerLoginState, the step where the player's login is authenticated, about ten seconds after BattlEye connected.
Players in Bohemia's Feedback Tracker threads usually fixed it on their own PC, but not always. On August 17, 2023, many players on different servers were kicked at once, and some blamed Steam. Bohemia's tracker account in those threads asked questions but never posted a fix.
Fix it, step by step
Close Discord and other overlay programs before joining
In a 2022 Feedback Tracker thread, three players said turning off unnecessary programs before logging in fixed it, naming Discord in two cases and the Overwolf app in one. Another said running Discord as administrator once and then normally worked. Two other players said closing Discord or running it as administrator changed nothing, and Bohemia's tracker account (Geez) asked whether Discord was up to date with no unofficial plugins.
Log out of Steam, exit it completely, then start it again
One reply (May 2023) in a tracker thread opened in January 2023 said logging out of Steam, exiting Steam and restarting the PC fixed it, guessing that Steam had been logged in too long. In a March 2025 post, another player said fully restarting Steam resolved it and restarting only DayZ did not, and that it happened mostly when jumping from one community server straight to another.
- NoteUnconfirmed
On August 17, 2023 players on several servers hit this together, and restarts didn't help them. One said "Steam is having issues, not DayZ". That is a player's guess, not an official statement. Check the live status page first.
- NoteUnconfirmed
One player said deleting the
DayZ,DayZ LauncherandBohemia_Interactivefolders in AppData fixed it, then said two days later that the problem persisted. Another reported that setting the network adapter's MTU to 1492 let them in once, then the error returned, and that player doubted it works. Neither is a recommended fix.
Sorted. Glad that worked.
Nothing worked. Here's what to do next.
You've ruled out every step on this page, which is useful. Send this to support or drop it in the community Discord so nobody makes you repeat yourself.
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.
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
Other DayZ error codes
Recently added
- AION 2 "insufficient gameplay record" market listing block
- ARC Raiders error ARMR0014 on Storms and Night Raids
- Enshrouded server exits 0xC0000135 on Windows Server Core (fix)
- Gears of War: E-Day stuck on "Fetching Data" (fix)
- Gears of War: E-Day lucas-gnasher: reward expired
- Gears of War: E-Day reaver-tyrus: can't queue ranked
- Valheim server "App 896660 state is 0x6" after update (fix)
- Valheim Unity crash error (0xc0000005): what to try