This is not related to issue "0016347". Kn1fes' crash is most likely happening because he's running out of memory. He's running a 32 bit operating system, which means that Windows is absolutely correct, when it reports that only 2.51GB of RAM is available. That's a limitation of 32 bit Windows. Doesn't matter if he had 128GB of RAM; he'd still not have more than 2.5GB-3.5GB of RAM available.

Why are you even running a 32 bit Windows on that kind of hardware? Your 32 bit Windows 7 license also covers the 64 bit version. This means you can legally install a 64 bit Windows 7 with that license.

BIS Iceman: I was hoping todays update would fix the problem, but it has not; situation remains unchanged.

I would send you the mission file, but I don't think you can use it for anything, without the server scripts, right?

For the programmers:
Please do not blame the mission. A badly made mission shouldn't be able to crash the game. The game is not programmed in freakin' Java.

the Demongod: It should not matter how the server is configured; it should never, ever crash the client. Also, my computer is most definitely not unstable. ArmA 3, and this mission in particular, is the only game I've got any problems with recently. I've played Metro: Last Light all the way through, and am currently playing Thief, and I've had no issues with either. Metro: LL was set to stress my computer to the absolute max, and Thief is running with highest settings.

BIS Iceman: I only set those parameters, to see if I could do something about the crashes. They have no effect, on the crashes, whatsoever.

The crashes does not appear to happen on any other maps out there. I've only tried like 3 or 4 of them though.

I can do any of the big known benchmarks out there. I have yet to see a BSoD on my computer.

In my 20+ years of using computers, ArmA 2 and ArmA 3 have given me the biggest problems. Well, there were a couple of contenders on the Commodore 64, but I'll be fair to myself, and not consider them in this case...

I'll update the issue, to reflect what else I've tried since yesterday. There's new information, that should rule out that it's my computer that's doing something wrong.