can't upload my crash reports

It said "drag and drop files to upload"
I could not do that this weekend, but it looks like I can do this now.
But this week I am out on travel. I can upload on saturday. Sorry for that.

Here are the reports.

There are no crash dumps and no logs besides one from 22nd June inside your reports.
Can you please try to start your game again and crash it and make a new report.
Also try starting it over the A3 Launcher and also try manually starting the arma3.exe in your Arma folder by just double clicking it.

In the After reinstal report there are no dumps and in the pre-reinstal there is just the one from the 22nd June.

Please trigger the crash once more and send the most current reports you have.

Thank you. :)

started directly from catalog "F:\SteamLib1\steamapps\common\Arma 3"
arma3.exe starts ok
arma3_x64.exe crashes. Does NOT produce a arma error report.

via launcher
Arma 3 - 32-bit starts ok
Arma 3 - 64-bit crashes. This produces an error report

This is the log from Windows Event Viewer:

Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x0000000000000000
Faulting process id: 0x3168
Faulting application start time: 0x01d363ca285f743e
Faulting application path: bad_module_info
Faulting module path: unknown
Report Id: ba1e72d1-b59f-4699-a4de-349716bd4d68
Faulting package full name:
Faulting package-relative application ID:

Okay.

Have you tried some of these possible solutions?

• Update the graphics card drivers to a newer version.
• Rollback the graphics card drivers to an older version.
• Check the temperature of your GPUs and CPUs.
• Verify the integrity of the game cache using Steam.
• Re-install DirectX.
• Uninstall the Visual C++ 2013 Redistributable package (both x86 and x64 version), restart your computer and install the package again (do not use the Repair function).
• Run a Windows System File Check tool to repair corrupted system files.

Sorry for LOOONG delay...

Did all you asked about and nothing helped.
But since you did not get anything in the report file, I started thinking.
It had to bne a windows module that was casuing the issue.

Then I removed my Saitek 3D Flight Stick, removed all drivers and software for it and restarted my computer.
Now ArmA works again. So I think the 64-bit Saitek drivers don't work well with windows 10.

Case closed. Now I need a new flight stick.