In T189923#2779961, @Gooon wrote:

@Geez What else can we do to help you investigate this?

At the moment we do not require any further information.
We are looking into the issue and possible fix will be deployed once implemented and properly tested. I however cannot provide any estimates as to when this could be as this is a more complex issue. Sorry for any inconveniences and thank you for understanding.

Thank you

Hopefully this gets taken care of soon! Would really be nice.

similar problem

Reason: Access violation. Illegal read by 0x7ff6af35bfb0 at 0x8


Class:      'ASVAL'
Entity id:3023575

Function: 'SaveCurrentFSMState'
Stack trace:
scripts/4_World/entities\firearms\weapon_base.c:574

SymGetSymFromAddr:487, addr:0x7ff6af35bfb0
SymGetSymFromAddr:487, addr:0x7ff6af3dfcb9
SymGetSymFromAddr:487, addr:0x7ff6af3e121f
SymGetSymFromAddr:487, addr:0x7ff6af3c5be4
SymGetSymFromAddr:487, addr:0x7ff6af3c2d75
SymGetSymFromAddr:487, addr:0x7ff6af3c79e2
SymGetSymFromAddr:487, addr:0x7ff6af3c324f
SymGetSymFromAddr:487, addr:0x7ff6af5f9714
[CDPInitServer]: ??? addr:0x7ff6af7b2359
[CDPInitServer]: ??? addr:0x7ff6af79ec98
[CDPInitServer]: ??? addr:0x7ff6af79cc33
[CDPInitServer]: ??? addr:0x7ff6af79f05f
[CDPInitServer]: ??? addr:0x7ff6af7ac020
[CDPInitServer]: ??? addr:0x7ff6af79e38c
[CDPInitServer]: ??? addr:0x7ff6af7bcb3a
[CDPInitServer]: ??? addr:0x7ff6af79e620
[CDPInitServer]: ??? addr:0x7ff6af7afe91
SymGetSymFromAddr:487, addr:0x7ff6af3e514c
SymGetSymFromAddr:487, addr:0x7ff6af3e5c57
SymGetSymFromAddr:487, addr:0x7ff6af3e654b
SymGetSymFromAddr:487, addr:0x7ff6af3ef94a
SymGetSymFromAddr:487, addr:0x7ff6af3ef989
[BaseThreadInitThunk]: ??? addr:0x7fffd9e94de0
[RtlUserThreadStart]: ??? addr:0x7fffdb35ec4b
[RtlUserThreadStart]: ??? addr:0x7fffdb35ec4b

another week, will we get some feedback??

WIN-NO3O948RSQA, 01.04 2025 20:50:07
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\EscapeFromChernarus\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff69863df45 at 0x7

Class: 'WeaponFSM'
Function: 'Write'
Stack trace:
scripts/4_World/entities\firearms\weaponfsm.c:406
scripts/4_World/entities\firearms\weapon_base.c:566

SymGetSymFromAddr:487, addr:0x7ff69863df45
SymGetSymFromAddr:487, addr:0x7ff6983f1384
SymGetSymFromAddr:487, addr:0x7ff698640267
SymGetSymFromAddr:487, addr:0x7ff698625be4
SymGetSymFromAddr:487, addr:0x7ff698622d75
SymGetSymFromAddr:487, addr:0x7ff6986279e2
SymGetSymFromAddr:487, addr:0x7ff69862324f
SymGetSymFromAddr:487, addr:0x7ff698859714
[CDPInitServer]: ??? addr:0x7ff698a12359
[CDPInitServer]: ??? addr:0x7ff6989fec98
[CDPInitServer]: ??? addr:0x7ff6989fc970
[CDPInitServer]: ??? addr:0x7ff698a0cdfc
[CDPInitServer]: ??? addr:0x7ff6989fe31a
[CDPInitServer]: ??? addr:0x7ff698a1cb3a
[CDPInitServer]: ??? addr:0x7ff6989fe620
[CDPInitServer]: ??? addr:0x7ff698a0fe91
SymGetSymFromAddr:487, addr:0x7ff69864514c
SymGetSymFromAddr:487, addr:0x7ff698645c57
SymGetSymFromAddr:487, addr:0x7ff69864654b
SymGetSymFromAddr:487, addr:0x7ff69864f94a
SymGetSymFromAddr:487, addr:0x7ff69864f989
[BaseThreadInitThunk]: ??? addr:0x7ffe0cb84cb0
[RtlUserThreadStart]: ??? addr:0x7ffe0e99edcb
[RtlUserThreadStart]: ??? addr:0x7ffe0e99edcb

WIN-NO3O948RSQA, 31.03 2025 06:59:22
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\EscapeFromChernarus\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff698459864 at 0x10

Function: 'SaveCurrentFSMState'
Stack trace:
scripts/4_World/entities\firearms\weapon_base.c:564

