all your claims about your "fastest" private miners were beaten by Enemy. And Enemy is not the best Cuda coder )) Just imagine what speed private alexis miner has )) 

2 t3syncro

forget about ggs. it is buggy as hell. maybe some day some time but not now

Yes, it is rog strix

I'm running asus x370-f gaming with 7 gpus (2 on board, 4 on risers, 1 on riser and m2 adapter). There was a problem with 7 gpus with April bios but it is fixed with latest one now.

Asus prime x370-pro should be fine also. A friend of mine uses it but not with 7 cards yet

thanks for all and for this especially !

You are liar again.  enemy 1.09 v5 has no kernel improvements comparing to 1.09 v1 . Only stratum and devfee part was updated and some minor bug fixed. That gives additional boost.

In case of normal v7 vega with 16gb becomes compute bounded. Vega 8gb is memory size bounded with heavy.
It is just like with polaris 8gb and v7. You can set intensity to use all 8gb ram but due to lack of compute units it cannot handle it. But with heavy Polaris 8gb uses all its memory and has the same hashrate as with v7

Well. with all respect to Eliovp, OhGodAGirl and Wolf, all it seems like amd and nvidia are willing to give miners extra boost in threat of bitmain expansion

You'll better find the way to tweak mem timings for Vega.
For nvidia there is a solution already - OhGodETHEnlargement.

For polaris your program is a piece of ... well ... I just don't like it.
I tested it yesterday with my fresh computer with new rx570 8gb sapphire nitro+ micron memory. 18.3.4 drivers. Original bios.
First of all from the start your program screwed up my downvolt settings (made by overdriventool) and fired it up mining with huge voltage.
Than I tried to tweak (downvolt, timings) using your program only.
And it gets bsods "thread stuck in device driver" every try
I had no time to struggle with your buggy undocumented software. I've just flashed good timings, applied 850mv and went mining SUMO with 1khs@80watt with doctor's SRBminer ...

total bullshit ...

In my case with 2 gpu miners running (ccminer and srbminer) I got performance degradation running 8 threads instead of 6. Either cache got flooded with gpu-miners or not enough compute power of ryzen 1600 to get benefit. I think it is the second.

should double hash provide advantage for ryzen 1600? it has more than 2 mb L3 cache  per physical core

Cast xmr works better for vega and heavy. Srbminer is best for v7

I mean what is the reason to release 32-bit code ? It will be useful only for botnets or non-honest sysadmins to run on large old networks.
No miner uses win32 nowadays. Legacy cpus consume more than earn. Only if you steal computer power it will be profitable

speaking about 32 bit code for legacy cpus - are you hoping to get some fees from botnet runners? Isn't it bad? ))

1 hour of work is nothing due to probability nature ... Moreover, pool can assign different diff for your workers. So you'll have less shares but more "valuable" ones

ryzens g-series have only half of cache memory, amd was not able to fit gpu core and big cache on this die. So it will not be as good for cryptonight as classic ryzens are

OverdriveNtool is working like a charm with newest drivers.
Here is a screen of my Sapphire Pulse Vega56 with shitty hynix mem mining cryptonight-heavy @ 140watt

My PP tables won't help you as they are very specific for liquid bios and old blockchain drivers.
But it is easy to get the same result using latest 18.3.4 driver and softpowerplay mod with overdriventool (based on your own bios).
Just make it work with clocks and volts I posted above and don't forget about good cooling. You need to keep your temps low for HBM2 on such high clocks

No problem getting 2100k/s with vega64 and samsung mem

clocks are 1408/1140@875mv, rock stable.
first card is vega56 flashed to 64
And sorry 2 srb doctor, I'm greedy bastard sometimes ))