ATIFlash- 6600XT (Error 43)

[LeonIncognito]

Hi everyone,

Thank you SO MUCH for the help. It actually haven't returned to the PC since I last posted 2 days ago, I work in a hospital and get too wiped. I assume we've addressed the issue.

To be super safe I think I'll repeat the steps before but this time also EnableULPS beforehand.

impero: I have slotted this thing in and out so many damn times I worry a bit about that too.

But I also got the notice today that my RMA request from PowerColor was approved. Should I use it? Or would they just look at the card, say it's fine, and send it right back to me.

 

[Chrispy_]

To be super safe I think I'll repeat the steps before but this time also EnableULPS beforehand

EnableULPS is usually set to 1 by a driver install. If you set it to 0, then DDU and reinstall drivers, those will put it back to 1. The trick is to get a clean driver install done and set EnableULPS to 0 in the registry before rebooting.

The fact that error43 goes away after a clean driver install means that it's likely not a hardware fault and your RMA will just be a waste of time and postage costs. The RMA won't time out right away so you can always try the machine for a week or so to see how it is after a clean install, then RMA it anyway if the error comes back and you've run out of other things to try.

I have 4 ETH rigs with identical hardware/firmware versions and 6 Radeons in each each running identical BIOSes and drivers. They all run identical software, I cloned the OS and software settings so they are as identical as they can get, and they all run the same driver version.

One (and only one) of the rigs, a few weeks back, for NO REASON, decided to have this issue that was traced down to a silent update to an incorrect driver. I swear Microsoft just uses customers at random to beta test stuff as part of WHQL validation.... I know that sounds like a conspiracy theory but how can one of four identical hardware/firmware/software machines doing identical jobs at the same time have this mystery driver install?!

 

[LeonIncognito]

That stinks. Sounds like getting this Intel with the Integrated Graphics was sort of the problem in a way.

So if I can/should only disable ULPS AFTER a clean install and last time I did this the screen instantly went black and required a hard reset upon driver install... what should I do? I guess just disable ULPS now when I get home without bothering with a new clean install

 

[Chrispy_]

That stinks. Sounds like getting this Intel with the Integrated Graphics was sort of the problem in a way.

So if I can/should only disable ULPS AFTER a clean install and last time I did this the screen instantly went black and required a hard reset upon driver install... what should I do? I guess just disable ULPS now when I get home without bothering with a new clean install

Yeah, just disable UPLS since you've recently done a full safe-mode DDU and clean driver install, presumably with the setting that disabled driver updates via Windows Update.

ULPS in a multi-GPU system can result in black screens every other boot and long boot times of over a minute. Since you only have one dedicated GPU then there's no reason to ever use ULPS, and you can't harm your system by disabling it.

I'm not saying for sure that the Windows Update driver is causing the problem but your symptoms match what I'm describing on multiple machines. If you still get error 43 check that the Windows Update driver download is still disabled:

and if it's still set to no and you're getting error 43, use that RMA

 

[RJARRRPCGP]

Everyone I know has Macs.

That sounds more like my earlier school days.

 

[Imperator]

EnableULPS is usually set to 1 by a driver install. If you set it to 0, then DDU and reinstall drivers, those will put it back to 1. The trick is to get a clean driver install done and set EnableULPS to 0 in the registry before rebooting.

The fact that error43 goes away after a clean driver install means that it's likely not a hardware fault and your RMA will just be a waste of time and postage costs. The RMA won't time out right away so you can always try the machine for a week or so to see how it is after a clean install, then RMA it anyway if the error comes back and you've run out of other things to try.

I have 4 ETH rigs with identical hardware/firmware versions and 6 Radeons in each each running identical BIOSes and drivers. They all run identical software, I cloned the OS and software settings so they are as identical as they can get, and they all run the same driver version.

One (and only one) of the rigs, a few weeks back, for NO REASON, decided to have this issue that was traced down to a silent update to an incorrect driver. I swear Microsoft just uses customers at random to beta test stuff as part of WHQL validation.... I know that sounds like a conspiracy theory but how can one of four identical hardware/firmware/software machines doing identical jobs at the same time have this mystery driver install?!

When i told people to be patient, they told me i am insane.
Of course this things can drives you crazy but still...
Because that thing happened to myself also, i suggest to my forum fellow to do as much as possible before they RMA.
Why ? Because it is more likely to have a driver issue then a hardware one after your item functioned well for a long period of time and w/o any interfere from user it leads to that nasty error.
So yeah you are absolutely right mate! That is why i modified in my registry to block windows to autoupdate.

 

[LeonIncognito]

Haha, thanks again.

Last question, this time about DRAM Frequency since research makes it unclear: My 3200MHz RAM defaults to 2133MHz in both my old AM4 board and this new Z690. Except there are now 4 options in this new board for 3200MHz:

3200 24x000.000 1.33 G1
3200 24x000.000 1.33 G2
3200 32x000.000 1.00 G1
3200 32x000.000 1.00 G2

From what I understand, G =Gears 1 and 2. Gear 2 is about halving the speed but having "broader memory access". I have 32GBs, don't ever need Gear 2.

The 1.00 vs 1.33 might be about speeds, so 1.33 is better?

The long string of numbers idk. 24 vs 32, etc.

I also set my DRAM voltage from Auto (1.2v) to 1.35v because that's what I was told a while back.

So right now I'm on 3200 24x000.000 1.33 G1 with 1.35v. I have the G.SKill Ripjaws V 3200MHz DDR4

 

[Chrispy_]

Haha, thanks again.

Last question, this time about DRAM Frequency since research makes it unclear: My 3200MHz RAM defaults to 2133MHz in both my old AM4 board and this new Z690. Except there are now 4 options in this new board for 3200MHz:

3200 24x000.000 1.33 G1
3200 24x000.000 1.33 G2
3200 32x000.000 1.00 G1
3200 32x000.000 1.00 G2

From what I understand, G =Gears 1 and 2. Gear 2 is about halving the speed but having "broader memory access". I have 32GBs, don't ever need Gear 2.

The 1.00 vs 1.33 might be about speeds, so 1.33 is better?

The long string of numbers idk. 24 vs 32, etc.

I also set my DRAM voltage from Auto (1.2v) to 1.35v because that's what I was told a while back.

So right now I'm on 3200 24x000.000 1.33 G1 with 1.35v. I have the G.SKill Ripjaws V 3200MHz DDR4

I have no experience with Alder Lake's new 133MHz base clock. I would assume 24x1.33 is better than 32x1.00 but 32x1.00 is the standard we've had for 3200MHz RAM for years. If you have any weird compatibility issues, it might be worth going back to 32x1.00

G1 is definitely faster than G2, you don't want to use G2 unless you're using very high frequency RAM.

 

[eidairaman1]

Hi everyone,

Thank you SO MUCH for the help. It actually haven't returned to the PC since I last posted 2 days ago, I work in a hospital and get too wiped. I assume we've addressed the issue.

To be super safe I think I'll repeat the steps before but this time also EnableULPS beforehand.

impero: I have slotted this thing in and out so many damn times I worry a bit about that too.

But I also got the notice today that my RMA request from PowerColor was approved. Should I use it? Or would they just look at the card, say it's fine, and send it right back to me.

I suggest you record the bar code info down even qr code for model and serial number down, i do this for all hardware that goes rma.

USE IT

When i told people to be patient, they told me i am insane.
Of course this things can drives you crazy but still...
Because that thing happened to myself also, i suggest to my forum fellow to do as much as possible before they RMA.
Why ? Because it is more likely to have a driver issue then a hardware one after your item functioned well for a long period of time and w/o any interfere from user it leads to that nasty error.
So yeah you are absolutely right mate! That is why i modified in my registry to block windows to autoupdate.

People are idiots here now

 

[LeonIncognito]

I wouldn't want to RMA if they'll just test it and send it back as is.

Ok... So when trying to change the registry I somehow ended up with a problem where the log in screen would just give me the smile face with no way to get into my Windows and I couldn't troubleshoot it.

So I reinstalled Windows AGAIN and tried the method before but could not get the AMD drivers to not revert to Error 43 before making the registry change.

I decided to embrace the Devil and fully installed the drivers for the 770 Intel Chipset and have it active and my main output while having the 6600XT slotted but not plugged into to PSU. Then I did DDU via safe mode, restarted, plugged the GPU into the PSU and while still outputting via Intel 770 installed AMD Radeon (Because the software detected the powered card). After it installed I went into Registry and defaulted to 0 for THREE keys (EnableULPS, EnableULPS_NA, EnableCrossfire). Restarted and plugged DP into the GPU. Everything has been fine the last couple of days.

Again I have Intel Graphics fully installed and it seems to not cause an issue.

What happens with the next Radeon driver update? Will it re-enable Crossfire?

From what I'm reading this will be a problem with every single driver update.

 

[eidairaman1]

I wouldn't want to RMA if they'll just test it and send it back as is.

Ok... So when trying to change the registry I somehow ended up with a problem where the log in screen would just give me the smile face with no way to get into my Windows and I couldn't troubleshoot it.

So I reinstalled Windows AGAIN and tried the method before but could not get the AMD drivers to not revert to Error 43 before making the registry change.

I decided to embrace the Devil and fully installed the drivers for the 770 Intel Chipset and have it active and my main output while having the 6600XT slotted but not plugged into to PSU. Then I did DDU via safe mode, restarted, plugged the GPU into the PSU and while still outputting via Intel 770 installed AMD Radeon (Because the software detected the powered card). After it installed I went into Registry and defaulted to 0 for THREE keys (EnableULPS, EnableULPS_NA, EnableCrossfire). Restarted and plugged DP into the GPU. Everything has been fine the last couple of days.

