i tryed your like still got the same crash as before and thanks for the help

Just to warn i do not own the dlc, =/

I've also got the same issue mentioned here on my Linux server as well. I've deleted & redownloaded the addons/ directory and verified cache too for good measure, but still the error appears.

Oh! thank you for this point, I understand you can filter what you need in crates with the "virtual" tab.

disable all mods and start adding them back one by one until you find the culprit.

Thing is, this would take ages (i got 50 mods active)

And another one (same cause I think?)

@Alwin Here you are. Do note that this core dump doesn't belong to the gdb trace I provided with the initial report so I will upload one that does belongs as a .txt-file.

While playing.

Here is a new (large?! o_O ) one:

But the crash keeps happening on the usual dev build

Thanks. I´ll let you know.

@Alwin Here you go. Fresh, vanilla, unconfigured Arma3 DS installed via SteamCMD as of Thu Jan 12 14:13:34 CET 2017. Crash was triggered via sending SIGINT. arma3server binary sha1sum is 20d928b05ecd5e1613efbd6c1d7f1e1c56a3de5d.

Hello again,

YESSSS finally! What are next steps? :) Checking in debug mode what happens on client/server upon "spamming" zoom key?

Thank you for a good observation. We´ll decide what to do with this.

Thank you for a good observation. We´ll decide what to do with this.

Would I ask you about your game report? Path: C:\Users\*username*\AppData\Local\Arma 3 If your game crashes, I´ll ask you about your crash dumps. You can get them via troubleshooting report in Launcher.

I´ve watched on your report again. Fault adress is located here: F:\Steam\steamapps\common\Arma 3\arma3.exe
Could you try reinstall your libraries using this link? It´s possible that your .exe don´t react with your GPU drivers.

For your information, your issue has been added to our system and wr´re investigating right now. I´d ask you for patience. If you didn´t upload crash dumps. Could you do it, please? :)

We´re greatly appreciate your cooperation. I´ll take a look on your issue today. Information provided by you has been added to our system. I´d ask you for your crash dumps, please?

yes, your´re right. Information provided by you is correct. Currently, we´re investigating your problem. Therefore, I ask you for patience. :)

I was able to erratically reproduce this issue with a Titan MPRL Compact using the steps that @Deranged provided. Mission was: Custom_KingOfTheHill_by_Sa-Matra_for_TEAMREVOLT

Actually got it working! :

Encountered this bug with a modded vehicle I'm building. Have 4 turrets with the same weapon and magazine and can not get their ammo count as the command reads only the one magazine.

yep i have tryed all of that to nothing really seem to to work wich makes me sad cause i really like playing arma 3

Interesting fact: yesterday no issues, only got a wierd crash message upon exiting the game after playing a long while, so issue SEEMS resolved, will see! :)

just one question did anyone actually take a look? if you can see the only activity on the ticket is from my side (reports, updates for those reports). I'm a software developer so I know that sometimes things fall from the desk :)
I can try to see if the issue still happens but the issue seems to be the same as the other one mentioned on this same ticket, the instructions I provided (pbo + instructions) are an easy way to reproduce the issue I even shared the core file to speed up the debugging process.
I'll try to update my linux server and try to reproduce the issue but if nobody took a look on your side I doubt it was resolved.

@Alwin Your efforts are much appreciated :)

I´m sorry for that. Obviously, I´ve noticed your previous similar issue you mentioned.
We´re investigating it right now. Don´t worry. We´re trying to solve each problem here to players happiness.

May I ask you for your Dxdiag, please?

@Alwin While you're at it, you may also want to take a look at T80679. It describes how it should be possible to trigger a graceful shutdown not only with SIGINT, but with SIGTERM as well. I reported it 2 years ago ;)

In 1.67.139940 seems to be solved, I just received the update.

thanks for report. We´ll investigate your issue.

Thanks for game report. I´ll report to system and let you know.