SymGetSymFromAddr:487, addr:0x7ff698459864
SymGetSymFromAddr:487, addr:0x7ff6986241ef
SymGetSymFromAddr:487, addr:0x7ff69863db62
SymGetSymFromAddr:487, addr:0x7ff698625bcf
SymGetSymFromAddr:487, addr:0x7ff698622d75
SymGetSymFromAddr:487, addr:0x7ff6986279e2
SymGetSymFromAddr:487, addr:0x7ff69862324f
SymGetSymFromAddr:487, addr:0x7ff698859714
[CDPInitServer]: ??? addr:0x7ff698a12359
[CDPInitServer]: ??? addr:0x7ff6989fec98
[CDPInitServer]: ??? addr:0x7ff6989fcc33
[CDPInitServer]: ??? addr:0x7ff6989ff05f
[CDPInitServer]: ??? addr:0x7ff698a0c020
[CDPInitServer]: ??? addr:0x7ff6989fe38c
[CDPInitServer]: ??? addr:0x7ff698a1cb3a
[CDPInitServer]: ??? addr:0x7ff6989fe620
[CDPInitServer]: ??? addr:0x7ff698a0fe91
SymGetSymFromAddr:487, addr:0x7ff69864514c
SymGetSymFromAddr:487, addr:0x7ff698645c57
SymGetSymFromAddr:487, addr:0x7ff69864654b
SymGetSymFromAddr:487, addr:0x7ff69864f94a
SymGetSymFromAddr:487, addr:0x7ff69864f989
[BaseThreadInitThunk]: ??? addr:0x7ffe0cb84cb0
[RtlUserThreadStart]: ??? addr:0x7ffe0e99edcb
[RtlUserThreadStart]: ??? addr:0x7ffe0e99edcb

WIN-040M49FQNLM, 31.03 2025 21:17:33
NULL pointer to instance
Class: 'WeaponFSM'
Function: 'SaveCurrentFSMState'
Stack trace:
scripts/4_World/entities\firearms\weaponfsm.c:406
scripts/4_World/entities\firearms\weapon_base.c:566

Runtime mode
CLI params: config serverDZ.cfg.active port 2302 profiles profiles adminlog freezecheck mod @CF;@GameLabs;@Dayz Editor Loader;@Mag Obfuscation;@VPPAdminTools;@Item Rarity;@DayZ-Expansion-Core;@DayZ-Expansion-Licensed;@DayZ-Expansion-Hardline;@DayZ-Expansion-Personal-Storage;@DayZ-Expansion-Market;@DayZ-Expansion-Animations;@DayZ-Expansion-Quests;@FlipTransport;@Forward Operator Gear;@CorpseSearching;@CJ187-LootChest;@WindstridesClothingPack;@Dabs Framework;@NoRelogHere;@SkyZ - Skybox Overhaul;@RedFalcon Watercraft;@RedFalcon Flight System Heliz;@Stalker NewHorizon Objects;@DayZ-Expansion-Vehicles;@Vehicle3PP;@RA Base Building;@Dogtags;@BuildingsMegaModPack;@GSC Gameworld Assets;@Inventory Move Sounds;@LootChest Keys;@DayZ-Expansion-Map-Assets;@Care Packages V2;@Escape From DeerIsle;@DeerIsle; serverMod @ServerMod;

WIN-040M49FQNLM, 31.03 2025 21:17:34
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\EscapeFromDeerIsle\DayZServer_x64.exe
Reason: Access violation. Illegal write by 0x0 at 0x0

Function: 'SaveCurrentFSMState'
Stack trace:
scripts/4_World/entities\firearms\weapon_base.c:564

WIN-040M49FQNLM, 31.03 2025 14:34:10
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\EscapeFromDeerIsle\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff7dfd39864 at 0x10

Function: 'SaveCurrentFSMState'
Stack trace:
scripts/4_World/entities\firearms\weapon_base.c:564

SymGetSymFromAddr:487, addr:0x7ff7dfd39864
SymGetSymFromAddr:487, addr:0x7ff7dff041ef
SymGetSymFromAddr:487, addr:0x7ff7dff1db62
SymGetSymFromAddr:487, addr:0x7ff7dff05bcf
SymGetSymFromAddr:487, addr:0x7ff7dff02d75
SymGetSymFromAddr:487, addr:0x7ff7dff079e2
SymGetSymFromAddr:487, addr:0x7ff7dff0324f
SymGetSymFromAddr:487, addr:0x7ff7e0139714
[CDPInitServer]: ??? addr:0x7ff7e02f2359
[CDPInitServer]: ??? addr:0x7ff7e02dec98
[CDPInitServer]: ??? addr:0x7ff7e02dcc33
[CDPInitServer]: ??? addr:0x7ff7e02df05f
[CDPInitServer]: ??? addr:0x7ff7e02ec020
[CDPInitServer]: ??? addr:0x7ff7e02de38c
[CDPInitServer]: ??? addr:0x7ff7e02fcb3a
[CDPInitServer]: ??? addr:0x7ff7e02de620
[CDPInitServer]: ??? addr:0x7ff7e02efe91
SymGetSymFromAddr:487, addr:0x7ff7dff2514c
SymGetSymFromAddr:487, addr:0x7ff7dff25c57
SymGetSymFromAddr:487, addr:0x7ff7dff2654b
SymGetSymFromAddr:487, addr:0x7ff7dff2f94a
SymGetSymFromAddr:487, addr:0x7ff7dff2f989
[BaseThreadInitThunk]: ??? addr:0x7ffc6aad4cb0
[RtlUserThreadStart]: ??? addr:0x7ffc6be1edcb
[RtlUserThreadStart]: ??? addr:0x7ffc6be1edcb

