Bitcointalk Mobile Browser presented by IRLBTC™

<< >> (p.514)

Author

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

wpsd

Newbie

Offline

Activity: 41
Merit: 0

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 01:09:02 AM

#10261

Hi. Claymore

Could you add current pool worker info from "miner_getstat1" API, currently it only show the active pool

What format you use for sending and receiving data in "miner_getfile" API, the data is encoded

PPOC

Hero Member

Offline

Activity: 575
Merit: 500

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 04:42:09 AM

#10262

Quote from: Elder III on May 05, 2017, 09:20:29 PM

Quote from: PPOC on May 05, 2017, 05:44:32 PM

Quote from: AzzAz on May 05, 2017, 05:30:37 PM

Quote from: jackbox on May 05, 2017, 04:59:22 PM

Quote from: AzzAz on May 05, 2017, 04:27:39 PM

Quote from: jackbox on May 05, 2017, 02:44:23 PM

Quote from: notbatman on May 05, 2017, 02:12:57 PM

I seem to have an issue, well two issues.

#1 the miner crashes/freezes after it exits or the watchdog restarts it and I can't figure out why.

#2 here's a the log file of the GPUs halting and the miner restarting. Why did the GPUs stop, I can't figure out why? It crashed/froze after it restarted and I lost many hours of mining time.

Code:

00:23:58:748 3cff9700 parse packet: 236
00:23:58:748 3cff9700 ETH: job changed
00:23:58:748 3cff9700 new buf size: 0
00:23:58:748 3cff9700 ETH: 05/05/17-00:23:58 - New job from musicoin.nomnom.technology:9999
00:23:58:748 3cff9700 target: 0x0000000225c17d04 (diff: 2000MH), epoch #13
00:23:58:748 3cff9700 ETH - Total Speed: 98.703 Mh/s, Total Shares: 1080, Rejected: 2, Time: 06:02
00:23:58:748 3cff9700 ETH: GPU0 15.153 Mh/s, GPU1 19.916 Mh/s, GPU2 21.565 Mh/s, GPU3 21.514 Mh/s, GPU4 20.555 Mh/s
00:23:58:748 3cff9700 DCR - Total Speed: 5922.173 Mh/s, Total Shares: 1150, Rejected: 3
00:23:58:748 3cff9700 DCR: GPU0 909.169 Mh/s, GPU1 1194.958 Mh/s, GPU2 1293.899 Mh/s, GPU3 1290.819 Mh/s, GPU4 1233.328 Mh/s
00:23:58:888 68a84740 GPU0 t=62C fan=90%, GPU1 t=63C fan=84%, GPU2 t=61C fan=43%, GPU3 t=59C fan=40%, GPU4 t=62C fan=40%
00:23:58:888 68a84740 em hbt: 1, dm hbt: 1, fm hbt: 1,
00:23:58:888 68a84740 watchdog - thread 0, hb time 2758
00:23:58:888 68a84740 watchdog - thread 1, hb time 2794
00:23:58:888 68a84740 watchdog - thread 2, hb time 2801
00:23:58:888 68a84740 watchdog - thread 3, hb time 2775
00:23:58:889 68a84740 watchdog - thread 4, hb time 2775
00:23:58:889 68a84740 watchdog - thread 5, hb time 2799
00:23:58:889 68a84740 watchdog - thread 6, hb time 2771
00:23:58:889 68a84740 watchdog - thread 7, hb time 2796
00:23:58:889 68a84740 watchdog - thread 8, hb time 2809
00:23:58:889 68a84740 watchdog - thread 9, hb time 2783
00:23:59:318 3cff9700 ETH: checking pool connection...
00:23:59:318 3cff9700 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

00:23:59:352 3cff9700 got 237 bytes
00:23:59:352 3cff9700 buf: {"id":3,"jsonrpc":"2.0","result":["0xadeb49a0172a832df58961677253b80dbd44e1be76f0d1dc9743b9f55427fbe0","0x9b1ca7a86d339a3f175e48937848ac1cc012678e046b8c433a226d06f0f9bf9b","0x0225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"]}

