Any word on amd vega hash rates?

[Yerba]

I followed hellaes instructions. Step by step. Vega 56 without flashing to vega 64.
Every time I turn off miner or restart it - all settings are gone and hashrate is again 600-600. I DDU drivers, reinstalled all again and it mines nicely around 1000 and 850 hash per card. Until restart..
What could be wrong?

It seems that driver crashes on miner exit. Maybe memory clocked to high or voltage is to low for you card

Tried with HBM memory 900 also and power limit -20. Still same case..
Or gigabyte cards are worst?

[BHTeam]

You can check the Equihash mining speed of Vega on https://www.crypto-coinz.net/ in the calculator.

[esson]

Hello guys, I've just ordered 12 x RX Vega 56 8GB HBM2 and a Biostar TB250 BTC pro for 12 X GPU's and I've got some questions..which OS should I use? Windows or Linux? Can I enable/disable HBCC for all or just for 4? Thanks

[Yerba]

Well, drivers doesnt crash anymore. Wattman settings are ok. But still problems with HBCC slider. After every restart hashrate is lower until I turn off slider, turn on and push slider to the max.
Why so..

[m_sin]

Unfortunately vega sovsemy crude product. I bought 2 pieces. Installed launched. The first broke in 30 minutes. The second one when I tried to surrender both to the store. It broke directly in their service on the test of performance.

[rednoW]

Well, drivers doesnt crash anymore. Wattman settings are ok. But still problems with HBCC slider. After every restart hashrate is lower until I turn off slider, turn on and push slider to the max.
Why so..

yes, it is current common behavior. You need to reapply HBCC settings after every reboot. But then it works stable. I have my vegas running 1900+h/s each more then 3 days already. If you have speed loss - look for the reasons - bad cooling, power save windows options or some programs that halt HBCC (gpu-z or nvidia scheduled tasks)

[rednoW]

Unfortunately vega sovsemy crude product. I bought 2 pieces. Installed launched. The first broke in 30 minutes. The second one when I tried to surrender both to the store. It broke directly in their service on the test of performance.

please don't post direct google translation without editing. Very difficult to understand.
There are a lot of people with Vega around - and there are some problems with drivers, settings, but I didn't know about any card death with proper installation.
You and your servicemen seem to do something wrong to kill cards.

[Yerba]

Well, drivers doesnt crash anymore. Wattman settings are ok. But still problems with HBCC slider. After every restart hashrate is lower until I turn off slider, turn on and push slider to the max.
Why so..

yes, it is current common behavior. You need to reapply HBCC settings after every reboot. But then it works stable. I have my vegas running 1900+h/s each more then 3 days already. If you have speed loss - look for the reasons - bad cooling, power save windows options or some programs that halt HBCC (gpu-z or nvidia scheduled tasks)

Ok, thank You for explanation - if HBCC behaves so by default then I must accept it.
Cooling is pretty ok in server room - cards are 53 degrees Celsius and fans 3000 rpm. Power saving is turned off, no GPU-z or nvidia..
Well, lets hope that one day HBCC will behave more nicely.

[spectune]

Got it now for Vega 56 - W10 installed, just use the Monero hints posted on reddit (Monero and Vega - the definitive guide), use Bios from Vega 64, AMD blockchain driver, use DDU before, if any driver was installed, after blockchain driver installation set in Wattman all voltages to manual, import the Vega_64_Reg_GPU_0000-1050HBM.reg (powerplay pre-settings), with OverdriveNT - adjust P7 1060 /865mV and mem P3 1090 / 875mV.
Got a stable hashrate of about 42,5 Mh/s on ETH with Claymore 9.8 with 230 Watt at the wall. Think that is the maximum actually....sadly not the 80...90 Mh/s as posted in any fake posts

[rednoW]

Got it now for Vega 56 - W10 installed, just use the Monero hints posted on reddit (Monero and Vega - the definitive guide), use Bios from Vega 64, AMD blockchain driver, use DDU before, if any driver was installed, after blockchain driver installation set in Wattman all voltages to manual, import the Vega_64_Reg_GPU_0000-1050HBM.reg, with OverdriveNT - adjust P7 1060 /865mV and mem P3 1090 / 875mV.
Got a stable hashrate of about 42,5 Mh/s on ETH with Claymore 9.8 with 230 Watt at the wall. Think that is the maximum actually....sadly not the 80...90 Mh/s as posted in any fake posts

use Claymore 10 with vega asm kernel to get 44.2 ))
And you need 1222/1100@820mV to be in 150watt range

[spectune]

Got it now for Vega 56 - W10 installed, just use the Monero hints posted on reddit (Monero and Vega - the definitive guide), use Bios from Vega 64, AMD blockchain driver, use DDU before, if any driver was installed, after blockchain driver installation set in Wattman all voltages to manual, import the Vega_64_Reg_GPU_0000-1050HBM.reg, with OverdriveNT - adjust P7 1060 /865mV and mem P3 1090 / 875mV.
Got a stable hashrate of about 42,5 Mh/s on ETH with Claymore 9.8 with 230 Watt at the wall. Think that is the maximum actually....sadly not the 80...90 Mh/s as posted in any fake posts

use Claymore 10 with vega asm kernel to get 44.2 ))
And you need 1222/1100@820mV to be in 150watt range

thanks - good hint - will try it !

[Truthchanter]

Got it now for Vega 56 - W10 installed, just use the Monero hints posted on reddit (Monero and Vega - the definitive guide), use Bios from Vega 64, AMD blockchain driver, use DDU before, if any driver was installed, after blockchain driver installation set in Wattman all voltages to manual, import the Vega_64_Reg_GPU_0000-1050HBM.reg, with OverdriveNT - adjust P7 1060 /865mV and mem P3 1090 / 875mV.
Got a stable hashrate of about 42,5 Mh/s on ETH with Claymore 9.8 with 230 Watt at the wall. Think that is the maximum actually....sadly not the 80...90 Mh/s as posted in any fake posts

use Claymore 10 with vega asm kernel to get 44.2 ))
And you need 1222/1100@820mV to be in 150watt range

Does 44mhs eth need hbcc on? if so, what is hashrate with it off?

[jmumich]

Any thoughts why my hashrate is dropping?

Either HBCC is turning off somehow (some other program or task starting?) or your fans aren't high enough (put em around at least 3000) to keep the HBM mem cool enough to sustain the high hashrate

I've had the same problem - I don't think it's HBCC, becasue I can restart the miner without touching HBCC and speeds are back to normal. That made me think it was temp - but even with fans over 4000rpm in a cool room it would still happen.

I tried both using the iGPU, as others have suggested, and going into Control Panel - System - Advanced System Settings - Performance Settings, and then switching to adjust for best performance (Disabling all the windows animations). That worked for me.

[STT]

HBCC does help some, whether it adds to a maximum figure could vary.   If you are close to the limit, things like a web pages gif or pictures even might cause a driver reset so the mention above with best performance mode is correct I think.  I always switch to that anyway, its my default but I do think it has some effect in processing unlikely as that might seem with an unused machine.

There is various extraneous services that windows doesnt need and can be shut down, Ive yet to find any that would noticeably alter hash rate for now.

[rednoW]

Got it now for Vega 56 - W10 installed, just use the Monero hints posted on reddit (Monero and Vega - the definitive guide), use Bios from Vega 64, AMD blockchain driver, use DDU before, if any driver was installed, after blockchain driver installation set in Wattman all voltages to manual, import the Vega_64_Reg_GPU_0000-1050HBM.reg, with OverdriveNT - adjust P7 1060 /865mV and mem P3 1090 / 875mV.
Got a stable hashrate of about 42,5 Mh/s on ETH with Claymore 9.8 with 230 Watt at the wall. Think that is the maximum actually....sadly not the 80...90 Mh/s as posted in any fake posts

use Claymore 10 with vega asm kernel to get 44.2 ))
And you need 1222/1100@820mV to be in 150watt range

Does 44mhs eth need hbcc on? if so, what is hashrate with it off?

no, eth mining with claymore 10 doesn't depend on HBCC

[spectune]

Got it now for Vega 56 - W10 installed, just use the Monero hints posted on reddit (Monero and Vega - the definitive guide), use Bios from Vega 64, AMD blockchain driver, use DDU before, if any driver was installed, after blockchain driver installation set in Wattman all voltages to manual, import the Vega_64_Reg_GPU_0000-1050HBM.reg, with OverdriveNT - adjust P7 1060 /865mV and mem P3 1090 / 875mV.
Got a stable hashrate of about 42,5 Mh/s on ETH with Claymore 9.8 with 230 Watt at the wall. Think that is the maximum actually....sadly not the 80...90 Mh/s as posted in any fake posts

use Claymore 10 with vega asm kernel to get 44.2 ))
And you need 1222/1100@820mV to be in 150watt range

Does 44mhs eth need hbcc on? if so, what is hashrate with it off?

no, eth mining with claymore 10 doesn't depend on HBCC

Short correction to the hashrate - I have 43,5 Mh/s ! with these settings ..... not 42,5 Mh/s , sorry for the typing error....but even better :-)

[spectune]

Got it now for Vega 56 - W10 installed, just use the Monero hints posted on reddit (Monero and Vega - the definitive guide), use Bios from Vega 64, AMD blockchain driver, use DDU before, if any driver was installed, after blockchain driver installation set in Wattman all voltages to manual, import the Vega_64_Reg_GPU_0000-1050HBM.reg, with OverdriveNT - adjust P7 1060 /865mV and mem P3 1090 / 875mV.
Got a stable hashrate of about 42,5 Mh/s on ETH with Claymore 9.8 with 230 Watt at the wall. Think that is the maximum actually....sadly not the 80...90 Mh/s as posted in any fake posts

use Claymore 10 with vega asm kernel to get 44.2 ))
And you need 1222/1100@820mV to be in 150watt range

thanks - good hint - will try it !

With Claymore 10 and asm I get 43.8 - quite close to 44.2 - good job so far, thanks.

[tarui]

by chance I saw the reddit link and guide so I tried it out and my results are a little different. I used the "1100MHz HBM @ 905mV" reg file and this is what I got.



https://www.youtube.com/watch?v=8Uq3Om2MXOE

notice the voltages for the core and memory are different from the youtube video by oldcomer?


so far, the highest hashrate for eth is about 43mh/s but my lcd is connected to this card with other software running as well. so this might have impacted performance.
hwinfo shows gpu core using 68w, mem 21w
I manually changed the p7 core clock to 1221mhz in wattman

[frostedace]

Whenever I try to use the blockchain drivers, my screen pixelates grey and then crashes. I've reinstalled the drives with ddu but still get the same end result. The regular drivers work fine though. Any thoughts?

I have same issue. Do you have integrated gpu on your motherboard? If you have, uninstall drivers with DDU, reboot, set igpu to first in bios. Plug your monitor to igpu. Install driver again and try Hellae instructions.
I got 1850 h/s with sapphire vega 56

Can't believe I never tried activating internal graphics. Thanks for the tip, works perfectly now.

[spectune]

by chance I saw the reddit link and guide so I tried it out and my results are a little different. I used the "1100MHz HBM @ 905mV" reg file and this is what I got.

https://i.imgur.com/Yjmb9G0.jpg?1

https://www.youtube.com/watch?v=8Uq3Om2MXOE

notice the voltages for the core and memory are different from the youtube video by oldcomer?


so far, the highest hashrate for eth is about 43mh/s but my lcd is connected to this card with other software running as well. so this might have impacted performance.
hwinfo shows gpu core using 68w, mem 21w
I manually changed the p7 core clock to 1221mhz in wattman

Could be a reason if you run any other software. Not sure that hwinfo shows the right information about, use any Watt meter device at your power cord is better. One important hint - use the OverdriveNTool version 0.2.1 beta - it has direct access(press right mouse button at the tool) to the powerplay area in the registry, so you can adjust some values directly(after that reboot the settings are active) - you must start this tool with admin rights to get access to the registry. Have fun.