@Geez Another update came out today, was the issue in this ticket fixed with this update or do we have to wait some more?

In T189923#2784140, @ArtemDozhd wrote:

@Geez Another update came out today, was the issue in this ticket fixed with this update or do we have to wait some more?

There was no fix in this update for this issue.

@Geez What are we supposed to tell our clients when the server has been crashing every half hour for close to 2 weeks, and the latest hotfix is for “farming”?. What progress have you made with this issue considering it is affecting MANY large servers?

dropping min in here.

This happens all day. That's just the last three.

Here comes the weekend again, player count constantly dropping and no status update on this issue

Same error today

MSK-TR-1940, 05.04 2025 14:42:04
Unhandled exception

Program: D:\DZ\servers\FAS_CHERNO_1\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff6eba39864 at 0x10

Function: 'SaveCurrentFSMState'
Stack trace:
scripts/4_World/entities\firearms\weapon_base.c:564

SymGetSymFromAddr:487, addr:0x7ff6eba39864
SymGetSymFromAddr:487, addr:0x7ff6ebc041ef
SymGetSymFromAddr:487, addr:0x7ff6ebc1db62
SymGetSymFromAddr:487, addr:0x7ff6ebc05bcf
SymGetSymFromAddr:487, addr:0x7ff6ebc02d75
SymGetSymFromAddr:487, addr:0x7ff6ebc079e2
SymGetSymFromAddr:487, addr:0x7ff6ebc0324f
SymGetSymFromAddr:487, addr:0x7ff6ebe388b4
[CDPInitServer]: ??? addr:0x7ff6ebff14f9
[CDPInitServer]: ??? addr:0x7ff6ebfdde38
[CDPInitServer]: ??? addr:0x7ff6ebfdbdd3
[CDPInitServer]: ??? addr:0x7ff6ebfde126
[CDPInitServer]: ??? addr:0x7ff6ebfeb1c0
[CDPInitServer]: ??? addr:0x7ff6ebfdd52c
[CDPInitServer]: ??? addr:0x7ff6ebffbcda
[CDPInitServer]: ??? addr:0x7ff6ebfdd7c0
[CDPInitServer]: ??? addr:0x7ff6ebfef031
SymGetSymFromAddr:487, addr:0x7ff6ebc2514c
SymGetSymFromAddr:487, addr:0x7ff6ebc25c57
SymGetSymFromAddr:487, addr:0x7ff6ebc2654b
SymGetSymFromAddr:487, addr:0x7ff6ebc2f94a
SymGetSymFromAddr:487, addr:0x7ff6ebc2f989
[BaseThreadInitThunk]: ??? addr:0x7ff9d2c74cb0
[RtlUserThreadStart]: ??? addr:0x7ff9d3e7ecdb
[RtlUserThreadStart]: ??? addr:0x7ff9d3e7ecdb

I am also continuing to have these crash logs which in turns causes the server to crash. @Geez this has been an ongoing issue for almost a month. The current state of DayZ community servers have made it almost impossible to keep servers open. Every update that is done breaks so many different things players leave. From the time of your last update you have lost 4.28% of your player base. At what point will you realize you are causing more harm with every update that is pushed? Without modded communities DayZ would have a fraction of its current player count.

CHI-2A31-U33, 06.04 2025 15:50:33
NULL pointer to instance
Class: 'WeaponFSM'
Function: 'SaveCurrentFSMState'
Stack trace:
scripts/4_World/entities\firearms\weaponfsm.c:406
scripts/4_World/entities\firearms\weapon_base.c:566

Runtime mode
CLI params: config serverDZ.cfg.active port 2302 profiles profiles adminlog freezecheck dologs mod @CF;@Dabs Framework;@VPPAdminTools;@Dayz Editor Loader;@BuilderItems;@BaseBuildingPlus;@DayZ-Expansion-Core;@DayZ-Expansion-Licensed;@DayZ-Expansion-Market;@DayZ-Expansion-Quests;@Care Packages V2;@Custom Keycards;@Dogtags;@Code Lock;@Breachingcharge;@BodyBags;@CannabisPlus;@AscentWeapons;@AscentVehicles;@AscentHelis;@FlipTransport;@MuchCarKey;@Ascent_Core;@AscentServerPack;@AscentClothing;@Item Rarity;@Vehicle3PP; serverMod @GameLabs;@No Sickness;@SlowerMetabolism;@RaidSchedule - New and Improved;@BreachingCharge RaidSchedule Compatibility;@Breachingcharge Codelock Compatibility;

