No AMD Graphics driver installed error message coming up despite them being displayed in device manager

CriKeyy

Commendable
Oct 28, 2016
2
0
1,510
Hey guys,

So I have been having troubles with my graphics drivers and after reading many suggestions about uninstalling/reinstalling in device manager and through a uninstall wizard etc. sadly none of that has worked for me. I even tried doing it multiple times as sometimes people would comment to try that and still nothing. So I decided I would ask for help specific to my computer and just hope for a solution.

So the problem is I am getting like no FPS when trying to play games, I decided to look into the device manger after reading about other people experiencing the same problem and getting advice on numerous forum posts, when I originally looked it was saying that I was getting an error code 43 on the graphics card, which seems to be temporarily gone now? So as I said before I would uninstall and reinstall the drivers multiple times but still nothing and now when I try to open the settings for my graphics card I get an error message saying I don't have one installed even though its showing them in the device manager. Please HELP!

I am no tech savvy computer person at all but I have tried to collect all the information I think will be needed to help find a solution, if you require more details just comment.

Error code:
http://imgur.com/WtTlFms

Device manager showing the graphics card:
http://imgur.com/TS5F2sj

PC specs:
http://imgur.com/eWfmYWr

Thanks in advance!
 
I have seen this before. try this

1) Go to all settings, then search for programs and features and uninstall all ATI/AMD drivers you see.
2) got to the official web page for DDU (http://www.wagnardmobile.com/?q=node/110) and run this program and let it find the residual ATI drivers lingering in the background, and stuck services, and reboot
3) LET WINDOWS find the drivers and come up normally (2-5mins) reboot.
4) download a fresh driver from AMD (http://support.amd.com/en-us/download) and install a fresh copy. then REBOOT.
test again.
 

CriKeyy

Commendable
Oct 28, 2016
2
0
1,510


Tried doing your suggestion, unfortunately did not work.