Author

Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 283. (Read 6590718 times)

newbie
Activity: 1
Merit: 0
Hello,

I'm running version 10.5 and i have a issue that my RIG stopped running. GPU0 has a watchdog timeout.

How can i fix this the next time? (now manually killed at 10:12)

start file:
Code:
:start
timeout 30
EthDcrMiner64.exe -di 01234 -allpools 1 -dbg 1 -ftime 0 -minspeed 169 -r 10 -mode 0
goto start

Log file:
Code:
23:21:50:854	fec	ETH: 03/31/18-23:21:50 - New job from eu1.ethermine.org:5555
23:21:50:854 fec target: 0x0000000112e0be82 (diff: 4000MH), epoch 178(2.39GB)
23:21:50:854 fec ETH - Total Speed: 170.387 Mh/s, Total Shares: 151, Rejected: 0, Time: 00:53
23:21:50:854 fec ETH: GPU0 34.071 Mh/s, GPU1 34.091 Mh/s, GPU2 34.050 Mh/s, GPU3 34.088 Mh/s, GPU4 34.088 Mh/s
23:21:50:870 fec DCR - Total Speed: 1703.870 Mh/s, Total Shares: 114, Rejected: 2
23:21:50:870 fec DCR: GPU0 340.706 Mh/s, GPU1 340.907 Mh/s, GPU2 340.499 Mh/s, GPU3 340.881 Mh/s, GPU4 340.877 Mh/s
23:21:51:214 1a3c buf: {"id":null,"method":"mining.notify","params":["1d3c","38d2ff8c6d9a6a1c32675111dd56fecb2dbde5ff15c124160000000f00000000","1c4160b4d98dd1a3f1a2e200baea58f2834950fb68a5caa08328992cef9c5c0715050b51046571a2131ed6c95cdf47bae26757b6b156681ec9d5948fb77e4b710100b30e7fae961705000300b19e000099cd1819e90d2d0002000000c4720300d5150000edfbbf5a0000000000000000","05000000",[],"05000000","1918cd99","5abffbed",false]}

23:21:51:214 1a3c DCR: 03/31/18-23:21:51 - New job from dcr.coinmine.pl:2222
23:21:51:214 1a3c target: 0x000000002161e804 (diff: 32GH), block #225988
23:21:53:776 48c DCR: put share nonce 18b87322 enonce a1f50014
23:21:53:792 1a3c DCR: 03/31/18-23:21:53 - SHARE FOUND - (GPU 0)
23:21:53:792 1a3c sent: {"params": ["myaccount.RIG1", "1d3c", "00000000a1f5001458154546", "5abffbed", "2273b818"], "id": 10, "method": "mining.submit"}

23:21:53:823 1a3c buf: {"id":10,"result":true,"error":null}

23:21:53:823 1a3c DCR: Share accepted (32 ms)!
23:21:53:886 fec sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xa27f9b6", "0x00000000000000000000000000000000000000000000000000000000f503be10"]}

23:21:53:901 fec buf: {"id":6,"jsonrpc":"2.0","result":true}

23:21:56:308 ac4 DCR: put share nonce aee111b enonce 235f003d
23:21:56:339 1a3c DCR: 03/31/18-23:21:56 - SHARE FOUND - (GPU 0)
23:21:56:339 1a3c sent: {"params": ["myaccount.RIG1", "1d3c", "00000000235f003d58154546", "5abffbed", "1b11ee0a"], "id": 10, "method": "mining.submit"}

23:21:56:370 1a3c buf: {"id":10,"result":true,"error":null}