00:23:59:352 3cff9700 parse packet: 236
00:23:59:352 3cff9700 ETH: job is the same
00:23:59:352 3cff9700 new buf size: 0
00:24:03:769 3dffb700 GPU4 DAG creation time - 5018 ms
00:24:03:769 3dffb700 Setting DAG epoch #121 for GPU4 done
00:24:03:769 3dffb700 DevFee: restart timer because of updating DAG
00:24:03:769 5544e700 Setting DAG epoch #121 for GPU1
00:24:07:855 3cff9700 send: {"id":6,"worker":"linux","jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x139a9fb", "0x000000000000000000000000000000000000000000000000000000003a79d94e"]}

00:24:07:889 3cff9700 got 39 bytes
00:24:07:889 3cff9700 buf: {"id":6,"jsonrpc":"2.0","result":true}

00:24:07:889 3cff9700 parse packet: 38
00:24:07:889 3cff9700 new buf size: 0
00:24:08:763 5544e700 GPU1 DAG creation time - 4894 ms
00:24:08:763 5544e700 Setting DAG epoch #121 for GPU1 done
00:24:08:763 5544e700 DevFee: restart timer because of updating DAG
00:24:08:763 3f7fe700 Setting DAG epoch #121 for GPU2
00:24:09:319 3cff9700 ETH: checking pool connection...
00:24:09:319 3cff9700 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

00:24:09:354 3cff9700 got 237 bytes
00:24:09:354 3cff9700 buf: {"id":3,"jsonrpc":"2.0","result":["0xadeb49a0172a832df58961677253b80dbd44e1be76f0d1dc9743b9f55427fbe0","0x9b1ca7a86d339a3f175e48937848ac1cc012678e046b8c433a226d06f0f9bf9b","0x0225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"]}

00:24:09:354 3cff9700 parse packet: 236
00:24:09:354 3cff9700 ETH: job is the same
00:24:09:354 3cff9700 new buf size: 0
00:24:10:864 5544e700 ETH: put share nonce 289644a40270f06d
00:24:10:864 5544e700 DevFee: ETH round found 1 shares
00:24:10:864 3bff7700 DevFee: ETH: 05/05/17-00:24:10 - SHARE FOUND - (GPU 1)
00:24:10:864 3bff7700 send: {"id":4,"method":"eth_submitWork","params":["0x289644a40270f06d","0xd3fceb4972e2bb316d331c1ac07c817488888b6fbea6fca37f6bcce90a169121","0x479ed8ffc20b8e8989ea6ac9dd0d411f394bd07777174f2c774a65a4d2f5a815"]}

00:24:10:961 3bff7700 got 39 bytes
00:24:10:961 3bff7700 buf: {"id":4,"jsonrpc":"2.0","result":true}

00:24:10:961 3bff7700 parse packet: 38
00:24:10:961 3bff7700 ETH: Share accepted (96 ms)!

00:24:10:961 3bff7700 new buf size: 0
00:24:10:980 3bff7700 got 248 bytes
00:24:10:980 3bff7700 buf: {"id":0,"jsonrpc":"2.0","result":["0x2cf04207cd9afbc1e426cda6b5e286ca84d6986fe0f5aa063a7d398af9b661b5","0x064ef82d7269405eb06162f7d33f2b6aa2a23741c9a0d06a648460e17b48ab4c","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x37bf46"]}

00:24:10:980 3bff7700 parse packet: 247
00:24:10:980 3bff7700 ETH: job changed
00:24:10:980 3bff7700 new buf size: 0
00:24:10:980 3bff7700 DevFee: ETH: 05/05/17-00:24:10 - New job from us1.ethpool.org:3333
00:24:10:980 3bff7700 target: 0x0000000112e0be82
00:24:13:879 3f7fe700 GPU2 DAG creation time - 5017 ms
00:24:13:879 3f7fe700 Setting DAG epoch #121 for GPU2 done
00:24:13:879 3f7fe700 DevFee: restart timer because of updating DAG
00:24:13:879 3e7fc700 Setting DAG epoch #121 for GPU3
00:24:16:907 68a84740 Got incorrect temperature 511, ignore
00:24:16:907 68a84740 Got incorrect temperature 511, ignore
00:24:16:907 68a84740 Got incorrect temperature 511, ignore
00:24:16:908 68a84740 Got incorrect temperature 511, ignore
00:24:19:321 3cff9700 ETH: checking pool connection...
00:24:19:321 3cff9700 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

