So far so good, just switched some of my cards to ZEC and this was the miner I was advised to use and here I am.
I have several questions I would to get answers to and find solutions.
I'm running 8xGigabyte 1080s on one rig and they are working like a charm, no specific config, nothing, except OC, all cards running about 565-575 Sol/s - mems 120/600. Uptime 16 days.
Second one is with 8x EVGA FTW 1080s, first try was 125/680 which was working fine for more then 12 hours, then I got "Looks like GPU0 are stopped. Restart attempt." after what I lowered the mems on same as Gigabyte 120/600, but I constantly getting the same error.
So the question is next: (I will solve the OC problem with EVGA but if you have any suggestions I'd be glad to hear that) how can I configure the miner that if it stops hashing to restart itself?
With Claymore's miner I'm using script which force stops the terminal itself and launches it again, but in case of Claymore I have a triger to run the bat file to do this (in case anyone interested here's the script)
@echo off
call :sub >log-%DATE:~-4%-%DATE:~4,2%-%DATE:~7,2%_%time:~0,2%%time:~3,2%%time:~6,2%.txt
exitb
:sub
echo. #############################################
echo. %time% Check if old miner process exists and kill it
taskkillfim EthDcrMiner64.exe
echo. %time% Starting new Miner process one...
startd "E:\Claymore's Miner" start.bat
echo. %time% Done!
timeout 5 >nul
exit 0
So, is there any solution with EWBF miner to make it more autonomous?
The next and less important for now question is how can I combine different rigs in one monitoring also like in Claymore's monitoring? For ether 100+ rigs are monitored with one monitoring instance and emailing and sms monitoring gives me ability to quickly respond if something happens, how is this possible in EWBF case?
