Run a tool like MSI Afterburner on the side as you play the night mission, but make sure to enable hardware logging. Once your graphic driver resets, stop the tool you're using and then stop playing. Check your graphics card temperatures, temperatures at around 105 degrees or hotter for a longer period of time is usually the cause of what you're experiencing.

The interesting question here is though, were you experiencing this prior to 1.08 (version 1.05)?
Arma wasn't exactly made for laptops with an Intel chip and an i5-3210M, so it wouldn't be a surprise if this was a continuous issue. You'll have to keep in mind that Arma is an extremely taxing game where even a beasty GTX660 and an i5-4670k can sometimes run into problems - these specs are pretty much the complete opposite of what you have right now.

This is also not an ArmA3 related error as it's your graphics card overheating due to load.

I uploaded a picture of my MSI Afterburner settings as well as 3 pictures of my Arma 3 settings. They're in the attachments now.

The first mentioned picture shows that there is no option to enable GPU temperature monitoring, only GPU usage, fan speed and the framerate twice, or it might be just me being completely blind.

The three other screenshots in the Arma 3 Settings.rar show that I have nothing special enabled (AO, Caustics, FSAA, ATOC, PPAA, Aniso. Filtering, Bloom, Blur).

Looking forward to your reply.

downvoted, never experienced.

Thank you very much for your answer.

I downloaded and installed the MSI Afterburner but didn't find an option to monitor temperatures, only fan speeds and GPU usage.
However, what I did find is that the GPU usage stays around 30-50% when playing Arma 3 during the night mission and then it rises to 99% for the duration of the driver crash.

I uploaded the hardware monitoring file. It's just a text file as .hml files are not allowed to be uploaded here. It clearly shows the GPU usage rising.

To answer your question, No, I did not experience these crashes prior 1.08.
I was able to play fine since the Beta started (Alpha didn't work at all) for many hours.

I know that Arma 3 can be quite a challenge for my poor little laptop but I'm not sure if that's the issue here, as I was able to play this game nice and easy before 1.08 emerged. Something in that patch changed the game radically for my graphics driver.

Go into Settings, Monitoring and then enable GPU temperature, Usage, and framerate. Disable everything else.

Next time you start it up make sure to delete the HTML file beforehand as it caps at 10 MB. The biggest part is GPU temperature as usage shouldn't spike at 100% continuously.

1.08 and 1.10 has also seen the addition of a few graphic options (HDAO for 1.10), so general ArmA settings would be nice to have attached aswell.

related to http://feedback.arma3.com/view.php?id=21108 ,
http://feedback.arma3.com/view.php?id=19548
and http://feedback.arma3.com/view.php?id=4351

Duplicate of #4351

hha nahw sorry,i overreacted :)yeah that would be soo cool,well youre right,uhm its kinda loong ago but i once could open the doors with the scroll down menü but as i tried it the next day it wasnt possible anymore so :/.

I apologize if you took my comment as a personal attack, that was not my intention. I for one would really like to see usable vehicle doors (and/or windshield wipers for the new rain).

Unfortunately this ticket lacks of a proper summary and description and the reproduction steps are really vague. Why are you unable to reproduce not being able to open vehicle doors?

okay hang on,now turn your brain on,still confused yes?okay i'll help you,but first finish your baby meal okay,done yes?cause i dont know there was a forum -.-

I'm confused. Why is this a ticket? There are Forums for questions like that.

Sad to hear that,thanks guys.

They were removed because the devs couldn't ensure that all vehicles would receive similar updates and offer the same amount of detail. It was either all of them or none at all.

It's not patched out. The animations for opening doors etc just don't get played when you use the action "Get in X", or similar actions.

really?but i cant choose them.

1. no
2. yes
3. yes

uploaded

Do you have hw overclock?
Do you have latest graphic drivers?
Did you try lower graphic settings?
Thank you for more info.

in multiplayer. absolutely any place and at any time. You can just go sit in the helicopter and sits down to 5-6 fps. tried to wait it out. suddenly pass. but the game crash after a while.

not played SP. I can not say.

in version 1.08 had the same problem

hoping for a fix in 1.10

Which places? SP or MP? Do you have same issue on same places, when you start game from editor?

Could you please upload crashdumps please? You can find crashdumps files here: C:\Users\<Name>\AppData\Local\Arma 3\ (.rpt file, .bidmp file, .mdmp file)
Thank you.

You should attach your system specs.

As of the latest patch, 1.14 (relased on 20/03), this issue is still present.
I just wanted to try the new jets, so I opened the editor, created the jet in the airport, a pair of enemy tanks and previewed the result. In the bottom right corner, a watermark saying Development Branch 1.14.xxx is present.

Ignore this ticket as I've found out this is related to the Virtual Ammobox System (VAS)

http://forums.bistudio.com/showthread.php?149077-Virtual-Ammobox-System-(VAS)

Potentially fixed in the latest version too (v2.3)

http://forums.bistudio.com/showthread.php?149077-Virtual-Ammobox-System-(VAS)&p=2603701&viewfull=1#post2603701

3rd Party Mod

This will be/has been resolved by the 3rd party mod that was the actual cause for the error message.

Hi,
do you have same issue in version 1.10?
Thank you for info.

Have tested, and no, seems fine.

Mass closing tickets marked as resolved more than 1 month ago.

