Quote from: mastermerlin on August 22, 2017, 08:39:22 AM

Quote from: costi.kocev on August 22, 2017, 06:00:14 AM

@Claymore, one of my rigs has been stuck on Dev Fee mining and Set New Dag for card number 0 - 5 because change of dev fee or something like that. I don`t have log, because I have no log in bat file. Can you think what was is the problem?

Log - Constantly changing DAG #128 - 139 and resetting DevFee Timer

9:46:04:275   30ac   DevFee: ETH: 08/22/17-09:46:04 - New job from eu1.ethermine.org:4444
09:46:04:281   30ac   DevFee: target: 0x0000000112e0be82 (diff: 4000MH)
09:46:04:393   2aa8   ETH: checking pool connection...
09:46:04:398   2aa8   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

09:46:04:407   1f04   Setting DAG epoch #128...
09:46:04:444   2aa8   got 248 bytes
09:46:04:448   2aa8   buf: {"id":3,"jsonrpc":"2.0","result":["0x735e77ae1b66ca17a62d0f18ca032347ab2acb9297e5f3ef6470b09257d6923e","0xc50f0eb9498c019d38f28db0aefec38f0a243f1bcbc67281ce622916ee182e4a","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3fec32"]}

09:46:04:453   2aa8   parse packet: 247
09:46:04:458   2aa8   ETH: job is the same
09:46:04:462   2aa8   new buf size: 0
09:46:07:096   30ac   DevFee: ETH: checking pool connection...
09:46:07:100   30ac   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

09:46:07:141   30ac   got 248 bytes
09:46:07:146   30ac   buf: {"id":3,"jsonrpc":"2.0","result":["0x59048890c11cd2ac7c2df92281bf975fc43040c993481e7d3e9a87e827f60d5f","0x7c4fb8a5d141973b69b521ce76b0dc50f0d2834d817c7f8310a6ab5becc6bb0c","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3acbd1"]}

09:46:07:150   30ac   parse packet: 247
09:46:07:154   30ac   ETH: job is the same
09:46:07:159   30ac   new buf size: 0
09:46:07:164   1f04   Setting DAG epoch #128 for GPU0
09:46:07:169   3af4   Setting DAG epoch #128 for GPU1
09:46:08:796   2aa8   got 248 bytes
09:46:08:801   2aa8   buf: {"id":0,"jsonrpc":"2.0","result":["0xaa753381e01fdfc07a87d0fa6008ba27786ad3f18e5c038148f845666e629756","0xc50f0eb9498c019d38f28db0aefec38f0a243f1bcbc67281ce622916ee182e4a","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3fec33"]}

09:46:08:805   2aa8   parse packet: 247
09:46:08:810   2aa8   ETH: job changed
09:46:08:814   2aa8   new buf size: 0
09:46:08:819   2aa8   ETH: 08/22/17-09:46:08 - New job from eu1.ethermine.org:4444
09:46:08:823   2aa8   target: 0x0000000112e0be82 (diff: 4000MH), epoch 139(2.09GB)
09:46:08:834   2aa8   ETH - Total Speed: 62.662 Mh/s, Total Shares: 61, Rejected: 0, Time: 01:20
09:46:08:841   2aa8   ETH: GPU0 31.341 Mh/s, GPU1 31.321 Mh/s
09:46:08:846   2aa8    SC - Total Speed: 626.618 Mh/s, Total Shares: 16, Rejected: 0
09:46:08:852   2aa8    SC: GPU0 313.412 Mh/s, GPU1 313.206 Mh/s
09:46:12:765   3af4   GPU1 DAG creation time - 5529 ms
09:46:12:770   3af4   Setting DAG epoch #128 for GPU1 done
09:46:12:777   1f04   GPU0 DAG creation time - 5573 ms
09:46:12:782   3af4   DevFee: restart timer because of updating DAG
09:46:12:783   1f04   Setting DAG epoch #128 for GPU0 done
09:46:12:796   1f04   DevFee: restart timer because of updating DAG
--- shortended ---
09:46:19:763   30ac   DevFee: ETH: 08/22/17-09:46:19 - New job from eu1.ethermine.org:4444
09:46:19:768   30ac   DevFee: target: 0x0000000112e0be82 (diff: 4000MH)
09:46:19:881   1bf0   Setting DAG epoch #139...
09:46:20:028   15b4   got 300 bytes
09:46:20:033   15b4   buf: {"id":6,"jsonrpc":"2.0","params":["88","0x000000000000002580faadcf154b9da95410ab4b20765c6c1897815a350901a70000000000000 00044e19b5900000000718058ed8d0b138b6afb9120ee5e82c4858dd73be23de477006721ace739 2b7e","0x0000000007547ff5d321871ff4fb4f118b8d13a30a1ff7b317f3c5b20629578a"],"method":"mining.notify"}

09:46:20:038   15b4   parse packet: 299
09:46:20:042   15b4   sc: job changed(2)
09:46:20:046   15b4   new buf size: 0
09:46:20:050   15b4    SC: 08/22/17-09:46:20 - New job from sia-eu1.nanopool.org:7777
09:46:20:056   15b4   target: 0x0000000007547ff5 (diff: 150GH)
09:46:22:744   fe8   Setting DAG epoch #139 for GPU0
09:46:22:742   1bf0   Setting DAG epoch #139 for GPU1

Yes, that was. We need info from @Claymore.