It looks like FileMode.APPEND does not work under Linux, the file is seemingly overwritten if opened in that mode. Note that I'm basing this off logs and files that people have sent me, as I currently don't have a Linux testing setup. If you want to test this theory, put this code into your init.c (e.g. at the bottom of the main function):

@lava76 indeed that case crashes on linux. I've debugged that in an older version of https://steamcommunity.com/sharedfiles/filedetails/?id=3381664818 and the mod was rewritten to use proper constructors and super calls as you would do it in c++, which fixed the segfault. The original constructor was in the form as mentioned above, rather simple, some variables in the child class, and the access to the base class segfaulted.

I tested it with opening launcher as admin. First time worked fine and second and third time same error.

I did give full permission to authenticated users, problem is still there.

To share the information I have up to this point, the issue seems to be related to FileSerializers. It looks like they cannot reliably be written, and maybe also not reliably be read, under Linux. The failures seem to be silent during the actual write/read, i.e. the game doesn't print or otherwise hint at anything being wrong, which is why the effects of these failures crop up later when the read data is attempted to be used.

We'll fix this, thanks!

There is no such thing as an uninitialized variable in EnforceScript. All variables are initialized to a default on declaration if there is no direct assignment (bool false, float 0.0, int 0 , string "", vector "0 0 0", anything other NULL), and this is a core language feature. Think Java/C#, not C/C++. The above example is valid code and completely fine. If that indeed crashes under Linux(?), that's a bug that needs to be fixed on that platform.

It also occurred to me how much Linux and how much Windows. My server runs on Linux. I'm going to try it on Windows, because I'm starting to get nervous.

Now let's get an overview of how many of these servers that are having problems are running under Linux like the OP.

we found a way to stop the crashing. we have removed all the revolvers (No matter If modded ones or the Vanilla one). Since that we dont have issues anymore. Try it maybe it will help you too. BUT we still have other fsm errors that are not related to the
revolvers, those dont crash the server.

In T190087#2774418, @Single_360 wrote:

Tried to search in the paste but didn't found it

EDIT: After doing a hell of updating my Drivers, it partially fixed. But now that DayZ updated, it is giving STATUS_ACCESS_VIOLATION error.
Here's the logs now:

DayZ_x64_2025-03-18_14-24-52.RPT11 KBDownload

DayZ_x64_2025-03-18_14-25-10.mdmp456 KBDownload

I believe those errors is happening because of the new Upd, and the servers might hasn't been updated yet.

This isn't a specific point issue.

Thank you.
The error is provided by Windows and not DayZ. Probably only a full windows re-install can help as the error isn't pointing to what is causing the error. Typically this error should include a path to the dll that is faulty but in this case it is blank.

Hey Geez,

Known issue. Closing the ticket as duplicate.

@Geez
Sooner or later, everyone will have such a crash. This crash happens on all servers. Somewhere more often, somewhere less often. Tell us what information we need to provide so that you indicate what exactly affects the crash? Stack trace shows vanilla functions. I tried to completely limit it, it did not help me

In 1.26 and 1.27 I regularly see a segfault when dayz is shutdown with the rcon shutdown command, but it doesn't seem to appear (or at least less...) when I send a TERM signal. Haven't seen a double free on shutdown yet.

Thank you for the report.
All hacking incidents are being investigated by BattlEye.
Regards,
Geez

Hello Necronon.
All hacking incidents are being investigated by BattlEye.
Unfortunately we do not reimburse any lost gear.
Regards,
Geez

Hello TityBoiTyler.
Can you please describe the issue in greater detail? Is there some sort of error? Can you take a screenshot?

Hello B1995.-
Please try the following:

Anybody else have this fault.
Any fixes available.
Cannot play DayZ or Arma3 anymore!!!

у меня не заходит в игру.зависает на черном экране.Потом игра не отвечает

Hey, we're facing the same issue regarding the error "Weapon.OnStoreLoad <WEAPON> trying to set muzzle index 5 while it only has 1 muzzles!".
Unfortunately we have not found any clear evidence when it occurs, sometimes 2 hours after serverwipe, sometimes 2 days.

3 Servers have been good so far since update.

So I run 6 live servers, 3 of them have been crashing multiple times per restart since 2-25. Those 3 servers just went a full restart, 3 hours, without a crash. This is a good sign.

In T189830#2774524, @fraky wrote:

It's the same for me, after restarting the server, health and water are reset to the default 599. and the player's ammo is replenished to a full 20 pieces, if he had less. I'm going to cry in the corner.

I've switched back from 2 to 4 hour restarts and turned on airdrops. Will report back if any crashes.

It's the same for me, after restarting the server, health and water are reset to the default 599. and the player's ammo is replenished to a full 20 pieces, if he had less. I'm going to cry in the corner.

