Topic: Any word on amd vega hash rates? - page 117. (Read 202748 times)

I have 2 vegas+5nvidia in the rig - no problem )) Will get third vega in this rig soon ))

@rednoW

Thanks for the info , didnt really help though.

1. Set you Virtual memory size to 64gb ... >>> done
2. Use blockchain 23Aug drivers...  >>>yep
3. Move HBCC slider to some new position or just switch it off / on depending on your current setting. Hit apply >>> All @ 170040mb
4. Set your HBM2 mem speed to 1100 ?!??!?!?

Its a vega 56 not 64 as i understand 56 has lower clocks (but better timings ? @ 920).... anything over 950 result in a crash
920 seems stable, 950 stability depends on STAK settings

(did the -30 speed / 950 mem / -20 power setting)

5. Run xmr-stak-amd with 2 threads and intensities 2016 and 1800. Maybe decrease intensity for monitor attached card.

2016 / 1600 works ... 1800 crashes...  had it upto 800 once now it's between 600 and 700 no matter what i try it wont go higher

6. (optional) Apply reg patch if you want to lower power consumption. For monitor attached card you will need much higher voltage.
Is the reg patch also working for vega56 (thought is is for 64) but first need to try to get things stable i guess...

P.S. Don't use GPU-Z. For monitoring use latest HWINFO64 with GPU I2C support disabled in settings >>> ok , thanks Both seem to work though

anyone have a trick to disable/enable hbcc quickly? i not have the slidder, system have only 4gb of memory

Verified once again that adding any AMD series R9 or RX card as the 5th disables HBCC so that 3/4 Vegas hash correctly. Changing PCI-E slots multiple times did not fix the issue making me think it's not due to PCI-E slot differences.

I'll try a test with Nvidia cards to see if it's an issue with the AMD cards populating and "taking up room" in Wattman thats causing the bug.

Exact same issue regarding how Wattman reacts.

4/6 cards when I modify the HBCC slider at all and hit apply cause the screen to flicker a bit, Wattman closes, you can hear the card "re init" as its fan spins up for a second then comes back to normal.

2/6 cards when I modify HBCC Wattman just closes.  Nothing else happens.

Thank you very much!
I will try to run two separate instances, one with vegas and the other with the 500's.
Only problem I anticipate is how to identify the numbers of the gpu's on xmr-stak and associate it to the corresponding card.

Is there any output file which one can generate to get some insight on how the numbering is decided?
Does it correlate to the registry numbers (0001, 0002,...) or more to the wattman order...things get crowded with multi gpu rigs!

Hellms Hellae's tweak ... FTFY Hellms tweak is the soft power tables on Regedit, a complete different thing.

About 2xV56 + 2xV64, I saw someone on reddit at /r/moneromining able to run them.

This is not an answer to your question, but more an advise to when you finally manage to have all cards working:
Do not run Vega's and 500s on the same stak instance. The variable difficulty of the pool will be increased by a lot with the Vega's and the 500s will strugle to submit valid, non expired shares.

Still haven't switched over to xmr yet so I guess I will phrase this as a question. While I haven't played with blockchain drivers in a while I assume its the same as 17.9.x where setting mem volt either in wattman or softtable doesn't change mem voltages but does effectively set a floor for core voltage? This is either a bug in 17.9.x or just how wattman/the card is.

I've always moved mem volts in p3 to at/the same as my undervolt (0.9mv) on the core to ensure it sets effectively.

Has someone succesfully tried to get 2x vegas 56, 2x vegas 64 working together with 2x rx570 + 2x rx580 on the same rig for mining XMR?

I am able to use the xmr-stak-amd miner and recognize all 8 GPUs. But when I try to use Hellms tweak of double threading the vegas (page 26), the Hash doesnt go up and Im stuck at ~ 750 H/s fo revery card, regardless of vega or rx580/570 and also without any effect on the intensities i put (2016/1600, 1000 or any combination).

I have blockchain drivers and win 10.

Thank you guys!

It's not possible to set the memory voltage, and neither additional tweaks can be tried.
Also, one can't adapt the table to a Vega 56 editor.

well, I had to hard shut down, after start it was just not working anymore. I had to reinstall drivers to make it work again. Updated to the new version 5.58 I think, you think now its safe to try again?
What exactly are you starting also, there are some ticks for the sensors. This sh.. is so messed up, that I am already scared to touch anything outside the console.

I had this issue with fans to the max. You need just turn off GPU I2C - on the first small startup window click setting and disable it. It is on the 3 tab afaik.

If you've already catch this wildfan bug just power off the system totally (not just reboot) and start it again ))

rednow - HWInfo 64 broke my whole system with miner not working. I could not even go to the settings to disable that GPU I2C, when I ran it - one of the cards fan started spinning wild, the system crashed and did not want to start windows normally anymore.

So ... be careful with it

Is there anyone who actually has 6x Vega 64 running with proper settings and proper speed?

Rod1970

1. Set you Virtual memory size to 64gb
2. Use blockchain 23Aug drivers
3. Move HBCC slider to some new position or just switch it off / on depending on your current setting. Hit apply
4. Set your HBM2 mem speed to 1100
5. Run xmr-stak-amd with 2 threads and intensities 2016 and 1800. Maybe decrease intensity for monitor attached card.
6. (optional) Apply reg patch if you want to lower power consumption. For monitor attached card you will need much higher voltage.

P.S. Don't use GPU-Z. For monitoring use latest HWINFO64 with GPU I2C support disabled in settings

Hi all, newbie in town ! Wonderfull thread btw..

Just build custom EK loop :

threadripper 1920 (with ek tr4 block)
4 x vega 56 (4 x ek nickel block)
samsung pro evo 512 m2 ssd (3200r / 1800w)
gskill 4x8gb 3200 cl 14-14-14-34
Corsair  1200i PSU
480 monsta rad
EK revo d5 xtop dual pump

POIDH : http://i68.tinypic.com/w7oaar.jpg

Max temp is @max 48 degree @ full load... (1000 watts) (normally around 45 water temp / 22 ambient )

Threadripper working with stak cpu at ~950 hashes
Did get the vega's once hashing at ~ 800+800 per card but messed up settings i guess (too many crashes)
now doing only ~200+200 per card ;(

Q.
I have for each card a HBBC slider ranging from about 11000 to 24000.
The HBBC is per card right ?
So 4 cards is minimal 1100 x 4 = 44 GB of ram ?

Q.
One card has monitor attached , it Always seems to be unstable (need lower settings or whatever) , same on my r9 rig i had.
Does disabeling Aero etc. help ?

btw, i see people with loops and ek blocks showing temp diff > 10 degree between hbm and core...
mine is only 1 degree off between the two !
FYI : I did use the Original four legged springy rhingy clamp from the air cooler (just use two plastic washers to keep them higher off the pcb so they dont touch the board. Improved pressure and core contact with waterblock

Q.
GPU z says 4 gb vram in use ?!? (with two thread setting 1012+1012) ?

How much MB do you see next to the HBCC slider with your setup? Try changing to more VRam than 64 if u have larger SSD.
I notice, that when I enable the HBCC, the system thinks for a second before closing the AMD Settings, and their fans change speed for a second, so it actually hear that this is being applied. On the other two , the settings just insta close.

Actually not.
I just made sure that none of the hex table can be altered manually to avoid misconfiguration.

Check column AC.
Lines 7-14: Core voltage for all states
Lines 16-23: GPU Clock for all states
Line 25: MEM Clock

These can freely configured. Allowed values range from 500-2000.
Enter your desired values, run reg creation and save file if you want to

Same with 4 cards only working with HBCC.  The other 2 do not listen to their HBCC settings.  See https://bitcointalksearch.org/topic/vega-64-cannot-enable-hbcc-on-26-cards-in-rig-after-reboot-2201970 for as much details as I can provide.

The worst is that 2 cards also ignore Soft Power Table settings in the registry.  Also a major clue I am sure as to why this is happening.

FYI it seems you need 8GB Virtual Mem per card.  My rig only has 8GB of RAM but I tried with 16 and 32 and it did not change anything regarding the HBCC issue on more than 4 GPU.

A major clue recently was that plugging in a dummy hdmi connector to one of the problematic cards while running xmr-stak-amd miner caused the hash rate to spike up for ~10s before it dropped back down.


I have yet to do a clean install of Windows as I would like to confirm why this is happening first so I can save others the trouble.  If I clean install Windows and it works then I lost my chance to debug it.

With that said I plan a methodical re-install of Windows to hopefully fix it.

55GB Virtual Mem because I'm restricted on the SSD for room and 16GB of physical DDR3 RAM

uh oh.
Whats your virtual memory and ram situation?