CHI-2A31-U33, 06.04 2025 15:50:33
NULL pointer to instance
Class: 'WeaponFSM'
Function: 'SaveCurrentFSMState'
Stack trace:
scripts/4_World/entities\firearms\weaponfsm.c:406
scripts/4_World/entities\firearms\weapon_base.c:566

Runtime mode
CLI params: config serverDZ.cfg.active port 2302 profiles profiles adminlog freezecheck dologs mod @CF;@Dabs Framework;@VPPAdminTools;@Dayz Editor Loader;@BuilderItems;@BaseBuildingPlus;@DayZ-Expansion-Core;@DayZ-Expansion-Licensed;@DayZ-Expansion-Market;@DayZ-Expansion-Quests;@Care Packages V2;@Custom Keycards;@Dogtags;@Code Lock;@Breachingcharge;@BodyBags;@CannabisPlus;@AscentWeapons;@AscentVehicles;@AscentHelis;@FlipTransport;@MuchCarKey;@Ascent_Core;@AscentServerPack;@AscentClothing;@Item Rarity;@Vehicle3PP; serverMod @GameLabs;@No Sickness;@SlowerMetabolism;@RaidSchedule - New and Improved;@BreachingCharge RaidSchedule Compatibility;@Breachingcharge Codelock Compatibility;

CHI-2A31-U33, 06.04 2025 15:50:33
NULL pointer to instance
Class: 'WeaponFSM'
Function: 'SaveCurrentFSMState'
Stack trace:
scripts/4_World/entities\firearms\weaponfsm.c:406
scripts/4_World/entities\firearms\weapon_base.c:566

Runtime mode
CLI params: config serverDZ.cfg.active port 2302 profiles profiles adminlog freezecheck dologs mod @CF;@Dabs Framework;@VPPAdminTools;@Dayz Editor Loader;@BuilderItems;@BaseBuildingPlus;@DayZ-Expansion-Core;@DayZ-Expansion-Licensed;@DayZ-Expansion-Market;@DayZ-Expansion-Quests;@Care Packages V2;@Custom Keycards;@Dogtags;@Code Lock;@Breachingcharge;@BodyBags;@CannabisPlus;@AscentWeapons;@AscentVehicles;@AscentHelis;@FlipTransport;@MuchCarKey;@Ascent_Core;@AscentServerPack;@AscentClothing;@Item Rarity;@Vehicle3PP; serverMod @GameLabs;@No Sickness;@SlowerMetabolism;@RaidSchedule - New and Improved;@BreachingCharge RaidSchedule Compatibility;@Breachingcharge Codelock Compatibility;

We join the common problem! We are waiting for a prompt decision from the developers

This is primarily not a DayZ core issue, but an issue with mods on the server, I have found the core issues and fixed them on our servers.

In T189923#2787568, @DozingChopper wrote:

This is primarily not a DayZ core issue, but an issue with mods on the server, I have found the core issues and fixed them on our servers.

maybe you can tell me what you did? After all, the developers, unfortunately, can't tell me anything, what exactly did you do to fix this problem?

because here most of the servers are quite popular with strong technical skills can't fix this problem, and you found it, I hope that you will share the solution

@DozingChopper What was the fix?

@DozingChopper , could you tell the solution? We've tried everything to fix the problem, but nothing helped. I think it would be nice for community to get this problem solved. Thank you.

Is there any news, gentlemen?

Hello, sorry for tagging, but the problem remains, the leak of players is happening further and further, I think it is unlikely that the person above found a way to solve the problem, because knowing that the problem is quite global, any person would share a solution to the problem to fix this error 'SaveCurrentFSMState'. My friend said that in his discord channel people complain about server crashes, I think he still has the same problem, I ask you to speed up the process of solving the problem, because we are losing the audience that we have been accumulating for so long due to the fact that the server does not work stably, and it consistently crashes 2-3 times a day. Please treat this with understanding, because we have been accumulating this audience for many years. @Geez

We are experiencing the same problem here, with a very large server.

My group was playing alteria flying heli and it made the whole server log out 4 times we confirmed for sure it was us crashing the server by redoing the same actions again and again (2 times the server actually crasshed and reset itself) I have the logs if somone wants too tell me how too post them.

was on escape from dayz us3 btw

We’re experiencing the same random server crashes caused by the SaveCurrentFSMState function. The crashes occur unpredictably—sometimes multiple times a day, other times the server runs for several days without issues. We're hoping for a prompt response and fix from the developers.

Is there any update on this? This same issue on our server. Have been following this post but not seeing much input from Bohemia on this one.

Doesn't matter if it's at 10pop or at 80pop. Crashing 4-5 times a day with this SaveCurrentFSMState Access Violation Crash

Are we going to see this crash fixed before 1.28 release?

Is everyone encountering this issue running the Community Framework mod (CF)?

@Salutesh We are and I’d say a very large majority of popular modded servers do too

@ELJubJubs Please make a ticket in EscapeFromDayZ discord regarding this so I can look into that further

Yep

We are. Been having at least 1-2 of these crashes daily, sometimes more, and it’s really really starting to hurt. We’re still growing and it’s really not helping. Doesn’t matter if we’ve got 5 on or 40… just random weaponfsm.c crashes.