23:21:56:370 1a3c DCR: Share accepted (31 ms)!
23:22:02:137 1dc8 em hbt: 16, dm hbt: 16, fm hbt: 110,
23:22:02:137 1dc8 watchdog - thread 0 (gpu0), hb time 375
23:22:02:137 1dc8 watchdog - thread 1 (gpu0), hb time 0
23:22:02:137 1dc8 watchdog - thread 2 (gpu1), hb time 0
23:22:02:137 1dc8 watchdog - thread 3 (gpu1), hb time 375
23:22:02:152 1dc8 watchdog - thread 4 (gpu2), hb time 15
23:22:02:152 1dc8 watchdog - thread 5 (gpu2), hb time 375
23:22:02:152 1dc8 watchdog - thread 6 (gpu3), hb time 390
23:22:02:152 1dc8 watchdog - thread 7 (gpu3), hb time 15
23:22:02:152 1dc8 watchdog - thread 8 (gpu4), hb time 15
23:22:02:168 1dc8 watchdog - thread 9 (gpu4), hb time 406
23:22:03:043 fec ETH: checking pool connection...
23:22:03:043 fec sent: {"id":3,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

23:22:03:059 fec buf: {"id":3,"jsonrpc":"2.0","result":["0x3b22e5151c5e9d8c63d54bd12f7c34c1c834e8ea61a2c823766712d20dd545ee","0x40910b6ac043b9a4c8a3a5100b00efcc1d90c39643cc754f24bf544c3e29c01c","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x51be2d"]}

23:22:06:121 d18 DCR: put share nonce 148d30d7 enonce 991b00c1
23:22:06:153 1a3c DCR: 03/31/18-23:22:06 - SHARE FOUND - (GPU 1)
23:22:06:153 1a3c sent: {"params": ["myaccount.RIG1", "1d3c", "00000000991b00c158154546", "5abffbed", "d7308d14"], "id": 11, "method": "mining.submit"}

23:22:06:184 1a3c buf: {"id":11,"result":true,"error":null}

23:22:06:184 1a3c DCR: Share accepted (32 ms)!
23:22:08:153 fec buf: {"id":0,"jsonrpc":"2.0","result":["0xf535c92a0c01e308e62181b453bc0097a76f3c25a351166362683f262c276cbd","0x40910b6ac043b9a4c8a3a5100b00efcc1d90c39643cc754f24bf544c3e29c01c","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x51be2e"]}

23:22:08:153 fec ETH: 03/31/18-23:22:08 - New job from eu1.ethermine.org:5555
23:22:08:153 fec target: 0x0000000112e0be82 (diff: 4000MH), epoch 178(2.39GB)
23:22:08:153 fec ETH - Total Speed: 170.435 Mh/s, Total Shares: 151, Rejected: 0, Time: 00:53
23:22:08:153 fec ETH: GPU0 34.085 Mh/s, GPU1 34.094 Mh/s, GPU2 34.086 Mh/s, GPU3 34.081 Mh/s, GPU4 34.088 Mh/s
23:22:08:169 fec DCR - Total Speed: 1704.349 Mh/s, Total Shares: 117, Rejected: 2
23:22:08:169 fec DCR: GPU0 340.849 Mh/s, GPU1 340.943 Mh/s, GPU2 340.863 Mh/s, GPU3 340.813 Mh/s, GPU4 340.881 Mh/s
23:22:13:888 fec sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xa285195", "0x00000000000000000000000000000000000000000000000000000000f503be10"]}

23:22:13:904 fec buf: {"id":6,"jsonrpc":"2.0","result":true}

23:22:15:076 ac4 DCR: put share nonce 1af463e3 enonce 235f014b
23:22:15:091 1a3c DCR: 03/31/18-23:22:15 - SHARE FOUND - (GPU 0)
23:22:15:091 1a3c sent: {"params": ["myaccount.RIG1", "1d3c", "00000000235f014b58154546", "5abffbed", "e363f41a"], "id": 10, "method": "mining.submit"}

23:22:15:122 1a3c buf: {"id":10,"result":true,"error":null}

23:22:15:122 1a3c DCR: Share accepted (31 ms)!
23:22:15:263 17b0 GPU0 t=52C fan=50%, GPU1 t=54C fan=50%, GPU2 t=53C fan=50%, GPU3 t=56C fan=50%, GPU4 t=55C fan=50%
23:22:30:702 d18 DCR: put share nonce f6680c8 enonce 991b0215
23:22:30:718 1a3c DCR: 03/31/18-23:22:30 - SHARE FOUND - (GPU 1)
23:22:30:718 1a3c sent: {"params": ["myaccount.RIG1", "1d3c", "00000000991b021558154546", "5abffbed", "c880660f"], "id": 11, "method": "mining.submit"}

23:22:30:749 1a3c buf: {"id":11,"result":true,"error":null}

23:22:30:749 1a3c DCR: Share accepted (31 ms)!
23:22:33:062 fec ETH: checking pool connection...
23:22:33:062 fec sent: {"id":3,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

23:22:33:077 fec buf: {"id":3,"jsonrpc":"2.0","result":["0xf535c92a0c01e308e62181b453bc0097a76f3c25a351166362683f262c276cbd","0x40910b6ac043b9a4c8a3a5100b00efcc1d90c39643cc754f24bf544c3e29c01c","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x51be2e"]}

23:22:33:906 fec sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xa27ca6f", "0x00000000000000000000000000000000000000000000000000000000f503be10"]}

23:22:33:921 fec buf: {"id":6,"jsonrpc":"2.0","result":true}

23:22:34:984 1dc8 em hbt: 15, dm hbt: 15, fm hbt: 31,
23:22:34:984 1dc8 watchdog - thread 0 (gpu0), hb time 656
23:22:34:984 1dc8 watchdog - thread 1 (gpu0), hb time 281
23:22:34:984 1dc8 watchdog - thread 2 (gpu1), hb time 281
23:22:34:984 1dc8 watchdog - thread 3 (gpu1), hb time 656
23:22:35:000 1dc8 watchdog - thread 4 (gpu2), hb time 297
23:22:35:000 1dc8 watchdog - thread 5 (gpu2), hb time 656
23:22:35:000 1dc8 watchdog - thread 6 (gpu3), hb time 672
23:22:35:000 1dc8 watchdog - thread 7 (gpu3), hb time 297
23:22:35:000 1dc8 watchdog - thread 8 (gpu4), hb time 297
23:22:35:015 1dc8 watchdog - thread 9 (gpu4), hb time 688
23:22:35:109 fec buf: {"id":0,"jsonrpc":"2.0","result":["0x3c9f515edfd65edbc51f0d49fab91176b9daf91b515e2f3db0210ebd088cb33d","0x40910b6ac043b9a4c8a3a5100b00efcc1d90c39643cc754f24bf544c3e29c01c","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x51be2f"]}

23:23:03:721 17b0 GPU0 t=53C fan=50%, GPU1 t=54C fan=50%, GPU2 t=53C fan=50%, GPU3 t=56C fan=50%, GPU4 t=55C fan=50%
23:22:46:219 1a3c buf: {"id":null,"method":"mining.set_difficulty","params":[15.0857389]}

23:22:50:111 d7c checked ETH share on CPU, spent 6ms
23:23:03:721 fec ETH: 03/31/18-23:22:35 - New job from eu1.ethermine.org:5555
23:23:03:737 1a3c buf: {"id":null,"method":"mining.notify","params":["1d3d","38d2ff8c6d9a6a1c32675111dd56fecb2dbde5ff15c124160000000f00000000","1c4160b4d98dd1a3f1a2e200baea58f2834950fb68a5caa08328992cef9c5c0715050b51046571a2131ed6c95cdf47bae26757b6b156681ec9d5948fb77e4b710100b30e7fae961705000300b19e000099cd1819e90d2d0002000000c4720300d515000024fcbf5a0000000000000000","05000000",[],"05000000","1918cd99","5abffc24",false]}

23:23:03:737 d7c sent: {"id":13,"method":"eth_submitWork","params":["0xaf1dc6a013ef3478","0x3c9f515edfd65edbc51f0d49fab91176b9daf91b515e2f3db0210ebd088cb33d","0xc8c0c54c21c4eeae1372ddecd3ab48d8202d8a6a40c2c8bb8aad6571203dc61f"]}

23:23:03:737 fec target: 0x0000000112e0be82 (diff: 4000MH), epoch 178(2.39GB)
23:23:03:737 fec gpu #0 dt 0.18 (0%, good)
23:23:03:737 193c checked ETH share on CPU, spent 4ms
23:23:03:737 1a3c DCR: 03/31/18-23:23:03 - New job from dcr.coinmine.pl:2222
23:23:03:737 d7c ETH: put share nonce af1dc6a013ef3478
23:23:03:753 fec gpu #2 dt 0.18 (0%, good)
23:23:03:768 fec gpu #4 dt 0.18 (0%, good)
23:23:03:768 fec ETH - Total Speed: 170.366 Mh/s, Total Shares: 151, Rejected: 0, Time: 00:54
23:23:03:753 193c sent: {"id":11,"method":"eth_submitWork","params":["0x024720202185a877","0x3c9f515edfd65edbc51f0d49fab91176b9daf91b515e2f3db0210ebd088cb33d","0x7bc6e5f4617a4629958221fbb2c740fc2ac4c61173c8e53a6f865c1eeea93284"]}

23:23:03:753 1a3c target: 0x0000000010f82b46 (diff: 64GH), block #225988
23:23:03:784 fec ETH: GPU0 34.069 Mh/s, GPU1 34.072 Mh/s, GPU2 34.067 Mh/s, GPU3 34.075 Mh/s, GPU4 34.084 Mh/s
23:23:03:784 fec DCR - Total Speed: 1703.662 Mh/s, Total Shares: 119, Rejected: 2
23:23:03:768 193c ETH: put share nonce 24720202185a877
23:23:03:784 fec DCR: GPU0 340.688 Mh/s, GPU1 340.719 Mh/s, GPU2 340.665 Mh/s, GPU3 340.747 Mh/s, GPU4 340.843 Mh/s
23:23:03:799 fec ETH: 03/31/18-23:23:03 - SHARE FOUND - (GPU 3)
23:23:03:799 fec buf: {"id":13,"jsonrpc":"2.0","result":true}

23:23:03:799 fec ETH: Share accepted (31 ms)!

23:23:03:799 fec ETH: 03/31/18-23:23:03 - SHARE FOUND - (GPU 1)
23:23:03:815 fec buf: {"id":11,"jsonrpc":"2.0","result":true}

23:23:03:815 fec ETH: Share accepted (47 ms)!

23:23:03:815 fec ETH: checking pool connection...
23:23:03:815 fec sent: {"id":3,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

23:23:03:815 fec sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xa2795b4", "0x00000000000000000000000000000000000000000000000000000000f503be10"]}

23:23:03:846 fec buf: {"id":3,"jsonrpc":"2.0","result":["0x3c9f515edfd65edbc51f0d49fab91176b9daf91b515e2f3db0210ebd088cb33d","0x40910b6ac043b9a4c8a3a5100b00efcc1d90c39643cc754f24bf544c3e29c01c","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x51be2f"]}

23:23:03:862 fec buf: {"id":6,"jsonrpc":"2.0","result":true}

23:23:07:159 fec buf: {"id":0,"jsonrpc":"2.0","result":["0x03f3116cc02fdbfe6905d14437705dd814c6d96620df3c47d377ea87f1fc375f","0x40910b6ac043b9a4c8a3a5100b00efcc1d90c39643cc754f24bf544c3e29c01c","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x51be30"]}

23:23:07:831 1dc8 em hbt: 672, dm hbt: 0, fm hbt: 62,
10:12:18:333 1dc8 watchdog - thread 0 (gpu0), hb time 38932984
23:23:25:489 48c checked ETH share on CPU, spent 3ms
10:12:18:349 17b0 GPU0 t=49C fan=50%, GPU1 t=55C fan=50%, GPU2 t=53C fan=50%, GPU3 t=56C fan=50%, GPU4 t=55C fan=50%
23:23:41:225 1a3c buf: {"id":null,"method":"mining.notify","params":["1d3e","38d2ff8c6d9a6a1c32675111dd56fecb2dbde5ff15c124160000000f00000000","1c4160b4d98dd1a3f1a2e200baea58f2834950fb68a5caa08328992cef9c5c0715050b51046571a2131ed6c95cdf47bae26757b6b156681ec9d5948fb77e4b710100b30e7fae961705000300b19e000099cd1819e90d2d0002000000c4720300d51500005bfcbf5a0000000000000000","05000000",[],"05000000","1918cd99","5abffc5b",false]}

23:24:19:136 13c0 DCR: put share nonce 71a3c1 enonce b3de05ef
23:25:30:018 d18 DCR: put share nonce 1a2632e7 enonce 250d07dd
23:26:02:069 c34 DCR: put share nonce 1945d112 enonce 52f30997
10:12:18:365 1aa4 DevFee: ETH: Stratum - connecting to 'eu1.ethermine.org' <51.255.64.43> port 5555 (SSL/TLS)
23:23:24:974 ac4 DCR: put share nonce 1a3a72a3 enonce c9980123
10:12:18:333 1dc8 WATCHDOG: GPU 0 hangs in OpenCL call, exit
10:12:18:349 48c sent: {"id":10,"method":"eth_submitWork","params":["0x0fd520dc18f88516","0x03f3116cc02fdbfe6905d14437705dd814c6d96620df3c47d377ea87f1fc375f","0xd317a29ec4b65960ad3767f613dd4fa4c7f6343272aef125e3b296746135575f"]}

10:12:18:380 48c ETH: put share nonce fd520dc18f88516
10:12:18:365 1dc8 watchdog - thread 1 (gpu0), hb time 0
10:12:18:333 fec ETH: 03/31/18-23:23:07 - New job from eu1.ethermine.org:5555
10:12:18:380 1a3c DCR: 04/01/18-10:12:18 - New job from dcr.coinmine.pl:2222
10:12:18:380 1340 checked ETH share on CPU, spent 6ms
10:12:18:380 1dc8 watchdog - thread 2 (gpu1), hb time 38742000
10:12:18:396 1dc8 WATCHDOG: GPU 1 hangs in OpenCL call, exit
10:12:18:380 1a3c target: 0x0000000010f82b46 (diff: 64GH), block #225988
10:12:18:396 1340 ETH: Stratum - socket send failed 10054, disconnect
10:12:18:380 fec target: 0x0000000112e0be82 (diff: 4000MH), epoch 178(2.39GB)
10:12:18:396 1dc8 watchdog - thread 3 (gpu1), hb time 47
10:12:18:411 1dc8 watchdog - thread 4 (gpu2), hb time 38773734
10:12:18:411 1340 sent: {"id":14,"method":"eth_submitWork","params":["0x8c6208602f1c8818","0x03f3116cc02fdbfe6905d14437705dd814c6d96620df3c47d377ea87f1fc375f","0xf3d7960bc40c4e55f609453bcc3528ff35b8c968dbae2816cdc194d5fd75c819"]}

10:12:18:411 fec gpu #1 dt 0.18 (0%, good)
10:12:18:411 1aa4 cert subject: /OU=Domain Control Validated/OU=EssentialSSL Wildcard/CN=*.ethermine.org
10:12:18:427 1a3c DCR: 04/01/18-10:12:18 - SHARE FOUND - (GPU 4)
10:12:18:427 1a3c DCR: Stratum - socket send failed 10053, disconnect
10:12:18:427 fec gpu #3 dt 0.18 (0%, good)
10:12:18:443 fec ETH - Total Speed: 68.144 Mh/s, Total Shares: 153, Rejected: 0, Time: 11:43
10:12:18:427 1aa4 cert issuer: /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
10:12:18:443 1aa4 SSL/TLS encryption is enabled
10:12:18:427 1dc8 WATCHDOG: GPU 2 hangs in OpenCL call, exit
10:12:18:427 1a3c sent: {"params": ["myaccount.RIG1", "1d3e", "00000000b3de05ef58154546", "5abffc5b", "c1a37100"], "id": 14, "method": "mining.submit"}

10:12:18:458 1a3c DCR: Connection lost, retry in 20 sec...
10:12:18:458 fec ETH: GPU0 34.089 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 34.055 Mh/s
10:12:18:458 fec DCR - Total Speed: 681.436 Mh/s, Total Shares: 120, Rejected: 2
10:12:18:443 1aa4 sent: devfee auth
10:12:18:474 1aa4 DevFee: ETH: Stratum - Connected (eu1.ethermine.org:5555) (SSL/TLS)
10:12:18:427 d4c checked ETH share on CPU, spent 4ms
10:12:18:427 1340 ETH: put share nonce 8c6208602f1c8818
10:12:18:474 fec DCR: GPU0 340.888 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 340.548 Mh/s
10:12:18:443 1dc8 watchdog - thread 5 (gpu2), hb time 79
10:12:18:474 1aa4 buf: {"id":2,"jsonrpc":"2.0","result":true}

10:12:18:474 d4c socket is null, exit
10:12:18:490 1dc8 watchdog - thread 6 (gpu3), hb time 38856453
10:12:18:490 1aa4 ETH: Authorized
10:12:18:490 d4c ETH: put share nonce 6fb036c48138a80f
10:12:18:505 1dc8 WATCHDOG: GPU 3 hangs in OpenCL call, exit
10:12:18:505 1aa4 sent: {"id":3,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

10:12:18:505 fec ETH: Stratum - connecting to 'eu1.ethermine.org' <188.165.226.213> port 5555 (SSL/TLS)
10:12:18:505 1dc8 watchdog - thread 7 (gpu3), hb time 38748016
10:12:18:490 2014 checked ETH share on CPU, spent 4ms
10:12:18:521 1dc8 WATCHDOG: GPU 3 hangs in OpenCL call, exit
10:12:18:521 2014 socket is null, exit
10:12:18:521 1dc8 watchdog - thread 8 (gpu4), hb time 47
10:12:18:521 2014 ETH: put share nonce 4de9f834f330c771
10:12:18:536 1aa4 buf: {"id":3,"jsonrpc":"2.0","result":["0x5de6183f68fc16eac32bab03ba8b643454f8ced10b5ebb11af9c9198c1a5be7f","0x40910b6ac043b9a4c8a3a5100b00efcc1d90c39643cc754f24bf544c3e29c01c","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x51c8f3"]}

10:12:18:536 1dc8 watchdog - thread 9 (gpu4), hb time 187
10:12:18:536 d7c checked ETH share on CPU, spent 4ms
10:12:18:552 d7c socket is null, exit
10:12:18:552 d7c ETH: put share nonce 7fe4ae819cb9a528
10:12:18:552 1aa4 DevFee: start mining
10:12:18:552 193c checked ETH share on CPU, spent 4ms
10:12:18:568 193c socket is null, exit
10:12:18:568 fec cert subject: /OU=Domain Control Validated/OU=EssentialSSL Wildcard/CN=*.ethermine.org
10:12:18:568 193c ETH: put share nonce 2fa44dfd6f44ab46
10:12:18:568 fec cert issuer: /C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Domain Validation Secure Server CA
10:12:18:568 fec SSL/TLS encryption is enabled
10:12:18:583 fec Pool certificate verified successfully
10:12:18:583 fec sent: {"id":2,"jsonrpc":"2.0","method":"eth_login","params":["0x9D9db56865757eb76D58Ab78198b7011572?????.RIG1","x"]}

10:12:18:583 fec ETH: Stratum - Connected (eu1.ethermine.org:5555) (SSL/TLS)
10:12:18:615 fec buf: {"id":2,"jsonrpc":"2.0","result":true}

10:12:18:615 fec ETH: Authorized
10:12:18:615 fec sent: {"id":3,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

10:12:18:646 fec buf: {"id":3,"jsonrpc":"2.0","result":["0x0b81eeb9a98d79c16d5b396193517444dcf65450e1c01ba0ddb1dcdd1a96db5f","0x40910b6ac043b9a4c8a3a5100b00efcc1d90c39643cc754f24bf544c3e29c01c","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x51c8f3"]}

10:12:18:662 1dc8 Quit, please wait...
10:12:19:974 1dc8 Restarting OK, exit...
newbie
Activity: 2
Merit: 0
Hi guys!
It looks like an update for Nviadia vga. I'm running v11.5 on AMD rx580 8gb vga, is it worth upgrading to v11.6?
jr. member
Activity: 64
Merit: 2
mined many coins with many programs , but im having a noob moment here lol .. anyone tell me why i get ETH shares rejected with this command line below .. i swear it worked last week


EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal 0xd942303B474fd7170A8a2Fa0e1Da25C1FC63E7.No1/s***[email protected] -epsw x -dpool stratum+tcp://xvg.antminepool.com:9008 -dwal DJniGwyhC2FMT3rW87DvGTVXDQkLdQ3H.No1 -dpsw x -dcoin blake2s  -dcri 40


2 possibilities: 1) pool is down (usually doesn't appear often) or more causable it's your settings. Use at least 11.5 (auto drci enabled) and try lowering your mclock (gpu memory clock speed). mclock gives you the hash but also the incorrect shares.
sr. member
Activity: 1008
Merit: 297
Grow with community
mined many coins with many programs , but im having a noob moment here lol .. anyone tell me why i get ETH shares rejected with this command line below .. i swear it worked last week


EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal 0xd942303B474fd7170A8a2Fa0e1Da25C1FC63E7.No1/s***[email protected] -epsw x -dpool stratum+tcp://xvg.antminepool.com:9008 -dwal DJniGwyhC2FMT3rW87DvGTVXDQkLdQ3H.No1 -dpsw x -dcoin blake2s  -dcri 40



I see no prob with the commandline, did you try lowering your OC settings or the -dcri

btw tried checking address on ethermine seems the pool has a prob, rejected shares may also cause on the pool side
member
Activity: 413
Merit: 17

Don't worry about memory errors, the cards have a built-in error correction. If you are stable and getting no rejected shares - keep it that way.
Half of my cards produce millions of errors per day but work fine.
Shocked Shocked Shocked Shocked
you will lose your card very soon

Sorry buddy, but that's now how it works.
newbie
Activity: 9
Merit: 0
mined many coins with many programs , but im having a noob moment here lol .. anyone tell me why i get ETH shares rejected with this command line below .. i swear it worked last week


EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal 0xd942303B474fd7170A8a2Fa0e1Da25C1FC63E7.No1/s***[email protected] -epsw x -dpool stratum+tcp://xvg.antminepool.com:9008 -dwal DJniGwyhC2FMT3rW87DvGTVXDQkLdQ3H.No1 -dpsw x -dcoin blake2s  -dcri 40

legendary
Activity: 1498
Merit: 1030
Still learning here...

The first page still says "10xx cards in Windows 10 x64: just use latest 372.54 drivers from Nvidia website"

It appears that 372.54 is about a year and a half old. Is that really best or should I use the latest (which is now 391.35)?

Thanks!

373.06 is probably the best overall driver for anything before the 1070 ti - not sure on Windows for that GPU or the 1050/1050ti but LINUX mining likes 384.98 very well indeed and that version works stable with older cards as well.


newbie
Activity: 29
Merit: 5
Still learning here...

The first page still says "10xx cards in Windows 10 x64: just use latest 372.54 drivers from Nvidia website"

It appears that 372.54 is about a year and a half old. Is that really best or should I use the latest (which is now 391.35)?

Thanks!
newbie
Activity: 197
Merit: 0

Don't worry about memory errors, the cards have a built-in error correction. If you are stable and getting no rejected shares - keep it that way.
Half of my cards produce millions of errors per day but work fine.
Shocked Shocked Shocked Shocked
you will lose your card very soon
newbie
Activity: 197
Merit: 0
Hello guys, i'm having too many memory errors and don't know what to do more. I'm using 1300/2000 clocks that's basically the default ones. Mining ETH i use 1300/2100 and i dont have problems. Also 950 mvddc and cvddc

what is your GPU?
newbie
Activity: 4
Merit: 3
 I couldn't find if this was reported before but the fan speed reported is incorrect. Gpu-Z and other software shows a lower fan speed.

 It will be great if this would be fixed.
member
Activity: 413
Merit: 17
Hello guys, i'm having too many memory errors and don't know what to do more. I'm using 1300/2000 clocks that's basically the default ones. Mining ETH i use 1300/2100 and i dont have problems. Also 950 mvddc and cvddc
Don't worry about memory errors, the cards have a built-in error correction. If you are stable and getting no rejected shares - keep it that way.
Half of my cards produce millions of errors per day but work fine.
jr. member
Activity: 170
Merit: 6
hihi all

I have updates it to v11.6 but it says

eth stratum connected eth-eu nanopool.org:9999 (unsecure)

Whats with the unsecure part?

I have already read the readme file but i cant find the solution?

can you help me the noob guys Cheesy

its a connection between your miner and the pool, if you want it more secured then use the SSL port

otherwise its a default connection where I also use it

Is it safe to use it "unsecure"?

yeah, what I could do is to set some security of my PC and close some ports one example is -mport options

So far. no attempts made idk if its just a waste of time penetrating my rigs though  Cheesy

Haha okok but there is nobody who has a solution for the "unsecure" problem who can help me with this

Wtf? The solution is to use ssl pools. "Unsecured" text is just a graphical bling bling to promote users to use ssl pools so you cant cheat his miner, thats all.

Using Claymore miner you might as well use the secure port if you're mining on a pool that supports ssl.
The miner will use the ssl connection anyway no matter which you select if the pool supports it.
You can use the unsecure port 4444 if you want, but the dev fee will use the secure 5555 port anyway.
So on any pool that supports the secure 5555 you're not going to cheat him becuase he is going to dev fee on the secure.
There is no cheat any more because the ssl is encryped and none of the work arounds that used to redirect the dev fee
back to your wallet work.



It just means you're too noob to make cheats work. Cheats still work. Thats what claymore had been trying to solve since implementing 11.2 (I mean every update). the rest are just bling blings and competiion.

You're full of it.
You're not cheating using ssl connections.
Try that lame story on some who is not a software engineer like I am.
Man, the crap that some dummies try to claim on these forums is funny.



Yeah you can claim whatever you want be in the internet you know.
Triggered yeah?
Fuck noobs all the way.
Did I say we can cheat ssl easily? No. But you can cheat the miner not to use ssl for devfee. Heck you can even use nanopool for the meantime. It means you're really so stupid to not discover it. And now that I mentioned it, expect another update. Cheesy

Fucking amateurs.

Hilarious,
You're one of those.
So all people you see as noobs on a forum are automatically not as smart as you.
Sorry punk, you're one comment alone about "can't beat ssl easily" makes you a moron by itself.
You can't beat it at all. So this will be my last post to you.
The old saying that you can't argue with an idiot has been proven again.
Go on in your dummy world and just keep breaking the ssl protocol, I know you can.

Some random nut (you) plops a couple of video cards in a PC and mines using someone else's software feels like he is now software genus.
Dream on.





newbie
Activity: 8
Merit: 0
hihi all

I have updates it to v11.6 but it says

eth stratum connected eth-eu nanopool.org:9999 (unsecure)

Whats with the unsecure part?

I have already read the readme file but i cant find the solution?

can you help me the noob guys Cheesy

its a connection between your miner and the pool, if you want it more secured then use the SSL port

otherwise its a default connection where I also use it

Is it safe to use it "unsecure"?

yeah, what I could do is to set some security of my PC and close some ports one example is -mport options

So far. no attempts made idk if its just a waste of time penetrating my rigs though  Cheesy

Haha okok but there is nobody who has a solution for the "unsecure" problem who can help me with this

Wtf? The solution is to use ssl pools. "Unsecured" text is just a graphical bling bling to promote users to use ssl pools so you cant cheat his miner, thats all.

Using Claymore miner you might as well use the secure port if you're mining on a pool that supports ssl.
The miner will use the ssl connection anyway no matter which you select if the pool supports it.
You can use the unsecure port 4444 if you want, but the dev fee will use the secure 5555 port anyway.
So on any pool that supports the secure 5555 you're not going to cheat him becuase he is going to dev fee on the secure.
There is no cheat any more because the ssl is encryped and none of the work arounds that used to redirect the dev fee
back to your wallet work.



It just means you're too noob to make cheats work. Cheats still work. Thats what claymore had been trying to solve since implementing 11.2 (I mean every update). the rest are just bling blings and competiion.

You're full of it.
You're not cheating using ssl connections.
Try that lame story on some who is not a software engineer like I am.
Man, the crap that some dummies try to claim on these forums is funny.



Yeah you can claim whatever you want be in the internet you know.
Triggered yeah?
Fuck noobs all the way.
Did I say we can cheat ssl easily? No. But you can cheat the miner not to use ssl for devfee. Heck you can even use nanopool for the meantime. It means you're really so stupid to not discover it. And now that I mentioned it, expect another update. Cheesy

Fucking amateurs.
jr. member
Activity: 170
Merit: 6
hihi all

I have updates it to v11.6 but it says

eth stratum connected eth-eu nanopool.org:9999 (unsecure)

Whats with the unsecure part?

I have already read the readme file but i cant find the solution?

can you help me the noob guys Cheesy

its a connection between your miner and the pool, if you want it more secured then use the SSL port

otherwise its a default connection where I also use it

Is it safe to use it "unsecure"?

yeah, what I could do is to set some security of my PC and close some ports one example is -mport options

So far. no attempts made idk if its just a waste of time penetrating my rigs though  Cheesy

Haha okok but there is nobody who has a solution for the "unsecure" problem who can help me with this

Wtf? The solution is to use ssl pools. "Unsecured" text is just a graphical bling bling to promote users to use ssl pools so you cant cheat his miner, thats all.

Using Claymore miner you might as well use the secure port if you're mining on a pool that supports ssl.
The miner will use the ssl connection anyway no matter which you select if the pool supports it.
You can use the unsecure port 4444 if you want, but the dev fee will use the secure 5555 port anyway.
So on any pool that supports the secure 5555 you're not going to cheat him becuase he is going to dev fee on the secure.
There is no cheat any more because the ssl is encryped and none of the work arounds that used to redirect the dev fee
back to your wallet work.



It just means you're too noob to make cheats work. Cheats still work. Thats what claymore had been trying to solve since implementing 11.2 (I mean every update). the rest are just bling blings and competiion.

You're full of it.
You're not cheating using ssl connections.
Try that lame story on some who is not a software engineer like I am.
Man, the crap that some dummies try to claim on these forums is funny.

newbie
Activity: 8
Merit: 0
hihi all

I have updates it to v11.6 but it says

eth stratum connected eth-eu nanopool.org:9999 (unsecure)

Whats with the unsecure part?

I have already read the readme file but i cant find the solution?

can you help me the noob guys Cheesy

its a connection between your miner and the pool, if you want it more secured then use the SSL port

otherwise its a default connection where I also use it

Is it safe to use it "unsecure"?

yeah, what I could do is to set some security of my PC and close some ports one example is -mport options

So far. no attempts made idk if its just a waste of time penetrating my rigs though  Cheesy

Haha okok but there is nobody who has a solution for the "unsecure" problem who can help me with this

Wtf? The solution is to use ssl pools. "Unsecured" text is just a graphical bling bling to promote users to use ssl pools so you cant cheat his miner, thats all.

Using Claymore miner you might as well use the secure port if you're mining on a pool that supports ssl.
The miner will use the ssl connection anyway no matter which you select if the pool supports it.
You can use the unsecure port 4444 if you want, but the dev fee will use the secure 5555 port anyway.
So on any pool that supports the secure 5555 you're not going to cheat him becuase he is going to dev fee on the secure.
There is no cheat any more because the ssl is encryped and none of the work arounds that used to redirect the dev fee
back to your wallet work.



It just means you're too noob to make cheats work. Cheats still work. Thats what claymore had been trying to solve since implementing 11.2 (I mean every update). the rest are just bling blings and competiion.
legendary
Activity: 1498
Merit: 1030
version 11.4-11.6 doesn't work with 8 NVIDIA video cards in system win7.
just closes when the program starts...
how can you solve the problem?

From what I've read Windows 7 will only manage 6 GPUs, try it out and see if your rig works with 6 cards.
If it works with 6 and not 8 then upgrade to Windows 10.

Windows 7 has issues with anything more than 4 GPUs - sometimes 5 if you're lucky, and there was a site that showed how to "patch" the drivers to work with more but that site has been down for a while.

I believe the same limit applied to 8/8.1 but I gave up on 8 a couple years ago when the UNUSABLE INTERFACE wasted 6 hours of my time trying to do one SIMPLE thing (FIND the pre-installed mining software and configure it and RUN it) and wouldn't let me do so no matter what I tried, causing me to blow 8 off the system entirely and replace it with XUbuntu (took me perhaps ONE HOUR to do a "from scratch" install, do all the needed updates, install drivers, install mining software, and have the system MINING - and I could have done it faster had I been paying 100% attention to the system).

I recommend a move to LINUX, which is currently running 7 various mixed Nvidia cards on my ASUS B250 Mining board under the 384.98 drivers with no issues (other than a KNOWN "doesn't report the power limit data correctly" bug with 1050 and/or 1050 ti cards but you can still SET the power limit and it works).

sr. member
Activity: 574
Merit: 261
version 11.4-11.6 doesn't work with 8 NVIDIA video cards in system win7.
just closes when the program starts...
how can you solve the problem?

From what I've read Windows 7 will only manage 6 GPUs, try it out and see if your rig works with 6 cards.
If it works with 6 and not 8 then upgrade to Windows 10.
legendary
Activity: 1030
Merit: 1006
Hi

Can anybody help me with what might cause claymore to be unable to read the GPU temperature and the fan turned?
And at the same time, the vga parameter settings entered in config.txt will not work!
fully reinstalled Windows 10 pro 64 bit activated official
AMD Driver for: Win10-64Bit-Radeon-Software-Adrenalin-Edition-18.3.1-March5
AMD settings are set to all hands because it has already worked.
Thanks for your help and sorry if I do not write well for a google translator!
Get last DDU, disconnect network, ddu ( safe mode) and reinstall driver ( you may go with 18.3.4 now). Connect  network and try
newbie
Activity: 1
Merit: 0
Hi

Can anybody help me with what might cause claymore to be unable to read the GPU temperature and the fan turned?
And at the same time, the vga parameter settings entered in config.txt will not work!
fully reinstalled Windows 10 pro 64 bit activated official
AMD Driver for: Win10-64Bit-Radeon-Software-Adrenalin-Edition-18.3.1-March5
AMD settings are set to all hands because it has already worked.
Thanks for your help and sorry if I do not write well for a google translator!
Jump to: