https://community.bistudio.com/wiki/Arma_3:_Unusual_Process_Exit#0xC0000135_-_STATUS_DLL_NOT_FOUND

There are no report or crashdump files in there.
And there is not enough information to do anything

Won't do.

Well your graphics card is crashing/disconnecting.
Can't see any reason why. Maybe other applications running in the background.

If you need anything else let me know thanks

kicked you mean crashed?
If you saved all 4, where are they? If you have crash reports please upload them

Unable to reproduce on stable and profiling branch, were you using any mods?

whoops, we forgot about green version
see class Land_HBarrier_01_tower_green_F, 150914 Dev
( ﾟ，_ゝ ﾟ)

Fixed internally - it didn't made it into 2.14 RC but it should be fixed in next update.

No this occurred (twice at least) on native mission (Canisy or Quibou Dangy one), just playing without any mod other than the DLC, on hosted LAN sever, one player only.
I guess you have something for performance optimization with your own simulation switch tool. This (these) unit(s) should be animated or hidden, or not spawned. Something like that.

@BIS_fnc_KK Any updates?

Well that is embarrassing. You are absolutely correct. I just don't remember having to set the variables to false in the past. I withdraw the submission.

This isn't a problem with the OR operator. This is happening because the variables unit1Dead and unit2Dead aren't defined at all until you set them as true. Trigger C is attempting to reference at least one undefined variable - and silently failing - until both variables are defined as a result of their units dying. Then the trigger can actually run its check without encountering an error.

@PiepMGI sorry only saw this report today - this is in custom mission, right?

After more investigation I found out it has something to do with the ownerShip of the vest/uniform. I'm 100% sure.

Bump ancient.
Would be nice to have to company the reload alt syntax

After some more Investigation I found out that the ownership on the server for the bug Vest/Uniform is 0 and not 2. It also stays on 0 when changing ownership via setOwner on a player and back to the server.

seems to be rather an Windows issue, the following steps resolved the issue:

I propose the addition of a getter function that allows server administrators to retrieve all handles created via the "spawn" SQF command. This function would provide a list of SCRIPT handles that could be used to terminate the scripts, along with relevant information such as the script name, execution status, and any associated variables, etc.

Car wheels provides a team of experienced and certified technicians who are dedicated to ensuring the safety and reliability of your vehicle

Gentlemen and scholars, all of you. Thank you!

Crash is already fixed on Profiling build (You can select it in the steam game properties under the beta's tab)
Will also be fixed in 2.14 which releases in a few weeks

sorry OS version is 10.0.19045

Hello,
this issue still preist and it would be nice if it could be fixed.

In T76533#2407341, @RSandiford wrote:

Will this be done for addWeaponWithAttachmentsCargo too? This command is needed to script removing a specific weapon with attachments from a crate.