In T189923#2787568, @DozingChopper wrote:

This is primarily not a DayZ core issue, but an issue with mods on the server, I have found the core issues and fixed them on our servers.

Claiming to have a fix for this issue and not sharing it is diabolical.

In T189923#2791286, @ad.HD wrote:

In T189923#2787568, @DozingChopper wrote:

This is primarily not a DayZ core issue, but an issue with mods on the server, I have found the core issues and fixed them on our servers.

Claiming to have a fix for this issue and not sharing it is diabolical.

Totally. Also we've just crashed again for the same reason.

I haven't checked this in a few days. Although yes the check itself is causing the crashing, its primarily because some weapon on your server is causing the crashing. It is checking continuously to see if the state of your weapon is correct and attempts to correct itself, if it can't it, causes the crash. Finding the fix for everyone is like finding a needle in a haystack. But for us, we improve crashing ten-fold by going through every weapon, attachment and checking to see if it is set up correctly. After finding minor issues, it improved. Although we are still getting a crash due to a final weapon we are working out, we can report that it is self fixable. My recommendation is your Units / Weapon Config & setups are all 100% correct. I will be more readily available come Sunday to look into fixing more unique instances that people may be struggling with.

I do recommend DayZ has more of a look into the check to see if it can just be avoided completely but, chances are it is just needed to operate.

Well I really hope they do. We’ve gotten rid of like 90% of the crashes on our server by taking magazines out of weapons that spawn inside of modded crate loot, like keycards, care packages etc… but still get one every couple days for a ground weapon. It’s really annoying and I’m not at all confident that the DayZ team is going to do anything about it.

Is anyone here using SNAFU weapons on their server and still getting these FSM crashes? We used SNAFU last wipe on 1.27 and never got them, but now that we’re using A6 weapons we get them all the time. I just want to see if anyone is using SNAFU and getting these crashes before I consider going back to those weapons and getting rid of A6.

I am using A6 and I recognize a few others in here that use A6 as well. I would be interested to see how many in here are using A6 Weapon and A6 Gunplay.

Hello everyone.
There are some changes in 1.28 which could improve this issue. Can you please test this problem on current experimental version and provide feedback?

Has anyone been able to test on experimental?

In T189923#2797412, @ad.HD wrote:

Has anyone been able to test on experimental?

You can't check it because it's random.

My thoughts exactly. Not to mention I don’t have an experimental server set up to test on and I definitely don’t have players to test on it even if I did. It’s hard to just up and test this issue on experimental. Was just wondering if everyone else had the same thoughts.

I guess we just keep our fingers crossed that it’s actually fixed?

In T189923#2796531, @Geez wrote:

Hello everyone.
There are some changes in 1.28 which could improve this issue. Can you please test this problem on current experimental version and provide feedback?

Hi Geez, we're trying on the experimental branch.

I've added a NULL Pointer check to the vanilla code to prevent server crashes. More specifically I've added NULL pointer checks on the variables ctx, state, and m_fsm in the modules weapon_base.c and weaponfsm.c. I've published this as a workshop item WeaponFSM Fix . Keep in mind this hardcodes these two modules with 1.27 code so it may break when 1.28 is released. Please remember to remove this mod when 1.28 is released.

In T189923#2797917, @ad.HD wrote:

My thoughts exactly. Not to mention I don’t have an experimental server set up to test on and I definitely don’t have players to test on it even if I did. It’s hard to just up and test this issue on experimental. Was just wondering if everyone else had the same thoughts.

I guess we just keep our fingers crossed that it’s actually fixed?

heh, most players don't know how to run mods that are ON the workshop 🤣 Trying to teach them how on exp it'll be pushed live by time players join.

@nachoooo I've added this to my server, but am still getting the exact crash you have listed in the steam workshop. It has def cut down on the number of the crashes in my crash log, but we still get them sometimes.

In T189923#2800197, @ForePlayDZ wrote:

@nachoooo I've added this to my server, but am still getting the exact crash you have listed in the steam workshop. It has def cut down on the number of the crashes in my crash log, but we still get them sometimes.

The fatal crashes or just still showing up in the logs?

I found that in addition to ctx being NULL, the WeaponDebugger and current_state_id can also cause crashing. I've added error checks for those and also redid the overrides from prefix to modded overrides which should prevent any crashing. I'm uploading the new version now. WeaponFSM Fix

In T189923#2800213, @nachoooo wrote:

I found that in addition to ctx being NULL, the WeaponDebugger and current_state_id can also cause crashing. I've added error checks for those and also redid the overrides from prefix to modded overrides which should prevent any crashing. I'm uploading the new version now. WeaponFSM Fix

ZERO weaponfsm errors in my logs as of this morning’s scheduled restart after installing this last night. I could kiss you 😘

Happy to help out the community! @Gooon I'd like to have a chat with you, https://discord.gg/killerz

In T189923#2801301, @nachoooo wrote:

Happy to help out the community! @Gooon I'd like to have a chat with you, https://discord.gg/killerz

