After several hours 3.1 borks - all miners "fail" to start. after reboot it all works again
Any cure?
8 nvidia cards on H110btc+, all running at 75% power target. no overclock :/
I have the same issue but not with "all" miners. It's just some miners failing. I don't know if it's always the same miner but DSTM (for zcash) was surely one that failed to start after hours of mining.
By the way I have made my "HashRate" files inside the "Stats" folder read-only. Sometimes I run two instances of the miner for two different groups of cards, but if I don't have the files in read-only weird things happen when for example there are two instances of CCminers running.
I would highly advise you to use two copies of NemosMiner in two different base directories if you're trying to run them simultaneously (i.e. C:\NemosMiner and C:\NemosMiner2). You'll run into all sorts of weirdness otherwise, with conflicting config files, pool stats, miner stats. Given you likely want to tune the miners to the distinct groups of cards (assuming they are different hardware), this would allow you more flexibility.
Hello,
I have problems running two nemosminer instances at the same time. I have H110btc+ 10 1080ti gpus. I try to run 5 gpus on c disk and 5 on d disk to mine eth, but the latest nemosminer just cancels the last one and only one continues running. Also, when I try to run 1,2,3,4,5 gpus on one nemosminer and 6,7,8,9,10 gpu on another one, still both miners run the same 1,2,3,4,5 gpus. Seems like i can configure only one miner. Maybe you have any ideas ?
here is how I solved similar problem:
Do not configure via Nemos GUI
open files in \Miners folder and look for the line where GPU selection is passed
" -d $SelGPUCC ......"
replace it everywhere with explicitly listed GPUs to use. Say you want GPUs 0 to 3 from 1 instance and 4 to 7 on another
Then in In1 you put
" -d 0,1,2,3 ...."
in In2
" -d 4,5,6,7...."
Some miners use different list ( " -d 0 1 2 3" or "-di 0123")
Claymore's GPU ids may be different ... you have to check all used miners and replace " -d $SelGPUCC " with correct "hard" values
GL
