Bitcoin Forum

I cant resolve this it start to mine then immediatly throw this error also other mining programs dont work it immidiately goes offline
here is error lines:
=== Last 50 lines of /var/log/miner/claymore/lastrun_reboot.log ===
21:24:38:819   64bff700   GPU 0, GpuMiner cu_k1 failed 73, an illegal instruction was encountered
21:24:38:819   64bff700   GPU 0, GpuMiner kx failed 1
21:24:38:819   64bff700   Set global fail flag, failed GPU0
21:24:38:820   64bff700   GPU 0 failed
21:24:38:879   5effd700   GPU 1, GpuMiner cu_kd failed 73 (31), an illegal instruction was encountered
21:24:38:879   5effd700   GPU 1, Calc DAG failed!
21:24:42:379   5effd700   Set global fail flag, failed GPU1
21:24:42:379   5effd700   GPU 1 failed
21:24:42:379   5f7fe700   Setting DAG epoch #179 for GPU1
21:24:42:379   5f7fe700   GPU 1, CUDA error 73 - cannot write buffer for DAG

21:24:45:329   597f2700   buf: {"id":0,"jsonrpc":"2.0","result":["0x43850bb7fda14d56d2b47996c041dbb51380dcfd265f9676573facee674fe009","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"]}

21:24:45:329   597f2700   ETH: 04/06/18-21:24:45 - New job from eth.2miners.com:2020
21:24:45:329   597f2700   target: 0x0000000112e0be82 (diff: 4000MH), epoch 179(2.40GB)
21:24:45:329   597f2700   ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
21:24:45:329   597f2700   ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s, GPU6 0.000 Mh/s
21:24:45:379   5f7fe700   Set global fail flag, failed GPU1
21:24:45:379   5f7fe700   GPU 1 failed
21:24:46:632   597f2700   sent: {"id":6,"worker":"8_gtx_1060_6gb","jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x000000000000000000000000000000000000000000000000000000001f94060f"]}

21:24:46:633   597f2700   ETH: checking pool connection...
21:24:46:633   597f2700   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

21:24:46:678   597f2700   buf: {"id":6,"jsonrpc":"2.0","result":true}

21:24:46:725   597f2700   buf: {"id":3,"jsonrpc":"2.0","result":["0x43850bb7fda14d56d2b47996c041dbb51380dcfd265f9676573facee674fe009","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"]}

21:24:49:180   597f2700   buf: {"id":0,"jsonrpc":"2.0","result":["0xfc67448f1927f874c0de7d773dbff5ec71065fb5c9d80123606a8b1b7c2c0542","0xa74dd84414948aba4bfd6580908dbf9c32a494aa336609746d19a35bb4cccb24","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba"]}

21:24:49:180   597f2700   ETH: 04/06/18-21:24:49 - New job from eth.2miners.com:2020
21:24:49:180   597f2700   target: 0x0000000112e0be82 (diff: 4000MH), epoch 179(2.40GB)
21:24:49:180   597f2700   ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
21:24:49:180   597f2700   ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s, GPU6 0.000 Mh/s
21:24:49:693   f5482700   em hbt: 1, fm hbt: 28,
21:24:49:693   f5482700   watchdog - thread 0 (gpu0), hb time 7314
21:24:49:693   f5482700   watchdog - thread 1 (gpu0), hb time 7314
21:24:49:693   f5482700   watchdog - thread 2 (gpu1), hb time 7314
21:24:49:693   f5482700   watchdog - thread 3 (gpu1), hb time 7314
21:24:49:693   f5482700   watchdog - thread 4 (gpu2), hb time 7314
21:24:49:693   f5482700   watchdog - thread 5 (gpu2), hb time 7314
21:24:49:693   f5482700   watchdog - thread 6 (gpu3), hb time 7314
21:24:49:693   f5482700   watchdog - thread 7 (gpu3), hb time 7314
21:24:49:693   f5482700   watchdog - thread 8 (gpu4), hb time 7314
21:24:49:693   f5482700   watchdog - thread 9 (gpu4), hb time 7314
21:24:49:693   f5482700   watchdog - thread 10 (gpu5), hb time 7314
21:24:49:693   f5482700   watchdog - thread 11 (gpu5), hb time 7314
21:24:49:693   f5482700   watchdog - thread 12 (gpu6), hb time 7314
21:24:49:693   f5482700   watchdog - thread 13 (gpu6), hb time 7314
21:24:49:693   f5482700   WATCHDOG: GPU error, you need to restart miner :(
21:24:49:693   f5482700   Rebooting
any ides?
And it never rebooted

I put my OC setting to stock still same error

I see you are running the miner in Linux. What kind of Linux operating system do you have ? If it is HiveOS , the Claymore miner is already configured , you just have to change your ethereum address and start mining.

Here is a good guide/tutorial for you to check and even if you are not in HiveOS you should switch to it. It recognized 12 AMD cards out of the box in Asus B250 Mining Expert motherboard.

https://2miners.com/blog/hive-os-linux-mining-platform-review/ (https://2miners.com/blog/hive-os-linux-mining-platform-review/)

You seem to have Nvidia Gtx 1060 3gb version as these cards are suffering from the dag epoch. You should try to mine Zcash and see if the same error happens.

yes its hive OS and all was configured and fine for some time... now this BS
and crazy thing is I have GTX 1060 6GB cards  doesn't make sense this DAG error!!!??? :(

If you have the 6GB cards should not be affected by the dag epoch. Try to change to another coin for example to Musicoin which has low difficulty and see if the same happens.

Here is what you need to put as a mining pool configuration, in the place where it says Musicoin address, put yours. You can get one from Cryptopia just to try mining as Cryptopia exchange doesn't let you mine to your deposit address but just for testing purposes.

EthDcrMiner64.exe -epool musicoin.nomnom.technology:9999 -ewal Musicoinaddress -epsw x -allpools 1 -allcoins 1


It can also be possible an outdated driver of your video cards is causing the Dag epoch error. Update to latest version.

hm but hive OS automatically update drivers no?
I even updated hive OS version to latest

Yes it is possible to manually install drivers

https://gist.github.com/wangruohui/df039f0dc434d6486f5d4d098aa52d07 (https://gist.github.com/wangruohui/df039f0dc434d6486f5d4d098aa52d07)

In Windows versions this error was fixed about 50% of the times only by updating to the latest Nvidia drivers as only these cards are suffering from that error. No errors of that kind reported by AMD cards.