Hi! I’m guessing you’re talking about CNv8? Awesome if we keep the questions for CNv8 in the separate ann thread in the future, but no worries this time:

Nicehash mining is a little problematic with CN. Calculating a round of hashes for CN takes > 1 sec. For other hash functions numbers in a few ms are more common. So, CN has a much higher probability of your hashes being stale when the gpu job completes. For e.g. direct xmr mining, with a long block time, pools are generally nice about accepting shares for both the current and the previous pool job, so it doesn’t matter much if you got a new job 0.5 secs before you found a share.

For nicehash, this isn’t true. They can throw you around between client orders every 5 secs and are generally more picky with stale shares. A better way to handle nicehash is to abort ongoing gpu work when a new job comes in and start on the new job instead. This means you will throw away precious time on the gpu instead though whenever a job switch occurs, so it’s not 100% sure you’ll be better off anyway.

We have abort support but have not enabled it yet. Bottom line is that nicehash is problematic, we support mining there but you will take a hit in your poolside hashrate compared to normal/direct coin mining.

Can't mine with vega

https://monosnap.com/file/pOVKePjpVNLA5QDfTMaKIirJNMv30y

If you have asus GTX 1070 no ti it can hit 3.9 mhs per card its insane i love it

Did you forget to specify the path to your .exe? Windows/your bat file doesn't magically know where your exe is.
Try adding this to the top of your .bat file if your .exe is in the same folder: