Custom RAM Timings for GPU's with GDDR5 - DOWNLOAD LINKS - UPDATED

[nerdralph]

I'm trying to make some experiments as well, but so far all failed. Every time I get to desktop after flashing a BIOS with custom straps, I get "Thread stuck in device driver" BSOD in 10-30 secs from OS load. I have Sapphire Nitro RX 480 4 GB with Samsungs, OS is Windows 10 x64. I tried 1625 strap with TRRD 5, 1750 strap with TRRD 5 and 1750 with TFAW/T32AW = 0, all with the same result. I suspect that injecting custom straps into BIOS using Polaris BIOS Editor might be the cause here. Anyone experienced similar problems?

I've been using Polaris BIOS editor, copy the file to my Linux box, and use atiflash.  Works like a charm.

[1715181962]

1715181962

[1715181962]

1715181962

[1715181962]

1715181962

[phobosq]

I flashed with yours from three posts ago and it works.... so either my decoding/encoding fails or I don't really know how it works. Probably the latter.
Maybe I share some of my creations and you can tell me if it looks OK for Samsung 4 GB at 2000:
555000000000000022CC1C00CE595B40D0570C152DCB2409004007000B0314207A8900A00000000 0170F2D35922A3217 or
555000000000000022CC1C00CE595B40D0570F1531CB2409004007000B0314207A8900A00000000 0170F2D35922A3217

[laik2]

I'm trying to make some experiments as well, but so far all failed. Every time I get to desktop after flashing a BIOS with custom straps, I get "Thread stuck in device driver" BSOD in 10-30 secs from OS load. I have Sapphire Nitro RX 480 4 GB with Samsungs, OS is Windows 10 x64. I tried 1625 strap with TRRD 5, 1750 strap with TRRD 5 and 1750 with TFAW/T32AW = 0, all with the same result. I suspect that injecting custom straps into BIOS using Polaris BIOS Editor might be the cause here. Anyone experienced similar problems?

I've been using Polaris BIOS editor, copy the file to my Linux box, and use atiflash.  Works like a charm.

    WL = 3,  CL = 6,  TM = 0,  WR = 7,  BA0 = 0,  BA1 = 0,  BA2 = 0,  BA3 = 0
Here's the main reason
There are others but first u need to fix this.
# Fixed only MR0 & MR8 #
555000000000000022CC1C00CE595B40D0570C152DCB2409004007000B0414207A8900A00300000 0170F2D35922A3217

# 00300000 # This part is very important and unless you plan to lower your CLmrs below 20 and 21 for WR you shouldn't touch it.

[phobosq]

Thanks, it helped me identify a bug in my strap encoder, 10th word was zeroed on write it will be better now, I already improved and I'm doing ~340 sol/s @1300/2000.

[jstefanop]

Kinda OT since this is a RAM Timings thread, but ill ask this anyways :

For Sapphire RX 470 4GB (Ref) cards GPU Core Volt offset is at A992 correct?
Now for the cards with Hynix memory, I find the default 04 which is 4 X 6.25 or +25mv, which seems legit.
But for the cards with Samsung memory, the value at A992 is FF which is -1 X 6.25 or -6.25mv, so something looks off.
Do different memory versions of the card have different default offset values? Or is the location different?

Any help/guidance would be appriciated.

Seems like the samsung one doesn't have global offset.

Stock roms with global offset have either '03' +18.75mV value or '04' +25mV as VDDC offset.
I've never seen something else, or rather negative offset.. and i've opened up a lot of them ;-) 'But correct me if i'm wrong..'

Greetings.

Yea I got a batch of Samsung based reference saph 470s and manually added the offsets, but for some reason the gpu would not post with the offset added. Weird cause offsets on Hynix/micron cards worked fine. Never had time to investigate this.

[nerdralph]

You'll be happy to know your comment about a better Eth implementation (a long time ago) not increasing speed if not core-limited was correct. I finally got around to writing something really nice for Polaris (still tweaking it) - and while at low memclocks it does almost nothing, when you bump memclk and drop core for undervolting, it's faster.

Glad to hear you're working on a new kernel tuned for Polaris, as you're still better than me when it comes to writing optimized kernels.  Tonga seems to have a limit of 92-93% of the peak memory bandwidth for eth mining, so for a R9 380 clocked at 840/1500, that's just over 22Mh.  For people that haven't read all my old posts, it's physically impossible to get more than 24Mh (192GB/s memory bandwidth / 8KB ethash reads).

For a Rx 480 clocked at 2Ghz, 92% efficiency would be 29.5Mh, and that should be doable with a core clock of 1100.  However I don't recall seeing anyone getting over 29Mh without going over 2Ghz for the memory clock.

[deadsix]

Yea I got a batch of Samsung based reference saph 470s and manually added the offsets, but for some reason the gpu would not post with the offset added. Weird cause offsets on Hynix/micron cards worked fine. Never had time to investigate this.

What location were you adding the offsets at? Because I don't think they can be added at A992 for cards that dont already have a programmed offset built in.
Maybe the learned folk on this thread could shed some light on how to go about adding an offset location to a bios that doesn't have one.

[Eliovp]

Yea I got a batch of Samsung based reference saph 470s and manually added the offsets, but for some reason the gpu would not post with the offset added. Weird cause offsets on Hynix/micron cards worked fine. Never had time to investigate this.

What location were you adding the offsets at? Because I don't think they can be added at A992 for cards that dont already have a programmed offset built in.
Maybe the learned folk on this thread could shed some light on how to go about adding an offset location to a bios that doesn't have one.

Check out Overclock.net forum.

There are some threads there that'll get you a long way to be able to add global offset.

You basically have to find the voltage table (you can find this easily with atombiosreader)
Open your rom in a hexeditor, find that table, (For a lot of Sapphire models, the VDDC offset is already there) 00 8D 00 ** 00

If you want to add it you'll need to modify the table by adding those values in that table.
You then have to update the length of the VoltageObjectInfo (VOI) table & also update the length of the i2c table in VOI table <-- (something a lot of people tend to forget, i remember Wolf having issues with this as well until i told him that he had to change this value too (I2C table)).

After that you have to remove the amount of bytes you added in the legacy ROM section (or the size of the rom is incorrect).

That's not all, after doing that you have to modify the master table as well (there's a calculator for this, also on overclock.net).

It's not "that" difficult but the risk of bricking your card is A LOT higher here than screwing around with timings.

Greetings!

[nerdralph]

Glad to hear you're working on a new kernel tuned for Polaris, as you're still better than me when it comes to writing optimized kernels.  Tonga seems to have a limit of 92-93% of the peak memory bandwidth for eth mining, so for a R9 380 clocked at 840/1500, that's just over 22Mh.  For people that haven't read all my old posts, it's physically impossible to get more than 24Mh (192GB/s memory bandwidth / 8KB ethash reads).

For a Rx 480 clocked at 2Ghz, 92% efficiency would be 29.5Mh, and that should be doable with a core clock of 1100.  However I don't recall seeing anyone getting over 29Mh without going over 2Ghz for the memory clock.

Better to bring the mem clock up a lot more, after loosening the timings a bit. And you can get more than 24MH/s - just obviously not at 1500Mhz memclk.

Agreed, though I find 1625 to be about average for what I can OC the RAM on Tonga cards.  The best I had was a MSI R9 380 gaming that had heat spreaders on Samsung RAM, which was stable at 1700Mhz.  The worst is a MSI Armor2X with cooling for only 3 of the 8 Elpida RAM chips, and is not stable over 1550.

[deadsix]

I wrote a program to do it: https://github.com/OhGodACompany/OhGodATool -- OhGodAnOffset

Check out Overclock.net forum.
There are some threads there that'll get you a long way to be able to add global offset.
You basically have to find the voltage table (you can find this easily with atombiosreader)
Open your rom in a hexeditor, find that table, (For a lot of Sapphire models, the VDDC offset is already there) 00 8D 00 ** 00

And the masters come to the rescue. Thank you guys for all that you do for the community Give a man a fish, and you feed him for a day, teach him to fish, and he's fed for life.

[nerdralph]

Agreed, though I find 1625 to be about average for what I can OC the RAM on Tonga cards.  The best I had was a MSI R9 380 gaming that had heat spreaders on Samsung RAM, which was stable at 1700Mhz.  The worst is a MSI Armor2X with cooling for only 3 of the 8 Elpida RAM chips, and is not stable over 1550.

Bump VDDCI, drop temps any way you can?

I re-routed the fan power cable to try to improve airflow, but it didn't really help.  A copper heat spreader over the RAM would likely help, but I've just focused on getting new cards that have good RAM cooling.  I took a gamble with the Asus Strix Rx470 since I couldn't find any teardowns before I bought it.  It turns out it's RAM cooling isn't any better than MSI Armor2X, and clocking the Hynix RAM over 1875 is difficult.  My 2nd Rx470 is the Sapphire ref version (I think you mentioned you have one as well), which is rock solid at 2100.

[nerdralph]

For the strap mod wannabes, I've made a basic strap mod utility.  It just sets RRD to 5, ACTRD to 16 (0x10), and zeros FAW.
https://github.com/nerdralph/strapread/blob/master/strapmod.py

[nerdralph]

Keep in mind that there is huge diff linux/windows and amdgpu-pro <16.60, I've wrote u on zawawa's thread to update kernel to 4.10/4.11 and install only amdgpu-pro 16.60 ocl packages and their deps. Hashrate will increase +1.2MH guaranteed.

I just did a fresh 16.04.2 install, upgraded to kernel 4.10.5, and installed AMDGPU-Pro 16.60.  Performance only went up from 28.6 to 28.95.

edit: And what's worse is that my ethminer-nr Linux build no longer works like it did with 4.8/16.40.  It crashes the GPU hard, requiring a power cycle to reset it. :-(

[nerdralph]

I finally got around to writing something really nice for Polaris (still tweaking it) - and while at low memclocks it does almost nothing, when you bump memclk and drop core for undervolting, it's faster.

Really looking forward to that new kernel now.  With 4.10.5/16.60 and sgminer-gm 5.5.5 I get 28.95Mh with a 2100 mem clock.  I just tried Claymore 8.1 and it gets 30.2Mh.

p.s. it looks like Claymore is already using a Polaris/Linux optimized kernel:
GPU #0: set -etha as 2 (ETH algo for GPU-PRO drivers in Linux)

[klondike_bar]

got some MSI Gaming X RX 480 8GB cards today at a good price ($300 CAD, with free download code for DOOM, plus additional $20 rebate) and copied the 1750 timings and 1220MHz/2150MHz to get around 29.5MH/s

should i try the 1650 timings next, and will it limit the memory overclocking?

[jstefanop]

Yea I got a batch of Samsung based reference saph 470s and manually added the offsets, but for some reason the gpu would not post with the offset added. Weird cause offsets on Hynix/micron cards worked fine. Never had time to investigate this.

What location were you adding the offsets at? Because I don't think they can be added at A992 for cards that dont already have a programmed offset built in.
Maybe the learned folk on this thread could shed some light on how to go about adding an offset location to a bios that doesn't have one.

Check out Overclock.net forum.

There are some threads there that'll get you a long way to be able to add global offset.

You basically have to find the voltage table (you can find this easily with atombiosreader)
Open your rom in a hexeditor, find that table, (For a lot of Sapphire models, the VDDC offset is already there) 00 8D 00 ** 00

If you want to add it you'll need to modify the table by adding those values in that table.
You then have to update the length of the VoltageObjectInfo (VOI) table & also update the length of the i2c table in VOI table <-- (something a lot of people tend to forget, i remember Wolf having issues with this as well until i told him that he had to change this value too (I2C table)).

After that you have to remove the amount of bytes you added in the legacy ROM section (or the size of the rom is incorrect).

That's not all, after doing that you have to modify the master table as well (there's a calculator for this, also on overclock.net).

It's not "that" difficult but the risk of bricking your card is A LOT higher here than screwing around with timings.

Greetings!

Yea I've added the offset to multiple BIOSes, but for some reason this specific card with samsung memory does not like it.

Yep...nvm just checked the file and realized I forgot to update the i2c length on that one 

[nerdralph]

got some MSI Gaming X RX 480 8GB cards today at a good price ($300 CAD, with free download code for DOOM, plus additional $20 rebate) and copied the 1750 timings and 1220MHz/2150MHz to get around 29.5MH/s

should i try the 1650 timings next, and will it limit the memory overclocking?

A 1625 or 1650 strap will probably have CAS timing too tight for 2150.  Try dropping RRD to 5, ACTRD to 20 or lower, and zero FAW.

[VirosaGITS]

Kinda OT since this is a RAM Timings thread, but ill ask this anyways :

For Sapphire RX 470 4GB (Ref) cards GPU Core Volt offset is at A992 correct?
Now for the cards with Hynix memory, I find the default 04 which is 4 X 6.25 or +25mv, which seems legit.
But for the cards with Samsung memory, the value at A992 is FF which is -1 X 6.25 or -6.25mv, so something looks off.
Do different memory versions of the card have different default offset values? Or is the location different?

Any help/guidance would be appriciated.

Seems like the samsung one doesn't have global offset.

Stock roms with global offset have either '03' +18.75mV value or '04' +25mV as VDDC offset.
I've never seen something else, or rather negative offset.. and i've opened up a lot of them ;-) 'But correct me if i'm wrong..'

Greetings.

113-D0090101_103.rom

Stock at +37.5mV, that's when i decided to use literal offset, rather than writting -125 in the vbios name for F0 when stock was 04.

[laik2]

 04 is +25mV and F0 is -100, EC is -125

[coinzoid]

I'm trying to make some experiments as well, but so far all failed. Every time I get to desktop after flashing a BIOS with custom straps, I get "Thread stuck in device driver" BSOD in 10-30 secs from OS load. I have Sapphire Nitro RX 480 4 GB with Samsungs, OS is Windows 10 x64. I tried 1625 strap with TRRD 5, 1750 strap with TRRD 5 and 1750 with TFAW/T32AW = 0, all with the same result. I suspect that injecting custom straps into BIOS using Polaris BIOS Editor might be the cause here. Anyone experienced similar problems?

This has happened to me on a mixed environment before. I was using a custom bios but later decided to compare bioses between 4gb and 8gb models and edit straps myself. Later it works fine.