Show Posts
sure. But two of three rigs just hangs at this same moment (Rx 470 & Rx 480), it happens when ETC touch epoch 280. Below is my config.txt content (they nearly just the same on both machines)
Try "-eres 0".
hoooooly ff**. You are right! I've checked my config line by line and found that there were "-eres 20" option between my #comment lines at the very bottom of the file. I was sure, that at the bottom are only #comments lines with my tests, thoughts etc (mean et cetera, not ethereum classic
) so I did not paste them. After deleting "-eres 20" my miners can mine ETC again (AFAIR eres=2 by default). So it means miner tried to work with DAG epoch 280 + 20 = 300, and that is why it crashedTHANK YOU!
Looks like it's not enough memory to set DAG #280... Do you have enough virtual memory (page file) size?
And another one thing. You use -allcoins 1. This is what Claymore writes in readme:
-allcoins Specify "-allcoins 1" to be able to mine Ethereum forks, in this mode miner will use some default pools for devfee Ethereum mining.
Note that if devfee mining pools will stop, entire mining will be stopped too.
Miner has to use two DAGs in this mode - one for Ethereum and one for Ethereum fork, it can cause crashes because DAGs have different sizes.
Therefore for this mode it is recommended to specify current Ethereum epoch (or a bit larger value),
for example, "-allcoins 47" means that miner will expect DAG size for epoch #47 and will allocate appropriate GPU buffer at starting, instead of reallocating bigger GPU buffer (may crash) when it starts devfee mining.
Another option is to specify "-allcoins -1", in this mode miner will start devfee round immediately after start and therefore will get current epoch for Ethereum, after that it will be able to mine Ethereum fork.
If you mine ETC on some pool that does not accept wallet address but requires Username.Worker instead, the best way is to specify "-allcoins etc", in this mode devfee mining will be on ETC pools and DAG won't be recreated at all.
Try to set "-allcoins etc"
And another one thing. You use -allcoins 1. This is what Claymore writes in readme:
-allcoins Specify "-allcoins 1" to be able to mine Ethereum forks, in this mode miner will use some default pools for devfee Ethereum mining.
Note that if devfee mining pools will stop, entire mining will be stopped too.
Miner has to use two DAGs in this mode - one for Ethereum and one for Ethereum fork, it can cause crashes because DAGs have different sizes.
Therefore for this mode it is recommended to specify current Ethereum epoch (or a bit larger value),
for example, "-allcoins 47" means that miner will expect DAG size for epoch #47 and will allocate appropriate GPU buffer at starting, instead of reallocating bigger GPU buffer (may crash) when it starts devfee mining.
Another option is to specify "-allcoins -1", in this mode miner will start devfee round immediately after start and therefore will get current epoch for Ethereum, after that it will be able to mine Ethereum fork.
If you mine ETC on some pool that does not accept wallet address but requires Username.Worker instead, the best way is to specify "-allcoins etc", in this mode devfee mining will be on ETC pools and DAG won't be recreated at all.
Try to set "-allcoins etc"
thanx for response. I tried increase virtual memory before (set it even to 45000MB) and this did not help.
"-allcoins etc" could be solution but miner did not stay alive long enough to change dag epoch because of devfee, so probably this wouldn't help.
Anyway Claymore hit the bull's eye