Just had my first error/crash since installing your mod. One in two days is still one too many, but I’ll take what I can get.

Thats a bummer, I personally haven't had any crashes. Obviously its not a permanent fix but at least it will stop crashes 4-5 times a day. The main issue is the lack of sanity checks in the DayZ code and the short-circuit coding. As of this last update, Enfusion engine doesn't appear to properly handle && operator logic.

I'm going to make a couple tweaks to the current_state_id and see if that helps, most likely I'll upload later tonight when pop dies down

Thank you!

In T189923#2801943, @nachoooo wrote:

I'm going to make a couple tweaks to the current_state_id and see if that helps, most likely I'll upload later tonight when pop dies down

Not sure if this is helpful or not, but I'm now getting an fsm crash that calls out your mod:

DFW-4-2C-18, 01.05 2025 19:44:05
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\Beg4MercyCherna\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff75ec79864 at 0x10

Function: 'SaveCurrentFSMState'
Stack trace:
WeaponFSMmodfix/Scripts/4_world/entities\firearms\weapon_base.c:5

SymGetSymFromAddr:487, addr:0x7ff75ec79864
SymGetSymFromAddr:487, addr:0x7ff75ee441ef
SymGetSymFromAddr:487, addr:0x7ff75ee5db62
SymGetSymFromAddr:487, addr:0x7ff75ee45bcf
SymGetSymFromAddr:487, addr:0x7ff75ee42d75
SymGetSymFromAddr:487, addr:0x7ff75ee479e2
SymGetSymFromAddr:487, addr:0x7ff75ee4324f
SymGetSymFromAddr:487, addr:0x7ff75f0788b4
[CDPInitServer]: ??? addr:0x7ff75f2314f9
[CDPInitServer]: ??? addr:0x7ff75f21de38
[CDPInitServer]: ??? addr:0x7ff75f21bdd3
[CDPInitServer]: ??? addr:0x7ff75f21e1ff
[CDPInitServer]: ??? addr:0x7ff75f22b1c0
[CDPInitServer]: ??? addr:0x7ff75f21d52c
[CDPInitServer]: ??? addr:0x7ff75f23bcda
[CDPInitServer]: ??? addr:0x7ff75f21d7c0
[CDPInitServer]: ??? addr:0x7ff75f22f031
SymGetSymFromAddr:487, addr:0x7ff75ee6514c
SymGetSymFromAddr:487, addr:0x7ff75ee65c57
SymGetSymFromAddr:487, addr:0x7ff75ee6654b
SymGetSymFromAddr:487, addr:0x7ff75ee6f94a
SymGetSymFromAddr:487, addr:0x7ff75ee6f989
[BaseThreadInitThunk]: ??? addr:0x7ffdeff24ed0
[RtlUserThreadStart]: ??? addr:0x7ffdf0c0e39b
[RtlUserThreadStart]: ??? addr:0x7ffdf0c0e39b

Uploaded new version to check current_state_id = 0 as empty as defined in scripts\4_world\entities\firearms\fsm\states\weaponstablestate.c

In T189923#2802029, @ad.HD wrote:

In T189923#2801943, @nachoooo wrote:

I'm going to make a couple tweaks to the current_state_id and see if that helps, most likely I'll upload later tonight when pop dies down

Not sure if this is helpful or not, but I'm now getting an fsm crash that calls out your mod:

---

DFW-4-2C-18, 01.05 2025 19:44:05
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\Beg4MercyCherna\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff75ec79864 at 0x10

Function: 'SaveCurrentFSMState'
Stack trace:
WeaponFSMmodfix/Scripts/4_world/entities\firearms\weapon_base.c:5

SymGetSymFromAddr:487, addr:0x7ff75ec79864
SymGetSymFromAddr:487, addr:0x7ff75ee441ef
SymGetSymFromAddr:487, addr:0x7ff75ee5db62
SymGetSymFromAddr:487, addr:0x7ff75ee45bcf
SymGetSymFromAddr:487, addr:0x7ff75ee42d75
SymGetSymFromAddr:487, addr:0x7ff75ee479e2
SymGetSymFromAddr:487, addr:0x7ff75ee4324f
SymGetSymFromAddr:487, addr:0x7ff75f0788b4
[CDPInitServer]: ??? addr:0x7ff75f2314f9
[CDPInitServer]: ??? addr:0x7ff75f21de38
[CDPInitServer]: ??? addr:0x7ff75f21bdd3
[CDPInitServer]: ??? addr:0x7ff75f21e1ff
[CDPInitServer]: ??? addr:0x7ff75f22b1c0
[CDPInitServer]: ??? addr:0x7ff75f21d52c
[CDPInitServer]: ??? addr:0x7ff75f23bcda
[CDPInitServer]: ??? addr:0x7ff75f21d7c0
[CDPInitServer]: ??? addr:0x7ff75f22f031
SymGetSymFromAddr:487, addr:0x7ff75ee6514c
SymGetSymFromAddr:487, addr:0x7ff75ee65c57
SymGetSymFromAddr:487, addr:0x7ff75ee6654b
SymGetSymFromAddr:487, addr:0x7ff75ee6f94a
SymGetSymFromAddr:487, addr:0x7ff75ee6f989
[BaseThreadInitThunk]: ??? addr:0x7ffdeff24ed0
[RtlUserThreadStart]: ??? addr:0x7ffdf0c0e39b
[RtlUserThreadStart]: ??? addr:0x7ffdf0c0e39b

