ATIFlash- 6600XT (Error 43)

[LeonIncognito]

Hey all,

Long story short, I have Error 43 on my new PC build (Intel 12th, MSI Z690, 6600XT). The only thing not new is the GPU which worked fine in the old build. I've gone through every process to troubleshoot and am only left with flashing the GPU BIOS which is why I went to TPU. I've never cryptomined or otherwise messed with the GPU.

The latest version hasn't been updated since July and does not list the 6600XT in the compatibility for the 6000 series. Safe to use?

Thanks

 

[Imperator]

Hello there.
Please be so kind and share with us the whole process that lead to error 43.
I mean explain us step by step what you did in order to obtain that error.
I would not recommend yet to flash it.
I do not think that is something wrong with the card.
I would test that card in another system 1st, but be sure to remove old drivers using in safe mode DDU w/o network cable.
After restart you must use a WHQL version driver but i recommend to use enterprise version driver.
Then we will discuss depending the results you obtain.
(I would even recommend to try it in Linux environment not only in Windows)

 

[INSTG8R]

Hey all,

Long story short, I have Error 43 on my new PC build (Intel 12th, MSI Z690, 6600XT). The only thing not new is the GPU which worked fine in the old build. I've gone through every process to troubleshoot and am only left with flashing the GPU BIOS which is why I went to TPU. I've never cryptomined or otherwise messed with the GPU.

The latest version hasn't been updated since July and does not list the 6600XT in the compatibility for the 6000 series. Safe to use?

Thanks

Honestly I can’t see any benefit to attempting to flash a brand new card because there is really nothing to flash it too so any attempt will probably just brick it as the likely outcome. If anything I would be checking your BIOS for CSM/UEFI settings first.
Also despite the Code 43 a shot from GPUZ in its current state would be helpful.

 

[damric]

What power supply model and how old is it?

 

[LeonIncognito]

Thank you everyone,

MSI Z690 Pro
Intel i5 12600K
Noctua Cooler NH-U12S
DDR4 3200MHz RAM 32GB (4 Sticks, all duplicates)
WD SN750 500GB NvME (Boot Drive)
G.Skill 750W 80 Plus Gold
AMD Radeon 6600XT
ASUS BT 5.0 & WiFi Card

I've already gone through the process of replacing each piece of hardware outside of the GPU (which isn't an option, lulz). Originally I did not know what was causing the No Signal errors. Thought I have now made an RMA request.

My PC is up to date.
I've clean installed Windows 11 several times, on different drives.
BIOS is updated to the latest MSI version.
Ensured BIOS is set to PEG, no multiple displays, etc. Explored every option. Re-Size BAR and TPM 2.0 are enabled. Have not touched the voltage.
Disabled Windows from installing 3rd party updates for my hardware
Tried disabling the Intel Integrated Graphics in Device Manager
Set the GPU to Silent BIOS switch. It has a physical switch from "OC-Silent" and it came from the factory set to OC.
Tried downloading Windows 10 version of drivers. Tried stable/optional drivers. Clean installing the drivers with various other changes. I've used tools to fully remove older drivers
Installed drivers through Windows Update directly & Installed drivers from AMD Support directly
Searched for an Nvidia card to end the pain
Used Windows Troubleshooter (It says I have the latest drivers)

What happens is that the moment drivers are installed, whether they be from Windows Update or Radeon, the Display says No Signal and eventually Windows reverts to Microsoft Basic Display Driver with Error 43 in the Device Manager. Right now I have the Graphics Card removed and am reliably using the PC via the motherboard DP output with the i5-12600K.

 

[Imperator]

Well, maybe i made myself very hard to understand.
I am not a native english speaker.
My point was : at a moment your rig was functioning well.
Please rewind to that point and tell us what you did until the present moment when it did not function.
You explained all the software changes you've made but i did not get it how you got in that mess.
i need that in order to have a clear view of what happened.

 

[LeonIncognito]

I appreciate any effort you put in.

This is a new PC build, the GPU/Display has had this problem from Day 0. I've exchanged every part including the CPU, MoBo and PSU in an attempt to troubleshoot. Changed NvME boot drives.

It worked fine in my previous AM4/Ryzen 3000 computer.

 

[Imperator]

That is what i am expecting from you.
A rig where your gpu worked
So...could you test that GPU in some other configuration (apart from your rig) ?
Could you for instance take it to a friend and test it in his rig ?

 

[LeonIncognito]

Everyone I know has Macs. I would have to pay someone.

 

[Imperator]

Neah. That's not worth it.
I mean if you have bought that card new and you used it for a period of time w/o any problem, and you just put it in another rig (your actual one) where it does not work... well i am 100% that is not about video card at all.
Yes AMD are a pain in the ass when it comes to video drivers , but still i proved my point.
Do not leave the battle for now
Let's try to make it work in your current rig

 

[LeonIncognito]

Ok but a local PC place will test the card for free and I will try that too on Wednesday. I'm not bringing the entire PC just yet.

The only other idea I have is to just download Windows 10 (Which I assume I can do with a Windows 11 key)

 

[Imperator]

Even if you do not have a genuine key you can test win 10...that is more than enough.
I think (as far as i remember) you have 30 days for testing win 10.
When it asks for a key you will choose " i do not have a key"

 

[Chrispy_]

I think I understand this thread correctly - new build but with re-used GPU gets error 43 when using an old 6600XT that previously worked in an older system?

Don't BIOS flash it. Previous BIOS is 100% fine if it worked in another system. @impero has the right idea but I don't think he explained it too clearly:

