Overclock.net › Forums › Graphics Cards › AMD/ATI › Polaris Bios Editing ( RX5xx / RX4xx )
New Posts  All Forums:Forum Nav:

Polaris Bios Editing ( RX5xx / RX4xx ) - Page 19

post #181 of 3318
Anyone have luck with disabling driver enforcement in Windows 10 and trying the patch posted earlier?
post #182 of 3318
Quote:
Originally Posted by gooface View Post

So whats the consensus at this point?
How safe is it to flash the 4GB cards to 8GB? Any side effects?
Quote:
Originally Posted by gooface View Post

The XFX 4gb card works with the 8GB bios too right?
Quote:
Originally Posted by iRUSH View Post

My XFX 4gb RX 480 successfully flashed last night with the Black Edition bios! I now have 8gb vRAM and 1328 core clock. Worked like a charm with ATIflash thumb.gif

I did the same on my 4GB XFX card yesterday. Now have 8GB, 2000Mhz vram clock, and 1328 core. Running Doom at 1440p on ultra/nightmare settings and getting around 60fps average paired with a stock FX 8310 and 8GB ram. Card is stable with no artifacts or issues but I am using the new compatibility mode option in 16.7.1. Only 1 crash (in Doom) compared to a half dozen on another machine with a stock i7 and gtx 970.

However, I'm not a fan of flashing within Windows. Prefer the safer DOS Atiflash that I used for a R9 290 but windows method is only one I've seen so far for Polaris. Noticed someone had to manually set memory clock to 2000 after flashing due to the original 1750 still showing. So I uninstalled the Radeon drivers and rebooted before flashing though then reinstalled afterwards.
post #183 of 3318
Quote:
Originally Posted by gupsterg View Post

On current RX 480 ref PCB you can gain more VDDC by using this command switch on a MSI AB shortcut :-

/wi06,08,8d,xx

xx denoting the hexadecimal multiplier for SVI2 voltage step ie 01h = +6.25mV, so for say +100mV you would use 10h and command would be:-

/wi06,08,8d,10

If you wish to reset back to stock you can send command:-

/wi06,08,8d,00

Prior do doing above I would recommend either an i2cdump to verify IR3567B is on bus 6 device 8. To do an i2cdump via MSI AB you add command switch -i2cdump to shortcut. Whilst dump is being done you will not see any indication on desktop that it is occurring and an OK prompt will appear at end, then you will find log in MSI AB install dir.

The other method to send i2c command is:-
Then send commands for VDDC offset as above.

Be aware anyone using this command all DPM states get a voltage increase (ie idle to highest state). You will see VDDC in GPU-Z monitoring / HWiNFO alter, I would advise send i2c commands when such apps are not monitoring card.

I have tested this on 1 card that a friend owns, so use information at your own risk..

The stock ROM/MTP configuration of IR3567B from i2c dumps I've viewed has no VDDC limit for offset, so double check i2c command you send as error = bye bye GPU. I have verified this with The Stilt, see linked post.

Hi, it worked for me! thumb.gif +rep



I have 2 RX480 in crossfire. The command seems to only work for the first card. How do I get the second card fired up as well?
post #184 of 3318
Quote:
Originally Posted by fewness View Post

Hi, it worked for me! thumb.gif +rep


Just curious, what is the maximum core clock speed you can get with the default maximum voltage (1.15v if I'm correct) ?
post #185 of 3318
@fewness, is that stable at 1500mhz?

@SSBrainThe highest I've been able to get stable is 1370
Edited by comagnum - 7/10/16 at 11:10am
post #186 of 3318
Quote:
Originally Posted by SSBrain View Post

Just curious, what is the maximum core clock speed you can get with the default maximum voltage (1.15v if I'm correct) ?

1420 to pass 3DMark
post #187 of 3318
Quote:
Originally Posted by comagnum View Post

@fewness, is that stable at 1500mhz?

Seems stable in unigine valley, but not at all in 3DMark....not sure why...
post #188 of 3318
I'm sure why, because unstable OC.
post #189 of 3318
@gupsterg

this is my device 08 information (xfx bios): xfx1328mhz.zip 110k .zip file
Code:
Probing device 08...
28 17 15 02 17 1A 70 5A 4F 05 11 66 66 44 FF FF 
A2 22 88 10 22 FF 14 00 00 00 00 00 00 00 00 00 
00 00 9E 78 1C 2B FF 8D 00 24 A1 2C 38 9E 1E 2F 
6B 0F CC 72 6F 05 05 1D 81 BE 60 00 00 FF 00 00 
A8 90 00 00 00 00 00 00 14 14 00 40 80 60 A0 FF 
FF 00 40 88 34 88 44 12 02 02 88 00 20 20 00 3C 
3C 03 7E 60 91 9C 24 88 80 00 00 00 00 FF 06 FF 
FF 20 00 00 00 00 00 00 00 00 00 00 15 15 00 00 
00 00 00 00 00 00 00 00 88 88 01 C2 44 00 00 1F 
00 05 43 78 48 01 30 70 60 AB 66 00 01 47 21 1A 
00 00 00 00 00 00 01 01 08 51 A0 7F AF 00 00 02 
FF 00 00 00 FF 06 23 A3 00 00 6D B6 24 16 00 00 
00 00 01 7D 13 00 00 00 00 00 00 01 00 44 00 00 
00 00 AD 50 0C 00 10 00 3F 00 00 00 23 C0 F0 00 
00 00 00 10 01 03 01 88 00 00 00 00 00 00 00 00 
00 00 00 00 00 33 00 00 00 00 00 00 00 00 00 00

Edited by comagnum - 7/10/16 at 11:56am
post #190 of 3318
Quote:
Originally Posted by JackCY View Post

I'm sure why, because unstable OC.

Unstable OC will crash the driver, but this doesn't crash. In Valley it holds at 1500, in 3DMark it drops to ~1300 and finish the run.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD/ATI
Overclock.net › Forums › Graphics Cards › AMD/ATI › Polaris Bios Editing ( RX5xx / RX4xx )