Looks like a corrupted or deleted ctx value is being passed to ctx. I'll see if I can revise this

Updated ctx checking and sync intervals, appears to be more stable. WeaponFSM Fix

In T189923#2802687, @nachoooo wrote:

Updated ctx checking and sync intervals, appears to be more stable. WeaponFSM Fix

If the problem is fixed by Dayz, can we see a stable version of the fix for the problem with weapons from you at 1.28?

In T189923#2802844, @TWINKLE.Play wrote:

In T189923#2802687, @nachoooo wrote:

Updated ctx checking and sync intervals, appears to be more stable. WeaponFSM Fix

If the problem is fixed by Dayz, can we see a stable version of the fix for the problem with weapons from you at 1.28?

First and foremost I want to state that I am NOT a developer. I am a DayZ enthusiast who enjoys modding and coding.
The WeaponFSM system in DayZ is prone to crashes and desynchronization due to unsafe multithreaded state handling, unreliable short-circuit evaluation in Enforce Script (&& expressions), and invalid weapon/mod configurations.
In particular, the engine may evaluate both sides of a condition like if (state && state.Method()), even when state is null, leading to null reference crashes — especially during high-frequency operations or multiplayer synchronization.
This issue is amplified when modded weapons are missing expected FSM transitions, or .p3d models lack required memory points or proxies, causing the FSM to enter undefined or invalid states without fallback behavior.
If Bohemia fixes this, then there would be no need for additional null checks.

