Tuesday, July 17, 2012

ATI display driver issues

I'm running Vista x64 with an ATI Radeon HD 4800 Series graphics card and for a while now I've been periodically getting a BSOD caused by "atikmpag.sys". This has been an intermittent issue that usually happens right after logging into Vista. I've always kept my ATI drivers up-to-date for my graphics card by downloading the latest Catalyst Control Center (CCC) from AMD's website. But I decided to do some digging. Using Windows Device Manager, I learned that even though I'd been installing the latest drivers, Windows was loading an older version for some reason and uninstalling and re-installing the AMD CCC drivers did not rectify the problem.

Device Manager's Driver Properties Window


So I did some Internet searching and ran across a related post that mentioned a free utility named Driver Sweeper (a.k.a. Driver Fusion) that supposedly detects and repairs driver file issues. After uninstalling CCC, I ran the utility and deleted all the AMD display driver files, then rebooted and re-installed the latest AMD CCC and it worked (verified by looking at the ATI driver version in Device Manager). Yay! Will have to wait to see if this resolves the BSOD issue (see my follow-up below).

I did notice one other odd thing: when I installed CCC its default install path was c:\Program Files\ATI Technologies. But after installing, I found all the files under c:\Program Files\ATI and nothing under the "ATI Technologies" folder. Huh? That looked suspicious so during my final install I changed the path to just "ATI" and deleted the "Technologies" part. No idea if this is a real problem or not.

Moral of the story: Even if you've been installing the latest AMD drivers (or any driver), you should double-check Device Manager to ensure Windows is actually loading them. If it's not, you may have some cleaning up to do, and Driver Sweeper appears to have done the job for me.

Follow-up: Unfortunately, even though I'm now running the correct version of the display driver, my system still gave me a BSOD upon login today. Sigh.