"Display Driver AMD Stopped Responding Has Successfully Recovered" Only on Arma 2

[Adam9111 0]

I'm running the Steam version of the game, launching the game with Six Launcher. Launching the game as

ARMA 2 OA Beta Version 160.94700.

When I play the game it crashes after between 30 sec to 20 min, starting with the game freezing and then tabing

itself down to a white screen and sound still working. Up comes and error message "Display Driver AMD Stopped Responding Has Successfully Recovered". Then I have to Ctrl+Alt+Delete too shut down the game.

THIS ONLY HAPPENS WITH ARMA 2. Can play games like BF3 without problem.

I've reinstalled Arma, dayz mod, drivers and my computer.

Grafic card: AMD Radeon HD 6850

Operating System: Windows Ultimate 64-bit

CPU: Intel i5-2500K CPU @ 3.30GHz

Motherboard: Asus P8Z68-v

RAM: 16GB

So please if anyone knows a possible solution or have had the same problem. Please share some info, it will be much appreciated and I really like to get the full experience of DayZ without having to restart every minute.

[icomrade 201]

update your drivers.use 12.7 http://support.amd.com/us/gpudownload/windows/Pages/radeonaiw_vista64.aspx

[dsfjuicifer@live.co.uk 0]

I had the same problem, it was caused by video's running in the background (my youtube song playlist). The second I closed down youtube in the background my drivers work perfectly fine again.

[Adam9111 0]

I updated the drivers before, but gonna try a beta update.

And Im only running Steam and Skype in the background and it still happens :(

Edit

Installed latest Display drivers and game crashed after 1 minute.

Edited July 11, 2012 by Adam9111

[Nipos 3]

Which OA Beta version are you running? I had the same issue about a week and a half ago, but it magically disappeared after not changing anything but the OA Beta versions. During the time of getting the "AMD Driver has stopped working" errors, I was using OA Beta versions 94209 and 94364 (maybe even the version before 94209, can't remember). After updating to 94444, DayZ/ArmA II has been working perfectly, and the issue seems to have gone away.

Here's what I posted in another thread that was addressing this problem:

Sorry for necroing this thread, but I've been having the same issues in 1.7.1.5.

I've been monitoring my graphics card, because at first I thought it might be a temperature-related issue, but I'm fairly sure that's not it; temperature is sticking around 60-65 degrees Celcius when playing DayZ (idle/non-gaming temperature is between 44-48 degrees). I can run games like Battlefield 3 and Skyrim on high settings for hours without any problems.

After some searching, I found that this issue was present in earlier builds of ArmA 2, but was supposed to be resolved. Maybe it came back due to DayZ-specific content/code?

System specs:

-AMD Phenom II X4 955 Black Edition @ 3.2 Ghz (no overclock)

-HD5850 Toxic 1GB @ 820/1165 (slightly overclocked, standard clock is 765/1125)

-8GB DDR3 SDRAM

-2 x Samsung Spinpoint F3 1TB 7200 RPM

-Be Quiet! 520 Watt PSU

-Windows 7 Home Premium 64bit, SP1 (all latest updates present)

Software versions:

-DayZ: 1.7.1.5 (didn't notice these issues with previous DayZ builds)

-Operation Arrowhead Beta: 94364 (issues were present while using earlier versions too)

-AMD Catalyst Driver: 12.4

-Latest DirectX version

Like I said in the post, after some Googling, I found that ArmA II has been plagued by this issue before, so it's very likely - also looking at the thread where I made that post - that it's an ArmA II bug of some sorts. I'm still using the same AMD Driver version when I had this problem, by the way (12.4).

[Adam9111 0]

Ok thanks! I think i have Beta 94700, it says "version 160.94700" on the main menu in ARMA 2 OA, down in the bottom right.

Downloading 94444 now

Edited July 11, 2012 by Adam9111

[Nipos 3]

Have you been updating your OA Beta versions regularly (in other words; did your game crash/AMD Driver stop responding using earlier OA Beta versions)?

[Adam9111 0]

I uninstalled the whole game about two weeks ago, give or take. And I reinstalled the game through steam and the used six launcher to install the mod.

So I cant say I've been updating the beta, if i have, it has been auto through Steam or Six updater

[Adam9111 0]

I have the 94700 active now, "Version 160.94700"

How do I uninstall that version? Because when I installed the 94444, it didn't change to that version in the menu "version 160.94700"

[Nipos 3]

Alright, try installing an older OA Beta version (94364 or 94444) and see how that works out for you. This way we have a chance of ruling out the OA Beta as the cause. You can get those here: http://www.arma2.com/beta-patch.php

Delete the "beta" folder in your "arma 2 operation arrowhead\Expansion" folder first before installing a different beta version! That's the only proper (manual) way to uninstall OA Beta.

Edited July 11, 2012 by Nipos

[Adam9111 0]

Okay next problem, I deleted the beta folder, installed 94444 and then Six Launcher updates the beta to 94700. When I start the game through Steam it doesn't say Beta on the right side at the main menu and the version number in the bottom right is 160.8 something.

Can I make Six Launcher not update the beta?

[Nipos 3]

I don't know, actually. I've always avoided the use Six Launcher (mainly because of stuff you're encountering now). I've been updating DayZ and the OA Beta manually ever since I started playing DayZ to have full control over installing/uninstalling stuff, without some program forcing updates etc.

Also, make sure you've got the Beta set up properly (I don't know to which extent Six Launcher does this for you already):

1) Go to the Arma 2: Operation Arrowhead directory and right-click -> edit on the .cmd file "_runA2CO_beta.cmd".

2) Search for ":run" near the end of the file. Add ";@dayz" without quotes to "-mod=%_ARMA2PATH%;EXPANSION;ca" if it's not there already. It should say "-mod=%_ARMA2PATH%;EXPANSION;ca;@dayz".

[Adam9111 0]

Did all you said, started the game without steam or six updater. Now have 94444 patch but still crashes.

I'm gonna try some other patches using the same method. Will be back with update in a bit.

[Remix (DayZ) 14]

Hi,

Might be worth trying a Six Launcher replacement:

http://webcache.googleusercontent.com/search?q=cache:1AMTlOBYx98J:dayzmod.com/forum/showthread.php%3Ftid%3D31842+&cd=1&hl=en&ct=clnk&gl=au&client=firefox-a

[Nipos 3]

Hmm, it seems that the OA Beta can be ruled out as a cause of these crashes. There are a couple of things you can do:

1) Update your DirectX, so you're sure you're using the latest version (http://www.microsoft...aylang=en&id=35)

2) Fiddle around with the Video Memory settings within ArmA II. I've got mine set at Default, using the the full memory available on my GPU that way.

