Hmm. I have no problems mining using that batch script. Could you do me a favor and check your claymore directory for files ending in *_log.txt that contain references to eth.poolmining.org and send the file(s) to info@poolmining.org? You don't have to edit out wallet information from the file since that's known to the pool anyway.

No. You don't. Let me check this.

Did you forget the "-esm 3" option by chance?

The only explanation for this would be the miner directing a massive amount of hashpower on the pool roughly a day ago.

Reward was in line with previous blocks. The 1.8039736 DASH you might be referring to, went to the DASH master nodes. If you inspect the previous blocks you will notice a similar pattern. Roughly 50% always goes to the master nodes.

@Crypto Journey: Did you address me or shawn?

I've implemented several enhancements regarding how the pool's vardiff algorithm responds to wild fluctuations of incoming hashpower as it the case with NiceHash and will test those changes using Nicehash today. I'll keep you posted.

Don't worry. The reason that your balance does not increase is not your hashrate. Your balance will updated the next time the pool finds a block. If your computed balance after finding the block equals or exceeds the minimum payout of 0.15 XMR it will be sent to your wallet immediately and reset to zero afterwards. If your balances does not yet meet the minimum payout threshold it will displayed so that you know how much is left until the next payout to your wallet. The process is described in more detail here: https://poolmining.org/faq

Let me know if you have further questions.

Balances are rounded to three decimal places for display only. Internally they are stored with eight decimal places.

A whole sentence would be helpful :-)