It really feels like someone is saying, Lets add this to the game, someone quickly writes up a config, implements it, passes it to QA, QA goes. yup, it's there.

@Geez bump. This is still an ongoing issue.

2 updates in a row where one of my server's dayzserver.exe processes is stuck in Windows and can't be deleted/replaced without restarting the bare metal. Lovely.

@Geez I can provide memory dumps / rpt files, or if it helps I can keep the linux core file next time so you can load it into gdb

I had just a crash (after updating to the last release today), with the same origin. Not a vanilla server though:

Tried to search in the paste but didn't found it

In T189290#2774322, @Geez wrote:

In T189290#2774320, @Dirkalot wrote:

Doesn't look like today's hot fix addresses this issue.

It is in the patchnotes but under these two tickets T189322 and T189419 :)

@Geez Can you at least give us the information present in the dump files? What are the values of variables in the stack at the time? What are the classnames of the objects failing FSM state reconciliation? Which objects have been dereferenced? If this is, as you believe, an issue with modded content then we need more information to work around it.

I think it only appears after something was cooked.
Only happens sometimes.

I haven't seen anything, I did see they posted 5 days ago on X, that they were "consolidating" servers due to less demand from previous launches.

In T189290#2774322, @Geez wrote:

In T189290#2774320, @Dirkalot wrote:

Doesn't look like today's hot fix addresses this issue.

It is in the patchnotes but under these two tickets T189322 and T189419 :)

Unfortunately so far we are unsuccessful in replicating the issue

[ OK ] Updating dayzserver: Checking for update: SteamCMD

In T189290#2774320, @Dirkalot wrote:

Doesn't look like today's hot fix addresses this issue.

Doesn't look like today's hot fix addresses this issue.

@fraky what you are describing sounds like https://github.com/Arkensor/DayZ-CommunityFramework/issues/183 - which actually points to https://feedback.bistudio.com/T189290. The Muzzle error is - at least in my experience - not related to that.

@Geez Hello. Do you have enough information that more and more new players provide?

Could anyone assist with this error please.
I noticed this just after updating to DayZ 1.27.
my DayZ game loads until the very last loading window just before entering a server (Any server)
It then crashes with a report 0xC000001D-STATUS_ILLEGAL_INSTRUCTION

Hello, Unfortunately there is no Estimate I can provide.

It is in the appdata folder where the other files such as .RPT are found

Thank you.
Known and reported issue - closing the ticket as it is a duplicate.

Thank you for the report.
This is known and previously reported issue. Closing the ticket as it is a duplicate.

Hi,
any idea how to solve it? I made a new server without Expansion mod, because I assumed that the problem was there. But apparently it wasn't, only when using Expansion mod the server crashed when an error occurred with muzzle index. I tested the server myself for three days with about KA-101 weapons, ACC Honey badger from SNAFU mod. The problem didn't appear for me. Yesterday other players joined and the problem is back. The server doesn't crash, but the error message is displayed:

I agree, the footsteps sound insanely loud now. I feel as though someone is right beside me only to realise they are 15-25 meters away.

It would be nice to have ammo always automatically stacked. When unloading a magazine, the ammo should go to an existing stack if it exists. Same for picking up ammo in the world.

It's for the CF maintainer so it must be important ! :)

Thanks for answer, Geez.
Sorry if i sound a litte dumb, but where is this .mdmp file located? Is it in the logs folder too?

Can you share me some ETA?
We'd be very happy if this bug will be fixed in the upcoming update.
Because of this bug the development of one of our mods is put on pause.

Нет.

It would be nice if recent changes to audio and sounds were re-evaluated (and maybe also the people who are in charge of it). I get that DayZ isn't necessarily supposed to be pleasant, but using the technical aspects of the game to make players miserable shouldn't really be on the table.

Here is a scrubbed snippet from the RPT just before the server freezes. It shows 5 players connect and are put into WaitPlayerAssignedLoginState state. But this happens before the server is unlocked, which seems suspicious to me. Is this expected for players to be able to connect before the server is unlocked?

Hello Toggy.
The issue seems to be related to the modded content you are running.
Can you try to launch the server with no mods and fresh storage? If the issue does not occur when doing so, then the issue is in the mods.

Hello GOLD.
This seems like an issue related to the modded content you run.
You can try the following:
Try to verify the game and make sure your mods are up to date
If this does not help - unsubscribe and delete the mods
Delete the game profiles/configuration files
Verify the game data through Steam
Try to launch the game and join a server without mods
Subscribe back to the mods you have had previously

Hello.
The crash dumps point towards crashes when exiting the game.
We are aware of those and they are scheduled for a fix.
Regards,
Geez