1.8.0.2 Simultaneously restarts all algorithms

[Spoob]

The version of Naisheesh 1.8.0.2. Often restarts algorithms, from minutes to 15 minutes, once saw work 1.5 hours. The main issue is not this. And in that even if the system works, and for example to close one of the windows of miners, the nicehash opens it again, then both windows are closed and opened again. Those. When you change the algorithm of one, nicehash restarts and the second one too, but why?

p/s: RX-s are constantly mining a dagger/decred 1080ti jump on different close algorithms. According to the schedule of loading of cards it is visible that usually they all are simultaneously closed and open anew without a visible reason

[Spoob]

[2017-07-28 23:38:56] [INFO] [MiningSession] Current Global profit: 10.59002333 USD/Day [2017-07-28 23:38:56] [INFO] [MiningSession] Current Global profit: IS PROFITABLE MinProfit mine always regardless of profit [2017-07-28 23:38:56] [INFO] [MiningSession] PrevStateProfit 0.00251449709626258, CurrentProfit 0.00382518451352121 [2017-07-28 23:38:56] [INFO] [MiningSession] Will SWITCH profit diff is 0.52125230894351, current threshold 0.05 [2017-07-28 23:38:56] [INFO] [ClaymoreDual-MINER_ID(416)-DEVICE_IDs(NOT_SET)] NEW MINER CREATED [2017-07-28 23:38:56] [INFO] [ewbf-MINER_ID(417)-DEVICE_IDs(NOT_SET)] NEW MINER CREATED [2017-07-28 23:38:56] [INFO] [ClaymoreDual-MINER_ID(415)-DEVICE_IDs(0,1,2)] [pid(8820)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Shutting down miner [2017-07-28 23:38:56] [INFO] [ClaymoreDual-MINER_ID(415)-DEVICE_IDs(0,1,2)] Trying to kill all miner processes for this instance: [2017-07-28 23:38:56] [INFO] [ClaymoreDual-MINER_ID(415)-DEVICE_IDs(0,1,2)] Nothing to kill [pid(7016)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)], exMsg Процесс с идентификатором 7016 не выполняется. [2017-07-28 23:38:56] [INFO] [ClaymoreDual-MINER_ID(415)-DEVICE_IDs(0,1,2)] Trying to kill [pid(8820)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] [2017-07-28 23:38:56] [INFO] [ClaymoreDual-MINER_ID(415)-DEVICE_IDs(0,1,2)] Exception killing [pid(8820)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)], exMsg Отказано в доступе [2017-07-28 23:38:57] [INFO] [ccminer_NVIDIA-MINER_ID(414)-DEVICE_IDs(0,1)] [pid(9176)|bin(bin\ccminer_klaust\ccminer.exe)] Shutting down miner [2017-07-28 23:38:58] [INFO] [ClaymoreDualIndexing] Found 3 AMD devices [2017-07-28 23:38:58] [INFO] [ExtraLaunchParametersParser] ExtraLaunch params "-dcri 29" for device UUID PCI_VEN_1002&DEV_67DF_31ABA5D [2017-07-28 23:38:58] [INFO] [ExtraLaunchParametersParser] ExtraLaunch params "-dcri 29" for device UUID PCI_VEN_1002&DEV_67DF_798C2C0 [2017-07-28 23:38:58] [INFO] [ExtraLaunchParametersParser] ExtraLaunch params "-dcri 29" for device UUID PCI_VEN_1002&DEV_67DF_2D78AB8F [2017-07-28 23:38:58] [INFO] [ExtraLaunchParametersParser] Final extra launch params parse " -dcri 29,29,29" [2017-07-28 23:38:58] [INFO] [ExtraLaunchParametersParser] DisableAMDTempControl is TRUE, temp control parameters will be ignored [2017-07-28 23:38:58] [INFO] [ClaymoreDual-MINER_ID(416)-DEVICE_IDs(0,1,2)] Starting miner [pid(5016)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] -di 210 -dcri 29,29,29 -epool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -ewal 12XgA2s2f8aGnYXspa62ntn5HHDoFLw8Yg.Uley -mport 127.0.0.1:4004 -esm 3 -epsw x -allpools 1 -dcoin dcr -dpool stratum+tcp://decred.eu.nicehash.com:3354 -dwal 12XgA2s2f8aGnYXspa62ntn5HHDoFLw8Yg.Uley -dpsw x -dbg -1 [2017-07-28 23:38:58] [INFO] [ClaymoreDual-MINER_ID(416)-DEVICE_IDs(0,1,2)] [pid(5016)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Starting cooldown checker [2017-07-28 23:38:58] [INFO] [ExtraLaunchParametersParser] ExtraLaunch params "" for device UUID GPU-6aeca659-2dca-3407-a86b-ebb1fdcf740d [2017-07-28 23:38:58] [INFO] [ExtraLaunchParametersParser] ExtraLaunch params "" for device UUID GPU-9cf5a7f5-95d3-c1cd-b503-9217eeca9faf [2017-07-28 23:38:58] [INFO] [ExtraLaunchParametersParser] Final extra launch params parse "" [2017-07-28 23:38:58] [INFO] [ExtraLaunchParametersParser] DisableAMDTempControl is TRUE, temp control parameters will be ignored [2017-07-28 23:38:58] [INFO] [ewbf-MINER_ID(417)-DEVICE_IDs(0,1)] Starting miner [pid(2876)|bin(bin_3rdparty\ewbf\miner.exe)] --cuda_devices 0 1 --server equihash.eu.nicehash.com --user 12XgA2s2f8aGnYXspa62ntn5HHDoFLw8Yg.Uley --pass x --port 3357 --api 127.0.0.1:4005 --fee 0 [2017-07-28 23:38:58] [INFO] [ewbf-MINER_ID(417)-DEVICE_IDs(0,1)] [pid(2876)|bin(bin_3rdparty\ewbf\miner.exe)] Starting cooldown checker [2017-07-28 23:38:59] [INFO] [ERROR] Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:4005 [2017-07-28 23:39:00] [INFO] [ClaymoreDual-MINER_ID(416)-DEVICE_IDs(0,1,2)] GetSummary exception: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:4004 [2017-07-28 23:39:00] [INFO] [ERROR] Error converting value -1 to type 'System.UInt32'. Path 'result[0].solver', line 1, position 275. [2017-07-28 23:39:01] [INFO] [ClaymoreDual-MINER_ID(416)-DEVICE_IDs(0,1,2)] GetSummary exception: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:4004 [2017-07-28 23:39:03] [INFO] [ClaymoreDual-MINER_ID(416)-DEVICE_IDs(0,1,2)] [pid(5016)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Cooling UP, cool time is 10000 ms [2017-07-28 23:39:03] [INFO] [ewbf-MINER_ID(417)-DEVICE_IDs(0,1)] [pid(2876)|bin(bin_3rdparty\ewbf\miner.exe)] Cooling UP, cool time is 10000 ms [2017-07-28 23:39:04] [INFO] [ClaymoreDual-MINER_ID(416)-DEVICE_IDs(0,1,2)] GetSummary exception: Подключение не установлено, т.к. конечный компьютер отверг запрос на подключение 127.0.0.1:4004 [2017-07-28 23:39:13] [INFO] [ClaymoreDual-MINER_ID(416)-DEVICE_IDs(0,1,2)] [pid(5016)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] READ SPEED ZERO, will cool up [2017-07-28 23:39:13] [INFO] [ClaymoreDual-MINER_ID(416)-DEVICE_IDs(0,1,2)] [pid(5016)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Cooling UP, cool time is 20000 ms [2017-07-28 23:39:13] [INFO] [ewbf-MINER_ID(417)-DEVICE_IDs(0,1)] [pid(2876)|bin(bin_3rdparty\ewbf\miner.exe)] READ SPEED ZERO, will cool up [2017-07-28 23:39:13] [INFO] [ewbf-MINER_ID(417)-DEVICE_IDs(0,1)] [pid(2876)|bin(bin_3rdparty\ewbf\miner.exe)] Cooling UP, cool time is 20000 ms [2017-07-28 23:39:33] [INFO] [ClaymoreDual-MINER_ID(416)-DEVICE_IDs(0,1,2)] [pid(5016)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Reseting cool time = 5000 ms [2017-07-28 23:39:33] [INFO] [ewbf-MINER_ID(417)-DEVICE_IDs(0,1)] [pid(2876)|bin(bin_3rdparty\ewbf\miner.exe)] READ SPEED ZERO, will cool up [2017-07-28 23:39:33] [INFO] [ewbf-MINER_ID(417)-DEVICE_IDs(0,1)] [pid(2876)|bin(bin_3rdparty\ewbf\miner.exe)] Cooling UP, cool time is 40000 ms [2017-07-28 23:39:54] [INFO] [ewbf-MINER_ID(417)-DEVICE_IDs(0,1)] [pid(2876)|bin(bin_3rdparty\ewbf\miner.exe)] Shutting down miner [2017-07-28 23:39:54] [INFO] [ClaymoreDual-MINER_ID(416)-DEVICE_IDs(0,1,2)] [pid(5016)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Shutting down miner [2017-07-28 23:39:54] [INFO] [ClaymoreDual-MINER_ID(416)-DEVICE_IDs(0,1,2)] Trying to kill all miner processes for this instance: [2017-07-28 23:39:54] [INFO] [ClaymoreDual-MINER_ID(416)-DEVICE_IDs(0,1,2)] Trying to kill [pid(5016)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] [2017-07-28 23:39:54] [INFO] [ClaymoreDual-MINER_ID(416)-DEVICE_IDs(0,1,2)] Exception killing [pid(5016)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)], exMsg Отказано в доступе

