Question XFX 5700 XT Cards

Anthony

Mitglied
Mitglied seit
Nov 28, 2020
Beiträge
22
Bewertungspunkte
6
Punkte
2
Preface: @Mini_Me has demonstrated profound knowledge when modding the 5700 XT series of graphics cards, and for those looking for an awesome tutorial, please reference https://www.igorslab.de/community/threads/gigabyte-5700-xt-bios-mod-fails.3304/.

Story: At the present time, I own 40 XFX 5700 XT video cards; I have 40 more on order to make a total quantity of 80 cards. With this many cards, squeezing out an additional 1 MegaHash (MH) from each card would translate into +80MH. Out of the box, the stock bios on these XFX 5700 XT cards reflects about 51MH per card. With bios modifications and tweaks, it is possible for me to obtain between 54MH-56MH per card.

Configuration: I have 5 rigs in operation and soon I will have 5 more in operation. Each rig uses 8 cards. I am using HiveOS to manage my rigs.

The importance of bios modifications: Basically, using bios modifications allows each card to provide a better hashrate -- and as hashrate increases, potential ETH mined increases. (More Hash == More $$). Bios modifications also change how each card consumes electricity -- and aside from the initial cost of computer components, electricity is the second greatest cost when it comes to mining.
  • Stock Bios: 80 Cards x 51MH from each card = 4.080GH
  • Modified Bios: 80 Cards x (54MH || 56MH) = (4.320GH || 4.480GH).
The delicate balance in bios modification reflects a specific relationship between: 1.) Power Consumption, 2.) Temperature, 3.) Hashrate, and 4.) Stability vs. Instability. In my opinion, the goal of proper bios modification means that: (a.) each card consumes as little power as necessary, (b.) each card remains within "safe" temperatures to prevent card damage, (c.) each card produces the maximum hashrate, (d.) each card remains stable, which is to say that the card does not produce "invalid" shares or other errors that get in the way of making money.

The above mentioned thread link reflects a dialogue between two members, @Mini_Me and @AlleyCat. The thread is several pages long because it reflects a series of tests (trials, errors, and new trials with new errors, etc.) with different bios values and with different values in HiveOS. There are multiple variables in play (both on the bios tweaking side with MPT and RBE and on the software tweaking side in HiveOS), and changing one variable influences other variables. The thread is so long because many different settings were tried out in order to achieve the best possible result for specific card manufacturers, in this case manufacturer Sapphire and manufacturer Gigabyte.

This post in particular captured my attention: https://www.igorslab.de/community/threads/gigabyte-5700-xt-bios-mod-fails.3304/post-79315.

RBE modified values in use:
Option 1 (Preferable and Recommended), applying Apple Inc. vram timings straps linked below, once for MT61K256M32 Micron, and Save the vbios after that load the saved vbios and once again apply the straps for K4Z80325BC Samsung if it is existed and save the vbios again,
https://www.igorslab.de/community/a...-mt61k256m32_gddr6_optimized_timings-zip.6544

MPT modified values in use:
Features Tab:
PPTable Features -> Feature Control = Nothing done. Left at default.
Overdrive Features = All Boxes Checked.

Overdrive Limits Tab:
GFX Maximum Clock = 1550
Memory Maximum Cock = 1000
Power Limit Maximum = 0
Power Limit Minimum = 0
Memory Timing Control = 1
Fan RPM Maximum = 3500
Fan RPM Minimum = 1100
Fan Acoustic Limit RPM Maximum = 3500
Fan Acoustic Limit RPM Minimum = 1100
Zero RPM Control = 0

Power and Voltage Tab:
Maximum Voltage GFX = 900
Maximum Voltage SoC = 1150
Minimum Voltage GFX = 700
Minimum Voltage SoC = 750
Power Limit GPU = 140
TDC Limit GFX (A) = 140
TDC Limit SoC (A) = 14

Frequency Tab:
GFX Maximum = 1400
GFX Minimum = 300
SoC Maximum = 1267
SoC Minimum = 507
Memory DPM 0 = 100
Memory DPM 1 = 500
Memory DPM 2 = 625
Memory DPM 3 = 960

Curve Tab:
(Left Alone, no change).
AVFS (GHz->V)
Override box is not ticked.
a = 0.017810
b = -0.047280
c = 0.054020
StaticVoltageOffset (GHz->V) = 0.000000

