16.12.2 may be the latest driver for the 290x . i wouldnt try beta drivers like 17.7.1 with older cards. you could try 17.4.4 or 17.5.2 but if they dont work go back to the correct driver 16.12.2
an rx series beta driver may not work on a r9 card and 5 series versions up. its optional to try but if it dont work i would use the one that doe. mainly if 17.4.4 dont your probably where you need to be.
you could try to fix the code 43 after you install the driver by allowing windows to identify the new hardware as windows thinks it is. but then windows will intstall what it wants the driver to be and most likely 17.6.1 or 17.6.2 but there pretty unstable.
you may get lucky on 17.2.1 .. it has worked.
maybe someone will jump in here with a work around for a try.
The 17.7.1 drivers work fine on my R9 290...no issues installing or performance. Have you tried removing one card...installing the drivers, then install second card?
Make sure you have disabled any anti-virus/anti-malware/personal firewall/anti-anything while trying to install the drivers. If you have one of the super-duper protect you from anything anti-virus suites...check task manager to make sure no PART of it is running.
You could also turn your computer off and remove the CMOS battery...wait 5min, replace and restart.
Thanks for the suggestions thus far, much appreciated. If there are any others, keep them coming.
As far as 17.X.X not working on 290X that sounds a bit bizarre to me, considering I followed the "Manually Select Your Driver" on the driver download page, specifying "Desktop Graphics / Radeon R9 Series / Radeon R9 290X / Win10 64-bit". If 16.12.2 is in fact the latest, that would be really bad to point users to incompatible (or I guess "somewhat compatible") software. This would also be a shame considering the 290X still competes with newer cards like RX 580 in terms of performance. The 290X has had quite the lifespan and is still relevant.
rebelyell I tried various drivers in the 17 series but don't recall specifically trying 17.2.1. I can try my luck with that one. Also, do you mind elaborating on "fixing the code 43". I've tried disabling/re-enabling via device manager, and uninstalling the device and restarted. My device manager is error and warning free otherwise. Any other suggestions?
kingfish I can try a CMOS reset, but I did try setting my BIOS back to factory defaults. I'm aware it's different, but just figured I'd mention it. I believe at some point, I tried Installing on one card and adding the other but at this point everything is just a blur of troubleshooting. I'll try again: removing a card, DDU/restart, disable AV, install driver, install second card.
For AV, I am only using Microsoft Security Essentials or Defender, whatever it's called now.
Is it possible windows is forcing an old driver from C:\AMD (where my extracts go) or forcing a different driver from Windows Update?
yes it is possible. Always delete the CONTENTS of the C:/AMD folder...all of them.
Take the necessary steps to prevent/delay Microsoft from automatically installing graphics drivers...use one of these methods > Windows 10 Forums
Windows defender is the cause in a lot of cases...disable it completely...when installing drivers.
code 43 means windows needs to detect the new hardware then it will be ok. which is exactly what we dont want to happen. win 10 isnt happy today. why it thinks its new hardware is a micro mystery. just follow king fish for a workaround.. ill check back later.
1 of 1 people found this helpful
Thanks for the suggestions guys. I tried a whole bunch of things last night and got it working.
TL;DR: My cards are identical but bought at different times. The new 17.X.X drivers appear to require the card with the newer BIOS to be in the first slot. Running 17.4.4, when I'm feeling saucy again after a couple weeks I'll update again.
- Uninstalled ASUS AI Suite (wasn't sure if that was causing issues, probably not, but it does a lot of mobo related things)
- Disable microsoft defender or whatever
- Power down and remove second card
- Shut down and put the secondary card in the primary PCIE slot
- Installed driver and restart
- Install second card
This worked but my "second" card has pretty loud coil whine so I really want it as the second so I have to hear it in games that dont use CFX. Also, this helps identify when CFX kicks in.
I switched the cards back to their normal order and either the issue came back or there was no driver for either, running at a super low resolution.
- Downloaded GPUZ and checked the BIOS version of the cards. Noticed it worked with the newer card in the primary slot. Used GPUz to backup the BIOS on each card.
- Downloaded AMD/ATI flash util and updated the older card to the newer cards BIOS
- Repeated the procedure above.
Now things are working, hopefully this helps someone else with a similar issue.
MODERATOR NOTE: I am glad to see you have resolved your issue. To help keep this post on topic and help other with a similar issue, I am locking this thread.