If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.

Checkbox in UAV Terminal is already present in dev branch version, it should be in stable branch soon. However, I will mark this issue as resolved. With all these changes it seems there are a few ways how to disable auto-firing of UGV and we don't want to disable it by default. Thanks for feedback!

Hi, you should be able to stop this behaviour by that already mentioned right click on waypoint and setting behaviour to never fire. You can stop UAV from doing basically anything via new "Autonomous" checkbox in the UAV terminal.

You are probably right, that this option (automatic shooting) would be disabled by default in real life. But we are in the game and more users will probably use enabled weapons. However, if you want to set these options (never fire or autonomous) on start of a mission, you can use script commands setCombatMode and setAutonomous. This is entirely up to mission author.

I would like to ask you for retesting of that right click on waypoint in the UAV Terminal. If it doesn't work for you, then it seems there is some issue. But I am not able to reproduce it, some repro mission would be useful in case you can still reproduce it. Thanks!

Ok that sounds good, but i do not using waypoints, im always driving UGV by myself.

Scripts commands are a good idea, also checkbox would be good, i wanna test it.

Looks like that right clicking in UAV terminal not working, so UGV gets completly out of control...

Just like brainless killer that kills everything that is enemy, even when it may ruin whole mission.

Imagine mission where you must capture enemy commander alive, UGV will make it unable to do.

The controlling of UAVs and UGVs is rudimentary and needs improvement. The UAV terminal is a good idea but offers little control over those units. Indirect control via waypoints is too clunky. You can't switch to the turret from the UAV terminal. Accessing the the turret is only possible via the action menu (which is bad, there are already too many options in the action menu) or when piloting the autonomous unit.

How about extra buttons for rules of engagement and flight altitude?

Maybe you watched too many movies...

Maybe you stop insulting people's judgement head-on?

Any unmanned vehicles are NOT intended to attack enemy without human confirmation.

Who said that? You? Who you are?

Because otherwise it may cause some catastrophic effect, especially if im trying to sneak to enemy and UGV opens fire.

It's your problem, not game problem. If you don't know how to use a tool - don't use it.

@DarkWanderer
Please stop watching purely fictional movies then you will understand what i talking about ;-)

Because no real UGVs or UAVs are firing weapons without human confirmation.
Those things happen only in purely fictional movies and in...
...ArmA 3 ;-)

And i know how to use them, those UGVs are just unrealistic while they are firing without human confirmation.

@Imperator Pete, thanks for reply.

But i think that Never Fire should be default option.

Because otherwise it may cause some catastrophic effect, especially if im trying to sneak to enemy and UGV opens fire.
In those situations UGV fire is just like shouting "I AM HERE, SHOOT ME AND THEN KILL ALL GUYS NEAR ME".

This behaviour is controllable from the UAV terminal via right-clicking on the map and setting a behaviour to Never Fire.

Maybe you watched too many movies...
Realism in ArmA 3 should be on high level. Its not arcade game like BF3 ;-)

Any unmanned vehicles are NOT intended to attack enemy without human confirmation.
Even countermeasure system in aircraft needs to be switched in automatic mode to release flares without human input.

ArmA 3 should not be as unrealistic as hollywood movies...

Working as intended.

Hello,

There is allays collisions problem.

Yesterday, on our private server, 1 guy die because he walk in a ruin house.
and an other because a hunter catch him at 1 Kph

Wee are playing 4 hours missions with 1 revive so its really boring to die like that.

If you read the changelog notes in the dev branch you will see they have pretty much fixed this problem. Wait for today's stable patch.

Mass-close of resolved tickets not updated in last two weeks.

Let's make A3 consistent

I'll drink to that!

Think this is related: http://feedback.arma3.com/view.php?id=17295

Would probably be worth checking that this also works after fix: http://feedback.arma3.com/view.php?id=17226

Mass-close of resolved tickets not updated in last two weeks.

OMG of course! Epic facepalm! I'm so sorry :(

Never mind... since DEV. 114900 radio slot will be re-scan right after assigning of itemRadio. Let's make A3 consistent

All works now.

You know what is even more funny? I recently updated wiki with note that you have to have itemradio in your inventory to read or post into sidechat... and then did this! globalChat would have worked better.

Shall I close it or you wanna mark it as solved?

it seems to be OK now

Killzone_kid: you owe me two hours of my life ;-)A3 is processing EETake even for radio, but you can't get an information from sidechat, because action Take is being processed before simulation in which Soldier checks its slots(radio, nvg, ..). So I can modify code to call slot items scan right after proper action, but I don't know if it is really necessary

Here is the video just in case: http://www.youtube.com/watch?v=B9iiMkwluvg

To add even dragging radio into uniform doesn't trigger Take.

Total fail for itemRadio!

Not that TAKE does not fire if you pick it up with default action, dragging it manually doesn't fire TAKE either. (tried on dedicated server)

It's Christmas tomo!

LOL Sorry @japapatramtara, I did not change it from feedback to assigned :) the ticket system seems to be bugged.

FIXED since DEV.114819 (will be distributed tomorrow)

Never mind, the problem still exist now it seems to be harder to trigger.

The game saved with a dependency that only allows me to play with M.C.C. I can not load the campaign without it.

Mass-close of resolved tickets not updated in last two weeks.