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

[ExcelThroughKnowledge]

@claymore , could you help me out?

I've been using version 4.3 until recently upgraded to 9.3

Under the same settings, 4.3 works perfectly fine, but when running 9.3, artifacts starts to appear. Solo eth mining does not affect anything but I'm doing dual mining all along..

Are there anyways to fix that?

I'm using 380x gpus

[laik2]

On both version - v9.0 and v9.3 I have the same cpu usage on (latest G4560 3.5 GHz) about 1-2% overall cpu usage of whole system

If you are sure that the reason is the miner, not your pool or internet connection, you can create two log files and PM them, I will compare them.

I can confirm that actual hashrate(current hashrate) is a bit lower on 9.3.My average hashrate dropped with 10 since I updated to 9.3 from 9.1

true but 2nd coin got x2 increase do mind that asm optimizations shifted optimal dcri
also try "-eqlim 288" for polaris

Ok, Boss, affirmative
already got 36 CU recognized, -dcri is 7/8 depends on gpu memory type and no , I do not dualmine.

[Ursul0]

this is confusing. I'd think that 'ms' is the time measured from the moment you submitted the share till you got response from the pool. and if so it wouldn't probably have to do anything with the miner version, but the network conditions.  also obviously when the block time is short your ping better be fast.

Let's try another explanation.

If your computer is running basic addition........

... meaning the lowest difficulty setting on that port is a lot higher than 3334.

This is all fascinating, seems that you're on the right track - a bit more learning and you'll understand how it all works.
However my point was that the EdjOne's claim is likely an absurd one.
And the same goes to you on your difficulty talk. EDIT: Meaning - it has nothing to do with the poll response time.

[jhenrikb]

hi, any way to run both ETC and ETH on same comp using claymore?

I tried to direct GPU 0+1 to ETC and 2345 to ETH.
ETC using client 9.1, and ETH client 9.2 So both using different folders etc.

However I can only run 1 at a time.
Bind failed with error: 10048: (port for remote management is busy, use different -mport value)
Port value is 3333 according to page 1. can I put "-mport 3334" on ETC? or will this screw up with the pool?

[EdjOne]

this is confusing. I'd think that 'ms' is the time measured from the moment you submitted the share till you got response from the pool. and if so it wouldn't probably have to do anything with the miner version, but the network conditions.  also obviously when the block time is short your ping better be fast.

Let's try another explanation.

If your computer is running basic addition........

... meaning the lowest difficulty setting on that port is a lot higher than 3334.

This is all fascinating, seems that you're on the right track - a bit more learning and you'll understand how it all works.
However my point was that the EdjOne's claim is likely an absurd one.
And the same goes to you on your difficulty talk. EDIT: Meaning - it has nothing to do with the poll response time.

Maybe you are right, but it's easy to see that profit of ETH on same rig with same internet and environment with 8.0 and 9.3 is different. Only the reason to stay with 9.3 is due to possibility to continue mine dcr same time (dual mining). I'm beginner in mining (few month only). I'm understand about difficulty of the  block, but profit is better on 8.0

[golden0707]

hi, any way to run both ETC and ETH on same comp using claymore?

I tried to direct GPU 0+1 to ETC and 2345 to ETH.
ETC using client 9.1, and ETH client 9.2 So both using different folders etc.

However I can only run 1 at a time.
Bind failed with error: 10048: (port for remote management is busy, use different -mport value)
Port value is 3333 according to page 1. can I put "-mport 3334" on ETC? or will this screw up with the pool?

Hi ! -mport is used to monitor your rig. You can use different port for each miner instance.

No matter to the pool.

[cryptolelefla]

hello. Do someone experiences problems with claymore's manager...
sometimes tells me problems with rig, but rig is working good... this append with 9.3 version....

[dudleyar]

Hi All,