Fan Tab:
PWM Minimum = 15
Fan Acoustic Limit RPM = 1550
Fan Throtteling RPM = 3200
Fan Maximum RPM = 3500
Fan Target Temperature = 85
Fan GFX Clock = 800
Zero RPM Enable Box is ticked.
Stop Temperature = 60
Start Temperature = 68

As you can see, in order to achieve stability (prevent invalid shares, rejected shares, and phoenixminer reboots), I have to run most cards at 1375 core. Other cards I had to reduce to 1325 core. Some cards run at memory 930, some at 905, some at 900, and some at 890.

I know my cards can give better performance. Even though I have reduced power values to reduce # of invalid-rejected shares, phoenixminer still reboots from time to time, and sometimes, I will have a card that will "stop" and disappear ... which causes the phoenixminer rebooter. For these cards, I reduce values.

Any advice from master @Mini_Me would be appreciated.


RIG #1
RIG1.png

RIG #2
RIG2.png

RIG #3
RIG3.png

RIG #4
RIG4.png

RIG #5
RIG5.png
 
In the image attached, you will see an example of a "reboot" error.
No invalid shares were produced. No drop in hashrate for the rig on the status screen.
But when I examined the cards inside the rig for power values, I saw one card at 29W, so that's the problem card.
I had MEM=910 and VDDCI at 900 because it is a Samsung card.
I left VDDCI at 900 and lowered MEM to 900.

error-example-png.8168
 

Anhänge

  • Error-Example.png
    Error-Example.png
    84,7 KB · Aufrufe : 399
Here is another error that happened after 20 minutes of operation without error.
Error: Invalid Share.
VDDCI was at 900 and MEM was at 910 for 20 minutes before an error happened.
I therefore -10 to MEM.

Error-20mins.png
 
I find on my system that the "dead GPU" errors are mostly because of VDD is too low (or the core is too high for the selected VDD). Try increasing the GPU2 VDD from 790 to 800 or 810 at a core = 1420.

At 900 - 910 MHz memory clock, I run VDDCI between 780 to 800mv, depends on the card. I think VDDCI at 900 mv is not an efficient setting.

Try to deal with GPU4 memory error by reducing the core clock to 1380/770. I have one XFX card with Samsung memory and I cannot run it stable above 55.5 MH/s. Therefore, I suspect that you are pushing the card a little too hard. If you drop the core, the hash will decrease a little, but there will be a significant drop in power consumption, and the card may get more stable.

GPU4 looks like a similar GPU to your GPU7.
 

Anhänge

  • Screen Shot 2020-12-06 at 5.40.16 PM.png
    Screen Shot 2020-12-06 at 5.40.16 PM.png
    107,3 KB · Aufrufe : 36
Here is another error that happened after 20 minutes of operation without error.
Error: Invalid Share.
VDDCI was at 900 and MEM was at 910 for 20 minutes before an error happened.
I therefore -10 to MEM.

Anhang anzeigen 8169
Greetings Anthony,

My apologies for the late reply,

Let us verify everything step by step to ensure that all is checked,

- If your motherboard bios is not updated yet to the latest version then please clear the CMOS and update it,

- I believe that a proper and sufficient power supply was chosen for the rig(s) and all the components were connected correctly and properly to the power supply following the motherboard manual,

- I believe that a proper and sufficient ventilation is already provided for the rig(s),

- In order to prevent the drop out hashrate of the card, in the motherboard bios settings, set R6 (Render Standby) to Disabled,

- Remember to set the PCI-e configuration from Auto to Gen 3 in the motherboard bios setting,

- I recently refined the guide again on pages 2, 15, 28 and 32, the guides that interest you are on pages 15 and 32, please check it out and note that the guide on page 15 is for cards with sensitive (restricted) power curve,

- Regarding the recommend parameters to be used in HiveOS, you can use one of the below,
Core State: 1
Memory State: 1
Core clock, VDD, Memory clock, VDDCI, MVDD
For Power Saving and lower temperature,
~ 1370 MHz, 760 mV, 900 MHz, 780 mV, 1290 mV,
~ 1385 MHz, 770 mV, 905 MHz, 800 mV, 1310 mV (or 1350 mV),
~ 1385 mV, 770 mV, 905 MHz, 850 mV, 1310 mV (or 1350 mV),

For Performance,
~ 1430 MHz, 795 mV, 950 MHz, 850 mV, 1350 mV (or 1360 mV),
~ 1430 MHz, 795 mV, 950 MHz, 900 mV, 1350 mV (or 1360 mV),
~ 1440 MHz, 800 mV, 960 MHz, 900 mV, 1350 mV (or 1365 mV),

