Page MenuHomeFeedback Tracker

Crash to Desktop - Multiple errors/artifacting
Closed, ResolvedPublic

Description

When I launch ARMA3 MP or SP, my game will crash within a few minutes. This crash is heralded most of the time by flashing ground textures, which appear to be artifacting.

Crashes were causing BSODs until I flashed BIOS. Crashes report as a variety of errors, PhysX3, Runtime error, etc. After the crash, my browsers will also crash, reporting memory errors, and various open windows may artifact slightly. DxDiag attached, crashlogs in filedropper link.

http://www.filedropper.com/arma3_2 {F23985}

Details

Legacy ID
2539859288
Severity
None
Resolution
Fixed
Reproducibility
Always
Category
Game Crash
Steps To Reproduce

Launch A3

Enter Game

Wait 1-3 Minutes

Additional Information

System information: AMD 6870, Athlon x6 BE, 3.5~ghz, 12GB DDR3, SSD/HDD combo (install attempted on both, no change). Crashes/artifacting do not occur unless A3 is run.

Stresstest information: Furmark will run for hours on full stress, with GPU running close to 100C. GPU runs at 80~C in ARMA3.

Event Timeline

aurumaethera edited Additional Information. (Show Details)
aurumaethera set Category to Game Crash.
aurumaethera set Reproducibility to Always.
aurumaethera set Severity to None.
aurumaethera set Resolution to Fixed.
aurumaethera set Legacy ID to 2539859288.May 7 2016, 6:38 PM

Hello,

thank you for uploading the ticket. From your crashdumps we can tell that you are using Battle Royale mod. It is necessary you tried to run your Arma without any mods. If the crashes still happen then, please send another crashdumps.

Mods are not official content from Bohemia Interactive. Sorry for inconveniences.

Have a nice day!

Hey there Iceman.

I'll get on generating more crashdumps, but I should also note that some of the dumps I uploaded should be mod-free, as I removed Breaking Point and Battle Royale early in my attempts to fix the crashes!

If you could have a quick check through the dumps for any which are mod-free, I'll pop some more up.

Thanks!

Hi,

I checked again and unfortunately there are no crashdumps without the mod activated (crashdump is rpt + bidmp + mdmp file with same name). If you could add some, it would be great.

Cheers!

Hey there,

Looks like these crashes are inconsistent in generating reports. I just induced another crash, with a DX3D texture error this time, and only the rpt and bidmp were produced. Uploading them anyhow to see if they help, but based on their tiny filesizes I imagine ARMA is producing bad logs? Will continue to try and generate a proper crashlog.

http://www.filedropper.com/arma3_3

Finally!

Took a few hours because my system kept taking the crashes badly, but after heavily reducing the graphical settings, I managed to produce a crashlog. This was with no mods installed, and no mods in launch settings.

Crash occured on a Wasteland server, I believe I'm right in saying that Wasteland is a scenario, not a mod, as it introduces no new content. Dump attached.

http://www.filedropper.com/arma3_4

Hello,

something really strange is going on. After unpacking, the rpts have 697 and 43 MB (normally they have cca 1-3 MB). I can't even open them for analysis. Could you please try to verify your game through Steam?
https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335

Thank you.

Local files verified A-OK, and have done before.

I've reinstalled windows to try and fix this issue, it didn't work. However normal crash logs have been created finally!

http://www.filedropper.com/arma3_5

Hope those logs enable an analysis! Really stuck here.

Hello,
the problem seems to be that some animation are corrupted for you. Could you please verify your data through Steam?
https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335

After then, please try to run your Arma as an admin.

Thank you.

Hello,
are these crashes happening on current 1.20 Stable version?

MadDogX added a subscriber: MadDogX.May 7 2016, 6:38 PM

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.