@Sycholic, have you tried verifying the integrity of the game cache?

Could you provide some more information for the developers:

1. Are you able to reproduce the crash?
2. What are you doing leading up to the crash?

== "C:\Program Files (x86)\Steam\steamapps\common\Arma 3\arma3.exe" -high -noSplash -malloc=system -mod= -connect=160.202.165.21 -port=2302

-high is not a launch parameter. This can be removed.

The memory allocator used can significantly affect both the performance and stability of the game. Try using the default memory allocator by either removing -malloc=system or replacing it with -malloc=tbb4malloc_bi.

yes already have done a verify.
doing: normally just out killing or dying. hardcrash just comes out of nowhere. no warning no nothing
intel malloc is not an option destroys FPS on this system also has even worse stability. game was stable up to 1.66 using 'system' malloc

as for repo: hence why its marked 'random' as I cant notice a common method of when/why/where it happens.

Hi,

try to use some crash solutions from this web page. In any case, I will report your problem by our programmers.
If you will be able to reproduce us more crash information, please do it.

Thank you.

would adding -crashDiag as a param possibly help?

This should help.

Seems that this is related to using the win7 system malloc handling. I removed (albeit kinda unwillingly) the -malloc=system parameter and so far have not been able to cause or repo the issue. I will try and get a more 'detailed' dump using it but while digging some more came up with a very odd and curious error when dealing with the original issue. Maybe this could be related to why I'm having 'stuttering issues' when using the intel malloc?

https://www.dropbox.com/s/tudrx0kk4orokqr/Screenshot%202016-12-28%2008.22.16.png?dl=0

https://www.dropbox.com/s/e9a3vnubwzsazv6/Screenshot%202016-12-28%2008.24.49.png?dl=0

As you can see for some reason BattleEye is constantly bombarding Norton360 with access probing and thus denials. Given the amount of probing and the timing of it. it just seems too fitting that is applies to my stuttering issues at hand when using the normal malloc vs system (albeit I'd have to test to make sure the system malloc doesnt do the same)

@BISWizard ?

Can you help us with that, please. Thank you.