ASUS RX560-O2G issue

[djuro13]

Hi!
I would kindly ask for your help.
I have just bought 2nd hand ASUS RX560-O2G graphic card (6 months old) and it seems that I have an issue with it.
I have my picture on monitor, but when it comes to any 3D activity I am facing a problem and receiving warning that "there is no valid rendering device available".
Also, my Device manager shows code error 43 - Windows has stopped this device because it has reported problems. (Code 43).
I have performed several DDU uninstalation procedures (Safe Mode) and several installation of different AMD Radeon Drivers (the latest one and older) - with the same outcome.

There are also some quite strange GPU-Z readings - please, find it here:
http://gpuz.techpowerup.com/18/09/22/29b.png (there are no data for Pixel and Texture Fillrate, no Computing details at the bottom, no data for GPU speed and temp etc...)

I have quite old PC :
Intel E5200 Dual Core
Gigabyte EP35-DS3L motherboard
4GB DDR2 800MHz
Samsung EVO SSD 250GB
LC Power 6600GP PSU...

Looking forward to hear from you.
Thanks in advance!

 

[INSTG8R]

By the GPUZ shot it appears that it’s had a bad BIOS flash judging by the missing info and your Code 43.

 

[djuro13]

By the GPUZ shot it appears that it’s had a bad BIOS flash judging by the missing info and your Code 43.

Does it mean that previous owner had tried to flash wrong BIOS or that card is "bricked" now? Is it reversible?
Thanks!

 

[INSTG8R]

Does it mean that previous owner had tried to flash wrong BIOS or that card is "bricked" now? Is it reversible?
Thanks!

Yes that appears to be the issue. Yes it’s reversible if you can find the correct BIOS in this sites database. I’ll just tag @eidairaman1 as he can quickly walk you through it.

 

[eidairaman1]

Yes that appears to be the issue. Yes it’s reversible if you can find the correct BIOS in this sites database. I’ll just tag @eidairaman1 as he can quickly walk you through it.

He's gonna need to post white stickers from back of card and if possible barcode from his original box. Memory and video out layout/configs are typically cause of bricking, hopefully the card wasn't damaged.

 

[king of swag187]

Yikes! A dual core E5300 in 2018? 4GB RAM????? Hello, bottleneck city.....

But yes likely a wrong VBIOS flashed and now the drivers are going screwy

 

[eidairaman1]

Yikes! A dual core E5300 in 2018? 4GB RAM????? Hello, bottleneck city.....

But yes likely a wrong VBIOS flashed and now the drivers are going screwy

Ram brand and timings and port layout maybe different from the card he actually has.

 

[Caring1]

https://www.techpowerup.com/vgabios/194113/asus-rx560-2048-170510
That's the only 02G listed VBIOS version is the same as shown in his screenshot

 

[djuro13]

He's gonna need to post white stickers from back of card and if possible barcode from his original box. Memory and video out layout/configs are typically cause of bricking, hopefully the card wasn't damaged.

Thanks!
Here is picture of white label from original box:

 

[Readlight]

Hapens when there is 2gpu in system or bios need to chainge.

 

[silentbogo]

One of my buddies just brought over 3x RX560 from Gigabyte with the same issue.
He used those for mining XMR for a few months, before giving up and ultimately parting out the rig.
Cards were fully functional in his PC (Ubuntu+some modded drivers), but the first buyer returned the card within a couple of days saying that he is unable to install the driver (and gets ERROR 43 in device manager).
He brought those over to me and I was able to confirm the problem on ALL of his remaining cards.
The issue was his "optimized" vBIOS with modified timings. I've simply flashed the stock one from TPU vBIOS DB and now all cards are working again.

Just download the latest ATIFlash, then get a proper BIOS and go ahead with flashing.

 

[eidairaman1]

https://www.techpowerup.com/vgabios/194113/asus-rx560-2048-170510
That's the only 02G listed VBIOS version is the same as shown in his screenshot

Clock speed is way off there compared to the card advertised here.

https://www.asus.com/us/Graphics-Cards/RX560-O2G/specifications/

Also unverified bios files there is only 2.

Look at device ID and subsystem ID, 1 matches due to Letter D but that is 1210, the B version is 1176. (Closer than 1210...)

https://www.techpowerup.com/vgabios...sion=&interface=&memType=&memSize=2048&since=