I´ve closed this issue because here was not some new situation report. The last was from a half of December.
The problem still persists? If yes, I´ll reopen this ticket.
I´ve reported your issue to system, don´t worry.

I´ve seen on your callstacks and it seems like issue realted to virtual memory.
In any case, i´ve reported your issue to system so don´t worry.
btw. did you try some common solutions like a verify game cache integrity, delete your profile and create a new one, remove mods and missions and so on?

I´m seeing your last crash report from November. Can you send us a new on with 1.66 version please,

Jawsh: To reproduce this issue use some sniper rifle ie. lynx with LPRS scope (or use Titan launcher) and while aiming to the AO in KotH from any distance outside of said AO while area has players inside.

The solutions, I´ve suggested to you are common nature. They are helpful in many cases. I understand that your problem is with dynamic simulation, don´t worry.
I´ve reported your issue and still waiting for respond so keep patience please. We´re trying to resolve each issue quickly to the satisfaction of players.

Would be definitely worth a check.

Interior Audio also https://youtu.be/rmc7rw9s5NE

Here's another video showing the same issue, using Today's DEV branch.

In T121720#1560882, @DanielNL wrote:

Jawsh can you try to reproduce on "CCG Wasteland Tanoa" server please?

I just found out I don't have an arma3.exe in this part of the regedit: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\arma3.exe Also I have the troubleshoot report from when I tried tried arma3diag_x64.exe earlier today.

Seriously, that was now the last time that I report a bug or a crash.

The same bugged zeroing behavior can also be observed with the TRG-20 and the (A)RCO optics.
You have to aim significantly lower than expected.
And it matches the same pattern with a largely deviating initSpeed between magazine and weapon:

Jawsh can you try to reproduce on "CCG Wasteland Tanoa" server please?

Not since the 10 GB patch. Should I ?

I can confirm this bug.

seems the ticket I raised with the easy to reproduce instructions was closed (with no explanation), please let me know if you need me to share my core and PBO files again.

Alwin, since the issue is marked as resolved, I will remove the dropbox file as it is taking space in my dropbox, if needed again please let me know and I'll share the information again

Thanks for reporting this ;) Unfortunately, nobody bothered to investigate (or even fix) this issue following my initial report.

Taking a quick look at the involved registers in both this and T122774, I'd take an educated guess that the underlying issue is the same and can be triggered by either SIGINT or #shutdown. It just moved around a little in the meantime (new binary version). With the arma3server binary version 1.66.139586 (sha1sum 20d928b05ecd5e1613efbd6c1d7f1e1c56a3de5d) both my servers crash at exactly the same instruction address as in T122774.

im starting from a fresh set up ran all the updates for everything this problem didnt start tell i got apex dlc i have also tryed the all in one runtimes program to see if that would fix it and still get the same thing i can get a little bit more time out of the game when i turn apex off i have all setting in the game turned to lowest they can go and still didnt fix the problem

Not sure, your crashdumps are a little bit weird and not showing much.

In T121977#1559897, @razazel wrote:

Issue should be already fixed in dev branch and should be available in next stable/main branch update.

At 1.66 I have a problem happens rarely. I can well 1.5-3 hours of play. But at any time, the memory error may occur.
It does not depend on the game settings, you can always appear the situation with the failure of the FPS, when Arma3.exe process pagefile VM reaches 3200-3500mb. There is a gradual increase in the use of volume pagefile VM and RAM up to a critical value.
If we compare this with DEV Arma3_X64.exe - always a stable value of the use of the VM and RAM ~ = 4000mb. Dips FPS sometimes there (to 30-20), but critical memory access no error.

Try the below possible solutions one-by-one:

Try the below possible solutions one-by-one:

Try the below possible solutions one-by-one:

This ticket is here for too long without any new reaction. I´ll close it. In case of persisting isuue, please create a new one.

This ticket is here for too long without any new reaction. I´ll close it. In case of persisting isuue, please create a new one.

This ticket is here for too long without any new reaction. I´ll close it. In case of persisting isuue, please create a new one.