Again I have Intel Graphics fully installed and it seems to not cause an issue.

What happens with the next Radeon driver update? Will it re-enable Crossfire?

From what I'm reading this will be a problem with every single driver update.

Use the Radeon Pro for Enterprise Drivers and turn off automatic updates.

Fyi RMA is good whether the card is bad or not,if it comes back as good, then something else is fugged in your system

 

[frozenwind]

I got similar hardware to yours and had similar issue. But the cause is the cable.

Weird red devil 6600 xt no output issue

After many hours researching online and troubleshooting, I found that the cause is the displayport cable. The whole long story: Got a new build two months ago. i7-12700K, msi z690-a pro ddr4 wifi, powercolor red devil 6600 xt, corsair 8Gx2 3600 cl16, seasonic 850w. At first I didn't have the...

www.techpowerup.com

 

[LeonIncognito]

Let me try that because everything worked great for a week except trying to wake up the computer from sleep which resulted in no signal and Error 43 this most recent time.

Now stuck in the same loop of clean installing drivers-Direct to Black

 

[eidairaman1]

Let me try that because everything worked great for a week except trying to wake up the computer from sleep which resulted in no signal and Error 43 this most recent time.

Now stuck in the same loop of clean installing drivers-Direct to Black

Rma is needed

 

[LeonIncognito]

I secured a 3070 Ti from Best Buy yesterday instead.

 

[eidairaman1]

I do 1 or 2 rmas before I switch to a different card maker(not die) but that is just me.

 

[frozenwind]

Let me try that because everything worked great for a week except trying to wake up the computer from sleep which resulted in no signal and Error 43 this most recent time.

Now stuck in the same loop of clean installing drivers-Direct to Black

damn! after a shutdown and reboot, it never works again. Previous work around, cold boot with HDMI cable didn't work anymore. I even bought a new DP cable and with that cable reboot was fine. Still not sure what is the real problem.

 

[LeonIncognito]

I'm sorry to hear you're also going through this. John Linneman from Digital Foundry is using my board and another 12th gen Intel and having the same problem.

https://twitter.com/x/status/1482463543681241089

All kinds of theories.

I just hope my 3070 Ti has stronger compatability. I'm actually very excited! I've never had Nvidia. Back in the day I used ATI, then a Ryzen/Radeon combo when I got back into PC gaming last year. And there are so many issues with DirectX 9 games with any AMD card so Far Cry, Assassin's Creed games, Hat in Time, would be unstable. And certain graphical effects in Far Cry 4 or FFXV would be Nvidia-only.

Really looking forward to a premiere experience going forward. Gonna use that DLSS to run 1080p with RT on upscaled to 1440p!

 

[frozenwind]

I'm sorry to hear you're also going through this. John Linneman from Digital Foundry is using my board and another 12th gen Intel and having the same problem.

https://twitter.com/x/status/1482463543681241089

All kinds of theories.

I just hope my 3070 Ti has stronger compatability. I'm actually very excited! I've never had Nvidia. Back in the day I used ATI, then a Ryzen/Radeon combo when I got back into PC gaming last year. And there are so many issues with DirectX 9 games with any AMD card so Far Cry, Assassin's Creed games, Hat in Time, would be unstable. And certain graphical effects in Far Cry 4 or FFXV would be Nvidia-only.

Really looking forward to a premiere experience going forward. Gonna use that DLSS to run 1080p with RT on upscaled to 1440p!

great. please update how 3070 ti works. I would rather the card not boot at all if faulty like others. But it's weird it can boot and works in windows with basic graphic drivers if not installing amd drivers.

 

[LeonIncognito]

I think our cards, and cables, are perfectly fine. I'm using a DP braided cable that's relatively new from monoprice. It's some kind of driver conflict, but whether the blame/solution lies with MSI, Intel, Windows or AMD is a complete mystery.

I'm really just hoping that it was AMD drivers being lame and using Nvidia solves it.

 

[eidairaman1]

I think our cards, and cables, are perfectly fine. I'm using a DP braided cable that's relatively new from monoprice. It's some kind of driver conflict, but whether the blame/solution lies with MSI, Intel, Windows or AMD is a complete mystery.

I'm really just hoping that it was AMD drivers being lame and using Nvidia solves it.

Wintel, fyi use enterprise drivers

 

[LeonIncognito]

Problem solved: I'm using Nvidia now. DDU'd the AMD drivers, fully installed the Intel drivers and then installed the 3070 Ti. 0 issues from beginning to present.

 

[Imperator]

It is not the best expected solution, but it worked
Enjoy your new card!

 

[95Viper]

Problem solved

locked