The last bios written for the gigabyte motherboard is from 2009- F6 version- way before uefi. Could be a uefi incompatibility too.

 

[djuro13]

Clock speed is way off there compared to the card advertised here.

https://www.asus.com/us/Graphics-Cards/RX560-O2G/specifications/

Also unverified bios files there is only 2.

Look at device ID and subsystem ID, 1 matches due to Letter D but that is 1210, the B version is 1176. (Closer than 1210...)

https://www.techpowerup.com/vgabios...sion=&interface=&memType=&memSize=2048&since=

The last bios written for the gigabyte motherboard is from 2009- F6 version- way before uefi. Could be a uefi incompatibility too.

Would it be useful to post other tabs form GPU-Z?
I am not familiar with some of the readings...

http://gpuz.techpowerup.com/18/09/23/u7k.png
http://gpuz.techpowerup.com/18/09/23/kkf.png
http://gpuz.techpowerup.com/18/09/23/5yw.png

@eidairaman1 - I am aware that my MoBo is ancient - I have flashed the latest BIOS (F6 version that you have mentioned) last night.
I have recently used R7 250X on it, without an issue.
You are correct - it seems that UEFI can be an issue.
Anyway, there was a plan to upgrade my machine in some closer future - I would only be glad to be sure somehow that graphic card is OK itself (no hardware issue) and prepare for upgrade.

 

[eidairaman1]

Would it be useful to post other tabs form GPU-Z?
I am not familiar with some of the readings...

http://gpuz.techpowerup.com/18/09/23/u7k.png
http://gpuz.techpowerup.com/18/09/23/kkf.png
http://gpuz.techpowerup.com/18/09/23/5yw.png

@eidairaman1 - I am aware that my MoBo is ancient - I have flashed the latest BIOS (F6 version that you have mentioned) last night.
I have recently used R7 250X on it, without an issue.
You are correct - it seems that UEFI can be an issue.
Anyway, there was a plan to upgrade my machine in some closer future - I would only be glad to be sure somehow that graphic card is OK itself (no hardware issue) and prepare for upgrade.

I am not here to insult you on the age of the rig.
I only was giving truth about the situation and only trying to help.

Ok to prevent further peril so you can recover incase 1 of the 3 bios files fails and you get no display at all, Do not flash your GPU till you do this first, then get back with us.

1. This may make no sense but buy a cheap PCI (Not PCI Express) video card. Put it in, hook your monitor up to it, don't bother installing any drivers for it.

2. Back up your existing gpu bios file. Change the name without changing the extension to something easy you can remember. Grab other bios files do the same to them.

3. Write down all directory paths to those bios files in case you need to do a command line/dos prompt emergency flash.

My Signature has all info needed to do such a flash, but before you do anything you gotta have a backup plan.

 

[djuro13]

Please, take my apologize - I did not have an idea that my reply could sound that I am offended by comment about my MoBo and rig.
I really appreciate your efforts and all suggestions.

As I have performed backup of VBIOS from graphic and downloaded these other VBIOS files - what would be next step?
Should I flash VBIOS from Windows, as suggested above?
There were threads that suggests usage of DOS bootable USB.
What to do?
Thanks, again.

 

[eidairaman1]

Please, take my apologize - I did not have an idea that my reply could sound that I am offended by comment about my MoBo and rig.
I really appreciate your efforts and all suggestions.

As I have performed backup of VBIOS from graphic and downloaded these other VBIOS files - what would be next step?
Should I flash VBIOS from Windows, as suggested above?
There were threads that suggests usage of DOS bootable USB.
What to do?
Thanks, again.

Ok do not bios flash till you have a pci graphics card that you can have your monitor running off of just incase your 560 bios flash fails.

 

[djuro13]

Ok do not bios flash till you have a pci graphics card that you can have your monitor running off of just incase your 560 bios flash fails.

@eldairaman1 - thanks for your instructions and great help.
Thanks also to other forum members that shared their thoughts on this issue.

Due to my and card seller's impatience - I have been told by card seller to flash VBIOS from TPU, by using ATIWinflash tool (he accepted all potential risks for this procedure, with money-back option). I suppose that this was not quite smart and reasonable behaving, but that is how thing went yesterday.
I have found backup old PCI-E card in case that something went wrong.

