For those who are experiencing:
-some cards hashing at stock while the rest are perfect
-random OpenCL issues on random cards after X hours
-unstable and/or fluctuating hash rates
just update your rigs to Win10 Fall Creator's Update and to AMD's latest 17.10.3 driver and your problems will be solved!
Tried this method just for kicks because i'm in the brink of reinstalling windows and poof, it worked!
My 8x Nitro 580 rig is now stable AF running 15+ hours and counting.
Topic: [GUIDE][TUTORIAL][XMR,ETH]How To Mod Bios RX470/570/480/580 VEGA Mining 💰⛏ - page 37. (Read 220957 times)
October 29, 2017, 08:17:24 PM
October 29, 2017, 05:04:23 AM
I have used AB beta 19, mc: 2100, but I received memory error 251000.
My bios was trapped with 1500 to higher.
My bios was trapped with 1500 to higher.
October 29, 2017, 02:40:27 AM
Hi all!
I tried to follow the instructions correctly. But I only achieved hash speed 26mhs. My GPU: 6 x MSI RX570 Amor 4G - Hynix, CC: 1150, MC: 2000, PL: +50 (Dual eth-lbc).
Please help me.
Tks .
You also need OC the memory. I tried to follow the instructions correctly. But I only achieved hash speed 26mhs. My GPU: 6 x MSI RX570 Amor 4G - Hynix, CC: 1150, MC: 2000, PL: +50 (Dual eth-lbc).
Please help me.
Tks .
October 29, 2017, 12:51:38 AM
Hi all!
I tried to follow the instructions correctly. But I only achieved hash speed 26mhs. My GPU: 6 x MSI RX570 Amor 4G - Hynix, CC: 1150, MC: 2000, PL: +50 (Dual eth-lbc).
Please help me.
Tks .
I tried to follow the instructions correctly. But I only achieved hash speed 26mhs. My GPU: 6 x MSI RX570 Amor 4G - Hynix, CC: 1150, MC: 2000, PL: +50 (Dual eth-lbc).
Please help me.
Tks .
October 28, 2017, 02:24:02 AM
Hi, thanks a lot for you tutorial on how flash bios, its really nice of you.
You say in your tutorial about undervolting:
"The trick for easy undervolting is put lower values than it is. Voltages need to be equal or higher than the previous on".
Though before reading that I simply set-up the last value at 1200 (without changing the previous ones) and my cards always worked very good. In afterburner the GPU clock never change and is fixed at 1200mgh.
I decided to try to increment value like you said and now my cards are using 10W more and in afterburner the GPU clock always vary a little bit.
Do you know if it can damage may cards if they always run at 1200?
Thanks!
If you cool it right then probably not. You say in your tutorial about undervolting:
"The trick for easy undervolting is put lower values than it is. Voltages need to be equal or higher than the previous on".
Though before reading that I simply set-up the last value at 1200 (without changing the previous ones) and my cards always worked very good. In afterburner the GPU clock never change and is fixed at 1200mgh.
I decided to try to increment value like you said and now my cards are using 10W more and in afterburner the GPU clock always vary a little bit.
Do you know if it can damage may cards if they always run at 1200?
Thanks!
October 27, 2017, 07:32:36 PM
I follew the definitive guide in reddit, vega56 with stock bios get 1850h/s @～190w, 3000rpm fan. with vega64 bios cannot work stable. Some questions:
1. how to check power consumption with software? nvidia-smi shows clearly for nvidia cards, if there is an AMD equivalent?
2.1800h/s is fine, but the fan @3000 rpm is too noisy to me, how to make the card cool enough with lower fan speed, maybe undervolt?
That's good. You can check it in GPU-Z or HWinfo64, but you have to sum up VRM and chip wattage. It still won't be probably 100% accurate. I don't have VEGA so I don't know what it shows. Sure undervolting will give you lower temps also you can add additional fans.1. how to check power consumption with software? nvidia-smi shows clearly for nvidia cards, if there is an AMD equivalent?
2.1800h/s is fine, but the fan @3000 rpm is too noisy to me, how to make the card cool enough with lower fan speed, maybe undervolt?
specs:
8G ram, 40G virtual memory
2xVega56 with stock BIOS
Windows10 fall creator update x64
auguest 23 blockchain AMD driver
use power play table in registry, core clock 1350@880mv, mem clock 935@880mv
fan 2200rpm
XMR-stak-amd, intensity 2016/1600
The rig has run 8 hours, very stable, it uses 360 watts from killawatt, card temp is 53C, 3700h/s.
October 27, 2017, 04:44:31 PM
Hi, thanks a lot for you tutorial on how flash bios, its really nice of you.
You say in your tutorial about undervolting:
"The trick for easy undervolting is put lower values than it is. Voltages need to be equal or higher than the previous on".
Though before reading that I simply set-up the last value at 1200 (without changing the previous ones) and my cards always worked very good. In afterburner the GPU clock never change and is fixed at 1200mgh.
I decided to try to increment value like you said and now my cards are using 10W more and in afterburner the GPU clock always vary a little bit.
Do you know if it can damage may cards if they always run at 1200?
Thanks!
You say in your tutorial about undervolting:
"The trick for easy undervolting is put lower values than it is. Voltages need to be equal or higher than the previous on".
Though before reading that I simply set-up the last value at 1200 (without changing the previous ones) and my cards always worked very good. In afterburner the GPU clock never change and is fixed at 1200mgh.
I decided to try to increment value like you said and now my cards are using 10W more and in afterburner the GPU clock always vary a little bit.
Do you know if it can damage may cards if they always run at 1200?
Thanks!
October 27, 2017, 05:54:38 AM
I follew the definitive guide in reddit, vega56 with stock bios get 1850h/s @～190w, 3000rpm fan. with vega64 bios cannot work stable. Some questions:
1. how to check power consumption with software? nvidia-smi shows clearly for nvidia cards, if there is an AMD equivalent?
2.1800h/s is fine, but the fan @3000 rpm is too noisy to me, how to make the card cool enough with lower fan speed, maybe undervolt?
That's good. You can check it in GPU-Z or HWinfo64, but you have to sum up VRM and chip wattage. It still won't be probably 100% accurate. I don't have VEGA so I don't know what it shows. Sure undervolting will give you lower temps also you can add additional fans. 1. how to check power consumption with software? nvidia-smi shows clearly for nvidia cards, if there is an AMD equivalent?
2.1800h/s is fine, but the fan @3000 rpm is too noisy to me, how to make the card cool enough with lower fan speed, maybe undervolt?
October 26, 2017, 09:38:25 PM
I follew the definitive guide in reddit, vega56 with stock bios get 1850h/s @～190w, 3000rpm fan. with vega64 bios cannot work stable. Some questions:
1. how to check power consumption with software? nvidia-smi shows clearly for nvidia cards, if there is an AMD equivalent?
2.1800h/s is fine, but the fan @3000 rpm is too noisy to me, how to make the card cool enough with lower fan speed, maybe undervolt?
1. how to check power consumption with software? nvidia-smi shows clearly for nvidia cards, if there is an AMD equivalent?
2.1800h/s is fine, but the fan @3000 rpm is too noisy to me, how to make the card cool enough with lower fan speed, maybe undervolt?
October 25, 2017, 09:55:07 AM
I'm using the elpida timing strap from a post early on on this thread. My mem clock now is only at 2050 so I still have a long way to go.
This is not how these things work, but it's rather strap dependent.
I mean i made a strap that gives 30mhs at 2030, so i should be able to go up to 2150 and get 35mhs , right ?
Forgive my lack of knowledge about timing straps, I though that's how they are.
But i'm now hitting 31.3 Mh at 2100 clock and 4 out of 8 cards are doing it. So I'd say there's really potential depending on the card if it could be pushed higher.
I'll post pictures tomorrow after work.
If only 4 out of 8 are able to work at 2100, I bet those 4 that do work have lots of memory errors
See for yourself
October 25, 2017, 04:18:58 AM
Forgive my lack of knowledge about timing straps, I though that's how they are.
But i'm now hitting 31.3 Mh at 2100 clock and 4 out of 8 cards are doing it. So I'd say there's really potential depending on the card if it could be pushed higher.
I'll post pictures tomorrow after work.
It's how it works but you can't expect some big hashrate changes in just few MHz. I said if your card is good and you won the silicon lottery you can have 31MH/s with this timing.But i'm now hitting 31.3 Mh at 2100 clock and 4 out of 8 cards are doing it. So I'd say there's really potential depending on the card if it could be pushed higher.
I'll post pictures tomorrow after work.
For example the Uber-mix 3.1 on 2000MHz you will have around 30MH/s on 2200MHz you might have 31.5MH/s, but most cards won't be able to run 2200MHz.
October 25, 2017, 01:48:03 AM
I'm using the elpida timing strap from a post early on on this thread. My mem clock now is only at 2050 so I still have a long way to go.
This is not how these things work, but it's rather strap dependent.
I mean i made a strap that gives 30mhs at 2030, so i should be able to go up to 2150 and get 35mhs , right ?
Forgive my lack of knowledge about timing straps, I though that's how they are.
But i'm now hitting 31.3 Mh at 2100 clock and 4 out of 8 cards are doing it. So I'd say there's really potential depending on the card if it could be pushed higher.
I'll post pictures tomorrow after work.
If only 4 out of 8 are able to work at 2100, I bet those 4 that do work have lots of memory errors
October 25, 2017, 01:22:36 AM
Hi, all
Says Mal can someone here adapt a guide to the Vega 56 and Vega 64?
Somehow I have my problems.
Says Mal can someone here adapt a guide to the Vega 56 and Vega 64?
Somehow I have my problems.
October 25, 2017, 01:06:35 AM
I'm using the elpida timing strap from a post early on on this thread. My mem clock now is only at 2050 so I still have a long way to go.
This is not how these things work, but it's rather strap dependent.
I mean i made a strap that gives 30mhs at 2030, so i should be able to go up to 2150 and get 35mhs , right ?
Forgive my lack of knowledge about timing straps, I though that's how they are.
But i'm now hitting 31.3 Mh at 2100 clock and 4 out of 8 cards are doing it. So I'd say there's really potential depending on the card if it could be pushed higher.
I'll post pictures tomorrow after work.
October 24, 2017, 09:17:42 AM
This is not how these things work, but it's rather strap dependent.
I mean i made a strap that gives 30mhs at 2030, so i should be able to go up to 2150 and get 35mhs , right ?
That would be awesome :3 I mean i made a strap that gives 30mhs at 2030, so i should be able to go up to 2150 and get 35mhs , right ?
October 24, 2017, 01:48:55 AM
I'm using the elpida timing strap from a post early on on this thread. My mem clock now is only at 2050 so I still have a long way to go.
This is not how these things work, but it's rather strap dependent.
I mean i made a strap that gives 30mhs at 2030, so i should be able to go up to 2150 and get 35mhs , right ?
October 23, 2017, 11:01:21 PM
really helpful post , thanks ~
October 23, 2017, 09:42:38 PM
Hey Matt, do you have an experience of a Nitro+ 580 4gb hitting 31Mh stable?
I'm running 8x right now (just finished setting it up last night) and I could get them to run at 30.5 stable for >12hrs now. You think they can push 31?
If you are using timings from the PBE 1.6, so probably yes.I'm running 8x right now (just finished setting it up last night) and I could get them to run at 30.5 stable for >12hrs now. You think they can push 31?
Mattthev,
Thanks for the great tutorial
running RX 470 4G with Elpida memory and mining ETH with it.
Stock: 20MHs
After following the guide and a couple of questions: 26.4 MHs
Happy with this for now.
More tuning later.
Mark
You need also OC the memory.Thanks for the great tutorial
running RX 470 4G with Elpida memory and mining ETH with it.
Stock: 20MHs
After following the guide and a couple of questions: 26.4 MHs
Happy with this for now.
More tuning later.
Mark
What does the temperature target in BIOS indicate. The values are 70 on RX 570 Gaming X. Will the card throttle if it crosses this limit? RX 580 Nitro+ has this at 75.
@Mattthev maybe you would like to add a note in the OP. While using ATIflash not to have HWInfo or other softwares that reads off BIOS. They interrupt the flashing process. Have experienced this several times.
I've never had problem with this. It's only recommended to close MSI Afterburner or other OC utilities.@Mattthev maybe you would like to add a note in the OP. While using ATIflash not to have HWInfo or other softwares that reads off BIOS. They interrupt the flashing process. Have experienced this several times.
Hi Mattthe V,
I applied the timing string and boosted the memory to 2000. It will not take any more. I am sure there is more tweaking to be done.
Mark
October 23, 2017, 03:54:09 PM
Thanks!
And if things go south, i'd just change them back to the lower mem clock settings.
I've meant that you need better timing to achieve that. Only if your card is super awesome that timing from PBE will do 31MH/s and more.And if things go south, i'd just change them back to the lower mem clock settings.
I'm using the elpida timing strap from a post early on on this thread. My mem clock now is only at 2050 so I still have a long way to go.
Regarding achieving >31, I got them to do that but only during tweaking them with 3 cards connected.
October 23, 2017, 01:30:58 PM
Thanks!
And if things go south, i'd just change them back to the lower mem clock settings.
I've meant that you need better timing to achieve that. Only if your card is super awesome that timing from PBE will do 31MH/s and more. And if things go south, i'd just change them back to the lower mem clock settings.
Jump to: