Author

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

newbie
Activity: 11
Merit: 0
I was able to use the latest version of Crimson 16.3 with this mining program. By doing so, I was able to go into Catalyst and manually change the fan speed. I could not do that in this mining program, as it kept crashing the program. Also, the program does not like it when you adjust mclock through it, although I can do that  "normally" in Catalyst without crashing my cards. Leaving it at the factory settings still resulted in the card producing the optimum MH/s when mining Ethereum. That was a plus, since overclocking creates all kinds of problem, as a general rule. The rejection rates are almost zero in this mining program, which is unbelievable. I brought the DCR intensity up to 50. It affected the Eth hashrate little. DCR hashrate, at this setting, is cooking away at 672 MH/s without damaging the Eth hashrate much. I will attempt to ramp up the intensity further once I have everything else set properly. Here is what I have for R9 290. Others seem to have differing success rates:


"EthDcrMiner64.exe -epool coinotron.com:3344 -ewal XXXXXXX.XXXXXXX -esm 2 -epsw XXXX -dpool stratum+tcp://dcr.suprnova.cc:2252 -dwal XXXXXXX.XXXXXXX -dpsw XXXX -allpools 1 -ethi 13 -dcri 50 -dcrt 5"

I changed -dcrt to 5, because the miner popped up failures due to get-work not happening fast enough, for some reason. Part of this may have been from using the non stratum access to suprnova, which I never knew existed. It may not be a problem now, but I left it in regardless.

This program is something else, I must say. I am curious as to whether there are other coin combinations out there which could benefit from this program, tweaked to the pairs and algos. Considering I have 3 Eth rigs here, this will boost daily revenues by around $8-$10, as long as DCR does not fall even more than it has recently.
hero member
Activity: 700
Merit: 500
So i tried moving some other machines over to dual mining and having alot of problems with the 3.2 version

several machines will just reboot them selves while mining the dual alogos, no error message nothing.  I wiped one machine with 6 290x cards back to stock windows 10 default drivers 15.300  ( always gets installed no matter what i do, even if i turn off network and mnually install 15.12 crimson when i check the device i see 15.300 /shurg  one machine with that same driver works fine in dual mode)


tried default intensity 30 and higer same deal machines just randomly die after about 10 mins

any ideas ?

Don't use win 10... problem solved Tongue
Windows 10 works perfectly fine. Marvell1's problem sounds like power, excessive overclock, or similar.
hero member
Activity: 799
Merit: 1000
So i tried moving some other machines over to dual mining and having alot of problems with the 3.2 version

several machines will just reboot them selves while mining the dual alogos, no error message nothing.  I wiped one machine with 6 290x cards back to stock windows 10 default drivers 15.300  ( always gets installed no matter what i do, even if i turn off network and mnually install 15.12 crimson when i check the device i see 15.300 /shurg  one machine with that same driver works fine in dual mode)


tried default intensity 30 and higer same deal machines just randomly die after about 10 mins

any ideas ?

Don't use win 10... problem solved Tongue
hero member
Activity: 682
Merit: 500
So i tried moving some other machines over to dual mining and having alot of problems with the 3.2 version

several machines will just reboot them selves while mining the dual alogos, no error message nothing.  I wiped one machine with 6 290x cards back to stock windows 10 default drivers 15.300  ( always gets installed no matter what i do, even if i turn off network and mnually install 15.12 crimson when i check the device i see 15.300 /shurg  one machine with that same driver works fine in dual mode)


tried default intensity 30 and higer same deal machines just randomly die after about 10 mins

any ideas ?

Maybe just try upgrading to a newer driver.

I'm using 16.3.1 on one PC and 16.3.2 on another and not had a single issue.

Could also be your cards are getting too hot or not enough power from your PSU.
legendary
Activity: 2408
Merit: 1102
Leading Crypto Sports Betting & Casino Platform
So i tried moving some other machines over to dual mining and having alot of problems with the 3.2 version

several machines will just reboot them selves while mining the dual alogos, no error message nothing.  I wiped one machine with 6 290x cards back to stock windows 10 default drivers 15.300  ( always gets installed no matter what i do, even if i turn off network and mnually install 15.12 crimson when i check the device i see 15.300 /shurg  one machine with that same driver works fine in dual mode)


tried default intensity 30 and higer same deal machines just randomly die after about 10 mins

any ideas ?
legendary
Activity: 1164
Merit: 1010

Use stratum also for decred.
Replace -dpool http://dcr.suprnova.cc:9112 with -dpool stratum+tcp://dcr.suprnova.cc:2252

The rejects will drop to 1-3% Wink
And You have to wait for almost 24h for DCR confirmation.

Thanks that made a difference btw can this Cannot parse JSON! be ignored?

Quote
ETH: Stratum - Connected
 DCR: Stratum - Connected
Need to check DAG file (epoch #46), starting...
ETH: Authorized
Cannot parse JSON!
 DCR: Authorized
DAG file (epoch #46) is ok.
Need to check next DAG file (epoch #47) in back
Applying DAG epoch #46 for GPU #0
Create GPU buffer for GPU #0
Applying DAG epoch #46 for GPU #0 done
Applying DAG epoch #46 for GPU #1
Create GPU buffer for GPU #1
Applying DAG epoch #46 for GPU #1 done
DAG file (epoch #47) is ok.

Ya, I see the same after switvhing to supernova stratum.  It caused the miner to constantly restart (with watchdog), so I've deleted my DAG files and having the miner regenerate them.  Not really sure if that will help or not...
sr. member
Activity: 322
Merit: 250
No it's Actiontech as I have FIOS now Frontier 80/80MB connection.  Ok I found I needed to lower my intensity on my main gpu for my system.

-ethi 16,4

My 4GB 380x is my primary card and my 3GB 280x is my secondary but ethminer sees it the opposite direction. So lowering intensity to 4 reduced lag in my Windows and that lowered disconnects down quite a bit.  But still having a few just not as many now.  It hasn't effected the performance much either.

Quote
ETH: 04/23/16-15:04:43 - New job (target 0x00000001310a5081) from coinotron.com:3344
ETH - Total Speed: 37.289 Mh/s, Total Shares: 26, Rejected: 0, Time: 00:39
ETH: GPU0 21.067 Mh/s, GPU1 16.222 Mh/s
 DCR - Total Speed: 559.327 Mh/s, Total Shares: 292, Rejected: 0
 DCR: GPU0 316.004 Mh/s, GPU1 243.323 Mh/s
 DCR: 04/23/16-15:04:46 - SHARE FOUND - (GPU 0)
 DCR: 04/23/16-15:04:46 - SHARE FOUND - (GPU 0)
 DCR: 04/23/16-15:04:46 - SHARE FOUND - (GPU 1)
 DCR: 04/23/16-15:04:48 - SHARE FOUND - (GPU 0)
 DCR: Share accepted (1966 ms)!
 DCR: Share accepted (1966 ms)!
 DCR: Share accepted (1966 ms)!
 DCR: Share accepted (1966 ms)!
 DCR: 04/23/16-15:04:51 - SHARE FOUND - (GPU 1)
 DCR: Share accepted (514 ms)!
 DCR: 04/23/16-15:05:01 - SHARE FOUND - (GPU 0)
 DCR: Share accepted (125 ms)!
ETH: 04/23/16-15:05:10 - New job (target 0x00000001310a5081) from coinotron.com:3344

Now to the other I have this PC as a DMZ host with mininum security.  I rely on PC firewall for any real threats.  The only other thing I have is inbound packets scanning ports are dropped on the main ports that are scanned.

RPC - TCP Any -> 135   
Net_BIOS - TCP Any -> 139   
HTTPS - TCP Any -> 443   
MSFT_DS - TCP Any -> 445   
SSH - TCP Any -> 22   

and block ip fragments. So that should not affect anything. Response time on many test sites are 51-52 ms for latency.
hero member
Activity: 539
Merit: 500
Quote
ETH: 04/23/16-14:12:04 - New job (target 0x00000001310a5081) from coinotron.com:3344
ETH - Total Speed: 40.911 Mh/s, Total Shares: 109, Rejected: 0, Time: 02:37
ETH: GPU0 21.052 Mh/s, GPU1 19.859 Mh/s
 DCR - Total Speed: 613.668 Mh/s, Total Shares: 1334, Rejected: 11
 DCR: GPU0 315.781 Mh/s, GPU1 297.887 Mh/s
 DCR: 04/23/16-14:12:11 - New job (target 0x00000000ffff0000, block #21943) from dcr.suprnova.cc:2252
ETH: 04/23/16-14:12:18 - New job (target 0x00000001310a5081) from coinotron.com:3344
ETH - Total Speed: 41.391 Mh/s, Total Shares: 109, Rejected: 0, Time: 02:38
ETH: GPU0 21.066 Mh/s, GPU1 20.325 Mh/s
 DCR - Total Speed: 620.868 Mh/s, Total Shares: 1334, Rejected: 11
 DCR: GPU0 315.996 Mh/s, GPU1 304.872 Mh/s
 DCR: 04/23/16-14:12:19 - SHARE FOUND - (GPU 0)
 DCR: Share accepted (109 ms)!

Seemed to be doing pretty good now.. BTW I get this intermittently.

Quote
ETH: 04/23/16-14:14:24 - New job (target 0x00000001310a5081) from coinotron.com:3344
ETH - Total Speed: 40.910 Mh/s, Total Shares: 110, Rejected: 0, Time: 02:40
ETH: GPU0 21.062 Mh/s, GPU1 19.848 Mh/s
 DCR - Total Speed: 613.646 Mh/s, Total Shares: 1343, Rejected: 11
 DCR: GPU0 315.924 Mh/s, GPU1 297.722 Mh/s
 DCR: 04/23/16-14:14:25 - SHARE FOUND - (GPU 0)
 DCR: 04/23/16-14:14:36 - SHARE FOUND - (GPU 1)
DCR: Stratum - socket send failed 10053, disconnect
 DCR: 04/23/16-14:14:40 - SHARE FOUND - (GPU 1)
DCR: Stratum - socket send failed 10038, disconnect
 DCR: Stratum - connecting to 'dcr.suprnova.cc' <178.33.228.14> port 2252
 DCR: Stratum - Connected
 DCR: Authorized

right after this disconnect is when I will get 2 or 3 rejects at least..  How can I resolve this disconnect issue?

do you have an Asus Router ? if yes, try without "AiProtection"
sr. member
Activity: 322
Merit: 250
Quote
ETH: 04/23/16-14:12:04 - New job (target 0x00000001310a5081) from coinotron.com:3344
ETH - Total Speed: 40.911 Mh/s, Total Shares: 109, Rejected: 0, Time: 02:37
ETH: GPU0 21.052 Mh/s, GPU1 19.859 Mh/s
 DCR - Total Speed: 613.668 Mh/s, Total Shares: 1334, Rejected: 11
 DCR: GPU0 315.781 Mh/s, GPU1 297.887 Mh/s
 DCR: 04/23/16-14:12:11 - New job (target 0x00000000ffff0000, block #21943) from dcr.suprnova.cc:2252
ETH: 04/23/16-14:12:18 - New job (target 0x00000001310a5081) from coinotron.com:3344
ETH - Total Speed: 41.391 Mh/s, Total Shares: 109, Rejected: 0, Time: 02:38
ETH: GPU0 21.066 Mh/s, GPU1 20.325 Mh/s
 DCR - Total Speed: 620.868 Mh/s, Total Shares: 1334, Rejected: 11
 DCR: GPU0 315.996 Mh/s, GPU1 304.872 Mh/s
 DCR: 04/23/16-14:12:19 - SHARE FOUND - (GPU 0)
 DCR: Share accepted (109 ms)!

Seemed to be doing pretty good now.. BTW I get this intermittently.

Quote
ETH: 04/23/16-14:14:24 - New job (target 0x00000001310a5081) from coinotron.com:3344
ETH - Total Speed: 40.910 Mh/s, Total Shares: 110, Rejected: 0, Time: 02:40
ETH: GPU0 21.062 Mh/s, GPU1 19.848 Mh/s
 DCR - Total Speed: 613.646 Mh/s, Total Shares: 1343, Rejected: 11
 DCR: GPU0 315.924 Mh/s, GPU1 297.722 Mh/s
 DCR: 04/23/16-14:14:25 - SHARE FOUND - (GPU 0)
 DCR: 04/23/16-14:14:36 - SHARE FOUND - (GPU 1)
DCR: Stratum - socket send failed 10053, disconnect
 DCR: 04/23/16-14:14:40 - SHARE FOUND - (GPU 1)
DCR: Stratum - socket send failed 10038, disconnect
 DCR: Stratum - connecting to 'dcr.suprnova.cc' <178.33.228.14> port 2252
 DCR: Stratum - Connected
 DCR: Authorized

right after this disconnect is when I will get 2 or 3 rejects at least..  How can I resolve this disconnect issue?
hero member
Activity: 602
Merit: 500
!!! WARNING !!! You seem to be sending a large amount of INVALID shares ! Check your rigs, you might be mining the wrong algo and your hashrate could be displayed wrong! !!! WARNING !!!

 DCR - Total Speed: 205.617 Mh/s, Total Shares: 5451, Rejected: 2075
 DCR: GPU0 205.617 Mh/s
 DCR: Submitted share rejected!
 DCR: 04/23/16-21:03:38 - SHARE FOUND - (GPU 0)
 DCR: Submitted share rejected!
 DCR: 04/23/16-21:03:39 - SHARE FOUND - (GPU 0)
 DCR: Submitted share rejected!
Pool returned error #56.
 DCR: Failed to check work on pool, retry in 20 sec...
legendary
Activity: 3416
Merit: 1059
I used to mine with Ethos, now claymore seems to be available only on windows. Does anybody have any idea on how much RAM I need per card ? Most of my rigs are with 390s. The good thing about Ethos was that it was running fine with only 4Gb of RAM for a 6 card rig and not even consuming all 4.

To mine ETH you need a minimum 2 Gb RAM per card, otherwise the DAG won't load into the cards's memory

so, my fifth card wont work with 8gb of ram?! sh Angry Angry, i did not know that...

unless this software is different, thats false.

etereum needs as much system ram as it needs GPU ram, because the DAG is loaded on both. But it only needs one copy in the ram for every running instance (and the DAG is only ~1.4GB, so even 5 seperate ethminer instances would be ~7.1GB of RAM usage)

if you have all your cards running in te same instance of ethminer your RAM usage will only be 1.4Gb (size of the DAG)

on windows 7 64bit you need system ram of 4gb, my rig with 2gb and 3gb can't mine until i upgraded it to 4gb..using ethminer

haven't tried system ram downgrade with this dual miner yet..
sr. member
Activity: 406
Merit: 250
www.cryptocompare.com
okay, thought i had something else to worry about. i have always heard ram didnt matter much but since this miner is diff from most, that post got me wondering. thx Smiley

(still having freezes with my r9 290, i think that setting a FIXED value for gpu clock (factory) will fix it, can anyone give an opinion on this? I have fixed BSOD forcing constant voltage and got the temp down to 86-87 with 100% fan. which i may reduce to 70% depending on the temp.. I am running a test with the other 3 cards r9 280x to see if it may be something else)
legendary
Activity: 2128
Merit: 1005
ASIC Wannabe
I used to mine with Ethos, now claymore seems to be available only on windows. Does anybody have any idea on how much RAM I need per card ? Most of my rigs are with 390s. The good thing about Ethos was that it was running fine with only 4Gb of RAM for a 6 card rig and not even consuming all 4.

To mine ETH you need a minimum 2 Gb RAM per card, otherwise the DAG won't load into the cards's memory

so, my fifth card wont work with 8gb of ram?! sh Angry Angry, i did not know that...

unless this software is different, thats false.

etereum needs as much system ram as it needs GPU ram, because the DAG is loaded on both. But it only needs one copy in the ram for every running instance (and the DAG is only ~1.4GB, so even 5 seperate ethminer instances would be ~7.1GB of RAM usage)

if you have all your cards running in te same instance of ethminer your RAM usage will only be 1.4Gb (size of the DAG)
legendary
Activity: 1151
Merit: 1001
Of course not, just make your virtual memory 8 to 16GB min and it will work.
sr. member
Activity: 406
Merit: 250
www.cryptocompare.com
I used to mine with Ethos, now claymore seems to be available only on windows. Does anybody have any idea on how much RAM I need per card ? Most of my rigs are with 390s. The good thing about Ethos was that it was running fine with only 4Gb of RAM for a 6 card rig and not even consuming all 4.

To mine ETH you need a minimum 2 Gb RAM per card, otherwise the DAG won't load into the cards's memory

so, my fifth card wont work with 8gb of ram?! sh Angry Angry, i did not know that...
newbie
Activity: 15
Merit: 0

DCR rejects 1-2% at this pool.

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

EthDcrMiner64.exe -epool asia1.ethpool.org:3333 -ewal <> -epsw x -dpool stratum+tcp://mine.zpool.ca:5744 -dwal <> -dpsw c=BTC,decred

Thanks!  Smiley
legendary
Activity: 1834
Merit: 1080
---- winter*juvia -----
Currently I'm only mining Eth and want to test the dual mining feature.

What DCR pools exist where I don't need to signup?

Thanks

zpool.ca

just provide BTC address

Thanks! Smiley

password for DCR in zpool.ca will be "-psw c=BTC,decred"

what's you reject rate for DCR on this pool?
and, could you please post your full command when you use this pool? I've been toying around with it, but can't seem to get it working..

DCR rejects 1-2% at this pool.

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

EthDcrMiner64.exe -epool asia1.ethpool.org:3333 -ewal <> -epsw x -dpool stratum+tcp://mine.zpool.ca:5744 -dwal <> -dpsw c=BTC,decred
full member
Activity: 192
Merit: 100
Running claymore's miner (eth only) for 55 hours straight with 0 eth rejects. Loving this miner. Smiley  

i am getting rejects all the time ;(

i did delete DAG 2 times already but i am still getting rejects. any1 an idea why?

using following command

EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -esm 1 -ewal 0xCcB701a1F4axxxxxxxxxxxxxxxxxxxxxxxxxxxxx.rig2 -epsw x

also tried us1 adress for stratum, but no changes

Use stratum - also tried us1 adress for stratum, but no changes. <- didnt see that part

when i the miner was updated to allow dcr stratum that solved my dcr rejected shares.. :\ maybe try another pool?


Yeah  i need try to use smile pools without stratum. But stratum should work too. Using the last version of claymore
newbie
Activity: 15
Merit: 0
Currently I'm only mining Eth and want to test the dual mining feature.

What DCR pools exist where I don't need to signup?

Thanks

zpool.ca

just provide BTC address

Thanks! Smiley

password for DCR in zpool.ca will be "-psw c=BTC,decred"

what's you reject rate for DCR on this pool?
and, could you please post your full command when you use this pool? I've been toying around with it, but can't seem to get it working..
sr. member
Activity: 322
Merit: 250

Use stratum also for decred.
Replace -dpool http://dcr.suprnova.cc:9112 with -dpool stratum+tcp://dcr.suprnova.cc:2252

The rejects will drop to 1-3% Wink
And You have to wait for almost 24h for DCR confirmation.

Thanks that made a difference btw can this Cannot parse JSON! be ignored?

Quote
ETH: Stratum - Connected
 DCR: Stratum - Connected
Need to check DAG file (epoch #46), starting...
ETH: Authorized
Cannot parse JSON!
 DCR: Authorized
DAG file (epoch #46) is ok.
Need to check next DAG file (epoch #47) in back
Applying DAG epoch #46 for GPU #0
Create GPU buffer for GPU #0
Applying DAG epoch #46 for GPU #0 done
Applying DAG epoch #46 for GPU #1
Create GPU buffer for GPU #1
Applying DAG epoch #46 for GPU #1 done
DAG file (epoch #47) is ok.
Jump to: