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

[fittsy]

Claymore, how about adding a mirror with direct http links with easy to remember file names ? (for easy downloading with wget on linux)

Could he just make a bit.ly link to the latest linux version?

Then keep that one link updated?

How can I make this link for a file on google drive or mega?

I know on Google drive you select the file, right click and select "share" from the options.  One of the options will give you a link that you can share with others. I would guess that link might work with bit.ly.

I'm not sure if that will work with bit.ly or not. It's worth trying.

If you setup a bit.ly account you can have permanent links for free. like bit.ly/claymore-win64  bit.ly/claymore-linux or whatever.

[1714304709]

1714304709

[1714304709]

1714304709

[1714304709]

1714304709

[joaocha]

Why they blocked claymore account?

[cptfisher]

-U --cuda-extragpu-mem 4096 --cuda-streams 1 --cuda-block-size 64 --cuda-grid-size 4096
for genoil
for ccminer i use 1.8.2 with -i 23 no special parameter (but also not specifing intensity is giving me same results)

With these options, at stock clocks I get about 195MH/s LBC and 6.7MH/s ETH (ETH-only shows 25MH/s, LBC-only shows 278MH/s). It's difficult to see exact hashrates since both LBC and ETH miners show various numbers all the time in this mode. Sometimes Genoil shows 12MH/s, a couple of times I even saw 15MH/s, but average hashrate is 6.5...7MH/s. LBC miner shows more stable numbers, 180-210MH/s, average is 195MH/s.
With my miner at "-dcri 500" I get 147MH/s LBC and 13.7MH/s ETH.
So right now I don't see that Genoil+ccminer faster/better. However, I agree that LBC is not very good coin for dual mode anyway, it takes too much resources so ETH speed suffers.

dont know what to say.. here is screen with my config... 270 w from wall atm ... same hasrates of 3 heavily overclocked cards but instead they have heavy downclock.....

[Claymore]

dont know what to say.. here is screen with my config... 270 w from wall atm ... same hasrates of 3 heavily overclocked cards but instead they have heavy downclock.....

As I said before, I don't overclock cards, I always use stock clocks. From your screenshots I see that single card shows 103MH/s LBC and 17MH/s ETH (to get average hashrate I added all hashrate lines and divided them by the number of lines). In my miner on stock single 1070 I can get 17MH/s ETH on "-dcri 220", it shows 83MH/s LBC. But you changed clocks for your cards, so these results cannot be compared to your results. You should start my miner and use "+" and "-" keys to get 17MH/s ETH per card, then see LBC hashrate.

[BTCBusinessConsult]

Stupid question:

Are there separate downloads for Claymore miner for Win 7 vs Win 10? From what I can see on the google doc area its just "Windows" so I am assuming its the same?

[Trimegistus]

Stupid question:

Are there separate downloads for Claymore miner for Win 7 vs Win 10? From what I can see on the google doc area its just "Windows" so I am assuming its the same?

It's the same 

[joaocha]

Stupid question:

Are there separate downloads for Claymore miner for Win 7 vs Win 10? From what I can see on the google doc area its just "Windows" so I am assuming its the same?

Same thing, only use diferents version of cuda, if you are mining with nvidia

[qqqq]

What about GTX 1080 and 20 Mh\s on ETH ? What issue cause this weak hashrate ? Or it's ok for GTX 1080?

[manotroll]

It has as mine eth in a portfolio and sia in another possible?

eth would minergate
and that Asia portfolio which I use?

[tvasbn]

iv seen that the "-tt" option does not work in ubuntu 16 whit the RX400 cards, also pwmcontrol it dosent has anyoane find a solution for increasing fan% on 85-90% ?

[GenTarkin]

BUG: w/ new DAG and claymore miner.

Up until recently ... the following has worked fine:

Mining EXP and SIA or DCR on my rig on 2 7970's

As of the latest DAG .... this now causes a crash when switching to devpool (subsequently having to change epoch to ETH's epoch), the DAG creation takes 2x longer than usual and at the end of it the machine reboots w/ bug check of a hung device thread status.
Ive repeated this across multiple sets of cards - so its not hardware related.

[rednoW]

What about GTX 1080 and 20 Mh\s on ETH ? What issue cause this weak hashrate ? Or it's ok for GTX 1080?

gddr5x suxxx - big latency

[Claymore]

BUG: w/ new DAG and claymore miner.

Up until recently ... the following has worked fine:

Mining EXP and SIA or DCR on my rig on 2 7970's

As of the latest DAG .... this now causes a crash when switching to devpool (subsequently having to change epoch to ETH's epoch), the DAG creation takes 2x longer than usual and at the end of it the machine reboots w/ bug check of a hung device thread status.
Ive repeated this across multiple sets of cards - so its not hardware related.

If you use same version and it started to generate DAG slowly - reboot PC, it's not miner issue, drivers or hardware failed. I have several rigs turned on right now and they work fine with latest 7.2 on Win10.
What version of the miner do you use? What pool do you use to mine EXP?

[dexxa05]

Guys,

What is your hashrate with 1070 and your power consumption ?

Thx in advance

[nevermind41]

@dexxa05 115 watt +900 mem 32+ mh with GTX 1070

[dexxa05]

@dexxa05 115 watt +900 mem 32+ mh with GTX 1070

Thx ! I'm thinking it will be lower power consumption with 1070 but it's not.

[SwedishBTC]

I have a question about the new version 7.2 and LBRY dual mining. Before I was using an older version of Claymore's Dual miner and mined ETH + DCR with my RX 480 and was running 27.3 MH/s on Ethereum, but after I updated to the v7.2 and started to mine Ethereum + LBRY I only get about 24.4 MH/s on Ethereum mining on the same settings, is this normal when mining LBRY instead of DCR?

[GenTarkin]

BUG: w/ new DAG and claymore miner.

Up until recently ... the following has worked fine:

Mining EXP and SIA or DCR on my rig on 2 7970's

As of the latest DAG .... this now causes a crash when switching to devpool (subsequently having to change epoch to ETH's epoch), the DAG creation takes 2x longer than usual and at the end of it the machine reboots w/ bug check of a hung device thread status.
Ive repeated this across multiple sets of cards - so its not hardware related.

If you use same version and it started to generate DAG slowly - reboot PC, it's not miner issue, drivers or hardware failed. I have several rigs turned on right now and they work fine with latest 7.2 on Win10.
What version of the miner do you use? What pool do you use to mine EXP?

Using win7 x64, 15.12, have tried miner 5.3 and the latest 7.2 .... same issues. I dont understand how its a hardware problem. No cards on rig exhibit this problem when generating either EXP or ETH DAG on miner start, only while mining and switching to devfeepool has the problem shown up(going from EXP mining to devfeepool mining). Could it be size of larger new dag and exp dag cant coexist on a card? ( I dont know how the ongpu dag creation works - is the old DAG discarded prior to the GPUs generate a new one? ... if not then its easily a DAG size issue)

Completely different GPU's on this rig exhibit same problem ... I doubt all the GPU's are failing ..

[xeridea]

I have a question about the new version 7.2 and LBRY dual mining. Before I was using an older version of Claymore's Dual miner and mined ETH + DCR with my RX 480 and was running 27.3 MH/s on Ethereum, but after I updated to the v7.2 and started to mine Ethereum + LBRY I only get about 24.4 MH/s on Ethereum mining on the same settings, is this normal when mining LBRY instead of DCR?

Library slows down Eth somewhat.  It is a harder algorithm to dual mine.  DCR and SIA don't slow down Eth (with proper dcri), but LBRY does.

[Claymore]

BUG: w/ new DAG and claymore miner.

Up until recently ... the following has worked fine:

Mining EXP and SIA or DCR on my rig on 2 7970's

As of the latest DAG .... this now causes a crash when switching to devpool (subsequently having to change epoch to ETH's epoch), the DAG creation takes 2x longer than usual and at the end of it the machine reboots w/ bug check of a hung device thread status.
Ive repeated this across multiple sets of cards - so its not hardware related.

If you use same version and it started to generate DAG slowly - reboot PC, it's not miner issue, drivers or hardware failed. I have several rigs turned on right now and they work fine with latest 7.2 on Win10.
What version of the miner do you use? What pool do you use to mine EXP?

Using win7 x64, 15.12, have tried miner 5.3 and the latest 7.2 .... same issues. I dont understand how its a hardware problem. No cards on rig exhibit this problem when generating either EXP or ETH DAG on miner start, only while mining and switching to devfeepool has the problem shown up(going from EXP mining to devfeepool mining). Could it be size of larger new dag and exp dag cant coexist on a card? ( I dont know how the ongpu dag creation works - is the old DAG discarded prior to the GPUs generate a new one? ... if not then its easily a DAG size issue)

Completely different GPU's on this rig exhibit same problem ... I doubt all the GPU's are failing ..

I just tried to mine EXP, it mines it, after a few DAG switches it still works, no rejected/invalid shares. EXP has epoch #13 and ETH has epoch #79, so it takes in about 1.5 times longer to create DAG for ETH.
Try to specify "-allcoins -1" option, see readme for details. If it does not help, ask here if someone mines EXP and has same problems, this way we can confirm that the problem is not in your hardware.
PS. If you use dwarfpool (or any pool that accepts wallet address directly) you can avoid DAG re-creation at all, miner can mine EXP in devfee too. Though it seems "-allcoins exp" option was broken in v7.x, I fixed it and I can send you an update.