OA video driver crash on GTX 280

[metalcraze 290]

CTDs on GTX285s have nothing to do with this issue.

This issue exists only on GTX260-280-295 chip tech which are the same (260 is 280 minus 1 core, 295 is two 260s) and causes game's renderer to crash, not the game itself.

I'm planning to wait for GTX560 most likely (provided the price will be adequate) but for now I'll just look for solutions.

I just want to know if anyone else experienced the performance drop when videocard is OC'd and the renderer crash happens and no performance drop when the videocard is at stock freqs.

Edited December 24, 2010 by metalcraze

[liquidpinky 11]

Poor BIS programming. Because no matter what driver version is used the issue is the same.

For now you just do what Liquidpinky wrote. Press ESC - if you will see a cursor - press Alt+Enter and then Alt+Enter again.

If you play at stock frequencies the performance will be restored to previous levels and so you won't have to stop your fun coop gaming to reboot. Continue playing as normal. The crash is an annoyance of course.

If you OC'ed the videocard the performance will most likely drop to 2D profile and will stay there.

I have to double-check the last bit though.

You can set the power to performance in NVIDIA control panel to stop the step back down to 2D mode, it is also recommended you do anyway as it has been known to stop some crashes with menus etc.

[metalcraze 290]

Couldn't find power settings in Control Panel of 260.99 and 265.90 so I installed RivaTuner instead where you can force performance mode. Haven't tried it yet because I've yet to experience a crash again. Hope the new beta that has an improved memory detection helps this issue to not return again.

[liquidpinky 11]

Couldn't find power settings in Control Panel of 260.99 and 265.90 so I installed RivaTuner instead where you can force performance mode. Haven't tried it yet because I've yet to experience a crash again. Hope the new beta that has an improved memory detection helps this issue to not return again.

Are they not in the actual ARMA 2 profile set up in NVIDIA control panel?

Can't remember as I havent got them installed now.

[metalcraze 290]

Ah that one. I was not sure if it helps. But I've set it to performance mode.

[seelix 10]

Thanks, I'm going to go out and spend $150+ just to fix a problem with Arma.

Why not ? Its worthy.

[metalcraze 290]

By the lack of the replies in this thread I guess you've noticed that with recent betas issue became more rare?

But as they are still there here's a "fix" that will help you avoid rebooting if you were running your videocard overclocked. Tested only on Win7, not sure whether it will work properly on XP at all.

(this relates only to GTX260, GTX280, GTX295 as they are the same chip tech and have the same issue)

- go into the device manager

- right click on your videocard and disable it

- then enable it*

- then go into your overclocking software of choice and bring the needed frequencies back

You will have to restart the game, but at least there is no rebooting.

*this will reset the driver into default 3D profile, which driver can't find after the error when you have your videocard OC'd and thus sets your videocard to the closest profile which is 2D

If you run your videocard without overclocking however - simply switching to windowed mode (alt+enter) and back after hitting ESC in the game to see the cursor will fix the issue without affecting frequencies and performance or the need to restart the game.

Edited January 12, 2011 by metalcraze

[musp3r 10]

I had the same issue, but with ATI 5770, so sorry if it's a wrong thread, but the issue is exactly the same.

ArmA2 OA freeze, fade to black screen and then switch to desktop, and stays active, as I can hear the sound and see the task running. It was happening on random times, but very often and it annoyed me very much.

I've took a look in event viewer, and saw my ATI driver (atinkvdm or something) has restarted every time i experience that error.

At that time I had CIV5, BF2:PR, MOH BlackOps, Massive Effect 2, and some more graphic and system intensive games running without a hitch. My system was ever stable, i could bet on it. Only ArmA 2 OA had issues. And I wanted to play that.

So I've replaced drivers, fiddled around with driver, game and system options, reinstalled OS, changed memory modules, power supply, disconnected disks, you name it.

I've searched the net for similar problems and on some gaming site (didn't manage to save links) I've read that for some game they had to increase the voltage to the processor, when experiencing same atinkvdm problem. So I've gave it a shot.

Usually, I never overclock my hardware.

My default q9550 processor voltage in BIOS was 1.2v, and i've increased it to 1.3v.

I'm playing ArmA2 OA ever since, not a single problem.

I was scared a bit increasing the voltage, but for that measly 0.1v I thought it will not be that stressful to the processor or mainboard. Give it a shot if you want. It worked on my system, maybe it will work for you.

* DISCLAIMER * It worked for me and my system. If you damage your system i take no responsibility for that in any way.

Cheers,

Mus

Edited January 17, 2011 by musp3r
Thread options

[almanzo 144]

I am still having this issue on my Gtx 260, especially when playing Iron front. Any word from the developers on what's causing this, and whether or not a fix is around the corner?

[MavericK96 0]

I was having a lot of problems with my GTX 280 setup in ArmA 2 until I started using the beta patches. One day the crashes just stopped, no idea why. Could have been some combo of driver updates and patches.

[carlitobrigante 10]

was getting it once in a blue moon with arma2, but every 5-10 mins on iron front so far :-(

[almanzo 144]

was getting it once in a blue moon with arma2, but every 5-10 mins on iron front so far :-(

Yeah, it seems like Iron Front somehow have manage to wake an old ghost. I don't experience it as often in arma, but still from time to time.

It annoys me greatly though, because so far, I've enjoyed what I've got to play in Iron Front very, very much!