https://www.newegg.com/Product/Product.aspx?Item=N82E16814202300&cm_re=vega_64-_-14-202-300-_-Product

$619

Nothing special really basically the settings discussed in this and other threads. Core freq: -30%, Mem freq: 920mhz, Core/Mem voltage: Auto, Power level: -20%, Minimum fan speed: 2500rpm. HBCC on at 16080GB RAM. Blockchain driver. Running xmr-stak-amd with 8 threads (2/board) and gpu_threads_conf like this:
{ "index" : 0, "intensity" : 2016, "worksize" : 8, "affine_to_cpu" : false },
{ "index" : 0, "intensity" : 1600, "worksize" : 8, "affine_to_cpu" : false },

These settings on 3 boards was basically set it and forget it. With the fourth board it crashed after a few hours. Lowered mem freq down to 900 and it lasted longer but eventually crashed. My current theory is the new board just can't take the RAM overclock. Running at 890 now for about 8 hours. If it makes it through tomorrow hopefully I'll have my answer and it has nothing to do with 4 boards but rather the fourth board just can't overclock as far. These boards are great miners but definitely not as easy to work with as the 1070s.

Got back around to messing with softpowerplaytable.

Running 3 64's around 1950ish a card right now. I need to bring down the power a bit. I'm currently at 155w per car at the wall.

How low are y'all running your core voltage? 900? 875?

I have 4 pcs of Vega 64 GPUs and I tried to use Oldcomer version of softpowerplaytable mod. Three of those Vegas worked well. I got about 1850 H/s per GPU, but one GPU has somekind of problem. If there is softpowerplay mod in windows register with that specific GPU, then I got blue screen with "THREAD STUCK IN DEVICE DRIVER" message at windows start up. On start up all other GPU initialized correct way with fast acceleration and decleration of blower. This problematic GPU blower accelerates and keep running on high speed till windows automatically restarts.

Everything worked well after I boot windows to safe mode and remove "PP_PhmSoftPowerPlayTable" instance from GPU 0004. I even try to change HBM clock rate from 1100 MHz to 1000 MHz and still get stuck with this one GPU.

I'm using integrated intel GPU for monitor. This is 0000 instance in [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\

0001 - 0004 are vega 64 GPUs.

I got about 7200 H/s with three vegas undervolted and this problematic one with stock voltage and clock settings.

Same problem with 2xVega 64. Let's try to boot from Intel GPU like davith75 suggested

I have a single Vega 64 that had the same issues. I ended up using the xslm spreadsheet that was posted a few pages back to create a series of custom .reg files and everything seems to be working well now - albeit at 925mV. Happy to share the settings I used if you pm me (saves cluttering the thread). Standard disclaimer of use at your own risk applies though - I take on no responsibility for failures.

I have 1 pcs of Vega 64 GPU and I use only wattman without regedit,-30 gpu, 1000 mem and xmr-stak-amd with intensity 2016 + 1800. HBCC on at 12GB RAM + 30GB swap file. On the pool I see this:
https://i.imgur.com/kcBewjN.jpg
Does anyone have something like that? Why is the hash rate unstable?

6x VEGA 64

Using https://github.com/halsafar/Vega64SoftPowerTableEditor
Modify registry:
- 1408mhz for P5,6,7.
- 1050mhz for mem
- 950 for core voltages

HBCC only works for 4/6 cards so I am short ~1000H.

Getting 10500H @ 1150W (total draw at the wall).

Total draw at the wall when idle is 250W.  

So that is ~150W per card.

Stable for 72 hours.  99% submission rate on nano pool.  My average on the pool is expected, 10500.

This is huge given if I try the same setup using stock settings the total draw is ~2000W.

The 64 bios has higher voltage limits and on the HBM memory its most useful.   HBM isnt using large amounts of power in any case, its like 10w difference
Theres a theory that the 56 actually overclocks and runs at high end better then the 64, maybe because it has less shaders.    That would be ironic, I guess mining is not using those extra shaders I dont know.  Its mostly about memory bandwidth I read.

With your setting of the power limit.  You want to lower the volts on left and right, lower the power limit yes but not long after you raise the power limit back up and this enables the best performance and you should retain the lowest voltage usage in any case.  It may wobble back and forth a bit, 120 to 140 watts I see but mostly its just showing a reading of 130w.   Some people no doubt have got lower power usage then that even, there is a correct sequence to get the best results though.  If driver crashes, log out and start over again as it wont run as well in my experience