I currently trying to use 9.3 to Mine Eth but it does not seem to work properly with Dwarfpool, it connects but does not receive any jobs and then Disconnects, I have tried other pools and they works mining Eth and Dwarfpool EXP works fine, I have been able to connect in the past, any ideas anyone?

Regards,

Andy

[Drawde]

Hi All,

I currently trying to use 9.3 to Mine Eth but it does not seem to work properly with Dwarfpool, it connects but does not receive any jobs and then Disconnects, I have tried other pools and they works mining Eth and Dwarfpool EXP works fine, I have been able to connect in the past, any ideas anyone?

Regards,

Andy

I use Dwarfpool with 9.3 and have no issues.  Here are my settings:

EthDcrMiner64.exe -wd 0 -epool eth-us2.dwarfpool.com:8008 -ewal 0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.worker1 -epsw x -mport -3332 -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal AccountName.worker1 -dpsw 1 -dcri 25 -allpools 1

[mraug]

Hello Claymore / forum,

I really need a hand with this one, not sure how to fix:

I'm mining single mode eth and encountering some hangups of the miner. Annoying thing is, despite using the "r" function the miner doesn't reboot when it hangs. I have to notice it being dead, then I have to hit a key (any), the miner then wakes up, realizes it's crashed and reboots itself. This caused me to lose several minutes / hours of mining time on few occasions.

Strange thins is, it's not crashing on OpenCL call, or anything GPU related (at least I think). It seems like it hangs when it tries to connect to the Developer Fee pool.

Here is a full log with debug enabled:

https://www.dropbox.com/s/ah8nqzo4yni2vsl/1493767776_log.txt?dl=0

and below is a cut from the log, the crash part:

15:29:27:006   1860   ETH - Total Speed: 167.456 Mh/s, Total Shares: 1636, Rejected: 0, Time: 13:59
15:29:27:006   1860   ETH: GPU0 25.107 Mh/s, GPU1 25.122 Mh/s, GPU2 29.488 Mh/s, GPU3 29.484 Mh/s, GPU4 28.749 Mh/s, GPU5 29.506 Mh/s
15:29:35:288   1860   ETH: checking pool connection...
15:29:35:288   1860   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

