Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)

[athas1985]

http://2.pik.vn/20170b5c0b2e-6891-454c-a393-69e343de3c3e.png
Help why gpu5 failed

Looks like you have overclocked. Remove it, install original bios und hopefully it would run stable. If not, you have destroyed your GPU.

no, i under lock
SP nitro+
1266 down to 1050

[Claymore]

@claymore:
1) Maybe I found a hint: Is it possible that it is some kind of IP address caching issue? It seems to happen to rigs which reboot and get another (dynamic) IP address. If I change the "IP" field in EthMan to the current numeric IP address or use an alternative DNS name which resolves to the same computer EthMan shows correct "up" state. If I change it to the old one its shown "down" again. Restarting EthMan seems to update these values and the rig ist shown online, even with the same old name ("IP" entry). Or it is some kind of update process which is only executed when adding/changing a rig entry. But maybe this helps...
2) Did you read my comment about retriggering above and understand my issue?

Please test this version:
https://mega.nz/#!C5xiUSYY!QY44OAExh5EQ2elGcH1DvfbkQMTkgMSwOEMLoG0lUCU
Let me know if you still have the issue.

DNS caching can cause some additional delays, but in a minute the lost rig must be found anyway.
I will add retriggering in next update.

Need advice from Mister Claymore or someone else.
I'm mining now at ethermine.org (Europe (France): eu1.ethermine.org:4444)
The pool uses diff 40M

My 3-4 cards rigs are doing fine, but I have 2 standalone comps with only one 30mhs card in each. And this one-card rigs have huge (5-15%) stale share rate reported by pool. all rigs have identical and fast Internet access with the multi-card rigs, 70-100ms latency to pool. Is it due to high pool diff and low (30mhs) rig speed? Is there a way to fix this without changing a pool? I can't move this cards to multi-card rigs ((
 
I'm using latest Claymore 9.5 but older versions seem to behave the same.
Thanx in advance

40M? May be 4000M? Stale shares can be caused by delays in new job broadcasts from pool side if the pool sends new jobs to faster miners firstly. Though it's just an idea.

[GH]

@claymore:
1) Maybe I found a hint: Is it possible that it is some kind of IP address caching issue? It seems to happen to rigs which reboot and get another (dynamic) IP address. If I change the "IP" field in EthMan to the current numeric IP address or use an alternative DNS name which resolves to the same computer EthMan shows correct "up" state. If I change it to the old one its shown "down" again. Restarting EthMan seems to update these values and the rig ist shown online, even with the same old name ("IP" entry). Or it is some kind of update process which is only executed when adding/changing a rig entry. But maybe this helps...
2) Did you read my comment about retriggering above and understand my issue?

Please test this version:
https://mega.nz/#!C5xiUSYY!QY44OAExh5EQ2elGcH1DvfbkQMTkgMSwOEMLoG0lUCU
Let me know if you still have the issue.

DNS caching can cause some additional delays, but in a minute the lost rig must be found anyway.
I will add retriggering in next update.

Thank you, downloaded, running and watching.

Maybe another hint: even with this EthMan version and CDM 9.5 this procedure can produce an identical looking error: Use EthMan to send a "Restart Miner" command to a "read only management port" rig. After a few seconds it will be shown offline (although the client refuses the command because management interface is in read-only mode and just keeps mining) and can not be brought back until EthMan is restarted or the "IP" field was changed like in my post above.

[wtfonly16]

WTF HE POST? THEN ITS NOT 10% SCAM!!!

[pedronesbr]

I HAVE A TROUBLE

09:15:49:337   1eac   This pool (eu1.ethermine.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
09:15:49:337   1eac   However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
09:15:49:337   1eac   Please read "Readme" file for details
09:15:49:337   1eac   This pool (eu1.ethermine.org) does not support Ethereum addresses as login (or requires worker name in "Login.Worker" format) and cannot be used for devfee mining, therefore it is not supported.
09:15:49:337   1eac   However, you can mine on this pool if you specify "-allpools 1" option, default pools (different from this pool) will be used for devfee.
09:15:49:353   1eac   Please read "Readme" file for details
09:15:49:353   1eac   Pool eu1.ethermine.org removed from the list
09:15:49:353   1eac   ETH: No pools specified! Specify at least one valid pool in "-epool" parameter.

SOMEONE CAN HELP?

[ivandel]

GeForce GTX 970 / WIN10

I'm using now QtMiner from ethermine.org
My .bat file: qtminer.exe -s eu1.ethermine.org:4444 -u 7c9dd56bf5d842246efecdf4af6c9d0bbe5d66d8.rig1 -G

but 3 days ago QtMiner get error "QtMiner.exe has stopped working".

Please, can you help me how to using Claymore with my Ethereum wallet 7c9dd56bf5d842246efecdf4af6c9d0bbe5d66d8

Thanks!

[Bob_chemist]

Please test this version:
https://mega.nz/#!C5xiUSYY!QY44OAExh5EQ2elGcH1DvfbkQMTkgMSwOEMLoG0lUCU
Let me know if you still have the issue.

The issue remains. Rig have restarted about half an hour ago, but EthMan shows that it stays offline. Choosing "view miner console" opens page with working rig.
I have static local ip on miner, so I think, the problem is not in dns

[MATHReX]

I've a VGA which doesn't dual mine at all even after removing most of the tweaks. I'm wondering if I can manage to dual mine 5 cards and single mine 1 card within the same instance of claymore rather than two different instances running because it causes a lot of fluctuations in MH and it keeps crashing after an hour or so. Any help will be appreciated. Thanks!

[FFI2013]

Does ethman work on 5XX cards in Linux or how to change clock setting I want to setup Ubuntu but I'm not that good with Linux

[biggee]

Hey guys,

Just upgraded all of my rigs from 9.3 to 9.5 (all AMD RX GPU's 470/480 4GB and 8GB / Win 10) and now I'm getting a worrying amount of rejected shares on both ETH and DCR across all rigs.

Example :
DCR - Total Shares : 4828 Rejected : 69
ETH - Total Shares : 5181 Rejected : 13

With v9.3 I was getting 0 rejected ETH shares and maybe the odd one or two every now and again on DCR.

I haven't adjusted any of my settings at all.

What's changed in the miner's code that could be causing this?

** Update **

Ran a test on one rig only mining ETH (no dual) and it's reporting 0 rejects after 3 hours so it looks like the issue is only when dual mining DCR. Maybe the intensity needs to be readjusted for 9.5?

[thameur]

  4 x R9 390 strix 8g Overclock No Voltage GPU tweak 2 for OC GPU Clock 1135 Mhz, +o mV, Memory Clock 6000 Mhz, Power target 150%,  After 6 months mining the hasrate drop from 129.2 Mh/s to 128.7 Mh/s, there is a risk with Overclocking long term card degradation and drop hasrate ? Temperature between 65 ° C to 72 ° C, connection with pool is ok, I have 6 months ago in mining ETH, ETC, ZEC with claymore V 8.1 ..

[mjkforum]

hey guys,

maybe someone can help me
so i'm mining for almost 3 weeks now with just an normal pc with a gtx 1060 (6gb)
But when i went back to my pc this morning, the program stopped completely and was shut down (the program, not the pc)

So I tried running it again but then it almost immediately stopped again, restarted my pc but still no luck

I did find out that windows defender had put Skeeyah.A!rfn in quarantine and according to windows defender it has something to do with the minder.

Could enyone help me so I can start mining again?

[derselben]

Guys are you getting with 280x previous 15mgh or it is down to 12.5 now?

4 x R9 390 strix 8g Overclock No Voltage GPU tweak 2 for OC GPU Clock 1135 Mhz, +o mV, Memory Clock 6000 Mhz, Power target 150%,  After 6 months mining the hasrate drop from 129.2 Mh/s to 128.7 Mh/s, there is a risk with Overclocking long term card degradation and drop hasrate ? Temperature between 65 ° C to 72 ° C, connection with pool is ok, I have 6 months ago in mining ETH, ETC, ZEC with claymore V 8.1 ..

Same with 7 x rx-480 sapphire, hasrate drop from 210.8 Mh/s to 209.9 Mh/s

[powerusa]

WHAY MY RIG IS GOING DOWN PLEASE LOOK AT THIS IS !@#$%%^ FOR ME:

08:03:02:473   1e18   GPU0 t=58C fan=73%, GPU1 t=63C fan=83%, GPU2 t=69C fan=96%, GPU3 t=64C fan=85%, GPU4 t=68C fan=91%
08:03:02:489   1e18   em hbt: 0, fm hbt: 62,
08:03:02:489   1e18   watchdog - thread 0 (gpu0), hb time 31
08:03:02:489   1e18   watchdog - thread 1 (gpu0), hb time 203
08:03:02:489   1e18   watchdog - thread 2 (gpu1), hb time 296
08:03:02:505   1e18   watchdog - thread 3 (gpu1), hb time 141
08:03:02:505   1e18   watchdog - thread 4 (gpu2), hb time 141
08:03:02:505   1e18   watchdog - thread 5 (gpu2), hb time 312
08:03:02:505   1e18   watchdog - thread 6 (gpu3), hb time 312
08:03:02:523   1e18   watchdog - thread 7 (gpu3), hb time 157
08:03:02:527   1e18   watchdog - thread 8 (gpu4), hb time 78
08:03:02:527   1e18   watchdog - thread 9 (gpu4), hb time 250
08:03:03:872   1f64   got 248 bytes
08:03:03:872   1f64   buf: {"id":0,"jsonrpc":"2.0","result":["0x03200243d25df57cd0f2ec5c5919481242a38dfaca86cc45ccf0e448b4b10ad7","0x3868abc5dcee23341dee7f75f1be7f90ca9904961fef9e0f102cedba1171408d","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3b152b"]}

08:03:03:888   1f64   parse packet: 247
08:03:03:904   1f64   ETH: job changed
08:03:03:920   1f64   new buf size: 0
08:03:03:925   1f64   ETH: 06/14/17-08:03:03 - New job from us1.ethermine.org:14444
08:03:03:926   1f64   target: 0x0000000112e0be82 (diff: 4000MH), epoch #129
08:03:03:926   1f64   ETH - Total Speed: 142.815 Mh/s, Total Shares: 89, Rejected: 0, Time: 00:37
08:03:03:926   1f64   ETH: GPU0 28.600 Mh/s, GPU1 28.564 Mh/s, GPU2 28.426 Mh/s, GPU3 28.592 Mh/s, GPU4 28.634 Mh/s
08:03:05:919   1f64   ETH: checking pool connection...
08:03:05:925   1f64   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

08:03:06:004   1f64   got 248 bytes
08:03:06:004   1f64   buf: {"id":3,"jsonrpc":"2.0","result":["0x03200243d25df57cd0f2ec5c5919481242a38dfaca86cc45ccf0e448b4b10ad7","0x3868abc5dcee23341dee7f75f1be7f90ca9904961fef9e0f102cedba1171408d","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3b152b"]}

08:03:06:027   1f64   parse packet: 247
08:03:06:027   1f64   ETH: job is the same
08:03:06:042   1f64   new buf size: 0
08:03:07:157   1c60   recv: 51
08:03:07:157   1c60   srv pck: 50
08:03:07:258   1c60   srv bs: 0
08:03:07:258   1c60   sent: 206
08:03:12:157   17bc   recv: 51
08:03:12:157   17bc   srv pck: 50
08:03:12:242   17bc   srv bs: 0
08:03:12:242   17bc   sent: 206
08:03:15:940   1f64   ETH: checking pool connection...
08:03:15:940   1f64   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

08:03:16:041   1f64   got 248 bytes
08:03:16:041   1f64   buf: {"id":3,"jsonrpc":"2.0","result":["0x03200243d25df57cd0f2ec5c5919481242a38dfaca86cc45ccf0e448b4b10ad7","0x3868abc5dcee23341dee7f75f1be7f90ca9904961fef9e0f102cedba1171408d","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3b152b"]}

08:03:16:041   1f64   parse packet: 247
08:03:16:041   1f64   ETH: job is the same
08:03:16:057   1f64   new buf size: 0
08:03:17:187   11a4   recv: 51
08:03:17:187   11a4   srv pck: 50
08:03:17:272   11a4   srv bs: 0
08:03:17:272   11a4   sent: 206
08:03:21:086   1f64   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x8866c0a", "0x000000000000000000000000000000000000000000000000000000008f29a7d8"]}

08:03:21:170   1f64   got 39 bytes
08:03:21:170   1f64   buf: {"id":6,"jsonrpc":"2.0","result":true}

08:03:21:170   1f64   parse packet: 38
08:03:21:186   1f64   new buf size: 0
08:03:22:222   10c4   recv: 51
08:03:22:222   10c4   srv pck: 50
08:03:22:323   10c4   srv bs: 0
08:03:22:323   10c4   sent: 206
08:03:25:969   1f64   ETH: checking pool connection...
08:03:25:981   1f64   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

08:03:26:056   1f64   got 248 bytes
08:03:26:062   1f64   buf: {"id":3,"jsonrpc":"2.0","result":["0x03200243d25df57cd0f2ec5c5919481242a38dfaca86cc45ccf0e448b4b10ad7","0x3868abc5dcee23341dee7f75f1be7f90ca9904961fef9e0f102cedba1171408d","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3b152b"]}

08:03:26:066   1f64   parse packet: 247
08:03:26:070   1f64   ETH: job is the same
08:03:26:075   1f64   new buf size: 0
08:03:35:995   1f64   ETH: checking pool connection...
08:03:36:011   1f64   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

08:03:41:561   1f64   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x000000000000000000000000000000000000000000000000000000008f29a7d8"]}

08:03:46:549   1f64   ETH: checking pool connection...
08:03:49:390   1f64   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

08:03:55:436   1f64   Socket was closed remotely (by pool)

[Metamorph]

I use pool dwarfpool and i have e-mail send when miner stop.
dwarfpool setting for e-mail is   : write email instead password.
Claymore readme:  parameter password is  -epsw
My setting is   -epsw xxx@xx.xx   but when miner stop (crash) nothing happens. Miner not work hour and not e-mail send.
Why?

[GH]

Please test this version:
https://mega.nz/#!C5xiUSYY!QY44OAExh5EQ2elGcH1DvfbkQMTkgMSwOEMLoG0lUCU
Let me know if you still have the issue.

The issue remains. Rig have restarted about half an hour ago, but EthMan shows that it stays offline. Choosing "view miner console" opens page with working rig.
I have static local ip on miner, so I think, the problem is not in dns

Damn. Seems at least that this one is not the cause.

Another try: Does anybody of you guys who encounters this problem use the new features like encrypted connection and/or authentication for the management? I don't...
And can you reproduce this "lock" by sending a restart command to a read only managment rig like I wrote before?

[joosep]

hey guys,

maybe someone can help me
so i'm mining for almost 3 weeks now with just an normal pc with a gtx 1060 (6gb)
But when i went back to my pc this morning, the program stopped completely and was shut down (the program, not the pc)

So I tried running it again but then it almost immediately stopped again, restarted my pc but still no luck

I did find out that windows defender had put Skeeyah.A!rfn in quarantine and according to windows defender it has something to do with the minder.

Could enyone help me so I can start mining again?

Download new copy of the minerprogram.

[mjkforum]

hey guys,

maybe someone can help me
so i'm mining for almost 3 weeks now with just an normal pc with a gtx 1060 (6gb)
But when i went back to my pc this morning, the program stopped completely and was shut down (the program, not the pc)

So I tried running it again but then it almost immediately stopped again, restarted my pc but still no luck

I did find out that windows defender had put Skeeyah.A!rfn in quarantine and according to windows defender it has something to do with the minder.

Could enyone help me so I can start mining again?

Download new copy of the minerprogram.

Thanks! that did the trick, but does anyone know what could have caused it?
And should I be worried someone has been in my pc an could have stole personal information?

[Shattered]

hey guys,

maybe someone can help me
so i'm mining for almost 3 weeks now with just an normal pc with a gtx 1060 (6gb)
But when i went back to my pc this morning, the program stopped completely and was shut down (the program, not the pc)

So I tried running it again but then it almost immediately stopped again, restarted my pc but still no luck

I did find out that windows defender had put Skeeyah.A!rfn in quarantine and according to windows defender it has something to do with the minder.

Could enyone help me so I can start mining again?

I sent you a message, hopefully it helps.
Cheers

[hacman]

Hi Claymore,

Firstly - thanks for your efforts on this. I’m new to mining, but got everything setup in no time at all!

So, I was wondering how you’re determining the number f TMUs/shaders that are available?

Is this detected in some way, or do you look at what each card identifies as and use hard coded values?

If the latter - is there any scope for adding a switch to allow manual config of these values?

Thanks!