• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

driver update issues

mdp

Weaksauce
Joined
Sep 17, 2007
Messages
87
I've been running the 13.9 drivers since I built this PC (specs in sig). With all the new betas coming out, I wanted to try them, however, I've been having an issue with all of them upon install. Everytime I try to do a clean install by uninstalling the old drivers using AMD's catalyst uninstaller, and then installing the new drivers, the system blue screens at the Windows login screen and I have to go back in and revert to the 13.9 drivers.

With the beta v9.2 that just came out, I tried again and same issue. So today I installed the driver over my existing 13.9. This seemed to work finally...until I tried to run GPU-Z. I tried twice and it bluescreened both times. After rebooting (and not trying to run GPU-Z again) I was able to run 3dmark11 ( score: http://www.3dmark.com/3dm11/7454313 ) and even play a little bit of BF4 single player campaign without issue. So I tried GPU-Z again and it worked. It's been working fine now for a couple hours with no instability.

Was the GPU-Z issue just a fluke? Why wouldn't the drivers work when trying to install them clean? Should I do anything else to make sure the system is fully stable? Thanks... :)
 
Perhaps certain low-level video card settings had carried over to the new drivers, causing the issue? To my knowledge, the official uninstallers, be it AMD or NVIDIA, don't do a thorough job at removing all traces of driver binaries and settings.

Did the BSODs show any error codes?
 
I should have taken a pic of the BSOD, but didn't. I did notice it said something about graphics drivers though. I guess if it does it again, I'll reproduce the issue and grab a pic so that I can look up the error code.
 
Back
Top