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

[preda]

Latest version is v10.3:

- added support for Adrenalin drivers (GPU sorting, fan/temperature/clocks management).
- fixed issue with possible GPU crash during miner shutdown.
- now miner shows PCI bus number for every GPU.
- a few minor improvements.
- EthMan: some bug fixes and minor improvements.

thanks!!!

[solarsolar99]

@claymore

Need you help please.

I installed 3pcs of RX560 with fresh install of ubunta. I follow instruction of http://www.cryptobadger.com/2017/04/build-ethereum-mining-rig-linux/.

Everything is fine except only 2 card is running. The script can detect GPU0, GPU1 and GPU2 (in purple word). However, only GPU0 and GPU1 is working.

Script as below and the configue.txt is default empty setting.

#!/bin/sh
export GPU_MAX_ALLOC_PERCENT=100
./ethdcrminer64 -epool eth-us-east1.nanopool.org:9999 -ewal 0xxxxxxxxxxxxxxxxxxxxxxd/Miner01 -epsw x -mode 1 -allpools 1 -tt 68

could you please advise ?

[numeracci]

Hi,
 today I'm getting various alert report from Eset Nod32 antivirus regarding Claymore 10.3
It says Win64/CoinMiner.BX is a trojan... I know a lot of times these are false positive....but I'm slightly worried about this.
Anyone else experienced the same issue?

[Matias]

Hi

I have ethos 1.2.9, claymore 10.2 and Gtx 970. Many claim that they get about 15-20 Mh/s ethereum with this card, but I can´t get more than 11 Mh/s.

My ethOS globalcore setting is 1650 and globalmem is 3650.

Can someone who is getting 15-20 mh/s please tell me what they are doing..

[DedMorozAU]

@claymore

Need you help please.

I installed 3pcs of RX560 with fresh install of ubunta. I follow instruction of http://www.cryptobadger.com/2017/04/build-ethereum-mining-rig-linux/.

Everything is fine except only 2 card is running. The script can detect GPU0, GPU1 and GPU2 (in purple word). However, only GPU0 and GPU1 is working.

Script as below and the configue.txt is default empty setting.

#!/bin/sh
export GPU_MAX_ALLOC_PERCENT=100
./ethdcrminer64 -epool eth-us-east1.nanopool.org:9999 -ewal 0xxxxxxxxxxxxxxxxxxxxxxd/Miner01 -epsw x -mode 1 -allpools 1 -tt 68

could you please advise ?

I believe it's not a miner issue, I had kinda same issue with rx570 on Ubuntu, like fan on 1 card wasn't working, then hash rate on 1 card was significantly low compare to others. So I played(plug to diff pcie ports and used diff rizers) with port on motherboard and rizers, and now it's fine and stable.

[et0nnic]

Hi,
 today I'm getting various alert report from Eset Nod32 antivirus regarding Claymore 10.3
It says Win64/CoinMiner.BX is a trojan... I know a lot of times these are false positive....but I'm slightly worried about this.
Anyone else experienced the same issue?

I am also seeing this

[tstempone]

I don't know why after use 10.3/10.2 tends to have temperature control thread hangs or Watchdog: GPU hangs in OpenCL after 30-60 mins and sometimes system restart, I never able to run for 2 hours.

Now I back to 10.0 everything stable and able to run without issue. My system is rx570 x6 per rig, no memory error and HW error, PSU load within limit.

I still don't know why... Is there some new engine or optimization on 10.2-10.3?



ps. I think future is here as Adrenaline Driver but 10.0 not fully support it and I have a lot of issue with 10.3

[adiman73]

I have one problem with my rig. I keep getting this error: “Socket was closed remotely (by pool) eth connection lost retry in 20 sec…” My rig is on cable not wifi. It works for 20h straigth but then i keep getting this errors and it cant connect for 1-2h. After that, when it finaly connects it works for 20-22h straight.
I use win 10 64 bit


Why is this happening?

[DedMorozAU]

Anyone knows when 10.3 for Linux planned to release?
Using 10.2 on Ubuntu 16.04 with dual mining, but quite often getting error Out Of Memory: Out of memory: Kill process 1842 (ethdcrminer64) score 0 or sacrifice chil. Any idea why? thanks

Hi

Regarding your question I have no idea, I'm sorry, but I would like to take this opportunity to ask you

You have compared the mining of windows vs linux, does performance improve much?

I'm thinking about trying a rig with linux

Hi mate,

I haven't tried yet windows, just sort of finish linux setup. But I do have everything ready for windows, basically I have other ssd with win 10 on board(prepared for tune cards), hope I'll find time today to test windows mining with same hardware setup before graph cards bios tune and after.

[numeracci]

Hi,
 today I'm getting various alert report from Eset Nod32 antivirus regarding Claymore 10.3
It says Win64/CoinMiner.BX is a trojan... I know a lot of times these are false positive....but I'm slightly worried about this.
Anyone else experienced the same issue?

I am also seeing this

And.....are you still mining? Do you think this is normal? First time happening to me in a couple months

[et0nnic]

Hi,
 today I'm getting various alert report from Eset Nod32 antivirus regarding Claymore 10.3
It says Win64/CoinMiner.BX is a trojan... I know a lot of times these are false positive....but I'm slightly worried about this.
Anyone else experienced the same issue?

I am also seeing this

And.....are you still mining? Do you think this is normal? First time happening to me in a couple months

yep still mining, never seen it flagged before though.

[Asgaroth]

Using 10.2 on Ubuntu 16.04 with dual mining, but quite often getting error Out Of Memory: Out of memory: Kill process 1842 (ethdcrminer64) score 0 or sacrifice chil. Any idea why? thanks

That looks like the OOM killer under linux, you need to see whats eating all your memory/swap on your box. Linux's OOM killer will nuke apps it deems uses most memory (simplistic explanation) just to keep the box running.

See here for a more in depth explanation.

You can disable it and/or increase your physical memory/swap.

Hope this helps.

[CryptonikaTrade]

Wow new version of my favourite miner app! Thanks Claymore

[nzalog]

So is there any reason why I would not want to run a separate instance of Claymore for each GPU? I'm using the "-di <gpu#>" switch to only select one card per instance.

I'm finding this much better when it comes to tuning a setup since one card crashing doesn't cause all cards to reload and waste precious mining time.

The only downside I'm seeing is reported hashrate on the pool is wrong since all instances have the same miner name but the calculated average looks spot on. Of course it might use a bit more memory and CPU but I don't think it's anything significantly important.

[cryptoillusion1]

So is there any reason why I would not want to run a separate instance of Claymore for each GPU? I'm using the "-di <gpu#>" switch to only select one card per instance.

I'm finding this much better when it comes to tuning a setup since one card crashing doesn't cause all cards to reload and waste precious mining time.

The only downside I'm seeing is reported hashrate on the pool is wrong since all instances have the same miner name but the calculated average looks spot on. Of course it might use a bit more memory and CPU but I don't think it's anything significantly important.

" since all instances have the same miner name" - To get individual names use /Miner01 /Miner02 etc where you have the miner name in each bat file.

[nzalog]

So is there any reason why I would not want to run a separate instance of Claymore for each GPU? I'm using the "-di <gpu#>" switch to only select one card per instance.

I'm finding this much better when it comes to tuning a setup since one card crashing doesn't cause all cards to reload and waste precious mining time.

The only downside I'm seeing is reported hashrate on the pool is wrong since all instances have the same miner name but the calculated average looks spot on. Of course it might use a bit more memory and CPU but I don't think it's anything significantly important.

" since all instances have the same miner name" - To get individual names use /Miner01 /Miner02 etc where you have the miner name in each bat file.

Ya, I know it's just not worth the work to get the correct hashrate to be reported.

I simply did something like this in my start.bat:
start "0" EthDcrMiner64.exe -mode 1 -ftime 10 -ethi 16 -altnum 3 -platform 2 -mport 3330 -mpsw pass -di 0
start "1" EthDcrMiner64.exe -mode 1 -ftime 10 -ethi 16 -altnum 3 -platform 2 -mport 3331 -mpsw pass -di 1
start "2" EthDcrMiner64.exe -mode 1 -ftime 10 -ethi 16 -altnum 3 -platform 2 -mport 3332 -mpsw pass -di 2

...and so on.

All my pool config is in epool.txt and this method does not need copies of the miner folder, so all instances are running from the one folder and exe.

Just wondering if there are any technical benefits of having all cards run under one instance like more efficiency etc...

[Biodom]

Something peculiar with VEGA 56 (bios flashed to 64) starting today:

card shuts down (mining), fans go full throttle, no PCI lights
restart
card mines for 30-40 min just fine, temp 72C, then restarts again

both 10.0 and 10.3 miner, blockchain driver (from 9/22), win 10

tried reinstalling driver with DDU-same thing (did not help); plenty of power and other three cards (not flashed) are fine

Anybody seen anything like this?
What to do-flash it back to 56, reflash to 64 again?

[MarkR8673]

Anyone else notice a drop in performance after upgrading to 10.3?

I noticed this morning that my average effective hashrate through ethermine has dropped.

[nico610]

Can you help me for this error : Temperature control thread hangs, need to restart miner!

My card has temps 62, the miner restart every 2 hours or less, every 20mn this morning

I have this error on claymore 10.2 and 10.3, i don't use previous version.
I haven't this problem with claymore for cryptonight or equihash

[muzuca]

Anyone else notice a drop in performance after upgrading to 10.3?

I noticed this morning that my average effective hashrate through ethermine has dropped.

I noticed that too, but I was thinking that maybe is the difficulty incresing.

Lets see if anyone else noticed too.