Still valid as of today. mentioned in A3/Discord by R3vo and verified. upon checking and trying ' findDisplay 46 ctrlCreate ["ctrlEdit", -1]; ' Arma completely freezes and goes unresponsive.. OS shutdown with no crash reporting triggered. Windows 10 is also effected, is not limited to win7.

I am not attempting to run buldozer, why would it be saying that? I am just trying to launch the game normally nothing special...
but I already have uninstalled and reinstalled the game and that was after verifying the game cache failed to solve it as well...

Right now Im trying to launch with no params at all, also tried it with -world=empty no luck.

It is definitely a launcher issue at hand. Running Arma3Battleye directly will launch Arma3 and get the game up and running without issue. Ive Googled for similar issues as mine and already have tried disabling HW acceleration and deleting the prefs folder in %appdata/local/bohemia......

Also tried clearing the one launcher folder as well that handles settings/config as found on the forums did not resolve the problem either.

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?

would adding -crashDiag as a param possibly help?

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