I'm having a bit of problem here. As you all know, Cryptonight V7 is more profitable than v6 after the monero hardfork, I started trying to mine with this algo in Nicehash.But I got an error. The Nicehash Legacy was showing 0 H/s in total (GPU+CPU) & XMR showed 0 H/s in only gpu but mining with CPU.so I reinstalled Nicehash Legacy. But this time the GPU can not be benchmarked. Though it had abnormal spikes in GPU usage.Then I used SRBminer-CN. It also had 0 H/s after a few minutes & the same identical spike i had when benching XMR stak in Nicehash.Then I switched to XMR stak (non NH). But no luck. It mines, gets new jobs from pool but result accepted by pool is one or two .( I'm confused in this. Does it still mining or not. Because I don't get a penny if the result is not accepted by the pool.)At last I tried Claymore CryptoNote AMD GPU Miner v11.3. This one mines pretty good but the total share is 0.enter image description hereSo I'm not so sure about this one that is this still mining or not..Hopes somebody can help me out.Thank you all. The problem isn't the miners... it's nicehash. I've tried reporting the problem to nicehash on thier bitcointalk page and even their facebook pages.
What's happening is that they are sending (cryptonight) instead of (cryptonightv7) on port 3363. it's easier to see when running cryptonightv7 on CastXMR because CastXMR reports whether you receive cryptonight or cryptonightv7.
When you receive a cryptonight (i.e. prefork), port 3363 will report a rejected share. it's looking for postfork cryptonightv7, not the prefork cryptonight. you would have the same result if you tried to mine sha256(i.e. bitcoin) on port 3363.. well.. you'd end up with 100% rejection instead.
Nicehashes 3363 port is sending cryptonight work to users mixed in with cryptonightv7 work to users, but only accepting completed cryptonightv7, while everything that isn't crytonightv7 is rejected.
your percentage of rejects is entirely dependent upon how many cryptonight they send mixed in with the cryptonightv7.
Cryptonight code is not the same as cryptonightv7 code and vice versa... the whole point of the fork was to invalidate the current available asics. the current available asics work on cryptonight, but not cryptonightv7.