00:24:19:357 3cff9700 got 237 bytes
00:24:19:357 3cff9700 buf: {"id":3,"jsonrpc":"2.0","result":["0xadeb49a0172a832df58961677253b80dbd44e1be76f0d1dc9743b9f55427fbe0","0x9b1ca7a86d339a3f175e48937848ac1cc012678e046b8c433a226d06f0f9bf9b","0x0225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"]}

00:24:19:357 3cff9700 parse packet: 236
00:24:19:357 3cff9700 ETH: job is the same
00:24:19:357 3cff9700 new buf size: 0
00:24:19:494 3cff9700 got 237 bytes
00:24:19:495 3cff9700 buf: {"id":0,"jsonrpc":"2.0","result":["0x3c2c66c4303add4353de34af2e76d112c2907f95e17ebd94372d57484596e0e4","0x9b1ca7a86d339a3f175e48937848ac1cc012678e046b8c433a226d06f0f9bf9b","0x0225c17d04dad2965cc5a02a23e254c0c3f75d9178046aeb27ce1ca574"]}

00:24:19:495 3cff9700 parse packet: 236
00:24:19:495 3cff9700 ETH: job changed
00:24:19:495 3cff9700 new buf size: 0
00:24:19:495 3cff9700 ETH: 05/05/17-00:24:19 - New job from musicoin.nomnom.technology:9999
00:24:19:495 3cff9700 target: 0x0000000225c17d04 (diff: 2000MH), epoch #13
00:24:19:495 3cff9700 ETH - Total Speed: 0.000 Mh/s, Total Shares: 1080, Rejected: 2, Time: 06:03
00:24:19:495 3cff9700 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
00:24:19:495 3cff9700 DCR - Total Speed: 0.000 Mh/s, Total Shares: 1150, Rejected: 3
00:24:19:495 3cff9700 DCR: 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
00:24:19:910 68a84740 Got incorrect temperature 511, ignore
00:24:19:910 68a84740 Got incorrect temperature 511, ignore
00:24:19:910 68a84740 Got incorrect temperature 511, ignore
00:24:19:910 68a84740 Got incorrect temperature 511, ignore
00:24:20:012 3bff7700 got 248 bytes
00:24:20:012 3bff7700 buf: {"id":0,"jsonrpc":"2.0","result":["0xe22b4abeb25b318936269369f09a2b7f3fee6ab4d84512e5d2490fc7444e1e5d","0x064ef82d7269405eb06162f7d33f2b6aa2a23741c9a0d06a648460e17b48ab4c","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x37bf47"]}

Same things happens to me so I used "-r 1" with a reboot. bat and the miner reboots my computer instead of restarting and hanging.

Mind to share your reboot.bat file ?
And- I had same "incorrect temp 511" log, riser was burning @ molex, yellow (12V ) pin...
Your cards are overburdened.

It is on the OP under the -r option. Claymore tells you what to put in the reboot.bat to execute a reboot. Just go to page 1 and the first post and look for it.

so your reboot.bat contains "shutdownrt 5f" ? Because that is where you pointed me.
See, I try to be helpful sharing my experience with you. From other side you tell me to read OP? Next time you ask for advice/help I will point you to page 1.

@PPOC: Temps?

Temp runs 88-92, warmer then I'd like but don't think it throttles till 95. Suprised on the temp with an EK block on it with a 3 fan Rad.

I'd not bother mining Eth+DCR with a GTX 1080, you will get much better results mining ZCASH on that GPU. ZCASH also runs cooler and uses less power, so that may solve your temperature issue as well as bringing in more $.

Turns out have a defective temp sensor on the GPU, I checked the liquid temps (with thermometer) and also CPU temp (via CPUz) in the same loop which is right after GPU and in the 60's while the GPU was going to 93 within minutes of miner starting. Did and RMA and should have new card next week, since I have to take apart the water block, will flush out and check for any buildup on the block also.

Thank you for all the comments!

BTC: 1Bo6YsPeHCrVRygHLJg9BwHeaLSQpppcJi
"Lost coins only make everyone elses coins worth slightly more. Think of it as a donation to everyone."

Havane

Jr. Member

Offline

Activity: 76
Merit: 3

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 05:39:04 AM

#10263

Hi

I have the EVGA SuperNOVA 1000W GOLD GQ (210GQ1000V2) power supply. It's a 80+ GOLD 1000W, with 92% (220VAC~240VAC) efficiency or higher under typical loads

