City of Heroes: Live Forum Archive

Game freezing with EVGA Precision/MSI Afterburner

je_saist

By je_saist,
Posted on: 2010-08-14 09:59 in ALL ACCESS Gameplay Technical Issues Bugs

 

Posted

Like the title says, the game is freezing for me while running EVGA Precision or MSI Afterburner GPU overclocking/monitoring software (and most likely would also freeze with RivaTuner, as these two programs are derivatives of it).

CoH will run if I'm running either of those programs, but it will lock up if I attempt to adjust any graphical options or log out of the game. I'm not the only person who's encountered this bug, as there was a thread (here: http://boards.cityofheroes.com/showthread.php?t=231842) that originally gave me the notion that it was Afterburner that was giving me the lock up problems. With Afterburner off, no lock up problems; with it on, I can't adjust any settings or properly log out.

Of course, the simple solution is to simply not run any of these programs while running CoH, but that's just a pain for me, as I prefer to be able to monitor my system temps and performance while gaming to stay ahead of any problems.

I'm just wondering if anyone has come up with a workaround for this issue, or if they know of a program that monitors video card performance/temperatures in a similar way, with an on-screen display or Logitech LCD display, that doesn't lock up the game?

I haven't actually tried using RivaTuner proper as yet, but my suspicion is that it would also lock up the game.

 

Posted

the only program that I'm aware of that will monitor Nvidia card attributes at the same time an OpenGL 3.x + application is running without interruption is GPUZ. I am aware of similar crashes against Heaven 2.x and Tropics 1.3 running in OpenGL modes under NT6.



However, I think you'll find that GPUZ doesn't monitor as many attributes as RivaTuner derived applications, nor does it allow control over the attributes of the gpu's through Coolbits. In addition, you have to run CoH in Windowed mode.

I think this is actually a combined issue with the way Coolbits attributes are exposed when running through OpenGL, and the method by which Microsoft implements OpenGL support under NT6, given that I've not heard of anybody encountering this issue under NT5.

It is likely you will be waiting on Nvidia to issue a driver level fix.