Ethash-LowMemory Getting Lot of Rejected Shares

I'm getting a lot of rejected shares using E3 on Ethash-LowMemory algorithm yesterday and today. Most seem to be being rejected.

Seems ok now. I rebooted my miner and specified which algorithm to use in the pass field instead of leaving it x. See if that resolves it.

Thanks for everything.

I've been getting a lot of suboptimal shares on ethash the past 3 days.

sonicrules wrote: I've been getting a lot of suboptimal shares on ethash the past 3 days.

What is your username?

It isn't possible to receive suboptimal shares on ethash because a suboptimal share means that a merge-mined coin is stale. With no merge-mining on ethash, we need to examine your account to determine the cause of this system bug.

Steve Sokolowski wrote:

sonicrules wrote: I've been getting a lot of suboptimal shares on ethash the past 3 days.

What is your username?

It isn't possible to receive suboptimal shares on ethash because a suboptimal share means that a merge-mined coin is stale. With no merge-mining on ethash, we need to examine your account to determine the cause of this system bug.

It's sonicrules, same as here on the forums.

Seems to be happening again. I'll keep monitoring. Not sure why it says miner is using incorrect algorithm.

My username is also the same..

'Algorithm Ethash-LowMemory
Coin Mined Nekonium
Block Number 6117713
Target Difficulty 1.000
Submitted Difficulty
Status Rejected (Miner is using an incorrect algorithm.)
Submission Time 5/14/21, 10:01 PM'

'Consider using the l=[RAM in GB] password argument to specify the miner's memory limit. Proswitching will only assign coins requiring a DAG that can fit in the l= memory limit'

How would I include that? For example if my pass were i=e3 or a=ethash-lowmemory? Not quite sure what I should set the pass as. Still getting a ton of rejected shares.

OK, I set pass as just l=4 for now. Will monitor. Sry for confusion.

Still having issue. Seems if I reboot the miner itll start getting shares and finding blocks without any rejections and then after some time shares will start being rejected. Not sure what the cause is. I've tried several variations of variables in my pass field.

romes wrote: Still having issue. Seems if I reboot the miner itll start getting shares and finding blocks without any rejections and then after some time shares will start being rejected. Not sure what the cause is. I've tried several variations of variables in my pass field.

This error implies that your miner isn't responding to the latest work being sent to it. It would still be mining an old job, which the mining servers need to reject because there is no money the pool can make by trying to find old blocks.

Unfortunately, I don't know how to resolve the issue, but I thought this information might be of some help.