Is it safe to stay at 1070w from the wall all day long ? Can I go up to 1100w ?

PPOC

Hero Member

Offline

Activity: 575
Merit: 500

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 05:41:30 AM

#10264

Quote from: Havane on May 07, 2017, 05:39:04 AM

Hi

I have the EVGA SuperNOVA 1000W GOLD GQ (210GQ1000V2) power supply. It's a 80+ GOLD 1000W.

Is it safe to stay at 1070w from the wall all day long ? Can I go up to 1100w ?

That kind of load I would use a 1300w PSU, you are getting crap efficiency pushing it to 1070w and will not last long at that load. You want to be at 80% load so a 1000w PSU should be 800w.

BTC: 1Bo6YsPeHCrVRygHLJg9BwHeaLSQpppcJi
"Lost coins only make everyone elses coins worth slightly more. Think of it as a donation to everyone."

ultimate360

Newbie

Offline

Activity: 2
Merit: 0

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 06:18:31 AM

#10265

So I was getting 27MH with my RX480. I just replaced it with a new RX580 and now my hashrate is only 21MH and won't go higher. This is using the same driver version and version of the miner (9.3), I have already attempted a clean driver reinstall with no luck. This hurts me seeing a newer and faster polaris card running quite a bit slower, it doesn't make sense. Any suggestions for why this might be?

boysie

Newbie

Offline

Activity: 43
Merit: 0

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 06:44:00 AM

#10266

hi Claymore

I'm not sure at what point this started happening but it seems the mclock and cclock settings when applied are not used until you stop and restart the miner, my guess is because they are applied too late and the GPU is already in use.

this results in tweaking actually being quite difficult.

this might be driver related but not sure. it does seems to apply just not get used and I'm guessing its because its basically in use 100% by the time it applies.

I've also seen 1 card take the setting and others not, again its a timing thing just getting there to late to effect the card before the miner kicks off.

I'm using 9.3 and RX480s, I'm using dual ETH/DCR ASM mode

I have noticed it starts a lot quicker with ASM so maybe that's why this is happening now.

Thanks

Boysie

ultimate360

Newbie

Offline

Activity: 2
Merit: 0

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 07:32:26 AM

#10267

Quote from: Strugus on May 07, 2017, 07:17:02 AM

Quote from: ultimate360 on May 07, 2017, 06:18:31 AM

It sounds like you were using a modded 480 and are now using a non modded 580?
What are your settings for the cards?

They both have the factory bios, I haven't touched them. The only thing I've done is raise the clock speeds a little higher on the core and memory on both. If I left both at stock, I'd have about 25 on the 480, but only 18 on the 580, it's just weird.

louklouk

Newbie

Offline

Activity: 4
Merit: 0

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 07:38:31 AM

#10268

I have 34.4 Mh/s with r9 290 ( 1220Mhz 1600 Mhz + 50 +100 ) with 17.5.1 catalyst but when I switch on 15.12 I lose so I guess I have to stay on the last ? Thx

Arnoldent

Newbie

Offline

Activity: 64
Merit: 0

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 08:46:41 AM

#10269

Quote from: louklouk on May 07, 2017, 07:38:31 AM

I have 34.4 Mh/s with r9 290 ( 1220Mhz 1600 Mhz + 50 +100 ) with 17.5.1 catalyst but when I switch on 15.12 I lose so I guess I have to stay on the last ? Thx

Stay with that one.

Ursul0

Sr. Member

Offline

Activity: 857
Merit: 262

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 12:08:15 PM

#10270

Quote from: sonerbo on May 06, 2017, 06:31:29 PM

@Claymore hi!!!

I have some 2gb cards and they can mine exp, musicoin , ubiq ect... and i can make Profit ! İf ı add -nofee 1 no problem miner works . Otherwise miner stops when try to mine eth for you. Can u fix that issue ?? I am sure lots of ppl has 2gb cards and needs this. Thx !!!

google DAG file

avirdoz

Legendary

Offline

Activity: 1190
Merit: 1001

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 12:56:54 PM

#10271

Sometime EthMan stops work properly - show all rigs offline and if i try close there are error message "Cannot terminate an externally created thread". Need kill and restart process via ProcessExplorer.

Claymore (OP)