Please feel free to message me whenever you like and your feedbacks are much appreciated,

You may have a good day,

Best Regards.
 
Zuletzt bearbeitet :
Hi guys!
Im not really sure if I picked the right topic to ask for a help, but I will appreciate if you could.
I got 2 5700xt cards (Sapphire Pulse and XFX Raw II). The second one consume much more power with the same settings like for the first one. Is it okay?
And what should I do to decrease consumptions and especially memory temps?
 

Anhänge

  • Screenshot_1.png
    Screenshot_1.png
    36,3 KB · Aufrufe : 41
Hi guys!
Im not really sure if I picked the right topic to ask for a help, but I will appreciate if you could.
I got 2 5700xt cards (Sapphire Pulse and XFX Raw II). The second one consume much more power with the same settings like for the first one. Is it okay?
And what should I do to decrease consumptions and especially memory temps?
Hi,

Regarding the recommend parameters to be used in HiveOS, you can use one of the below,

Core State: 1
Core clock, VDD, Memory clock, VDDCI, MVDD
For Power Saving and lower temperature,
~ 1370 MHz, 760 mV, 900 MHz, 780 mV, 1290 mV,
~ 1385 MHz, 770 mV, 910 MHz, 800 mV, 1310 mV (or 1350 mV),
~ 1385 mV, 770 mV, 910 MHz, 850 mV, 1310 mV (or 1350 mV).
 
Hi,

Regarding the recommend parameters to be used in HiveOS, you can use one of the below,

Core State: 1
Core clock, VDD, Memory clock, VDDCI, MVDD
For Power Saving and lower temperature,
~ 1370 MHz, 760 mV, 900 MHz, 780 mV, 1290 mV,
~ 1385 MHz, 770 mV, 910 MHz, 800 mV, 1310 mV (or 1350 mV),
~ 1385 mV, 770 mV, 910 MHz, 850 mV, 1310 mV (or 1350 mV).
Thanks!
Now I got this values. The rig is now staying in the warm flat, it will work outside on the balcony, I hope temperatures will be lower.
 

Anhänge

  • Screenshot_2.png
    Screenshot_2.png
    37,3 KB · Aufrufe : 49
Just wanted to provide a quick update. I've reached my goal regarding stability over time. After about 10 hours of operation, no errors, no reboots, no problems. I'm running Phoenixminer because because if my rigs show stability in Phoenixminer, then it's more likely that they'll also be stable using TeamRedMiner. Phoenixminer produced more errors more often, it seemed to me, so I wanted to iron out problems with the pickiest miner.

I want to thank everyone for their help and feedback. Hopefully someone will find the information in this post useful in the future. Every card is its own unique beast. I know that some of these values will look weird, but these are the values that produced stability over time.

Maybe there is room to tweak further, for example, I would like to figure out what's up with those cards that are stable at MEM=890. But as it is, I'm happy with these values. 🥳🎉🥳

10-hrs-Stable.png

1380-780PhoenixMiner
RIG#GPU#MANMHWATTSCOREDPMVDDVDDCIMVDDMEMMDPM
001​
0MICRON56.391151380178080013509301
0011SAMSUNG56.36841380178080013509001
0012SAMSUNG
55.71​
841380178080013508901
0013SAMSUNG56.341101380178080013509001
0014SAMSUNG56.871061380178080013509001
0015MICRON56.351181380178080013509301
0016SAMSUNG57.22861380178080013509001
0017MICRON57.141171380178080013509301
0020SAMSUNG56.95831380178080013509101
0021SAMSUNG56.33861380178080013509001
0022SAMSUNG55.73841380178085013508901
0023MICRON57.371171380178080013509301
0024SAMSUNG55.72821380178078013508901
0025MICRON57.241171380178080013509301
0026SAMSUNG56.95841380178080013509101
0027SAMSUNG55.71851380178078013508901
0030SAMSUNG56.32841380178080013509001
0031MICRON57.48961380178080013509301
0032SAMSUNG55.69831380178078013508901
0033SAMSUNG56.32841380178080013509001
0034MICRON57.361201380178080013509301
0035SAMSUNG56.94861380178080013509101
0036SAMSUNG55.70841380178085013508901
0037SAMSUNG55.71841380178080013508901
0040SAMSUNG56.911031380178078013509101
0041SAMSUNG56.271061380178078013509001
0042SAMSUNG56.301091380178080013509001
0043SAMSUNG55.671051380178081013508901
0044SAMSUNG56.301091380178080013509001
0045SAMSUNG56.301001380178078013509001
0046SAMSUNG56.921071380178078013509101
0047SAMSUNG56.301021380178078013509001
0050SAMSUNG56.331061380178080013509001
0051SAMSUNG56.331001380178078013509001
0052SAMSUNG56.321051380178078013509001
0053SAMSUNG56.641021380178078013509101
0054SAMSUNG56.961071380178078013509101
0055SAMSUNG55.711071380178078013508901
0056SAMSUNG56.331031380178078013509001
0057SAMSUNG56.941071380178080013509101
AVG56.4698.93795.75905.00
 