3) Try installing older AMD drivers. I'd recommend starting with 12.3 or 12.4. I'm currently using 12.4, and whilst having had the same issue with this driver about one and a half week ago, it only showed up about three times. Game has been running properly after that (with still keeping 12.4). Go to http://downloads.guru3d.com/search.php and do a search for "Catalyst". It will bring up a list of pretty much all previous Catalyst driver versions.

[Adam9111 0]

Okay thank you. I'm gonna try these things and see what happens, so far game crashes with the latest 4 beta patches.

[Adam9111 0]

Okay, had the latest DirectX and set the video settings in Arma to default.

Downloaded Catalyst 12.4, just ran the installation and played, game crashed.

Do I have to uninstall Catalyst 12.7 or something to replace it with 12.4 or is it

automatically replaced when installing the 12.4?

Edited July 11, 2012 by Adam9111

[Nipos 3]

Do I have to uninstall Catalyst 12.7 or something to replace it with 12.4 or is it

automatically replaced when installing the 12.4?

Well, that has been a debate going on for years. Some say it's best to remove a previous driver (with the uninstalling program that comes with it, and using a program like Driversweeper in Windows Safe Mode after that). Others say it doesn't matter, and you can install newer drivers "over" older ones.

I personally never remove older drivers first, unless there's something really borked.

[Adam9111 0]

Well tried just about everything to solve this problem, nothing seems to work.

I'll guess I have to wait for future patches and hope for the best.

Thank you very much for the help!

[Remix (DayZ) 14]

Hi,

You can always try some general troubleshooting fixes:

- Updating to 1.7.2.1 (to see whether it's patch related).

- Try running Steam as an admin. Steam has to edit the registry to apply Arma 2 keys when you run the game.

- Check the integrity files of ArmA OA via steam.

- Restart your PC after all this.

- Ensure you're running from Six Launcher.

- Launch from another launcher, I reccommend DayZ Commander.

Again, I really don't know these will help but you can always try.

Let me know if any of these help mate, cheers.

Edit: It seems you've illeviated the driver crashing issue, correct? If you have, honestly, we should be able to troubleshoot your issue.

Edited July 11, 2012 by Remix

[Adam9111 0]

Thanks Remix for your tips, i will try them out later tonight and post a mini report here later :)

Edit

Checked the files via Steam and first time it was two files failing to validate (think thats the translation from swedish).

Then I ran it a second time and it was one file failing to validate. And ran it a third and a fourth time and always one

file.

Think that might be the problem?

Edited July 11, 2012 by Adam9111

[Nipos 3]

The one file failing to validate is nothing to be worried about, that happens with pretty much everyone. It's just an install script being newer than the default script that Steam's trying to validate and is just a small glitch in Steam's validating system. Just Google for "arma 2 failed to validate" and you'll see tons of threads and questions about this.

It's not related to your problem. :)

[Adam9111 0]

Nothing seems to work....

Still crashing after updates, patches and adjustments.

[Nipos 3]

Weird, man. I don't know what to say...

Have you tried underclocking your GPU a tiny bit? Just go into AMD Vision Control Centre --> Performance --> Graphics Overdrive and turn the clocks one or two nodges down (both top and bottom slider). You may have to enable Graphics Overdrive first under the AMD Overdrive tab, found under the same Performance tab at the bottom (if you've never enabled it before).

[Adam9111 0]

Okay back with some possibly good news. I played last night a little without any crashes, going to play some more to day to really see if it's working.

But what I did was installing the DLC "Private Military Company" because I read somewhere it was "recommended" to have it installed.

I also updated my motherboard BIOS. But not sure if it's 100% fixed but I'm by tonight I'll have an answer. Also DayZ update 1.7.2.3 might have something to do with it.

I'll be back!

Edited July 15, 2012 by Adam9111