Donator
Legendary

Offline

Activity: 1610
Merit: 1325

Miners developer

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 02:02:55 PM

#10272

Quote from: sonerbo on May 06, 2017, 06:31:29 PM

@Claymore hi!!!
I have some 2gb cards and they can mine exp, musicoin , ubiq ect... and i can make Profit ! İf ı add -nofee 1 no problem miner works . Otherwise miner stops when try to mine eth for you. Can u fix that issue ?? I am sure lots of ppl has 2gb cards and needs this. Thx !!!

Try "-allcoins exp" option.

Quote from: avirdoz on May 07, 2017, 12:56:54 PM

How many rigs in EthMan do you have?
Currently I'm rewriting some parts of EthMan, network routines too, probably it will help.

Please read Readme and FAQ in the first post of this thread before asking any questions, probably the answer is already there.
List of my miners: https://bt.irlbtc.com/view/3019607

sigb0y

Member

Offline

Activity: 79
Merit: 10

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 02:06:31 PM

#10273

@Claymore

I have a problem with one of my RX480 cards. In the log I see before every crash the same message:

Code:

WATCHDOG: GPU 1 hangs in OpenCL call

Now I want to find out which of my GPUs this is! When I start claymore with the parameter "DI -1", can I be sure that it is directly pointing to GPU 1 or does the ordering changes?

keep mining or die trying

tuckker

Newbie

Offline

Activity: 2
Merit: 0

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 02:46:38 PM

#10274

Using 6 units of RX480 8GB, i noticed that if I mine ETH only, i can get a total of speed of 130Mh/s.

If i mine both ETH and Nicehash, my ETH speed is only 115Mh/s.

Is this expected?

kisk

Full Member

Offline

Activity: 126
Merit: 100

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 03:55:49 PM

#10275

New rig: I'm having an issue with HR dropping by 25%-75% for a second or two about every 10 seconds, sometimes less. NOTE: This is NOT the 9.x issue with dual mining where random cards drop 5-10Mh/s -- my problem happens with ETH only and 8.1 as well, and HR drops on ALL cards. I'll be a thorough as possible here. I hate when people post questions with little info:

Win10
AMD 16.12.2
CPU: Athlon II 170u 2Ghz (single core)
MOBO: Gigabyte 990FXA-UD3 R5 (all unnecessary options turned off)
8GB DDR3 (timings set correctly)
25GB VRam
60GB SSD
3x Gigabyte RX480 8GB (1750 straps)
3x Powercolor Red Devil RX480 8gb (1750 straps)

EthDcrMiner64.exe -epool us-east.ethash-hub.miningpoolhub.com:20535 -ewal user.rig02 -epsw x -ethi 16 -esm 3 -asm 1 -allpools 1 -mport XXXX -r 1 -di 530142 -dcri 10 -cclock 1145,1145,1145,1156,1167,1167 -cvddc 1037,918,1087,1031,1043,1037 -mclock 2150,2150,2150,2175,2175,2175

180Mh/s

The logs don't show me anything in particular out of the ordinary except for the drop in HR. I though it might be a power issue so I distributed the rig with 2 PSU's which didn't change anything. Tried 8.1, 9.0, 9.3. Set cards to default clocks. Tried ASM 0,1,2. multiple ETHI/DCRI values. Same. I did disconnect all 3 red devils and that fixed the issue. As soon as I connect a 4th GPU it starts happening again.

Couple things I'm thinking:
1) Maybe the CPU is too weak to keep up with certain functions? I have an Athlon 3.0ghz dual core on the way to test.
2) This motherboard does not have any settings for changing PCI-e options, gen1/gen2/gen3/Lat/etc. Maybe the lane bandwidth is hiccuping somewhere? I would think even 4 cards should be fine though, which its not.
3) I hot swapped this Win10 install from another rig (intel) and let Win10 reconfigure everything. Installed new drivers, and fresh installed video drivers. Maybe I'll try a full reinstall, or linux.
4) I don't think its a riser issue and it effects all the cards..

Hoping someone may see something I don't. Thanks for your help!!

Here are some logs:

GPU-z:
http://pasteboard.co/3rTLmaN7W.png

Code:

[b]10:21:54:543 544 ETH - Total Speed: 180.803 Mh/s, Total Shares: 23, Rejected: 0, Time: 00:12
10:21:54:593 544 ETH: GPU0 29.793 Mh/s, GPU1 26.330 Mh/s, GPU2 26.394 Mh/s, GPU3 30.455 Mh/s, GPU4 30.157 Mh/s, GPU5 30.241 Mh/s[/b]
10:21:57:749 169c recv: 51
10:21:57:749 169c srv pck: 50
10:21:57:952 169c srv bs: 0
10:21:57:968 169c sent: 241
10:22:02:483 82c recv: 51
10:22:02:483 82c srv pck: 50
10:22:02:655 82c srv bs: 0
10:22:02:671 82c sent: 241
10:22:07:140 544 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xa074716", "0x00000000000000000000000000000000000000000000000000000000bf453132"]}

10:22:07:280 544 got 36 bytes
10:22:07:327 544 buf: {"id":6,"result":true,"error":null}

10:22:07:374 544 parse packet: 35
10:22:07:421 544 new buf size: 0
10:22:07:499 544 got 195 bytes
10:22:07:515 544 buf: {"id":null,"method":"mining.notify","params":["d70e","e586ce62651f6de0be923da595f6773a2d1bd9b41ca0ad927456061ed15c0a14","782e4b91007316a5d95c60f5fdba91557a12f49b5aeaf6b2699087d95feaa3da",false]}

10:22:07:515 544 parse packet: 194
10:22:07:530 544 ETH: job changed
10:22:07:530 544 new buf size: 0
10:22:07:546 544 ETH: 05/07/17-10:22:07 - New job from us-east.ethash-hub.miningpoolhub.com:20535
10:22:07:561 544 target: 0x0000000112dfaba1 (diff: 4000MH), epoch #122
[b]10:22:07:561 544 ETH - Total Speed: 139.031 Mh/s, Total Shares: 23, Rejected: 0, Time: 00:13
10:22:07:587 544 ETH: GPU0 21.107 Mh/s, GPU1 23.758 Mh/s, GPU2 23.802 Mh/s, GPU3 23.707 Mh/s, GPU4 23.303 Mh/s, GPU5 23.354 Mh/s[/b]
10:22:07:603 e3c recv: 51
10:22:07:634 730 ETH: put share nonce 22c0000a400e00
10:22:07:634 e3c srv pck: 50
10:22:07:650 730 ETH round found 1 shares
10:22:07:665 544 ETH: Stale share found
10:22:07:712 544 ETH: 05/07/17-10:22:07 - SHARE FOUND - (GPU 4)
10:22:07:728 544 send: {"id": 4, "method": "mining.submit", "params": ["kisk.rig02","d70d","c0000a400e00"]}

10:22:07:806 544 got 36 bytes
10:22:07:806 544 buf: {"id":4,"result":true,"error":null}

10:22:07:821 544 parse packet: 35
10:22:07:821 544 ETH: Share accepted (94 ms)!
10:22:07:837 544 new buf size: 0
10:22:07:929 e3c srv bs: 0
10:22:07:929 e3c sent: 241
10:22:11:445 ff0 GPU0 t=64C fan=64%, GPU1 t=62C fan=65%, GPU2 t=68C fan=66%, GPU3 t=56C fan=63%, GPU4 t=60C fan=62%, GPU5 t=64C fan=65%
10:22:11:460 ff0 em hbt: 0, fm hbt: 16,
10:22:11:476 ff0 watchdog - thread 0, hb time 250
10:22:11:493 ff0 watchdog - thread 1, hb time 656
10:22:11:493 ff0 watchdog - thread 2, hb time 656
10:22:11:509 ff0 watchdog - thread 3, hb time 250
10:22:11:509 ff0 watchdog - thread 4, hb time 656
10:22:11:525 ff0 watchdog - thread 5, hb time 250
10:22:11:525 ff0 watchdog - thread 6, hb time 687
10:22:11:540 ff0 watchdog - thread 7, hb time 297
10:22:11:540 ff0 watchdog - thread 8, hb time 109
10:22:11:556 ff0 watchdog - thread 9, hb time 562
10:22:11:556 ff0 watchdog - thread 10, hb time 781
10:22:11:571 ff0 watchdog - thread 11, hb time 390
10:22:11:587 1104 ETH: put share nonce 22d55557ac76d5
10:22:11:587 1104 ETH round found 1 shares
10:22:11:603 544 ETH: 05/07/17-10:22:11 - SHARE FOUND - (GPU 5)
10:22:11:618 544 send: {"id": 4, "method": "mining.submit", "params": ["kisk.rig02","d70e","d55557ac76d5"]}

