Question GIGABYTE 5700 XT Bios mod fails

AlleyCat

Veteran
Mitglied seit
Okt 9, 2020
Beiträge
290
Bewertungspunkte
17
Punkte
17
Hi,
I am failing to update Gigabyte 5700 XT. The same procedure updates the BIOS on MSI cards with no problem. I follow the instructions on Igors Lab.

The sign of having trouble with the card bios flash shows in GPU-Z. After flash using amdvbflash the values of GPU and memory frequencies is empty. With stock bios there are Mhz frequencies.

Is there any known problems with flashing Gigabyte cards?
Any suggestions on what other forums I may ask for assistance?
Is it possible that the OEM bios is signed, and any modified bios will be rejected?
If the bios is signed, any tools to resign, or would I need to buy a card from a different vendor?

Thanks,

Alley Cat
 
Zuletzt bearbeitet :
My rx 5700 cards are very stable. Don't know much about mixing cards... although trm writed in hes release that this new kernel was for navi cards. Don't know how he implemented the same kernel with polaris. Did you mention your issue with the developer?
 
I think that you can flash the rx 5700 bios... someone, correct me if I'm wrong. I say this because your pulling too much wattage from the wall, and that's a xt version. You shoud get way more hashrate then me with original bios.
Also, could be the location, or the implemented kernel within linux. Who knows... you must debug that.
 
Thank you, but saddly I adjust with best micron settings and can't get more than 55,4. And unstable.

Also, more power and temp on memories, but not better performance.

