Читер на сервере 5420

Getting same crash like crazy
Function: 'SaveCurrentFSMState'
Stack trace:
scripts/4_World/entities\firearms\weapon_base.c:564

In T189487#2763107, @Geez wrote:

Hello LarryTheExplorer.
Are you still experiencing this sort of issue at the moment?

Getting this as well with the muzzle errors and the weird crashing, also running Linux (Centos 9)
Changed maps, fresh wiped, played with no mods, and eventually still ran into the error.

KERSAN KAIFAT ник в игре

и как долго рассматривается заявка

Having the same issue since 1.27 hotfix update{F5114147}

Hello official server player called me N word I clipped it how I send you can you bann him?

In T189290#2776759, @Corse wrote:

Since the update the server has mostly been stable but I am seeing a new behavior. Now instead of the server crashing, some players will log in and then crash to a 0xc0000005 error. When this happens, the server freezes on the number of players and will continue reporting that number, being unresponsive. No crash logs, it just hangs until it's restarted.

It seems only some players are affected by this. For most, everything is fine. Only some players have this happen, and the freeze and crash for them is random and then they are unable to log back in unless their entry in playerdb is wiped.

This is after a completely fresh install and wipe. Currently hosting on centos 9

Since the update the server has mostly been stable but I am seeing a new behavior. Now instead of the server crashing, some players will log in and then crash to a 0xc0000005 error. When this happens, the server freezes on the number of players and will continue reporting that number, being unresponsive. No crash logs, it just hangs until it's restarted.

This may be related to some code me and SFM recently added to our servers, I found that running Delete() for an item in hand then immediately running ServerTakeEntityToHands() for an item on the floor would consistantly fail to take the item into hands and nothing would happen, so instead I had to call the ServerTakeEntityToHands later like this GetGame().GetCallQueue(CALL_CATEGORY_SYSTEM).CallLater(TakeNewWeaponToHands, 34, false, action_data, G); but possibly in some cases DayZ still has issues knowing if the hand is free or not and it could potentially cause this?

I encountered the same problem on de 3737. I am in full armor, died from an aimbot that shot me through the wall. He is still not banned, you can see it by the number of Chinese nicknames in steam that play on the server, I think they are Chinese, considering the slight delay in registering a hit from the aimbot when he killed me I realized that this guy has a huge ping

You can not combine logs in the base game.

FYI: Adding my old 8 GB block to my laptop, seems to have fixed my problem :)

Thanks for reply,
Had a feeling this might be the issue.
Stretched the PC to the last.
Have to say, it performed well on all games up to now.
Like everyone, we will all be eventually decommissioned, retired
and thrown on the scrap heap.

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