Hello Jesser110.
Can you please provide more details?
The Crash reporter process remains open, even though you press Send the report or Close the window?
Can you send us a video? We are not able to produce the issue so far.

The game also doesn't crash (it exits normally like it should), but yet that reporter stays running.

todays screen . . .

Help me pls

A video would have been very useful.

I checked the integrity of the game files, updated the graphics card drivers, and reinstalled the game. nothing helped.

When launching the game through the original launcher, it runs for only a few seconds, then closes and throws an error with the code.
Exit code: 0xC0000005 - STATUS_ACCESS_VIOLATION

Never mind, wrote the changelog and found that one needs does precious keys for it.

todays screen, again (although screen is completely black) I can hear that I have been spawned to a completely different location

Almost 7 days ago I couldn't start Dayz - an Error message popped up (as in the title). I checked the files /verification - nothing, I reinstalled Dayz -/ deleting the remaining files - nothing, I reinstalled the card drivers without enabling overlays and leaving everything on "recommended", the game started - both on Official and Modded servers -, but after a few minutes the icons in the Store started blinking and the game stuttered. I turned on the FPS limitation in Steam and checked the integrity again, the game started - I reduced the settings in the game options to the lowest and now the game crashes after 1 to 2 hours (exactly the same as above), deleting temporary files - also nothing helps with shaders, the diagnostic program shows the parameters of the processor card, memory (clocking temperatures - normal), other games from Steam: Red Dead Redemption 2, Starfield Gray Zone Warfare, or apart from WoWs - war of Warship, work on high settings - without a problem. all guides from the Net, YT, reddit.com do not work. That is why I am asking for help.

This is still going on @Geez? I'd take a look at the net code. It seems like it's a sync issue, the server is seeing the person hit their fire, instead of just raising it.

Strange, there were no errors with mods from Steam Workshop before.
I'll keep watching and try to figure out which mod is ruining everything.

Hello LOUDY.
All of the crash dumps point towards the modded content you are running.
Regards,
Geez

Well there is still no change, hackers online all the time..

And to add that Geez referred to the method i mentioned above, thats now not working

Hello Kjalf.
Please provide detailed description of the problem you are experiencing.
Regards,
Geez

Thank you for the report.
This will be investigated by BattlEye.
Regards,
Geez

Hello omeba.
Can you please describe the issue in greater detail? As we are not sure what do you mean by

when the startup is delayed, an error occurs on the server.

Hello Airsking.
Please uninstall all the mods you are running and check if this occurs on vanilla server. If not, the problem is in the modded content you are running.
Regards,
Geez

Hello Pamplinas.
Please provide detailed information about the problem you are experiencing.
Regards,
geez

Thank you, this will be investigated by BattlEye.
Regards,
Geez

Thank you, seems to be related to the mods you are running.
Therefore there is nothing we can do.
Regards,
Geez

But look - they fixed official server listing by implementing pub-key verification :D

Also something I noticed is, that the CommandHandler(float pDt, int pCurrentCommandID, bool pCurrentCommandFinished) method is not called on the server while in this bugged state and as soon as it starts working again, this is called (this is also where the stamina handler is syncing the stamina)

https://youtube.com/shorts/HYGOL4kf5wU?feature=share

Well, the developers absolutely don’t care about this clownery in their own launcher ;)

Merci de régler se bug

FIX IT

Hi, Geez, I wrote the name in the launcher and everything worked, thank you so much. To answer the question, yes, the problem appeared on its own, I did not log into the game for about 6 months, and it appeared. I was kicked out immediately after trying to connect to the server. There was no such advice on the Internet. Thanks again.

Nevermind I figured it out. Delete.

Just to confirm that the fix above works a treat .. go onto documents , make a copy of dayz , delete the non copy dayz ,download dayz experimental , open it join game n close it down no back to documents, change the name of dayz exp to just dayz ..inside the dayz folder you just renamed change the name of dayz exp.cfg to dayz.cfg ..now run it ..should work just fine

What are you refuting exactly?
Did you try the above code snippet to find what yours is tripping on?

I've created a workaround now, which basically adds an additional TextWidget on top of the checkbox and moved it a few pixels to the right and then I set the text there and this works fine, but since the checkbox can have it's own text, this should not be the fix for it ^^

In T187950#2737908, @elemenopyunome wrote:

this is related to rag_baseitems, i've sent this notice to the mod author

Function: 'Error'
Stack trace:
scripts/1_Core/proto\endebug.c:92
CakeFactoryLiquidCrashingDetection/scripts/4_World/itembase.c:6
DayZExpansion/VanillaFixes/Scripts/4_World/dayzexpansion_vanillafixes\entities\itembase.c:8
scripts/4_World/entities\itembase.c:4648
scripts/3_Game/entities\entityai.c:2291
scripts/4_World/entities\itembase.c:4548
scripts/4_World/entities\itembase.c:4616
scripts/3_Game/entities\entityai.c:3783
DayZExpansion/Core/Scripts/4_World/dayzexpansion_core\entities\itembase.c:1259
SCRIPT    (E): 
Item rag_baseitems_coffee_mug_rag is misconfigured - liquid type 607 is not in CfgLiquidDefinitions!
Class:      'rag_baseitems_coffee_mug_base'
Entity id:2999323

The DayZ Community Server List's fake server issue has persisted for years. During this time, I've witnessed many community members reporting this problem to the officials, yet there has never been a direct response. I've reported this issue multiple times only to receive warnings and bans. As Geez mentioned, the officials have shown no progress in addressing this problem.

Reporting problems is good.
Creating new, duplicated tickets, even though you're fully aware that tickets for the issue already exist, is spam.
You insulting and throwing slurs at developers, now that gets you banned. Try to behave.

They beat the shit out of you pretty good

Ошибка 0xC0000005 - STATUS_ACCESS_VIOLATION