1. download the latest DDU from this page: https://www.wagnardsoft.com/forums/viewtopic.php?t=3847
2. download the 21.12.1 driver from the only official source: https://www.amd.com/en/support/grap.../amd-radeon-6600-series/amd-radeon-rx-6600-xt
3. boot into safe mode without networking (hold shift as you click on the restart option and get there via 'troubleshooting'
4. do a clean & restart option on AMD GPU drivers
5. on restart, disable internet connection via unplugging or flight-mode so that Windows Update doesn't try to install drivers automatically
6. run the 21.12.1 driver installer that you downloaded earlier.
7. reboot even if it doesn't ask you to
8. after reboot, you can reconnect to the internet.

Basically error 43 is a device ID error caused by driver-hardware mismatch. It's one of three things:

1. Mining BIOS on the GPU that doesn't support display output. If you haven't flashed the 6600XT's BIOS and it definitely worked before, then it's 100% not this.
2. Driver conflict caused by Windows Update or some OEM crapware you installed off the motherboard/GPU manufacturer's website.
3. Faulty hardware. That would be unfortunate in the current GPU market right now, but we need to rule out point 2 in this list before assuming it's a hardware fault given how hard it is for you to test that without other graphics cards available or other PCs to try it in.

 

[Imperator]

Basically error 43 is a device ID error caused by driver-hardware mismatch. It's one of three things:

1. mining BIOS on the GPU that doesn't support display output. If you haven't flashed the 6600XT's BIOS and it definitely worked before, then it's 100% not this.
2. driver conflict caused by windows update or some OEM crapware you installed off the motherboard/graphics card website
3. faulty hardware. Unfortunate right now, but we need to rule out point 2 in this list before assuming it's this.

I assumed that would be no2.
Why ? because the Video Card worked perfectly in older rig.
So, he must clean the system from crap and clean install it (as you also said)

 

[Chrispy_]

I assumed that would be no2.
Why ? because the Video Card worked perfectly in older rig.
So, he must clean the system from crap and clean install it (as you also said)

Yeah if it's not a dirty/incorrect driver install, it's faulty hardware.
DDU is always the answer but so many people fail to run it in safe mode, or fail to disable their internet. Hell, sometimes things are so bad you need to nuke the C:\windows\SoftwareDistribution folder too!

 

[LeonIncognito]

Thank you again, everyone.

I'm going to go through the steps listed before resetting to Windows 10. Or I could just install Windows 10 on a secondary NVMe.

As far as whether it's No. 2, I've clean installed Windows 11 several times and (Most of the time) not installed anything from OEM like Intel or MSI. Anything that showed up on the first install of Windows 11 I uninstalled in Remove Programs. And I did disable Windows from installing firmware for 3rd party hardware in their updates (It's in Control Panel). I would do a clean install, go right into Radeon and either download the latest version or sometimes use their compatibility tool (Which gave me the same Driver).

The only HINT that it's Windows Update is that on some occasions, the Radeon driver lasted a day or two before going Error 43 and regressing to Microsoft Basic Driver. But that was also when Windows was prevented from installing updates for the display via Control Panel.

If going to Windows 10 won't solve it idk But I'm doing Chrispy's guide first

 

[Chrispy_]

I'm not in front of a W11 machine right now but I think it's still in the same place.

run sysdm.cpl > hardware > device installation and untick automatic device driver installation; It sure does smell like Windows Update getting the wrong driver from what you're saying.

 

[LeonIncognito]

That's been a regular step for me and it's been one of my basic troubleshoot options.

alright boys

I did the steps outlined by Chris to the letter. When I installed the Radeon driver exactly as written... the screen went black and remained on No Source.

I did a hard reboot and it came back on with the drivers installed. I turn the internet back on and loaded up Steam and FFXV and it runs on high settings at a 117 cap. Gears 5 at Ultra/High benchmarks at 120. For now.

This has happened before. Windows Update is disabled from installing hardware drivers.

If the issue reoccurs, can this rule out this being a hardware error?

 

[LeonIncognito]

I just ran a manual Windows Update and it did not try to download AMD or any Display drivers.

 

[dark2099]

Have you tried the card in a different pcie slot on the motherboard?

 

[LeonIncognito]

Have you tried the card in a different pcie slot on the motherboard?

I only have one pcie 4.0 slot

 

[Chrispy_]

It'll still work just fine in a PCIe 3.0 slot, 2.0 slot, and 1.0 slot.
PCIe is both backwards and forwards-compatible.

 

[dark2099]

The point in trying a.different slot is to see if the slot you're using is the issue, doesn't matter what pcie spec it is.

 

[Chrispy_]

I did the steps outlined by Chris to the letter. When I installed the Radeon driver exactly as written... the screen went black and remained on No Source.

Oh, I just spotted that.

It's a bit late for me now but google EnableULPS. You want to disable it in the registry by setting that key to 0 instead of a 1 for every time you find it.
It's yet more indication of driver conflicts because ULPS turning the GPU off is because the driver(s) are detecting your primary (and only) GPU as a secondary GPU.

This is a recent thing I've seen only in the last few weeks and I'm pretty sure the problem is Microsoft pushing the wrong driver. Once it's there in the softwaredistribution folder of Windows it'll try and install that driver silently whilst providing no information that it's doing so unless you dive down into running processes with process explorer.

 

[Imperator]

Hello everyone.
As i said before in my post, AMD have some problems with its video card drivers.
I usually use an older version of the driver, (even the gamers will say that those drivers have lower fps in some games) because of stability.
So if you had a fully functional system, where the card worked for more than 6 months let's say, and you moved ONLY the card into a new system where it does not work....then we have the answer:
it is a software problem and i point to DRIVERS
In some cases there were some issues with the video cards when you move them into another system , that was caused by the owner who by accident removed some small electronic pieces from the video card pcb. But that was due to the lack of attention. if you handle it with care and you used all the safety measures, then you do not have to worry about hardware damage.