So to answer your question, Yes if (the problem is fixed by DayZ && No you won't see a stable version of the fix) { Guns go BRRRR } ;-)

Appreciate the explanation, it’s more than we get from the actual devs. I now go like two days with no crashes and then I’ll get three in three hours. It’s so frustrating.

I’ll send the logs here soon so you can see if you can address the crash further.

Yeah send me your logs, most likely its a bugged player, desync, or a buggy weapon/mod. I may include debug messages with the players name attached to the log so you can see if its one player in particular causing the issue. I have seen corrupted player profiles and cheaters causing memory corruption issues.

In T189923#2804049, @nachoooo wrote:

Yeah send me your logs, most likely its a bugged player, desync, or a buggy weapon/mod. I may include debug messages with the players name attached to the log so you can see if its one player in particular causing the issue. I have seen corrupted player profiles and cheaters causing memory corruption issues.

DFW-4-2C-18, 05.05 2025 10:55:31
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\Beg4MercyCherna\DayZServer_x64.exe
Reason: Access violation. Illegal write by 0x0 at 0x0

Function: 'SaveCurrentFSMState'
Stack trace:

WeaponFSMmodfix/Scripts/4_world/entities\firearms\weapon_base.c:5

DFW-4-2C-18, 05.05 2025 08:36:54
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\Beg4MercyCherna\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff75eddbfb0 at 0xffffffffffffffff

Class: 'A6_AK104'
Entity id:3017561

Function: 'SaveCurrentFSMState'
Stack trace:

WeaponFSMmodfix/Scripts/4_world/entities\firearms\weapon_base.c:7

DFW-4-2C-18, 05.05 2025 05:20:22
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\Beg4MercyCherna\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff75ec79864 at 0x10

Function: 'SaveCurrentFSMState'
Stack trace:

WeaponFSMmodfix/Scripts/4_world/entities\firearms\weapon_base.c:5

These are the three crashes we had this morning. Haven't had any since.

Which weapon pack is the A6_AK104 in? Also you may want to look at any crashes that are occuring seconds before the WeaponFSM crash as being the culprit. For instance I sometimes get a crash when the CarePackage mod cleans up old care packages, this is because its trying to delete something thats already been deleted so it gets a NULL pointer or illegal read operation
\

It’s A6 Weapons. I think a lot of people in this thread might be using them. It’s a private weapons mod that costs a good bit of money.

Is it only the A6_AK104 that you're seeing this issue with? Do you see any other guns listed? Its possible the A6_AK104 could be missing an FSM transition or memory point in the model

Funny thing is it doesn’t always list a gun, but both times it has listed a gun it’s been an A6 weapon. I don’t think it was the same one last time, I’d have to dig around and see if I can find the screenshot.

DFW-4-2C-18, 09.05 2025 19:27:23
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\Beg4MercyCherna\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff7694fbfb0 at 0x8

Class: 'A6_MK12'
Entity id:3055486

Function: 'SaveCurrentFSMState'
Stack trace:
WeaponFSMmodfix/Scripts/4_world/entities\firearms\weapon_base.c:7

In T189923#2804591, @nachoooo wrote:

Is it only the A6_AK104 that you're seeing this issue with? Do you see any other guns listed? Its possible the A6_AK104 could be missing an FSM transition or memory point in the model

In T189923#2806100, @ad.HD wrote:

DFW-4-2C-18, 09.05 2025 19:27:23
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\Beg4MercyCherna\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff7694fbfb0 at 0x8

Class: 'A6_MK12'
Entity id:3055486

Function: 'SaveCurrentFSMState'
Stack trace:
WeaponFSMmodfix/Scripts/4_world/entities\firearms\weapon_base.c:7

In T189923#2804591, @nachoooo wrote:

Is it only the A6_AK104 that you're seeing this issue with? Do you see any other guns listed? Its possible the A6_AK104 could be missing an FSM transition or memory point in the model

I uploaded a new version yesterday, try that one. It has more error checks in it. I had a look at the A6 weapon mod, its very complex and it changes a lot of hard coded values on the fly via config. I personally wouldn't use A6_Gunplay mod, the other A6 weapon mods should work fine without it, if you're using it only to disable weapon damage, theres other more stable mods for that.

In T189923#2806118, @nachoooo wrote:

In T189923#2806100, @ad.HD wrote:

DFW-4-2C-18, 09.05 2025 19:27:23
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\Beg4MercyCherna\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff7694fbfb0 at 0x8

Class: 'A6_MK12'
Entity id:3055486

Function: 'SaveCurrentFSMState'
Stack trace:
WeaponFSMmodfix/Scripts/4_world/entities\firearms\weapon_base.c:7

In T189923#2804591, @nachoooo wrote:

Is it only the A6_AK104 that you're seeing this issue with? Do you see any other guns listed? Its possible the A6_AK104 could be missing an FSM transition or memory point in the model

I uploaded a new version yesterday, try that one. It has more error checks in it. I had a look at the A6 weapon mod, its very complex and it changes a lot of hard coded values on the fly via config. I personally wouldn't use A6_Gunplay mod, the other A6 weapon mods should work fine without it, if you're using it only to disable weapon damage, theres other more stable mods for that.

The gunplay mod does quite a bit more than that. But I’ll give your new version a run. We haven’t had any additional crashes since that last one so they’re definitely few and far between.

In T189923#2806118, @nachoooo wrote:

In T189923#2806100, @ad.HD wrote:

DFW-4-2C-18, 09.05 2025 19:27:23
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\Beg4MercyCherna\DayZServer_x64.exe
Reason: Access violation. Illegal read by 0x7ff7694fbfb0 at 0x8

Class: 'A6_MK12'
Entity id:3055486

Function: 'SaveCurrentFSMState'
Stack trace:
WeaponFSMmodfix/Scripts/4_world/entities\firearms\weapon_base.c:7

In T189923#2804591, @nachoooo wrote:

Is it only the A6_AK104 that you're seeing this issue with? Do you see any other guns listed? Its possible the A6_AK104 could be missing an FSM transition or memory point in the model

I uploaded a new version yesterday, try that one. It has more error checks in it. I had a look at the A6 weapon mod, its very complex and it changes a lot of hard coded values on the fly via config. I personally wouldn't use A6_Gunplay mod, the other A6 weapon mods should work fine without it, if you're using it only to disable weapon damage, theres other more stable mods for that.

WIN-0Q27SSNU7BM, 18.05 2025 21:37:49
Unhandled exception

Program: C:\Users\Administrator\Desktop\OmegaManager\servers\Beg4MercyDayz\DayZServer_x64.exe
Reason: Access violation. Illegal write by 0x0 at 0x0

Class: 'A6_Beowulf'
Entity id:3075728

Function: 'SaveCurrentFSMState'
Stack trace:
WeaponFSMmodfix/Scripts/4_world/entities\firearms\weapon_base.c:7

If I were you, I'd reach out to the creator of the A6 weapon mod and see if they have an updated version or try running it without the A6_Gunplay

In T189923#2809806, @nachoooo wrote:

If I were you, I'd reach out to the creator of the A6 weapon mod and see if they have an updated version or try running it without the A6_Gunplay

The creator is zero help and offers zero support. I’ve been told by a few devs now that a lot of the problems lie within the configs for the weapons and attachments themselves but the creator accepts zero responsibility and just blames Dayz. I get the game function is causing problems, but it’s very clearly made worse by sloppy work. Wish I could get help from him, but I can’t. I just keep posting these in case it helps you find more fixes for the actual fsm function but I’m going to start going through the mod here this weekend and start trying to correct redundancies and other issues that I’ve been told cause problems. I appreciate all of your help bro, thanks again.

New one from our server, first one i have seen with a weapon name on it

Unhandled exception

Program: C:\OmegaManager\servers\au1\DayZServer_x64.exe
Reason: SEH exception thrown. Exception code: 0xc0000374 at 0x7fff4e9e3509


Class:      'TF_SR25'
Entity id:3005125

Function: 'SaveCurrentFSMState'
Stack trace:
WeaponFSMmodfix/Scripts/4_world/entities\firearms\weapon_base.c:10

How often are the crashes vs not using the mod?