All the things you have listed are there and working.

Your report contains old files from around July. Though your basic report shows 0xC0000135 - STATUS_DLL_NOT_FOUND.

Okay, so i have contacted Nvidia Support. They have referred me to what was apparantly a Windows issue. They let me set the 'Force WARP' option in DirectX. This solved the issue with Geforce Experience only giving a black screen, but ArmA III still gave the same error. I was then advised to roll back to Windows build 1703. Which i did.

As someone reminded me, this works with all laser guided bombs, namely: LOM, GBU, KAB and maybe others

Thank you for the report. Could you please send us your Minidump with any rpt. bidmp related to it?

Thank you for the report. We are aware of the problem and are working on a solution.

I will see what can be done. I I am going to suggest them that they should keep the old physics because of these time trials.

Thank you for the report. Are you using any mods? because, I am trying the model with the vanilla game in the Editor and I am unable reproduce it.

@redsky84 Oh. That is odd... I mean I am glad that you can play the game it just puzzles me a bit. Please keep me posted and if the issue doesn't occur again then I will close this ticket.

@Wulf - I will do this in the afternoon. Also I've got an update: After I've restarted the mission completely from the beginning, the problem did not occour anymore. I was able to play the whole cornerstone campaign without a single crash. Really strange.

@redsky84 - Thank you for removing the -noLogs. :) I see that you have a mdmp in your original report. But not in the one with the removed -noLogs. Try triggering the crash again and send us the report.

Does the game freeze occur also during the scouting missions received in the campaign, during the mission Gori?

Interesting, could you please send us your most recent rpts right after the crash?

@Wulf I was hoping AnEnglishmanShels' solution would also solve the problem for me. I've completely reformatted and reinstalled my computer today. I've just finished completely updating and installing everything. however, I'm afraid this has not yet solved the problem, i'm seeing the exact same error every time i try to start the game. Both in x64 and in x86 versions... I'm at a loss here really.

This turns the helicopter into a suicide machine.

The tail rotor should be sufficient to change the flight path to the left and right at any speed. Limiting the stroke of the pedal at high speeds - serves to limit the maximum permissible changes in the angle of the blades at high speeds.
The blades of the rear propeller, first of all, compensate the rotation of the helicopter body from the main screw, its different modes and different permissible speeds.

Close

Close

a lot of players have a problem with it battleye: Client not responding .....

So I tried doing everything you suggested, and the issue is still there. I was even able to upgrade from Windows 8.1 to Windows 10 in that time, and I've still got issues. I took a short video using my phone to show how severe the problem is. Maybe this could give you an idea of what it might be.

Error occurs in everyone without exception. I develop the server and this problem only appeared after the last DLC

Same problem

After removing "-nologs" it generates that report. It has more details.

Oh it did create a crash report:

Still in 1.80. Is there even sb working on this?

Since 1.80 I'm also experiencing crash to desktop. It happens randomly in the cornerstone (TacOps pack) mission. The game runs just fine but suddenly a crash-message pops up and that's it. I can click the "OK" button only by pressing spacebar, because no mouse visible. After this, I'm just back at my desktop. Nothing else happens.
It does not even generate a bug report zip file

Thank you for your reply. and I will take a look add the recommended / possible solutions.

It crashes to desktop with a screen talking about gathering the info in the zip file and to go to here for support.

Having this same issue. At first it was crashing shortly after loading the Scouting mission, later seemingly randomly during the mission and after reverting to a previous save during the mission, and now when trying to return to base to end the mission. Attached are relevant logs. The most recent is the crash on attempting to return to base. So far it is only on this mission I am experiencing crashes.
Deleting the My Documents/Arma3 folder seems to temporarily fix the issue. Before I deleted the folder I was crashing seconds after loading the mission for the first time, every time, but started crashing again later. Again, deleting the folder allowed me to return to base without it crashing when previously it was crashing every time I tried.

all tasks were complete right up to the last one

{F97862}The last few days i have had several freez ups and crashes. I play in the singleplayer campaign "East Wind" and I am currently in Gori, just finished with "Bingo Fuel" and on my way out on recon.
The games just freezes seconds after we deploy on a recon mission.

Duplicates T127389

@colmaniac Your task in this part of the mission is to support the units at key points. The key points appear one after another, step by step.
Perhaps the mission does not end, since the units did not receive timely support from you and many victims in the detachments. Check it out, try to follow the tasks.

I have the same problem with the error. and when i join a game my game crashes and says low memory when i never had this problem a few months ago.
Total Virtual Memory 7.91 GB
Available Virtual Memory 5.55 GB
Page File Space 0 bytes

In T127375#1659446, @Wulf wrote:

Hello.

Thank you for the report. I am able to replicate the getting stuck at the very top of the ladder, not at the bottom.

If these errors are really only produced by engine code and not by referencing errors related to script variables or commands, then these errors should not be pushed into the RPT, because no one can make any sense of them and they fill up the rpt for no reason like spam.

Yeah, this is a big problem, here i represent how i lock a hovering Mi-48 Kajman, whos hovering,(0kmh), gbu guides itself and destroys it. https://www.youtube.com/watch?v=BQvjv51a4h4

OK Wulf,
I will do that...Just thought you may have run across a fix.
BTW Arma 3 is awesome and you guys should be really happy about making such a phenominal game!
I have countless hours of fun playing and designing "Love the Arma Sandbox" !
Have a great day.

I have tried yesterday, In the old version of a game - everything works ideally. At 1.78 and in DEV the characteristic physics of wheels of Karts is broken.

I tested the file formation with marshalls and it works on the stable build. So, could you please let us know what the issue should be? Or with what vehicles it should be tested?

Thank you for the report. I am able to replicate the getting stuck at the very top of the ladder, not at the bottom.

Glad to hear that. Should the issue resurface let us know.

Ok, could you please upload here your rpts? They can be located here: C:Users>Username>AppData>Local> Arma 3

Great! Thank you for letting us know. :)

I am trying this bug right now on the stable build and the mission moves on as it should, no failed mission. Have you tried reverting the mission?

The latest update seems to have fixed the problem.

Uninstall the Visual C++ 2013 Redistributable package (both x86 and x64 version), restart your computer and install the package again solved my problem.
Thanks for the help.

Hmm. The best thing would be to contact the mod makers that created those maps as they know the limits and issues of their maps. We can theorise, but that might not help, your best bet would be to get information from the creators.

well, I changed my pc so i changed my windows too, it was a 7 and now it is a 10. all of the drivers and softwares came installed.

In T82570#1659417, @Chubbs wrote:

Not sure if that blocking task has anything to do with this one.

I do not understand how it happened. I created subtask.

In T127153#1659418, @Chubbs wrote:

This is maybe because the terminal that is connected to the UAV is still connected, and still on the dead body. You can only connect one at a time.

In the mission, dead bodies disappear quickly. After the respawn, after 2-5 seconds the dead body disappears. Sometimes the wait can be long, until you can connect to the UAV. Sometimes it is not possible to connect to UAV during the entire lifetime of the UAV.

This is maybe because the terminal that is connected to the UAV is still connected, and still on the dead body. You can only connect one at a time.

Not sure if that blocking task has anything to do with this one.

No problem; I've attached my report once more.
However I don't think I can help you guys with diagnostics anymore – I solved my problem with a full WIndows reset and update. I was working through steps with Nvidia support, and they told me to update my Windows to Build 16299.98, which apparently included a fix to DirectX. My computer would not update, and that then became the final straw.