Fix For Rage Drivers Crashing Other OpenGL Games Or Applications

Posted: October 11th, 2011 | Author: | Filed under: Hardware, Tips/Tutorials
Tags: , , , ,

UPDATE: Apparently 11.10 is now fine with the apps and games that the Rage drivers broke, so you’d want to update to the final release. Some people’s Rage turned blue, so those people should just use the atioglxx.dll from the Rage driver that works best for them (put it in Rage’s game folder): 11.10p v1, 11.10p v2, 11.10p v3.

I’m seeing reports of people saying that the Rage drivers broke all other OpenGL applications or games. No problem, there are two ways to quickly fix this for yourself.

You can go back to having 11.9 WHQL installed for the system, then simply place atioglxx.dll from the 11.10p Rage driver into Rage’s folder. (Wherever rage.exe is located, I don’t have the game.)

Or if you just want to fix 1 or 2 things while keeping the 11.10 preview installed for the system, just put atioglxx.dll from 11.9 into the game or application folder of what you want to fix. Java based games like Minecraft or Spiral Knights actually run java.exe, so you will put the dll into Java’s ‘bin’ folder instead.

I put in a couple other OpenGL driver files, atigktxx.dll and atiglpxx.dll, just in case if using the single atioglxx.dll alone did not work.

By the way, these are 32-bit dlls for 32-bit games/apps/Java. As for issues in Rage itself, I can’t do any tests since I don’t have the game. (Which would be useful since I’m a 4870×2 and I hear 4 series has the most problems at the moment.)

Last Modified: November 1st, 2011

23 Comments »

Fix For Enemy Territory Quake Wars atikmpag BSOD On Recent Catalyst Drivers

Posted: October 2nd, 2011 | Author: | Filed under: Hardware, Tips/Tutorials
Tags: , , , , ,

UPDATE: 11.12 seems to work fine, this should be good for 6 series cards that can’t use old dlls.

Not sure how widespread this is, but on my 4870×2, ETQW will freeze after a few seconds of playing and then BSOD with “Attempt to reset the display driver and recover from timeout failed.” The STOP code is 0x00000116 with atikmpag.sys as the faulting module.

This happens on… let’s say recent drivers. I can successfully play without issue using the handy 10.4 atioglxx.dll, which is the latest most stable driver for older OpenGL versions or games. I also used atigktxx.dll just in case. Simply place them into the main ETQW folder.

I’m also seeing that Doom 3 has a driver reset after a minute of play or when vsync is enabled, so the 10.4 files fix that as well.

Last Modified: December 15th, 2011

6 Comments »

Fix For CityEngine Startup Crash

Posted: July 19th, 2011 | Author: | Filed under: Hardware, Tips/Tutorials
Tags: , , , , , , ,

Here’s a similar situation to the Cities In Motion issue, this particular CAD software also has a problem running on ATI/AMD drivers newer than Catalyst 10.4, or at least 10.4 looks reliable enough to function properly. After launching, amdkmdap has a driver reset when the 3d rendering panel appears, crashing the application.

The fix is nice and simple, just place the appropriate OpenGL driver into the program’s folder where CityEngine.exe is.

If you have any other OpenGL game or application that is crashing after 10.4, try this fix or the Cities in Motion one.

For 32-bit: atioglxx.dll
For 64-bit: atio6axx.dll

Your card should support 10.4 drivers in the first place, I have no idea what you would do if you’re using one of the latest Radeons or if you’re using an nVidia card.

Last Modified: July 19th, 2011

No Comments »

Cities in Motion (and possibly other OpenGL games) Startup Crash Fix For ATI/AMD Cards

Posted: February 10th, 2011 | Author: | Filed under: Hardware, Tips/Tutorials
Tags: , , , , , , , ,

UPDATE: I was curious as to what this FAQ item was for Atom Zombie Smasher, so I tried the demo. Nothing appears, just the exe starts up. Seems the same atigktxx.dll trick does the job for this game as well, it loads up just fine now.