Just wanted to provide a quick update. I've reached my goal regarding stability over time. After about 10 hours of operation, no errors, no reboots, no problems. I'm running Phoenixminer because because if my rigs show stability in Phoenixminer, then it's more likely that they'll also be stable using TeamRedMiner. Phoenixminer produced more errors more often, it seemed to me, so I wanted to iron out problems with the pickiest miner.

I want to thank everyone for their help and feedback. Hopefully someone will find the information in this post useful in the future. Every card is its own unique beast. I know that some of these values will look weird, but these are the values that produced stability over time.

Maybe there is room to tweak further, for example, I would like to figure out what's up with those cards that are stable at MEM=890. But as it is, I'm happy with these values. 🥳🎉🥳

Anhang anzeigen 8337

1380-780PhoenixMiner
RIG#GPU#MANMHWATTSCOREDPMVDDVDDCIMVDDMEMMDPM
001​
0MICRON56.391151380178080013509301
0011SAMSUNG56.36841380178080013509001
0012SAMSUNG
55.71​
841380178080013508901
0013SAMSUNG56.341101380178080013509001
0014SAMSUNG56.871061380178080013509001
0015MICRON56.351181380178080013509301
0016SAMSUNG57.22861380178080013509001
0017MICRON57.141171380178080013509301
0020SAMSUNG56.95831380178080013509101
0021SAMSUNG56.33861380178080013509001
0022SAMSUNG55.73841380178085013508901
0023MICRON57.371171380178080013509301
0024SAMSUNG55.72821380178078013508901
0025MICRON57.241171380178080013509301
0026SAMSUNG56.95841380178080013509101
0027SAMSUNG55.71851380178078013508901
0030SAMSUNG56.32841380178080013509001
0031MICRON57.48961380178080013509301
0032SAMSUNG55.69831380178078013508901
0033SAMSUNG56.32841380178080013509001
0034MICRON57.361201380178080013509301
0035SAMSUNG56.94861380178080013509101
0036SAMSUNG55.70841380178085013508901
0037SAMSUNG55.71841380178080013508901
0040SAMSUNG56.911031380178078013509101
0041SAMSUNG56.271061380178078013509001
0042SAMSUNG56.301091380178080013509001
0043SAMSUNG55.671051380178081013508901
0044SAMSUNG56.301091380178080013509001
0045SAMSUNG56.301001380178078013509001
0046SAMSUNG56.921071380178078013509101
0047SAMSUNG56.301021380178078013509001
0050SAMSUNG56.331061380178080013509001
0051SAMSUNG56.331001380178078013509001
0052SAMSUNG56.321051380178078013509001
0053SAMSUNG56.641021380178078013509101
0054SAMSUNG56.961071380178078013509101
0055SAMSUNG55.711071380178078013508901
0056SAMSUNG56.331031380178078013509001
0057SAMSUNG56.941071380178080013509101
AVG56.4698.93795.75905.00
Thank you for your informative and organized feedback,

It is a great news that you achieved your goals,

Please stay safe and healthy and keep up the good work,

Best Regards.
 
Just wanted to provide a quick update. I've reached my goal regarding stability over time. After about 10 hours of operation, no errors, no reboots, no problems. I'm running Phoenixminer because because if my rigs show stability in Phoenixminer, then it's more likely that they'll also be stable using TeamRedMiner. Phoenixminer produced more errors more often, it seemed to me, so I wanted to iron out problems with the pickiest miner.

I want to thank everyone for their help and feedback. Hopefully someone will find the information in this post useful in the future. Every card is its own unique beast. I know that some of these values will look weird, but these are the values that produced stability over time.

