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

[preda]

I'm using 372.54 drivers and still I can mine ethereum with all my 3gb cards..
I don't know for long again I could

[1713941301]

1713941301

[1713941301]

1713941301

[1713941301]

1713941301

[1713941301]

1713941301

[1713941301]

1713941301

[Ursul0]

I'm fine, thanks, is v11.7 too old and you want v11.8 right now?

Maybe...
since the new kernels for polaris (around v 11) I've started to experience application crashes (maybe once in a week across some dozen workers), which never happened to me before. my guess is that this new behavior has to do with the driver.(I'm mostly using 18.2.2)  likely occurs with higher mem overclock
I have hw watchdogs so the machine would restart if the system hangs, so the new versions actually exhibit degraded performance, comparing to the previous ones in this regard.
I can configure the watchdogs to monitor for a certain process(will have issues switching algoes), or finally setup Chocolatey:)
But figuring out what exactly is wrong would be of course much nicer.

[thomflash]

Hi all,

I have two rigs mining on Ethermine with Claymore 11.7 and I copied the bat-file to the new rig. Is it ok like this and will it register right at the pool? Or do I have to name it differently? Seems like in principal no worker name is needed on Ethermine?

Thanks for any info

[Claymore]

I'm fine, thanks, is v11.7 too old and you want v11.8 right now?

Maybe...
since the new kernels for polaris (around v 11) I've started to experience application crashes (maybe once in a week across some dozen workers), which never happened to me before. my guess is that this new behavior has to do with the driver.(I'm mostly using 18.2.2)  likely occurs with higher mem overclock
I have hw watchdogs so the machine would restart if the system hangs, so the new versions actually exhibit degraded performance, comparing to the previous ones in this regard.
I can configure the watchdogs to monitor for a certain process(will have issues switching algoes), or finally setup Chocolatey:)
But figuring out what exactly is wrong would be of course much nicer.

You can use "-oldkernels 1" if you don't like new kernels. A lot of modded BIOSes and OC settings were made for old kernels so new kernels can cause problems if you don't readjust these settings, "-oldkernels 1" option is the solution for this case.

[DUzP7sBr]

You can free use 18.3.4 - they working fine.

What about 18.10 for Ubuntu 16.04?
Currently I use:
amdgpu-pro 17.40-483984

is there 18.3.4 for Linux?

[sir4o]

Hi,

I just upgraded to 1803 using 11.7 miner version. The miner now gets stuck at:

https://ibb.co/jVAeR7

It stays there for at least 1,5 hours till now.

Looking forward to your help!

I just had Bill on the phone. He confirmed we should wait at least 1803 minutes before some hashes appear. MS fee, just one time though.

[jamfro]

The only solution I found for the taking over 5 minutes to intialize Claymore.  Is reinstall os and not 'upgrade' to 1803.   Or  Reduce the number of card in rig to under 5 sometimes 6.   There is something that happened with 1803 that causes  claymore initializing process to take much longer.   To the point where if you have anything past 5 or 6 cards it times out at a hard coded 5 min.  Hope Claymore fixes this problem soon, if he can.   It might be a problem in the OS.  I've been wondering if I was the only one having this problem. 

[Ursul0]

I'm fine, thanks, is v11.7 too old and you want v11.8 right now?

Maybe...
since the new kernels for polaris (around v 11) I've started to experience application crashes (maybe once in a week across some dozen workers), which never happened to me before. my guess is that this new behavior has to do with the driver.(I'm mostly using 18.2.2)  likely occurs with higher mem overclock
I have hw watchdogs so the machine would restart if the system hangs, so the new versions actually exhibit degraded performance, comparing to the previous ones in this regard.
I can configure the watchdogs to monitor for a certain process(will have issues switching algoes), or finally setup Chocolatey:)
But figuring out what exactly is wrong would be of course much nicer.

You can use "-oldkernels 1" if you don't like new kernels. A lot of modded BIOSes and OC settings were made for old kernels so new kernels can cause problems if you don't readjust these settings, "-oldkernels 1" option is the solution for this case.

the performance improvement on the new kernels is very nice...so...
I did adjustments where it was required switching to the new kernels... currently on 70% of my rigs(mainly 12 GPUs setups) runtime is 200+ hours (latest reboot 16 hours ago), still once a week one/few may crash, and I'm not sure I can do more "fine tuning" as it's not clear what the problem is...
Also it seems there's higher probability of miner application crash if xmrig cpu miner runs alongside Claymore.

[Call_Me_Bambi]

Hi all,

I have two rigs mining on Ethermine with Claymore 11.7 and I copied the bat-file to the new rig. Is it ok like this and will it register right at the pool? Or do I have to name it differently? Seems like in principal no worker name is needed on Ethermine?

Thanks for any info

You can set worker name for mining on Ethermine.org. They don't seem to show how to do this anymore but I looked up an old Claymore configuration I have, gave it a spin on Ethermine.org and the worker name showed up after a couple of shares had been found. So you could set a different worker name for each rig.
This is the config I used, it's for v9.7 but you can change it for the latest version.

Code:

EthDcrMiner64 -epool eu1.ethermine.org:4444 -ewal 0x75a5b475e9579a2156f433bccc6dabbac1b2e306.WorkerName -epsw x 

[Vann]

You will get MUCH fewer stale shares on Ethermine if you use the ssl stratum on the server closest to you e.g.

-epool stratum+ssl://us1.ethermine.org:5555

[LordX]

Win10 64Bit Version 10.0.16299.309
Claymore 11.7
GTX 1060 3GB x 8pcs , Driver 388.13 ( windows working on Intel iGPU ).
DAG 183 working fine ( in use 2621MB from 3072MB ) , DAG 184+ have error , like DAG size problem , but this is strange if we have like 400MB free ?

Any tip to fix this in windows 10 ? I know about windows 10 allocating more vram now ( for all cards ? or just desktop card ? ) like I see only ~70mb allocated from total 3072MB

376.33

I'm using 372.54 drivers and still I can mine ethereum with all my 3gb cards..
I don't know for long again I could

what Windows build exactly ? what Claymore ?
did you tested if DAG 186 or 187  will work ? , test command = EthDcrMiner64.exe -benchmark 186

[alizali]

why -cvddc does not effect on AMD cards in windows?

[preda]

Win10 64Bit Version 10.0.16299.309
Claymore 11.7
GTX 1060 3GB x 8pcs , Driver 388.13 ( windows working on Intel iGPU ).
DAG 183 working fine ( in use 2621MB from 3072MB ) , DAG 184+ have error , like DAG size problem , but this is strange if we have like 400MB free ?

Any tip to fix this in windows 10 ? I know about windows 10 allocating more vram now ( for all cards ? or just desktop card ? ) like I see only ~70mb allocated from total 3072MB

376.33

I'm using 372.54 drivers and still I can mine ethereum with all my 3gb cards..
I don't know for long again I could

what Windows build exactly ? what Claymore ?
did you tested if DAG 186 or 187  will work ? , test command = EthDcrMiner64.exe -benchmark 186

yes it works perfectly



6x 1060 3gb with 372.54 driver calymore 11.7
settings
tdp 65
core 0
memory 699

[LordX]

Win10 64Bit Version 10.0.16299.309
Claymore 11.7
GTX 1060 3GB x 8pcs , Driver 388.13 ( windows working on Intel iGPU ).
DAG 183 working fine ( in use 2621MB from 3072MB ) , DAG 184+ have error , like DAG size problem , but this is strange if we have like 400MB free ?

Any tip to fix this in windows 10 ? I know about windows 10 allocating more vram now ( for all cards ? or just desktop card ? ) like I see only ~70mb allocated from total 3072MB

376.33

I'm using 372.54 drivers and still I can mine ethereum with all my 3gb cards..
I don't know for long again I could

What DAG file ? 186 or higher ? you tested = EthDcrMiner64.exe -benchmark 186

yes it works perfectly

https://s7.postimg.cc/ov8dw5387/Cattura.jpg

6x 1060 3gb with 372.54 driver calymore 11.7
settings
tdp 65
core 0
memory 699

what Windows build exactly ? What DAG you mining right now ?
did you tested if DAG 186 or 187  will work ? , test command = EthDcrMiner64.exe -benchmark 186

[Dark Oopa]

Hello, I have downgraded my 1060 rig to windows 7 for them to work but I have one that have a wierd behaviour.

The average hahsrate poolwise is very low, about half what it should be. The miner show normal hashrate but with big downswings on regular basis. The CPU seems to be used a lot, all by claymore.
The thing is, no other rig have the same behaviour. They have the same cards, same OS, same drivers, same CPU...

Is anyone have an idea?

thx

[igotfits]

claymore 10.7, latest windows 10 update...

My AMD build working fine.

my Nvidia build all 0 MHs and restarting every few minutes.

[ShirKhan76]

Hi,

Is the option -logfile also available unter Linux? I tried to configure a specific logfile directory in the config.txt file with / and \ at the end of the line:

-logfile /var/log/miner/
or
-logfile /var/log/miner\

Correct permissions are set on the log directory.

After a miner restart the logfile won't be written in the specific log directory neither in the miner directory (anymore).

Thanks for helping!

Cheers
ShirKhan76

[rabbi-t]

-logfile /var/log/miner/

-logfile /var/log/miner/name_of_file

[jaxnatax]

Hallo,


I think I have found an issue with newest claymore miner releases.

Explanation:
accidentally I had an issue with my cooling system, because noted that the fans are running at 95%.
Fortunately they could still keep the core below 65celsius, so no harm happened in the cards.

I recovered the cooling system, but got even surprised after...'cause the cores cooled down to 57Celsius, but the fans'speed stucked at 95%
I just updated to v11.7, remodelled the issue, but it is the same.

Everything else is working (raising the fan speed, voltage controls) but only this what is not.
After restarting the miner the fan controls working right again - except the down stepping.

Please investigate and solve this issue if you get the same results and a solution is feasible.

Regards,
J

[thomflash]

Hi all,

I have two rigs mining on Ethermine with Claymore 11.7 and I copied the bat-file to the new rig. Is it ok like this and will it register right at the pool? Or do I have to name it differently? Seems like in principal no worker name is needed on Ethermine?

Thanks for any info

You can set worker name for mining on Ethermine.org. They don't seem to show how to do this anymore but I looked up an old Claymore configuration I have, gave it a spin on Ethermine.org and the worker name showed up after a couple of shares had been found. So you could set a different worker name for each rig.
This is the config I used, it's for v9.7 but you can change it for the latest version.

Code:

EthDcrMiner64 -epool eu1.ethermine.org:4444 -ewal 0x75a5b475e9579a2156f433bccc6dabbac1b2e306.WorkerName -epsw x 

Thanks! Works great now.