Currently going through the entire A6 weapon mod and debugging it. I’ve been told that’s the only way to get rid of the crashes completely. It’s quite a task.

For me it gets rid of like 80% of the crashes. So it’s definitely helpful.

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

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.

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.

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

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.

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.

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.

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

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.

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

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

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

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.

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.

Has anyone been able to test on experimental?

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.

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.

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.

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.