If DIK Code results with -1 ARMA 3 will crash to the desktop. This come with latest update of ARMA 3. Before you get the message UNXPECTED_KEY_ID+
Description
Description
Details
Details
- Severity
- Crash
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Category
- General
Steps To Reproduce
enter
keyimage -1
into debug console.
(Not testet with other values below zero)
Additional Information
Happens with and without mods
Event Timeline
Comment Actions
@t.buur, could you upload a copy of your crash dump files for the developers to see?
To get the crash dump files:
- Start the Arma 3 launcher.
- Click "OPTIONS."
- Click "Prepare Arma 3 troubleshooting report...".
- Save the report.
- Upload it by dragging and dropping into the comment box.
If you have trouble uploading the file to the feedback tracker then try uploading it to a file sharing service such as Dropbox, Microsoft OneDrive, Google Drive, Mega, et cetera and then link to it here.
Comment Actions
@t.buur, you said the game crashes but I do not see any crash dumps (arma3.bidmp and arma3.mdmp) in your ArmaReport file; only arma3.rpt files. If you can reproduce the crash can you repeat the steps above?
Comment Actions
Unfortunately I cannot found crash dumps (arma3.bidmp and arma3.mdmp) in the prepared logs.
I changed everything in arma 3 launcher to standard.
When Arma crash a window pops up with following error report:
Beenden-Code 0xC0000005 - STATUS_ACCESS_VIOLATION
Maybe this helps
Comment Actions
Hello,
thanks for the feedback.
Please try to look for the crashdump files manually. Crashdump (set of mdmp + rpt + bidmp with same timestamp) files should be located in this directory:
C:\Users\<username>\AppData\Local\Arma 3
Comment Actions
Checked but there are no files. Allready done search over the whole file systems for the crashdump
Comment Actions
Also checked the integrity of the game cache using steam
Also run a Windows System File Check tool to repair corrupted system files.
Both ok
Comment Actions
Hello,
issue should be now fixed in the Development branch and should be also resolved in the next Main/Stable branch update.
Thank you