15:29:35:366   1860   got 243 bytes
15:29:35:366   1860   buf: {"jsonrpc":"2.0","id":0,"result":["0x6a2fcc2dac5a7fb341f7fa771030884dc694953b5a3677aacdcab7071315f491","0x064ef82d7269405eb06162f7d33f2b6aa2a23741c9a0d06a648460e17b48ab4c","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}

15:29:35:366   1860   parse packet: 242
15:29:35:366   1860   ETH: job is the same
15:29:35:366   1860   new buf size: 0
15:29:43:570   18bc   GPU0 t=67C fan=91%, GPU1 t=58C fan=78%, GPU2 t=54C fan=80%, GPU3 t=50C fan=78%, GPU4 t=59C fan=83%, GPU5 t=60C fan=84%
15:29:43:570   18bc   em hbt: 0, fm hbt: 94,
15:29:43:570   18bc   watchdog - thread 0, hb time 188
15:29:43:570   18bc   watchdog - thread 1, hb time 375
15:29:43:570   18bc   watchdog - thread 2, hb time 94
15:29:43:570   18bc   watchdog - thread 3, hb time 281
15:29:43:570   18bc   watchdog - thread 4, hb time 31
15:29:43:570   18bc   watchdog - thread 5, hb time 188
15:29:43:570   18bc   watchdog - thread 6, hb time 172
15:29:43:570   18bc   watchdog - thread 7, hb time 16
15:29:43:570   18bc   watchdog - thread 8, hb time 125
15:29:43:570   18bc   watchdog - thread 9, hb time 281
15:29:43:570   18bc   watchdog - thread 10, hb time 125
15:29:43:570   18bc   watchdog - thread 11, hb time 297
15:29:43:601   1860   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x9fbf161", "0x00000000000000000000000000000000000000000000000000000000e7f71ff7"]}

15:29:45:305   1860   ETH: checking pool connection...
15:29:45:305   1860   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

15:29:45:383   1860   got 243 bytes
15:29:45:383   1860   buf: {"jsonrpc":"2.0","id":0,"result":["0x6a2fcc2dac5a7fb341f7fa771030884dc694953b5a3677aacdcab7071315f491","0x064ef82d7269405eb06162f7d33f2b6aa2a23741c9a0d06a648460e17b48ab4c","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}

15:29:45:383   1860   parse packet: 242
15:29:45:383   1860   ETH: job is the same
15:29:45:383   1860   new buf size: 0
15:29:55:318   1860   ETH: checking pool connection...
15:29:55:319   1860   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

15:29:55:393   1860   got 243 bytes
15:29:55:394   1860   buf: {"jsonrpc":"2.0","id":0,"result":["0x6a2fcc2dac5a7fb341f7fa771030884dc694953b5a3677aacdcab7071315f491","0x064ef82d7269405eb06162f7d33f2b6aa2a23741c9a0d06a648460e17b48ab4c","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}

15:29:55:395   1860   parse packet: 242
15:29:55:396   1860   ETH: job is the same
15:29:55:398   1860   new buf size: 0
15:30:03:615   1860   send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x9f8cc49", "0x00000000000000000000000000000000000000000000000000000000e7f71ff7"]}

15:30:05:332   1860   ETH: checking pool connection...
15:30:05:333   1860   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

15:30:05:760   1860   got 243 bytes
15:30:05:761   1860   buf: {"jsonrpc":"2.0","id":0,"result":["0x6a2fcc2dac5a7fb341f7fa771030884dc694953b5a3677aacdcab7071315f491","0x064ef82d7269405eb06162f7d33f2b6aa2a23741c9a0d06a648460e17b48ab4c","0x00000000dbe6fecebdedd5beb573440e5a884d1b2fbf06fcce912adcb8d8422e"]}

15:30:05:763   1860   parse packet: 242
15:30:05:763   1860   ETH: job is the same
15:30:05:765   1860   new buf size: 0
15:30:15:081   1950   ETH: put share nonce 519bff80293b399a
15:30:15:083   1950   ETH round found 1 shares
15:55:40:216   1860   ETH: 05/03/17-15:30:15 - SHARE FOUND - (GPU 2)
15:55:40:220   1860   send: {"id":4,"method":"eth_submitWork","params":["0x519bff80293b399a","0x6a2fcc2dac5a7fb341f7fa771030884dc694953b5a3677aacdcab7071315f491","0xc475a1bca57fab5b20b8e7decf080360ebc074464b3e3677ecf9e7b3d2e321e1"]}

15:30:35:348   18c4   ETH: put share nonce c9d017803adfaecf
15:55:40:222   18c4   ETH round found 1 shares
15:32:15:445   1c38   ETH: put share nonce aa2ffde091330b49
15:55:40:224   1c38   ETH round found 1 shares
15:33:18:362   19ac   ETH: put share nonce 16413580c30e50f9
15:33:25:701   1538   ETH: put share nonce c62a64a0cf2ab6e9
15:33:45:627   1998   ETH: put share nonce aea2bf40bdd5013a
15:33:59:073   11fc   ETH: put share nonce d5d4dfc8d177f314
15:55:40:245   11fc   ETH round found 1 shares
15:37:13:318   1c24   ETH: put share nonce 51176b024f44ff13
15:55:40:249   1c24   ETH round found 1 shares
15:55:40:252   1230   DevFee: ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <185.71.66.38> port 9999
15:55:40:253   18bc   GPU0 t=67C fan=91%, GPU1 t=57C fan=77%, GPU2 t=54C fan=80%, GPU3 t=51C fan=78%, GPU4 t=59C fan=83%, GPU5 t=60C fan=85%
15:55:40:254   18bc   watchdog - eminer thread hangs
15:55:40:255   18bc   watchdog - fminer thread hangs
15:55:40:255   18bc   em hbt: 1525171, fm hbt: 638000,
15:55:40:256   18bc   Miner thread hangs, need to restart miner!
15:32:48:533   1964   ETH: put share nonce 50c1a748c9d2fd31
15:55:40:258   1964   ETH round found 1 shares
15:55:40:243   1538   ETH round found 1 shares
15:55:40:244   1998   ETH round found 1 shares
15:36:37:187   1950   ETH: put share nonce 519bff82a594e8dc
15:55:40:262   1950   ETH round found 1 shares
15:46:26:548   190c   ETH: put share nonce 485779c45debdbd4
15:55:40:221   1860   buf overflow: 0 23814
15:55:40:265   1860   ETH: Connection lost, retry in 20 sec...
15:55:40:236   19ac   ETH round found 1 shares
15:41:45:231   1c1c   ETH: put share nonce 9eb1f8027d2fe356
15:55:40:267   1c1c   ETH round found 1 shares
15:55:40:264   190c   ETH round found 1 shares
15:31:29:573   19a8   ETH: put share nonce 379f505059c527aa
15:55:40:271   19a8   ETH round found 1 shares
15:55:40:272   1cb0   
15:55:40:272   1cb0   GPU #0: Ellesmere, 4096 MB available, 36 compute units
15:55:40:273   1cb0   GPU #1: Ellesmere, 4096 MB available, 36 compute units
15:55:40:274   1cb0   GPU #2: Ellesmere, 4096 MB available, 36 compute units
15:55:40:274   1cb0   GPU #3: Ellesmere, 4096 MB available, 36 compute units
15:55:40:275   1cb0   GPU #4: Ellesmere, 4096 MB available, 36 compute units
15:55:40:276   1cb0   GPU #5: Ellesmere, 4096 MB available, 36 compute units
15:55:40:277   1cb0   ETH - Total Speed: 0.000 Mh/s, Total Shares: 1637, Rejected: 0, Time: 14:25
15:55:40:278   1cb0   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
15:55:40:278   1cb0   Incorrect ETH shares: GPU2 1, GPU3 3
15:55:40:279   1cb0   Pool switches: ETH - 1, DCR - 0
15:55:40:281   1cb0   Current ETH share target: 0x00000000dbe6fece (diff: 5000MH), epoch #121
15:55:40:311   1230   send: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0x34FAAa028162C4d4E92DB6abfA236A8E90fF2FC3", "x"], "id": 2, "method": "eth_submitLogin"}

15:55:40:311   1230   DevFee: ETH: Stratum - Connected (eth-eu1.nanopool.org:9999)
15:55:40:393   1cb0   GPU0 t=35C fan=91%, GPU1 t=34C fan=78%, GPU2 t=29C fan=81%, GPU3 t=28C fan=78%, GPU4 t=28C fan=83%, GPU5 t=34C fan=85%
15:55:40:395   1cb0   
15:55:41:439   18bc   Restarting OK, exit...

Notice the 20 minute delay between logs messages. Thats when I noticed it's not doing anything and pressed a key, then it promptly rebooted the miner.

[Claymore]

Hello Claymore / forum,

I really need a hand with this one, not sure how to fix:

Check FAQ section in readme or OP.

[Claymore]

Hi All,
I currently trying to use 9.3 to Mine Eth but it does not seem to work properly with Dwarfpool, it connects but does not receive any jobs and then Disconnects, I have tried other pools and they works mining Eth and Dwarfpool EXP works fine, I have been able to connect in the past, any ideas anyone?
Regards,
Andy

I use Dwarfpool with 9.3 and have no issues.  Here are my settings:
EthDcrMiner64.exe -wd 0 -epool eth-us2.dwarfpool.com:8008 -ewal 0xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.worker1 -epsw x -mport -3332 -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal AccountName.worker1 -dpsw 1 -dcri 25 -allpools 1

It seems Dwarfpool blocks default wallet address that is used in readme as a sample wallet, I see it for EXP at least. So make sure that you changed it to your wallet address. In the log file you will see "socket closed remotely" message in this case, this pool just closes connection if it does not like the wallet.

[mraug]

Hello Claymore / forum,

I really need a hand with this one, not sure how to fix:

Check FAQ section in readme or OP.

Hi Claymore,

If you are referring to this:

Sometimes miner cannot connect to devfee mining server at first attempt, does it cause longer devfee mining?
  No, during these connection attempts miner still mines for you.

Then it doesn't work as intended because my pool reports 20 minute break in mining in exactly the period when the miner process became unresponsive.

See picture:
https://i.imgur.com/3lCEZLQ.jpg


If you are referring to something else in the FAQ then give me a more specific hint.

[Claymore]

...
 I have to notice it being dead, then I have to hit a key (any), the miner then wakes up, realizes it's crashed and reboots itself.
...

- Miner freezes if I put cursor to its window in Windows 10 until any key is pressed. Sometimes miner freezes randomly until any key is pressed.
  You should make some changes in Windows:
  https://superuser.com/questions/555160/windows-command-prompt-freezing-on-focus
  https://superuser.com/questions/419717/windows-command-prompt-freezing-randomly?rq=1
  https://superuser.com/questions/1051821/command-prompt-random-pause?rq=1

[bilbo333]

I have an interesting issue with this miner.  I have been mining just fine with it but ran across an issue with my AT&T internet while mining.  I am hoping someone can help me figure it out and suggest a solution.

The issue is, when I am mining (directly plugged into AT&T wireless router) the wireless AT&T boxes in the rest of the house lose connection and will not reconnect.
I don't know enough out the router settings or what the miner is doing to address the issue.  The mining process clearly is messing with the signal or frequencies that the boxes try and connect to.
Then I get the rest of the house screaming for me to shut down my mining.

Anyway. Really hoping someone has an idea how to fix it.
Thanks!

Does anyone have any experience/thoughts on this issue or suggestions?  is anyone using AT&T?
Thank you.

[mraug]

...
 I have to notice it being dead, then I have to hit a key (any), the miner then wakes up, realizes it's crashed and reboots itself.
...

- Miner freezes if I put cursor to its window in Windows 10 until any key is pressed. Sometimes miner freezes randomly until any key is pressed.
  You should make some changes in Windows:
  https://superuser.com/questions/555160/windows-command-prompt-freezing-on-focus
  https://superuser.com/questions/419717/windows-command-prompt-freezing-randomly?rq=1
  https://superuser.com/questions/1051821/command-prompt-random-pause?rq=1

Hi,

Had the QuickEdit Mode already disabled. Now I switched off the "Insert option" as well, lets see if that helps.

I would imagine this would be just stopping the "text" in the command windows so you can select fast moving sentences, not stopping the whole process running in the windows. If it's just stopping the text, why would the miner stop mining?

If it's stopping also whatever is running in the command prompt then hats off to M$ for a awesome feature. /sarcasm off

[Claymore]

If it's stopping also whatever is running in the command prompt then hats off to M$ for a awesome feature. /sarcasm off

Exactly.

[mraug]

If it's stopping also whatever is running in the command prompt then hats off to M$ for a awesome feature. /sarcasm off

Exactly.

Thanks dude. 

[patrike]

I think I have identified a problem in the API output of the miner. When I'm running it on my system where I have one AMD and one nVidia card, I get the following temperature and fan reading from the API:
"79;4772;59"

The expected output should be on the format GPU#0 Temp; GPU#0 Fan; GPU#1 Temp; GPU#1 Fan
"79;47;72;59"

The result is that Awesome Miner doesn't display the correct temperature and fan information when mining.

[jackbox]

Claymore - When "s" is pressed for information can you add shares found per GPU? I know it doesn't really matter but I think it would be interesting to see if one is finding more shares than the other over time.