Not your fault Dok, it's not the miner, it's more a driver thing. Thanks for your patience, I'm sure the complaints get old after a while.
And double thanks for your continued development on what I believe is the best cryptonight miner around!

To those w/ FEs:

driver: win10-64bit-radeon-pro-software-enterprise-18.q3.1-oct1

But a couple of tricks you have to use to pull it off:

1. go into global settings and turn off HBCC memory.
2. if using SRBMiner, you have to have --enableduplicategpuid in the bat file, and then double up the threads in the config file for V8. I'm using 124 for intensity and 16 for worksize.

FE still the king, hashing V8 @ ~2125 H/s

one other thing: use the precompiled kernel that comes with SRBMiner, do not compile the kernel with the new drivers.

monero v8 made some instability to my vega rig so i lovered intensity from 120 to 100. Little less hasharate, but it is stable for few days.
12800 h/s on 7x vega 56 rig
1100w
1800-1850 hs on per card.

You need to start miner with intensity 60, let it work for a few minutes , then start it with intensity 56. This should get you over 1500+ easily.
Some call this foreplay.
And of course use v1.6.4

1. powerplay table : https://files.fm/u/s68u78zx
Overdrivent: GPU 1450/925mV , MEM 950/910mV

Im not looking to get the max hash from the card, just set a value that is stable and works for my miner development.

2. Same settings, as im only using it for testing the miner

in your config.txt file make sure you have something like this:

of course you can change the rig name and port number.

from another workstation in your LAN you use the IP address of your rig followed by the port, so something like this:


where 192.168.1.100 is the address of your miner.

If you want to access from the internet you may have to open up the port 4444 on your router.