Looks like Cities in Motion is an OpenGL game with the exact same issue that The Polynomial had for a few months. On drivers after Catalyst 10.4, it appears crossfire is breaking the game from working, and there is no way to disable it on a 4870×2 like myself. Some single gpu cards may be affected, so you might as well try this, too.

The simple fix should be placing 10.4’s atigktxx.dll into the game folder. Here’s an alternative fix that may or may not work for you if you have tried this atigktxx trick.

Do note that the file is from the 64-bit Vista/7 drivers, I’m not sure what the effect will be on 32-bit, XP, or on the latest 6 series cards. If you have crashes or freezes that happen after the game menu has loaded, then you might have a different problem unrelated to this. The beta, demo, and final release all should act the same. If the demo worked before (on drivers after 10.4) while the final does not, then you probably have a different issue.

Last Modified: September 15th, 2011

50 Comments »

Fix For The Polynomial Startup Crash

Posted: November 26th, 2010 | Author: | Filed under: Hardware, Tips/Tutorials
Tags: , , , , , , ,

FINAL UPDATE: This post is a mess… this should not be a problem anymore for anyone. You should be on drivers newer than 11.2 or older than 10.5. This used to affect the BIT.TRIP games, but those run fine now as well. What has not yet been fixed in updated drivers is Cities in Motion.

FINAL FIX: Turns out you just need atigktxx.dll in the game folder! No mess, not even the main atioglxx.dll. Download the 10.4 dll here, place it where polynomial.exe is, done! I also noticed after installing Catalyst 11.2, the dll might not be needed anymore.

FIX ATTEMPT: I tried a brute force method, I put every driver file of 10.4 into the game folder. You can do this while still having whatever newer Catalyst you have installed, just run the 10.4 installer, cancel it, open a cmd prompt at C:\ATI\Support\10-4_vista64_win7_64_dd_ccc_wdm_enu\Packages\Drivers\ Display\W76A_INF\B_98282 or similar, then simply ‘expand -r *.* c:\pathtoyourgamefolder‘ and voila! I have not yet tried deleting any of the files 1 by 1 to see which ones are required to stop the BSOD so the game folder would look cleaner, but so far it works!

UPDATE2: mixed reports saying 10.12 is good, it’s almost a guarantee that it’s good for 5970 users that were stuttering, but it’s the same crash for me still on 10.12.

UPDATE: this might be affecting Bit.Trip Beat as well. Something to do with crossfire, but there are some reports of 5970s working fine.

So I finally attempted to try the demo of The Polynomial, but the driver is crashing on startup of the game (it’s in OpenGL). I’m trying this on a 4870×2, Catalyst 10.11 WHQL, latest CAP, Vista 64.

It might be something to do with crossfire, or at least in my case and this user. The developer is also active in that thread, and I’ll try to get some form of exposure to ATI/AMD, so we’ll see how this goes.

Workarounds

-The whole older driver package: refer to the working fix at the top of this page.

Current iD Tech games (with this side effect! depends on the visualizer options): doom3.exe, etqw.exe, prey.exe, quake4.exe, wolf2mp.exe

Riddick Butcher’s Bay profile looks like a bunch of detail is lost, and the bloom is lower resolution, yet the bright flashing lights are gone: sbzengine.exe

An older atioglxx.dll: I tried 10.2 and 10.4, the game launched without glitches, but has a BSOD soon after. This must be because crossfire changed at 10.5, as mixing dx10/11 dlls older than 10.5 would also BSOD in Shattered Horizon and Bad Company 2. If you’re ok with not having the latest drivers (if you don’t need the fixes in there), you may be able to get away with installing 10.4 and just the latest CAP.

RadeonPro recently added some OpenGL support, but the crossfire options are not functional just yet. I can’t think of any DX9 things to test if the ‘disable crossfire’ option is different from just disabling CatalystAI, but if it is, then this would end up a working solution once this app is updated.

Dark Athena, older Quakes, Unigine, FurMark, and a couple other profiles I attempted to launch act like the original game’s driver crash.

 

I will update this post if there’s a workaround better than the iD one, if there’s some combination of settings to try, or if either the drivers or game manage to fix it.

Last Modified: September 15th, 2011

3 Comments »