Everything went well and smooth - suggested VBIOS was flashed without issues and Code 43 error has disappeared from Device Manager. Drivers have been regularly installed and GPU-Z have recognized the card (please see screenshot). I have checked card in some benchmarks - score is as expected.
It's behaving in WoT is regular, without any issue.

I really hope that this would be it.

Thanks once again!

 

[eidairaman1]

@eldairaman1 - thanks for your instructions and great help.
Thanks also to other forum members that shared their thoughts on this issue.

Due to my and card seller's impatience - I have been told by card seller to flash VBIOS from TPU, by using ATIWinflash tool (he accepted all potential risks for this procedure, with money-back option). I suppose that this was not quite smart and reasonable behaving, but that is how thing went yesterday.
I have found backup old PCI-E card in case that something went wrong.

Everything went well and smooth - suggested VBIOS was flashed without issues and Code 43 error has disappeared from Device Manager. Drivers have been regularly installed and GPU-Z have recognized the card (please see screenshot). I have checked card in some benchmarks - score is as expected.
It's behaving in WoT is regular, without any issue.

I really hope that this would be it.

Thanks once again!

So the particular file that I provided helped you? By the way try to upload it and see if it actually comes through if it does not let @W1zzard know and he'll actually make it a confirmed bios

 

[djuro13]

I have attached "original" VBIOS that came with the card (status of Code 43 error).
There is also VBIOS (saved by GPU-Z from the card, after flashing) that is suggested here.
It was not needed to use any of those 2 unverified VBIOS that are also in TPU database.

I have also attached screenshot from ATIWinflash - it seems that both of these 2 VBIOS had the same name but their size was different.
What can be the cause of this? (is it maybe a sign that somebody was trying to modify BIOS, and did it wrong?)

 

[eidairaman1]

I have attached "original" VBIOS that came with the card (status of Code 43 error).
There is also VBIOS (saved by GPU-Z from the card, after flashing) that is suggested here.
It was not needed to use any of those 2 unverified VBIOS that are also in TPU database.

I have also attached screenshot from ATIWinflash - it seems that both of these 2 VBIOS had the same name but their size was different.
What can be the cause of this? (is it maybe a sign that somebody was trying to modify BIOS, and did it wrong?)

Yup

 

[MrGenius]

I think this is that thing about the driver needing patched(with the AMD/ATI Pixel Clock Patcher) for use with a modded Polaris BIOS.
https://tutorials.technology/tutori...ios-mod-rx470-rx480-rx570-rx580-affected.html
https://www.techpowerup.com/228536/...th-relive-locks-out-polaris-bios-modders?cp=2

when you modify your card, your checksum changes, from a value that is known to the driver to a unknown value, the pixel patcher, reads your new checksum value and then modifies the checksum values in the driver so that it doesnt give a error 43 and render the card not usable by the OS.

https://www.reddit.com/r/EtherMining/comments/7s1501/_/dt16tx8

 

[djuro13]

I think this is that thing about the driver needing patched(with the AMD/ATI Pixel Clock Patcher) for use with a modded Polaris BIOS.
https://tutorials.technology/tutori...ios-mod-rx470-rx480-rx570-rx580-affected.html
https://www.techpowerup.com/228536/...th-relive-locks-out-polaris-bios-modders?cp=2


https://www.reddit.com/r/EtherMining/comments/7s1501/_/dt16tx8

If I understood this correctly - it is possible that I have bought modified, modded, slightly changed RX560 with VBIOS that has required Pixel Clock Patcher for appropriate functioning.
It seems that card seller was not aware of that as he was suggesting me to flash VBIOS instead of using Pixel Clock Patcher to make card acceptable to Windows driver.
It is OK for me how things have gone at the end - I am really happy that I have card that works now

 

[eidairaman1]

If I understood this correctly - it is possible that I have bought modified, modded, slightly changed RX560 with VBIOS that has required Pixel Clock Patcher for appropriate functioning.
It seems that card seller was not aware of that as he was suggesting me to flash VBIOS instead of using Pixel Clock Patcher to make card acceptable to Windows driver.
It is OK for me how things have gone at the end - I am really happy that I have card that works now

Here's the thing you should not be requiring any modified drivers just for the card to work in normal conditions. He might as well face it he probably bought the card from someone else and didn't know or he was playing stupid next time don't bother buying a used card