"No AMD Graphics Driver is installed or the AMD driver is not functioning properly..." EVERY REBOOT

MrLogic

Reputable
Oct 30, 2015
3
0
4,510
Hey everyone.

Recently for no reason out of the blue, I've started getting this error message after every single reboot I make. I have tried fixing this by:

1. Going to Device Manager and right-clicking my Display Adapter which isn't working and clicked "Update Driver Software". (This worked once then the error came back again.)
2. Downloading and installing Catalyst Drivers, the newest ones after using DDU to uninstall my AMD Drivers.
3. Used SFC /SCANNOW which pretty much did nothing.

Please help me!
What the error message says:
http://postimg.org/image/bk9hz8817/
What the Device Driver screen looks like:
http://postimg.org/image/ye6oe2719/

Please help me!!
Thank you

EDIT: I just checked my Windows Update History and this shows:
http://postimg.org/image/8i12guebl/
 


Sorry, didn't mean to tick your reply as the solution haha.

Heres my specs:
Processor AMD A10-5750M APU with Radeon(tm) HD Graphics
Manufacturer AMD
Speed 2.5 GHz
Number of Cores 4
Video Card 1 AMD Radeon HD 8650G
Manufacturer ATI
Chipset AMD Radeon HD 8650G
Dedicated Memory 2.7 GB
Total Memory 4.0 GB
Video Card 2 AMD Radeon(TM) HD8970M
Manufacturer ATI
Chipset Radeon HD 8970M
Dedicated Memory 2048 MB
Total Memory 2048 MB
Memory 16 GB
Operating System Microsoft Windows 10 (build 10240), 64-bit
Service Pack 0
Size 64 Bit


 


I just disabled my Display Adapter and Re-enabled it, and it seems that the problem is solved. However, this is most probably a temporary solution. I'll let you know if the problem continues.

UPDATE:
Yep, problem still persists.
 
I have the same problem. Tried DDU and reinstalled both 15.7.1 and later 15.10 beta, none of them made any difference.

I can also go into Device Manager, click on my graphics card device "AMD Radeon HD 7800 Series" and Disable/Enable to get it to work until next reboot.

I have a Sabertooth 990FX with a Phenom II X6 1090T and a Radeon HD7870XT. Running Windows 10. I never had this problem under 8.1