Hello,
unfortunately, your crashdumps are outdated. Would it be possible to upload only with current Steam Stable version and with default memory allocator?

Thank you.

The dump from yesterday (7/15, the last dump posted) should not be outdated. This was after the Bootcamp update.

I assume by default memory allocator, you are referring to my launch options that I have set. I currently have been using "-maxMem=2047 -maxVRAM=2047 -malloc=jemalloc_bi", in the hopes to provide myself some more stability. I have tried playing under multiple launch options, with no success. Clearly it has not been working, so I will remove them.

I will attempt to supply another crash dump tonight. Thank you for your response.

I have updated with more crash dump files.

Everything after my DxDiag is new and after the Bootcamp update. I have also removed all of my launch options, including -malloc=jemalloc_bi, which I believe is the memory allocator you were referring to. If there is something else I need to change or try please let me know.

Also please note that some of these files still only contain the rpt file alone, and others contain all 3 file types. I believe the ones that only contain the rpt are crashes that happen really quickly, like while I'm in a lobby before I even start a game. Not positive on that though.

Lastly, I've been finding that some servers I crash quicker than others. For example, if I'm playing King of the Hill CA#1, I can usually not crash for quite awhile. Other servers, like King of the Hill US#1 (which shouldn't be any different), I tend to crash almost immediately. Regardless though, I still crash in the end no matter where I go or what I'm playing. I doubt that information is helpful, but just wanted to be comprehensive.

Thanks again for your help.

I have uploaded a more recent crash dump. There have been many more on top of this one, but I figure you don't need all of them.

I had one crash that produced a file that was too large to upload. Mdmp was 39,000KB. Zip file wouldn't upload.

Also, there is a similar report made by another player recently, found here:

http://feedback.arma3.com/view.php?id=19628&nbn=12

I've found that if I preload the map ahead of time with the editor, I can prevent crashes on the launch of a mission, which I was also having issue with. I still crash once in the game eventually.

That's got to point you in the right direction for a solution to at least those launch types of crashes.

Perhaps this is a problem with loading certain files. Loading can fail on start of the game, and if you do get passed that hurtle then loading of a certain asset while within the game eventually occurs and also results in a crash.

I'm just trying to get the ball rolling with ideas. Please help us out with this.

This is the common error report that I get in my event viewer when the game crashes. Sometimes it says module "unknown", sometimes it says "msvcrt.dll", sometimes it says "arma3.exe", sometimes it says "PhysX3_x86.dll". In other words, different things are causing the crash according to Windows.

Faulting application name: arma3.exe, version: 1.24.125.979, time stamp: 0x53bea38c
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00001024
Faulting process id: 0x1b78
Faulting application start time: 0x01cfabbec8427b31
Faulting application path: F:\Steam\steamapps\common\Arma 3\arma3.exe
Faulting module path: unknown
Report Id: b42f0aa8-17b2-11e4-b47c-94de8066e3bb

Omacha,

I recently responded to threads that appeared similar to mine from users iburnfurbies and jls1cm. I do not recall responding to a thread by you, but I apologize if I did and was confused on the issue.

Even if this was the case, why do you suggest recreating my ticket? My issue may be different from yours, but my problem still stands on its own.

My ticket was created a couple of weeks ago now, and I've been having this problem for months. I'm really hoping someone gets back to me soon.

(not relevant)

Hi UGoBooMBooM,

I'm deeply sorry, I somehow landed on the wrong issue via my mail. I will delete my comment as of now.

Edit: I maybe followed your issue once... Whatever, good luck with your problem and I hope you're going to find a solution :)

New update 7/31/14

I have recently gone back to using various memory allocators to try to find some stability. I have seen some success with -malloc=system. I still crash regardless, but this seems to help me crash less frequently at the initial load, and also last longer before crashing.

I also recently reinstalled the game again. This time I switched it from my SSD to my HDD, in the hopes that the SSD was my problem. It was not the issue, as I am still crashing.

The next thing I will try is obtaining a copy of Windows 8.1 and seeing if my copy of Windows is the issue. Please note that I have already reformatted (that's why my crash dumps only began at 7/5), but a new and different OS is the only remaining thing I can think to attempt.

If it's not the SSD, and it's not my memory (I've run so many tests, it's not the memory), then the list is getting shorter. I highly doubt it's my video card (drivers are up-to-date and safely installed, temps and loads seem normal). Perhaps it could be the game's interaction with my motherboard or CPU (I'm not overclocked). Again though, I do not crash in ANY other game that I own. I'm suggesting that it is ARMA's interaction with my hardware that is the issue, not the hardware alone that is the issue.

Since the problem is not widespread, I can accept that there may be a very specific problem with ARMA interacting with certain hardware. However, it can not be an issue that is so specific that it's just my problem alone, as there are multiple tickets similar to my issue that crop up on a weekly basis. Here are some more:

http://feedback.arma3.com/view.php?id=19776
http://feedback.arma3.com/view.php?id=19628&nbn=12
http://feedback.arma3.com/view.php?id=20040

Please acknowledge that this is an issue that is being addressed. And please let me know if I'm spreading misinformation in these other threads about the issue. If anything I've said is false and unhelpful, I will certainly stop, but you must let me know. Discussing the issue with others is the only thing I can attempt to do now, in the hopes of someone finding a miracle cure.

Also, the newest crash dump I uploaded today (7/31) is with -malloc=system enabled. Perhaps having a dump on a different memory allocator can help you in some way.

Hello,
we applied couple of fixes based on your crashdumps, they are implemented in Steam Dev rev. 127768 and higher. Could you please try it on your end?

Mass-closing all resolved issues not updated in the last month.

Please PM me in BI Forums (http://forums.bistudio.com/member.php?55374-Fireball) if you feel your bug was closed in error.