AMD 13.8 beta driver glitch

djinno

Honorable
Jul 28, 2013
19
0
10,510
I don't know if I am the only one having this but I noticed something different after I upgraded to this new driver.

I am running on crossfire and have ULPS enabled. With that being said, after I play a game for about an hour or so, I would always leave my Firefox open so as to retain the secondary GPU active and be cooled gradually instead of just shutting down at once.

To my surprise it shows on my Afterburner that the secondary GPU is still at 100% usage keeping the temps up as if I am still gaming.

I already tried uninstalling and cleaning up my system before reinstalling the new driver but it remains the same. The only thing that gets it back to default is by rebooting the PC.

Any inputs on this or experiencing the same thing and has a better solution?

here's my PC spec:

CPU: AMD Vishera Fx 8320
mobo: Gigabyte 990fxa-ud3
RAM: Gskill 8Gb (2x4Gb) 1866mhz CL9
GPU: Sapphire 7950 Flex xfired with Powercolor 7950 v2
PSU: Antec HCP850W
 

djinno

Honorable
Jul 28, 2013
19
0
10,510


I used the ATIman uninstaller and then I used CCleaner.
 
ok both of you try using driver fusion instead to clean the driver remnants.

uninstall current driver and dont restart.
run driver fusion and clean amd drivers.
install latest amd beta driver 13.8 as a custom install and only install the display, hdmi driver (djinno install catalyst aswell for crossfire)

doing this always fixes driver problems and works better than ati uninstaller.
 


I don't see why I should need to use third party software, shouldn't AMD's own uninstall software just work properly?
 
just like nvidia they both end up leaving remnants behind such as configuration files and even driver components so its good to use driver fusion, it has fixed every graphics driver problem me and my friends have ever had and i run driver fusion between upgrading drivers as standard now for the best compatibility.

it is perfectly legitimate software, it can cleanly remove quite a few other manufacturer drivers as well that can cause problems.
 


But as I never needed to use such software when changing the drivers on any Nvidia card that I've ever used I don't see why I should have to use it for an AMD card.
 
then you were just lucky that your drivers didnt corrupt at any time, friends of mine with nvidia cards had many driver problems solved with driver fusion cleanly removing the driver.

its not that you need to, its just that if a driver corrupts then a regular uninstall will not fix the problem but a clean uninstall using driver fusion will which is what has happened in your case its not a matter of which drivers were better or what they should do, the simple fact is the driver corrupt somewhere for some reason and now its causing you the problems you are having.

i just do it as precaution and for best compatibility since the old driver i know then is completely removed.
 
if you previously had a nvidia card in the system it still probably has a lot of nvidia driver remnants left which driver fusion can easily and quickly clear also.

its up to you mate, either try it or leave it, its a quick and easy fix, just trying to help fix a problem.
 


because you can often get nice performance improvements and bug fixes for games months ahead of a WHQL release.

if you clean your old drivers before upgrading i rarely have problems with beta drivers.

often the beta drivers are practically release stable, they are just called beta since they have not gone through WHQL testing such as the 13.2 driver is basically the 12.11 beta 22 driver just having been through WHQL.
 

It's a clean install of W7 so that blows that out of the water doesn't it!
 
I've tried this card on two installs of W7 and was actually having better results on the old install that had been running Nvidia cards! Then I was able to change the driver to the 13.6 beta but kept getting the random 100% GPU usage when the PC was just sitting idle on the desktop with only MSI Afterburner running and on the clean install 13.6 BSOD'ed straight away but 13.4 installed just fine and now I'm stuck with it!
 

djinno

Honorable
Jul 28, 2013
19
0
10,510



currently running a game as of the moment. that's odd you were getting that on a 13.6 beta too? Mine was good and fine on 13.6 beta.
 

djinno

Honorable
Jul 28, 2013
19
0
10,510
I give up... reverting back to the previous driver. I thought this was to improve my xfire experience but instead it almost burn out my 2nd GPU. AMD should really check on their drivers first specially if it will cause damage to the hardware.
 
I actually sorted the issue I was having and mauller07's insistence that I use a driversweeper program like he advised would really have just been a waste of time and not helped with finding the cause of the problem, which turned out to be the HDMI component of the 13.8 driver package and nothing to do with previously used cards or current software.
 

djinno

Honorable
Jul 28, 2013
19
0
10,510


does this mean it's a driver issue? or there is still something I could do in my end to keep the 13.8 driver without getting the glitch?
 

DiGLoW

Honorable
Aug 17, 2013
1
0
10,510
my solution is if you're having problems in crossfire just disable and re-enable it (if you just updated the driver) otherwise download and run DriverSweeper and install the 13.8 clean. A lot of the time when updating drivers specifically AMD ones the windows installer doesnt properly extract and install the driver if there was one previously. so it will keep old ati/amd system files causing corruptions I.E BSoD