Thank you for the report.
Can you please provide us with more crash dump files?

Hello Vovka_Novikov.
According to your dxdiag, you are running the AMD Athlon(tm) II X4 640 CPU, which is a 2010 processor that is below minimum requirements and not supported.
In such case there is nothing we can do on our end.

Also, are you by any chance running an older CPU, possibly from AMD? Can you please provide a dxdiag file from your computer?

Hello again.
We have checked your dxdiag more thoroughly.
The dxdiag show you are running Intel Xeon X5365 Processor which is a 2007 CPU Which is below minimum requirements and it is not supported. In such case there is nothing we can do.
Regards,
Geez

Hello again.
Are you possibly running an older CPU from AMD? If so, then most likely you are running unsupported hardware below minimum requirements.
Regards,
Geez

Hello B
The dxdiag show you are running AMD Phenom(tm) II X6 Processor which is a 2010 CPU Which is below minimum requirements and it is not supported. In such case there is nothing we can do.
Regards,
Geez

Hello Farmacevt.
The dxdiag show you are running AMD Phenom(tm) II X6 1055T Processor which is a 2010 CPU Which is below minimum requirements and it is not supported. In such case there is nothing we can do.
Regards,
Geez

Hello redbuddha.
AMD Phenom II X6 1090T 3.7ghz is a 2010 CPU Which is below minimum requirements and it is not supported. In such case there is nothing we can do.
Regards,
Geez

Hello AlexWorkgroup.
Don't call SetOrientation, SetPosition or SetTransform on physically simulated objects.
Regards,
Geez

вчера поиграл в нее 5 часов на windows 11 pro 24h2 обновление 10.2024, переустановил систему на windows 11 pro 24h2 оюновление 02.2025 самую свежую официальную, но ошибка все таже

+1 from me, just stumbled upon this ticket. I rarely play on official due to cheaters. There are good and well working community servers that take care of the issues.
BE is not really helping, they don't seem to be able to track cheaters properly and I also know about false positives - and there is no way to get this issue solved.
Its far from optimal - and without community servers I would not be playing DayZ anymore.

Hello. Please check the following:
When starting my game with BattlEye enabled, I get the following error message: “Windows cannot access the specified device, path, or file. You may not have the appropriate permission to access the item.”

@TheRealLowlife

@Geez Resolved, mod causing the issue was singled out and removed

In T189830#2775168, @lava76 wrote:

No, it's very much related. The muzzle index being wrong on load is just an effect of the bug.

I've moved that into https://feedback.bistudio.com/T190201 - the muzzle error is a bug on its own.

No, it's very much related. The muzzle index being wrong on load is just an effect of the bug.

Same here...
Server start -> file gets created at 0KB
player enters -> no change...
player leaves afer a while -> no change...
Server resatrt -> no change...

I think this might need to go into a bug report on its own, this one is really about a bug in weapon/muzzle handling.

@lava76 I've changed the code to

+     FileSerializer s = new FileSerializer();
+         s.Open("$profile:test2.bin", FileMode.WRITE);
+         s.Write("TEST");
+         s.Close()
+     for (int i = 0; i < 2; i++)
+     {
+         s.Open("$profile:test2.bin", FileMode.APPEND);
+         s.Write("TEST");
+         s.Close();
+     }

My first observation is: test.bin does not get written at all on s.Close() - its still empty after the server started.
The server crashes on shutdown and the file is gone (!)
After the restart, the file is empty again...

In T189830#2775121, @lava76 wrote:

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):

FileSerializer s = new FileSerializer();
for (int i = 0; i < 2; i++)
{
    if (s.Open("$profile:test.bin", FileMode.APPEND))
    {
        s.Write("TEST");
        s.Close();
    }
}

After running that, the file test.bin in your server profile directory should contain (hex) 04 00 00 00 54 45 53 54 04 00 00 00 54 45 53 54 (same string twice). If it only contains 04 00 00 00 54 45 53 54 (once), then that's indeed the mode of failure.

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.