10:22:11:706 544 got 36 bytes
10:22:11:706 544 buf: {"id":4,"result":true,"error":null}

10:22:11:722 544 parse packet: 35
10:22:11:722 544 ETH: Share accepted (94 ms)!
10:22:11:738 544 new buf size: 0
10:22:12:964 a4c recv: 51
10:22:12:964 a4c srv pck: 50
10:22:13:152 a4c srv bs: 0
10:22:13:152 a4c sent: 241
10:22:14:277 544 got 195 bytes
10:22:14:277 544 buf: {"id":null,"method":"mining.notify","params":["d70f","e586ce62651f6de0be923da595f6773a2d1bd9b41ca0ad927456061ed15c0a14","565c37529fd81168f3f2488c2b99dfbc8ec533c1f4e2aaae613b73df1c71df88",false]}

10:22:14:292 544 parse packet: 194
10:22:14:292 544 ETH: job changed
10:22:14:308 544 new buf size: 0
10:22:14:323 544 ETH: 05/07/17-10:22:14 - New job from us-east.ethash-hub.miningpoolhub.com:20535
10:22:14:323 544 target: 0x0000000112dfaba1 (diff: 4000MH), epoch #122
[b]10:22:14:350 544 ETH - Total Speed: 180.698 Mh/s, Total Shares: 25, Rejected: 0, Time: 00:13
10:22:14:366 544 ETH: GPU0 29.070 Mh/s, GPU1 29.020 Mh/s, GPU2 28.926 Mh/s, GPU3 30.461 Mh/s, GPU4 29.413 Mh/s, GPU5 30.531 Mh/s[/b]
10:22:17:475 91c recv: 51
10:22:17:491 91c srv pck: 50
10:22:17:663 91c srv bs: 0
10:22:17:663 91c sent: 241
10:22:22:709 1404 recv: 51
10:22:22:725 1404 srv pck: 50
10:22:22:897 1404 srv bs: 0
10:22:22:897 1404 sent: 241
10:22:26:928 1108 ETH: put share nonce 2215555ff0ef45
10:22:26:944 1108 ETH round found 1 shares
10:22:26:959 544 ETH: 05/07/17-10:22:26 - SHARE FOUND - (GPU 0)
10:22:26:959 544 send: {"id": 4, "method": "mining.submit", "params": ["kisk.rig02","d70f","15555ff0ef45"]}

10:22:27:053 544 got 36 bytes
10:22:27:053 544 buf: {"id":4,"result":true,"error":null}

10:22:27:068 544 parse packet: 35
10:22:27:068 544 ETH: Share accepted (94 ms)!
10:22:27:084 544 new buf size: 0
10:22:27:162 544 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xaa1203c", "0x00000000000000000000000000000000000000000000000000000000bf453132"]}

10:22:27:240 544 got 36 bytes
10:22:27:240 544 buf: {"id":6,"result":true,"error":null}

10:22:27:256 544 parse packet: 35

sNaKeyz0r91

Member

Offline

Activity: 131
Merit: 10

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 04:37:23 PM

#10276

Quote from: sNaKeyz0r91 on May 05, 2017, 06:41:36 PM

Hi Claymore,
I have this error just before miner restarts. Sometimes after 50+ hours, sometimes after 20-30 hours of mining. I use Nicehash miner.
This is a peak to the log file:

[2017-05-05 20:26:50] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] READ SPEED ZERO, will cool up
[2017-05-05 20:26:50] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Cooling UP, cool time is 10000 ms
[2017-05-05 20:27:00] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] READ SPEED ZERO, will cool up
[2017-05-05 20:27:00] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Cooling UP, cool time is 20000 ms
[2017-05-05 20:27:20] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] READ SPEED ZERO, will cool up
[2017-05-05 20:27:20] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Cooling UP, cool time is 40000 ms
[2017-05-05 20:28:00] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] READ SPEED ZERO, will cool up
[2017-05-05 20:28:00] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Cooling UP, cool time is 80000 ms
[2017-05-05 20:28:25] [INFO] [NICEHASH] Balance get
[2017-05-05 20:28:27] [INFO] [NICEHASH] SMA get
[2017-05-05 20:29:20] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] READ SPEED ZERO, will cool up
[2017-05-05 20:29:20] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Cooling UP, cool time is 160000 ms
[2017-05-05 20:29:20] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] MAX cool time exceeded. RESTARTING
[2017-05-05 20:29:20] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Restarting miner..
[2017-05-05 20:29:20] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Shutting down miner
[2017-05-05 20:29:20] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] Trying to kill all miner processes for this instance:
[2017-05-05 20:29:20] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] Nothing to kill [pid(24904)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)], exMsg Process with an Id of 24904 is not running.
[2017-05-05 20:29:20] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] Trying to kill [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)]
[2017-05-05 20:29:20] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] Exception killing [pid(23228)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)], exMsg Access is denied
[2017-05-05 20:29:35] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] Starting miner [pid(32164)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] -di 01 -dcri 20,20 -asm 2,2 -epool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -ewal zzzxxxccc -mport 127.0.0.1:4000 -esm 3 -epsw x -allpools 1 -dcoin dcr -dpool stratum+tcp://decred.eu.nicehash.com:3354 -dwal cccxxxzzz -dbg -1
[2017-05-05 20:29:35] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(32164)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Starting cooldown checker
[2017-05-05 20:29:40] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid(32164)|bin(bin_3rdparty\claymore_dual\EthDcrMiner64.exe)] Cooling UP, cool time is 10000 ms
[2017-05-05 20:29:40] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] GetSummary exception: No connection could be made because the target machine actively refused it 127.0.0.1:4000
[2017-05-05 20:29:45] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] GetSummary exception: No connection could be made because the target machine actively refused it 127.0.0.1:4000
[2017-05-05 20:29:50] [INFO] [ClaymoreDual-MINER_ID(0)-DEVICE_IDs(0,1)] [pid

Please?
Could you please tell me which could be the problem restarting the miner?

Thanks

ccminer.net

Sr. Member

Offline

Activity: 595
Merit: 251

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 04:45:46 PM

#10277

Is it possible to mine ZCLASSIC with this miner?

avirdoz

Legendary

Offline

Activity: 1190
Merit: 1001

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 05:00:14 PM

#10278

Quote from: Claymore on May 07, 2017, 02:02:55 PM

How many rigs in EthMan do you have?
Currently I'm rewriting some parts of EthMan, network routines too, probably it will help.

Ten rigs.
Btw can any one share h/r on nvidia 1070/1080 in dual mode?

delle54

Sr. Member

Offline

Activity: 307
Merit: 250

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 05:17:01 PM

#10279

Quote from: ccminer.net on May 07, 2017, 04:45:46 PM

Is it possible to mine ZCLASSIC with this miner?

No. See Claymore's ZCash AMD GPU Miner v12.4 (Windows/Linux).

Claymore (OP)

Donator
Legendary

Offline

Activity: 1610
Merit: 1325

Miners developer

Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.3 (Windows/Linux)

May 07, 2017, 05:20:54 PM

#10280

Quote from: sNaKeyz0r91 on May 07, 2017, 04:37:23 PM

Hi Claymore,
I have this error just before miner restarts. Sometimes after 50+ hours, sometimes after 20-30 hours of mining. I use Nicehash miner.
This is a peak to the log file:

This is not the log of my miner, so it is completely useless for me.

Quote from: sigb0y on May 07, 2017, 02:06:31 PM

@Claymore

I have a problem with one of my RX480 cards. In the log I see before every crash the same message:

Code:

WATCHDOG: GPU 1 hangs in OpenCL call

Now I want to find out which of my GPUs this is! When I start claymore with the parameter "DI -1", can I be sure that it is directly pointing to GPU 1 or does the ordering changes?

If you did not use "-di" when it showed this message, then "-di 1" will select the card you want to find. Another way is to start miner as usual and press "1" key to disable GPU1 and check its temperature after a minute, it will be cooler than others.

Please read Readme and FAQ in the first post of this thread before asking any questions, probably the answer is already there.
List of my miners: https://bt.irlbtc.com/view/3019607

Pages: « 1 ... 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 [514] 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 ... 1410 »

Page 513

Viewing Page: 514