Maybe there is room to tweak further, for example, I would like to figure out what's up with those cards that are stable at MEM=890. But as it is, I'm happy with these values. 🥳🎉🥳

Anhang anzeigen 8337

1380-780PhoenixMiner
RIG#GPU#MANMHWATTSCOREDPMVDDVDDCIMVDDMEMMDPM
001​
0MICRON56.391151380178080013509301
0011SAMSUNG56.36841380178080013509001
0012SAMSUNG
55.71​
841380178080013508901
0013SAMSUNG56.341101380178080013509001
0014SAMSUNG56.871061380178080013509001
0015MICRON56.351181380178080013509301
0016SAMSUNG57.22861380178080013509001
0017MICRON57.141171380178080013509301
0020SAMSUNG56.95831380178080013509101
0021SAMSUNG56.33861380178080013509001
0022SAMSUNG55.73841380178085013508901
0023MICRON57.371171380178080013509301
0024SAMSUNG55.72821380178078013508901
0025MICRON57.241171380178080013509301
0026SAMSUNG56.95841380178080013509101
0027SAMSUNG55.71851380178078013508901
0030SAMSUNG56.32841380178080013509001
0031MICRON57.48961380178080013509301
0032SAMSUNG55.69831380178078013508901
0033SAMSUNG56.32841380178080013509001
0034MICRON57.361201380178080013509301
0035SAMSUNG56.94861380178080013509101
0036SAMSUNG55.70841380178085013508901
0037SAMSUNG55.71841380178080013508901
0040SAMSUNG56.911031380178078013509101
0041SAMSUNG56.271061380178078013509001
0042SAMSUNG56.301091380178080013509001
0043SAMSUNG55.671051380178081013508901
0044SAMSUNG56.301091380178080013509001
0045SAMSUNG56.301001380178078013509001
0046SAMSUNG56.921071380178078013509101
0047SAMSUNG56.301021380178078013509001
0050SAMSUNG56.331061380178080013509001
0051SAMSUNG56.331001380178078013509001
0052SAMSUNG56.321051380178078013509001
0053SAMSUNG56.641021380178078013509101
0054SAMSUNG56.961071380178078013509101
0055SAMSUNG55.711071380178078013508901
0056SAMSUNG56.331031380178078013509001
0057SAMSUNG56.941071380178080013509101
AVG56.4698.93795.75905.00
Great OC settings for stability. However, note that Pheonix miner reports fake hash; so, don't expect to see the same hash on the pool.
 
Greetings Anthony,

My apologies for the late reply,

Let us verify everything step by step to ensure that all is checked,

- If your motherboard bios is not updated yet to the latest version then please clear the CMOS and update it,

- I believe that a proper and sufficient power supply was chosen for the rig(s) and all the components were connected correctly and properly to the power supply following the motherboard manual,

- I believe that a proper and sufficient ventilation is already provided for the rig(s),

- In order to prevent the drop out hashrate of the card, in the motherboard bios settings, set R6 (Render Standby) to Disabled,

- Remember to set the PCI-e configuration from Auto to Gen 3 in the motherboard bios setting,

- I recently refined the guide again on pages 2, 15, 28 and 32, the guides that interest you are on pages 15 and 32, please check it out and note that the guide on page 15 is for cards with sensitive (restricted) power curve,

- Regarding the recommend parameters to be used in HiveOS, you can use one of the below,
Core State: 1
Memory State: 1
Core clock, VDD, Memory clock, VDDCI, MVDD
For Power Saving and lower temperature,
~ 1370 MHz, 760 mV, 900 MHz, 780 mV, 1290 mV,
~ 1385 MHz, 770 mV, 905 MHz, 800 mV, 1310 mV (or 1350 mV),
~ 1385 mV, 770 mV, 905 MHz, 850 mV, 1310 mV (or 1350 mV),

For Performance,
~ 1430 MHz, 795 mV, 950 MHz, 850 mV, 1350 mV (or 1360 mV),
~ 1430 MHz, 795 mV, 950 MHz, 900 mV, 1350 mV (or 1360 mV),
~ 1440 MHz, 800 mV, 960 MHz, 900 mV, 1350 mV (or 1365 mV),

Please feel free to message me whenever you like and your feedbacks are much appreciated,

You may have a good day,

Best Regards.

I have a quick dumb question, How do i get the "Core State" feature to appear in HiveOS overclock settings window?


1609179231263.png
 
Oben Unten