[lmlim]

yes, logically just close what is less profitable and run more profitable algo and ignore the other algos.

[Spoob]

Yes, that's right, on other versions, for example on the classic Nicehash worked 2 algorithms in two windows. Each window was restarted separately, regardless of each other. Radeons for example do not switch anywhere, they can dig the same thing for more than a day, and even if they restart it, it still starts what it was. Now they are jerking along with the cards. I tried version 1.8.0.1 - all the same.

[luongk]

I didn't quite understand Spoob's initial comment, but I think I'm seeting the same behaviour - in a multi-GPU setup (I have a 1080ti and a 980) both miners seem to be restarted even if one of them is still mining the same coin after the restart

e.g. 1080ti mining Blake2s, 980 mining DaggerPascal Blake2s profitability drops, 1080ti changes to Equihash but 980 miner also gets restarted (mining the same coin).

[Spoob]

Yes exactly. Previously, each algorithm worked by itself, now if 1080ti is necessary to switch to another algorithm, then it also restarts the RX570. Although the RX570 did not need to be restarted, and they start again on the same algorithm as before.

[Joern85]

i'm using a rx480 and gtx 970. everytime the algo for the gtx970 changes the miner for the rx480 is also being restarted. but the algo for the rx480doesn't change, it's always dagger decred

[DillonN]

Thanks for sharing this, it isn't the intended behaviour. Just to be clear, is there anyone experiencing this without at least one of the algorithms involved being a ClaymoreDual one?

[luongk]

My rig just went from 1080ti mining keccak + 980 mining Equihash to both mining equihash (with both miners restarting to reload in a single window), but I imagine that's intended behaviour.

[DillonN]

Yes in some scenarios a restart of the miner is necessary - mainly in situations like that (where the changing device is switching to the same algo as the non-changing one)

[luongk]

That being said it's not consistent - just went from 1080ti mining keccak + 980 mining equihash to 1080ti/x11gost and 980/equihash, the equihash miner didn't restart.

[Spoob]

I'm currently using dual mode on the RX570 and 1080TI. It is the same miner but in different windows. When restarting one of them, the second one of course can also restart. Before that, RX570 only got a dagger + decred, and 1080 ekvihesh / lbr / keccak and others. If 1080ti was restarted to change the algorithm, the RX570 was also restarted. RX570 ran the same algorithm as before. In other words, using different miners they do not restart individually independently of each other

[DillonN]

This was an issue with ClaymoreDual that was fixed