Question

Why Windows did not recognize GPU after reinstall

Long history short, i updated my AMD RX 560 drivers, i had some resolution problems and my second screen wasn't working, i reinstalled Windows 10 64b because i was fed up, but now my GPU is not getting dedected in any way shape or form, trust me, i tried EVERYTHING, the hardware Works on other computers, i cleaned it, its a software problem,

Things that i tried:
Updating BIOS
Updating Windows
Updating all my other drivers
Cleaning the hardware
Hardware dedecting programs
Msconfig
Device manager
Clean install of the right driver
AMD Auto install doesn't work, it showed the 182 error and now it says its already installed?
Installing C++ Packs
Re-re Installing Windows (i lost all my stuff)
DDU


My mother board and other stuff:
asus m5a78l-m lxbr - motherboard
amd rx 560 - gpu
Windows 10 64b- OS
amd fx-6300 six core 3.50 ghz - Processor

Discussion is locked

Answer
Follow
Reply to: Why Windows did not recognize GPU after reinstall
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: Why Windows did not recognize GPU after reinstall
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Comments
- Collapse -
Answer
maybe pray over it?

It's dead, dead, dead.

- Collapse -
Answer
Nope. Windows does NOT do this for us.

Samsungs and other models require you stick to the maker's issued drivers.
Samsung on top of that may not hand out drivers but some driver update app. YES I do see this appears to be some built desktop.

And BEST OF ALL REASONS: Microsoft Windows has NEVER installed drivers, BIOS and such in the right order for us. It's been over 2 decades and a Windows install still requires us to work at it to get a good install.

I do not supply step by step instructions as there are a million plus different PCs.
I do however have my own guide and will share it here.

1. Update the BIOS.
2. Take the BIOS defaults with as few changes as possible.
3. Install Windows. (Just Windows, no drivers yet and no this is not a fully functioning PC yet as the driver and app work is not done.

4. Install the motherboard chipset package or drivers.
5. Install the sound drivers.
6. Install the video drivers.
7. Install the rest of the drivers then any machine specific apps.
For example some PCs have apps to enable WiFi or control the PC volume and more.

This install method has served me well for over a decade but seems to upset those that just wanted to install Windows without all that work.

- Collapse -
this is a rehash of earlier thread

I guess he didn't like the answers given in that thread, so this one.

- Collapse -
I would be guessing that. Why?
- Collapse -
I may have gotten crossed up with this thread

Post was last edited on September 30, 2019 4:33 PM PDT

- Collapse -
AMD CPU but so many other changes.

"One this is not like the other.
Something's not quite the same."

- Collapse -
Deja Vu

I had a strong sense of that. I remember a thread where two RX520 video cards were involved, even pictures posted of them, and one never worked, no matter how it was tried. I thought it was here on CNET, but maybe was in another forum I frequent.

- Collapse -
Must be something other than RS520.
- Collapse -
PS. I forgot a thing.

There are a few machines that we must ALWAYS disable Microsoft's Driver Update feature. This could be one of those.

Post was last edited on September 30, 2019 2:51 PM PDT

- Collapse -
Grif writes about this thing at this link.
https://www.cnet.com/forums/discussions/windows-10-fall-2019-upgrade-coming-soon/#post-f9cdc520-6b21-482a-89c4-60be653c4173

"Sounds Like You Still Have Auto Driver Updates Enabled

For most, the best option is to disable Microsoft's automatic installation of device drivers. That way, they can't automatic install such drivers and cause the problem. And if the drivers have been incorrectly installed by Microsoft, then visit the network device manufacturer's website, or the computer manufacturer's website and install the correct network drivers from those sites.

Once that's done, disable automatic driver updates by using the steps below, then in the link below:

First, open the Control Panel, then System, then 'Advanced System Settings" on the left, then the "Hardware" tab, then "Device Installation Settings" button, then select "No". After that, follow the steps in the link below:

https://www.windowscentral.com/how-disable-automatic-driver-updates-windows-10

Hope this helps.

Grif"
- Collapse -
Just heard from Lee K.

He confirmed that history, posts and such remain if the user or others change the member's name.

- Collapse -
That's good to know

I've often wondered, but never had asked. Thanks for that info.

- Collapse -
Answer
getting back to the problem.
"fx-6300 six core 3.50 ghz - Processor & AMD RX 560 drivers"

The CPU has no integrated graphics, so that's not interfering at all in this.

The motherboard does have an integrated graphics chip onboard.

"Integrated ATI Radeon™ HD 3000 GPU
VGA output support : RGB port
- Supports RGB with max. resolution 2048 x 1536 @ 75 Hz
Maximum shared memory of 1024 MB
Hybrid CrossFireX™ Support
Supports DirectX 10.1"


So, there's two Radeon graphics involved.

Can the onboard video run a monitor at this time? When you installed drivers after reinstall of W10, you made sure to install the drivers for the onboard video chip also? Has W10 done any updates since that time? If so, then W10 may have installed different driver files. Do you have W10 set to disallow new hardware/ driver updates yet?
- Collapse -
Answer
Solution

This is usually caused by incompatible drivers so be sure to update them.

CNET Forums

Forum Info