Nothing we tried helps, I ask you to understand the situation, because it is impossible to tolerate.

https://medal.tv/nl/games/dayz/clips/jVwIgEaML6ds11qLu/spok?invite=cr-MSxRT1QsMTYzMzQ0NDcs.
this is the pov of the thrid death. All 3 deaths were instant and did not care for walls or cover. All 3 characters that died had full plates, full health and balistic helmet.

Thank you, i followed your steps and i managede to play without problems for around 10 min until the game crashed again. i have been playing without crash for about 8 months without any problem, before i changede my ram today.

meant to say no bug report but somehow spelled ban

Thank you.
Please try to disable Steam cloud sync, then delete the DayZ folder in documents and verify the game data. Also please make sure all drivers and software are up to date and there are no corrupted files or installations on your OS (run sfc/scannow).
Regards,
Geez

Hello Rado.
The crash dump points towards nvppex.dll file, indicating a problem with your GPU drivers. Please do a clean installation and check your OS for any corrupted installations/files. Also make sure your system is up to date.
Disabling HWAA in the game might resolve the issue but the root cause is somewhere on your system.
There is also a chance that if you are running Nvidia app instead of Ge-force experience that that is the cause of the problem.
Regards,
Geez

So with the following code

FileHandle handle;
for (int i = 0; i < 2; i++)
{
    handle = OpenFile("$profile:testraw.bin", FileMode.APPEND);
    if (handle) {
        Print("DEBUG APPEND - TEST");
        FPrint(handle, "TEST APPEND");
        CloseFile(handle);
    } else {
        Print("DEBUG FAILED TO OPEN FOR APPEND");
    }
}

@Geez More testing (thanks to @lava76 ) shows that append is also broken for a normal FileHandle.
Also a plain vanilla chernarus seems to have issues with persistance (things don't despawn in time and similar things), so my impression is its broken for the server in general. This is a really major issue, please fix it asap!

Even when you inherit RestCallback in an empty class and create an instance of it, it seems to be leaking

Hello, we will require the whole folder (as a rar or zip archive) containing the rpt, mdmp etc files.

Hello WTE.Ash.
Please check the BattlEye FAQ page https://www.battleye.com/support/faq/ and possibly contact the BE support here: https://www.battleye.com/contact/

I hope that was the correct one :)

Hello tripper.
You can drag and drop the report to this comment window to upload it to the ticket.
Regards,
Geez

Unfortunately no estimates I could provide.

In T189296#2776020, @iNTERCEPT18 wrote:

Can see this is now confirmed internally, great to see this has been recognized. Is there an update to when we might see a fix for this? @Geez

In T190218#2775817, @DrZiLLo wrote:

In T190218#2775658, @Geez wrote:

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

crashs.rar785 KBDownload

THIS!!! <3

Mesmo problema amigo acabei de criar um post deste servidor e do 2242 North America pro Sakhal.

Unhandled exception

Can see this is now confirmed internally, great to see this has been recognized. Is there an update to when we might see a fix for this? @Geez

Can see this is now confirmed internally, great to see this has been recognized. Is there an update to when we might see a fix for this? @Geez

In T190218#2775658, @Geez wrote:

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

At 15.10 - 15.15 Moscow time, I died from a cheater in the village of sinistok, it was on the server Europe de 3737. The guy shot me while behind the wall. He was raiding someone's base with a bolt-action rifle, he shot from it like a machine gun. Anti-cheat does not work as it did 5 and 10 years ago. I have never met so many cheaters in any game

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

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.