Page MenuHomeFeedback Tracker

Game freezes, causes whole PC to lock, reboot required
Closed, ResolvedPublic

Description

Game launched from Steam, select any showcase, loading screen comes up with bar across the top and bar speeds across to the right, the map flashes up for fraction of a second and then I get a freeze with a dark green screen with horizontal lines. The whole PC is frozen, no input works, CTRL-ALT-DEL does nothing, hard reset required. I have tried this at different resolutions, windowed and full screen, and get same results. {F18096}

Details

Legacy ID
1981883990
Severity
Crash
Resolution
Open
Reproducibility
Always
Category
Game Crash
Steps To Reproduce

Launch any showcase after running game from Steam.

Additional Information

Video drivers are latest version, using a Radeon 7970 with triple-head, giving a desktop resolution of 3150x1680 across all three screens. The resolution is reported correctly in the gfx settings, but have tried at 1024x768 with same result.

Event Timeline

Squeaker edited Additional Information. (Show Details)
Squeaker set Category to Game Crash.
Squeaker set Reproducibility to Always.
Squeaker set Severity to Crash.
Squeaker set Resolution to Open.
Squeaker set Legacy ID to 1981883990.May 7 2016, 12:41 PM

have you tried playing with a regular resolution on one screen?

Yes, get the same result.

We need dxdiag and files from this folder for solve your problem. C:\Users\<Name>\AppData\Local\Arma 3 Alpha\

Can you upload somewhere in winrar package please?
When package will be smaller than 5,000k, so you can attach here. Thank you.

http://feedback.arma3.com/how-to-user.html.html

Files uploaded as requested.

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.

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

Game starts up runs fine for me. I get crashes/lock up requireing reboot like this only in vehicles. They seem to happen due too lag? Its only when I stop and start moving again quickly.

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

Do you have same problem in multiplayer?
Can you try start some mission from editor? Add soldier, some vehicle and try start it.
Do you have overclocked graphic card?
Did you try clean instalation of drivers?

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.

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

Can you try it without eyefinity? Have only one monitor connected and try in native resolution of your connected monitor.
Crash dumps were not created and in log file is nothing usable for us, so we need locate where is problem.
Thank you.

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.

We tested and eyefinity worked correctly. This issue is maybe combination of eyefinity and some other software. We will try eyefinity again for sure.

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.

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?

Mass closing ancient tickets with no activity this year; assume fixed or too trivial etc.

If this issue is still relevant in current dev build, please create a new ticket referencing this one and request for it to be re-opened.