I have recently done a complete system rebuild, with everything new (cpu, memory, m/b, even the psu) except the gfx card. So i have tried again, and it's the same crash, running the latest version of Arma, and the error has now occurred in World Of Tanks, so it's not a problem with the software.

I have spent a long time on this, and I now believe it to be a hardware fault on a memory module. The reason it's taken so long to pin down is that arma is a heavy user of the memory on the card due to the details in high quality modes, and most other games were not at the time, but are starting to catch up now, so it's only hapenning in other games now.

The card is 16 months old, but the company I bought it from have confirmed they will still RMA it as it's a hardware fault, so assuming that goes ok, I think we ca close this issue.

Thanks for your help with trying to get this sorted out, and hopefully, I won't be raising another one in a few weeks when I have a new card!

Yes, just tried it, started playing the scuba showcase, and when i pressed M to bring up the map, it locked up.

I had just tried Heroes and Generals, and I experienced the same crash as in Arma III, so I have tried experimenting again.

The crash seems to be related to resolution, when I run a full resolution (2650x1440) version of the benchmarking test you recommended it crashes, but at 1920x1080 it's stable. Heroes and Generals also seems stable at this resolution, but Arma still crashes. I have tried dropping it right down to 1600x900 but it locked up on loading, and I couldn't even get into the game.

Other games seem to run fine at the full resolution.

I'm guessing you have no more suggestions for me on this issue?

Right, cancel my last, it still crashes, but it takes longer. I was able to play through a whole showcase mission, for the first time. Then crashed on the scuba one.

Ok, benchmarking failed on test 22 (I think), so did some more investigating.

It looks like if I have FSAA turned on (at any detail level) it crashes every time (usually when changing to a map).

All other graphics settings appear fine so far.

Any other suggestions for this issue?

No, all HW is stock. What DX11 benchmark would you like me to run? I can try anything if you think it'll help.

Files uploaded here as requested. Just tried the game again, still the same issue.

Just tried running this again, there's been no changes, I still get the same crash.

Is there anything I can do to help sort this out? Some sort of debugging mode I can run the client in?

Just FYI, I'm using 3 22" screens arranged in portrait mode to give a desktop res of 3150x1680. 2 of the screens are DVI, 1 is displayport.

Tried on a single screen with the other two physically disconnected, and I could run the game! My word it looks pretty!

So it looks like an eyefinity issue... any suggestions?

Got the same crash on exit though, after suspending the game and back to the main menu, select exit and PC lccks up, requires re-boot.

Oh, and no, gfx card not overclocked, just factory clock settings.

Yes, exactly the same in multiplayer.

Tried starting an editor game, select editor from the main menu, then as soon as I click start (or continue, whatever the button to proceed is called on the editor map selection screen) I get the same crash, system lock etc.

Tried a re-installation of the game and latest beta drivers, same result.

No, don't get as far as lag. I have yet to see the battlefield, except in map form on the loading screen. :-(

No change running new beta drivers, crashes at the same place.

I'm beginning to suspect it's a video driver issue, I have just had the same type of crash when trying out another new game (star confllct).

I'm running the latest stable version of the catalyst drivers (13.1) but I will download the latest beta drivers (13.3) and report back.

Yes, get the same result.

Files uploaded as requested.