When you say very many times, is it more than 3?
I recently changed benchmarking system to try to run algorithm for 3 switches before disabling. (Setting stat to 0). If is running longer than that, it may be a bug. I can test and address for next release, but this would be first report.
However, if you set the argument -No_Algo sib,keccak it should skip them.
Your oc seems fine, at least for a gtx 10 series. If you want to try to mine them, then adjust the intensity as I noted below. If not, then us -No_Algo and turn them off.
Let me know about the bechmarking, if its not stopping after third time of building database, or any other issues you may have.
-Timeout 1 -Benchmark 60 -Delay 1 -RigName1 4x1063 -StatsInterval 1 -Currency USD -CoinExchange BTC -PasswordCurrency1 BTC -Interval 60 -Location EUROPE -Auto_Algo Yes -Auto_Coin Yes -PoolName zergpool_algo,zergpool_coin -Type NVIDIA1 -Wallet1 1MbWiKvsBuCvMBTMRSHeeFZTtTUQXTDeza -ZergpoolWallet1 1MbWiKvsBuCvMBTMRSHeeFZTtTUQXTDeza -Zergpoolpassword1 BTC -CCDevices1 '0,1,2,3' EWBFDevices1 '0 1 2 3' DSTMDevices1 '0 1 2 3' -Donate 5
My config
I will look into what may be going wrong there to prevent you from benchmarking.
Do you actually see MM.Hash state in green that the name of the miner is running. Or is it an empty window with just a timer countdown?
If you add -No_Algo sib,keccack to your arguments, does it try to benchmark something else?
Look at the photos on github, and make sure arguments are in right location. I've had people set up miner wrong.
Regardless, ot should set the algos to zero and move on after a few switches. I will look into that.
Thank you. I will wait for news about the verification.