:(
Have you followed the guide in the kindly attached link below,

 
Start from scratch with original bios! Do one strap at the time. Follow the instructions below.
 

Anhänge

  • APPLE STRAPS.txt
    3,1 KB · Aufrufe : 38
  • MPT-INSTRUCTIONS.txt
    1,2 KB · Aufrufe : 46
Não estou a perceber... é isto que queres?
 

Anhänge

  • ASUS-DUAL-EVO-RX-5700-ORIGINAL-APPLE-STRAPS.mpt
    1,9 KB · Aufrufe : 2
  • SAPPHIRE-BLOWER-RX-5700-ORIGINAL-APPLE-STRAPES.mpt
    1,9 KB · Aufrufe : 3
I'm on boat... testing again!
I melted the connection from psu, was from sata port. I pulled out the connection and a part melted there. The cable now is trash!
I realy need to switch this to molex adapter or replace the riser.
 
I can see that the connection in psu is different from sata to molex, but since they all black i can't colour code them. I guess they aren't the same in amps and watt. Does anyone now more about this two types?
 
Greetings,

Please follow the guide below,

The below is the settings for best performance and power consumption for safe 24/7 operating,

÷ Using MorePowerTool from the kindly attached link below,


Apply the setting below,

- Under Features tab, set:
Zero RPM: Uncheck (Disable, for those who have high memory temperature)

- Under Overdrive Limits tab, set:
GFX Maximum Clock 1440 MHz
Memory Maximum Clock 960 MHz
Power Limit Maximum 0%
Power Limit Minimum 0%
Memory Timing Control: 1 [For computing (mining), default is 2 for gaming]
Zero RPM Control: 0 (For those who have high memory temperature)

- Under Feature Control, set:
GFXOFF: Uncheck (Disable, to prevent hashrate from dropping to 0 MH/s in addition to disable R6 Render Standby in the motherboard bios settings if exists),
ACDC: Uncheck (Disable),

- Under Power and Voltages, set:
Maximum Voltage GFX: 1050 mV
[must not be lower than this as the MVDD default value in the vbios is at 1350 mV and the VDD must be within 300 mV range with MVDD or components may get degraded and permanent damaged]
Maximum Voltage SoC: 1050 mV
[must not be lower than this like the Maximum Voltage GFX]
Minimum Voltage GFX: 750 mV
Minimum Voltage SoC: 750 mV
Power Limit GPU: 126 W (120 W for non XT)
TDC Limit GFX: 110 A (105 A for non XT)
TDC Limit SoC: 12 A (10 A for non XT)

- Under Frequency tap, set:
GFX Maximum: 1260 MHz
Memory DPM 3: 910 MHz
[Regarding SoC Maximum, must be kept at default 1267 MHz in the vbios, capping it at another value must be done inside the OS using a script in linux or editing the registry using MorePowerTool in Windows and at your own discretion, recommended values for memory types at specific clocks as below,
Memory Clock - - - > SoC Maximum,
910 (1820) MHz - - - > 957 MHz (Samsung & Micron),
950 (1900) MHz - - - > 1093 MHz (Micron, here the default 1267 MHz is preferred),

- Under Fan tab, set:
Zero RPM Enabled: Uncheck (Disable, for those who have high memory temperature)
Stop Temperature: 50° C
Start Temperature: 60° C

÷ Regarding the memory vram timings,

The 2 options below are the best ones for stability, performance and power consumption,

Option 1 (Preferred 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,

Option 2 (Universal), applying vram timings as below for both Samsung and Micron like before,

- K4Z80325BC (Samsung)
2000 MHz (Copy) - - - > (Paste) 2250 MHz
1800 MHz - - - > 2000 MHz
(1500 or 1550) MHz - - - > 1800 MHz

- MT61K256M32 (Micron)
1750 MHz - - - > (1875 - 2000) MHz
(1500 or 1550) MHz - - - > (1750 - 1800) MHz

Memory Clock - tREF
1000 MHz - 3900 (Samsung & Micron)
1250 MHz - 4875 (Samsung & Micron)
(1500 or 1550) MHz - 6045 (Samsung & Micron)
1750 MHz - 6825 (Micron only)
1800 MHz - 7020 (Samsung & Micron)
1875 MHz - 7315 (Micron only)
2000 MHz - 7800 (Samsung & Micron)
2250 MHz - 8775 (Samsung only)

÷ Regarding parameters settings as below,

- Core parameters,
Core State: 1 (HiveOS),
Mem State: 1 (HiveOS),
Core clock from (1380 to 1430) MHz, VDD at (770 - 790) mV, keep the ratio of Core clock to VDD = below 1.80 (preferred 1.76, default is 1.70) as beyond that negative scaling may start which means lowering performance and occurring instability and increasing temperature.

- Memory parameters,
~Samsung K4Z80325BC-HC14,
Memory clock at 910 MHz more than this is not stable, VDDCI at 850 mV, MVDD at 1350 mV,

~Micron MT61K256M32JE-14,
Memory clock at 910 MHz for power saving and lower temperature like for Samsung memory and 950 MHz for performance, VDDCI at 900 mV (850 mV is the minimum for memory clock 915 MHz and below), MVDD 1350 mV [the minimum is 1350 mV for memory clock 910 MHz and below],

[*Disclaimer regarding the memory temperature to avoid and prevent its degradation and being baked again that might lead to connection loose,

For Samsung memory K4Z80325BC-HC14,
For operating at 24/7, the temperature must not exceed 74° C,
Other than this will fall under the below,
At (80 ± 5)° C, operating for 24/7 requires putting the system on a break of 1 to 2 hour (depending on the ambient temperature) after 48 hour of operation,
At (100 ± 5)° C, operating for 24/7 requires putting the system on a break of 1 to 2 hour (depending on the ambient temperature) after 36 hour of operation,
At (125 ± 5)° C, operating for 24/7 requires putting the system on a break of 1 to 2 hour (depending on the ambient temperature) after 24 hour of operation,

For Micron memory MT61K256M32JE-14, it is the same as for Samsung K4Z80325BC-HC14 even thought Micron Inc. stated it can run from (0 to 95)° C, however this is for normal use and not for 24/7 of operation].

Due to air cooling is being used, the highly recommend setting as below,
[For optimal hashrate, keep the gap between the core clock and memory clock at 480 MHz]
[The recommended and safe ratio between VDDCI and Memory clock is 2.14, for example: 1820 (910*2) MHz ÷ 850 = ~2.14]
[The safe and recommend ratio between the MVDD and Memory clock is 1.39 for memory clock ABOVE 1870 (935*2) MHz]

Core clock, VDD : Memory clock, VDDCI, MVDD
- 1330 MHz, 750 mV : 850 (1700/2) MHz, 800 mV, 1350 mV,
- 1360 MHz, 760 or 770 mV : 880 (1760/2) MHz, 820 mV, 1350 mV,
- 1390 MHz, 780 or 790 mV : 910 (1820/2) MHz, 850 mV, 1350 mV,
- 1430 MHz, 800 or 810 mV : 950 (1900/2) MHz, 890 mV, 1365 mV.
The following new settings (page 32) will cause my Asus Strix 5700XT to be capped at 44MH. Reverting the changes produces a normal 56MH based on my overclocks / etc.

GFXOFF: Uncheck
ACDC: Uncheck

Note: I may not have disabled R6 Render Standby
 
The following new settings (page 32) will cause my Asus Strix 5700XT to be capped at 44MH. Reverting the changes produces a normal 56MH based on my overclocks / etc.

GFXOFF: Uncheck
ACDC: Uncheck

Note: I may not have disabled R6 Render Standby
I believe it is the ACDC (Activate Core Dual Computing), please could you verify this, it is really important to check if this will allow the 5600 XT hashrate to achieve more than 50 MH/s and 5500 XT to achieve more hashrate as well.
 
Zuletzt bearbeitet :
Oben Unten