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

[janding]

does anyone still dual mine? or is it dead?

In my past experience was not worth it. More power used. More heat generated. Small extra profit. Shortens life of the video cards.

God how I hate people who BEG for donations.
Get a job.

[1714811457]

1714811457

[1714811457]

1714811457

[1714811457]

1714811457

[iSuX]

Ethermine performance with Claymore.

Hello fellow miners.
I'm currently running some 10 day comparative testing, two identical rigs, identical hardware, same number of GPUs etc, (more on that later), but as it happened yesterday another GPU arrived, and it happened to bring the overall gpu count to an odd number.

So as I didn't want to upset the comparative test by having 1 more GPU running on one rig than the other, I decided to start a second instance of claymore, (using only this single GPU), and so as not to mess up the graphs at ethermine, I targeting this single GPU at ETC.

What is interesting is, after 24 hours, and allowing for the 6h average to normalise, this single instance, one GPU, is averaging above my local hash rate, while ETH is consistently lower.


Now, by no means can any conclusions be drawn at this stage, but it got me wondering....

So, for the next test, I'm going to configure 8 claymore instances, single GPU each, and go head to head with the other rig, running one claymore instance with 8 gpu.

I'm wondering if/how/what ethermine is doing differently, that single gpu instance is local hashing at 32.15, rock solid, but the @pool average in the last 12 hours, 35.25~33.6MH/s. (plus 7%!)

While the other rig, is running at -4%

Have any of you guys experienced something like this, or can point me to previous comparison tests?

Cheers

well, I already had my farm with more hashrate on 24 hours than supposed to. Wait another 24/48 hours to be sure it is not just randomness.

What are ou testing? pool or miner?

Yeah, I spotted that also. Actually I was testing against 2 different pools, that test will wrap next Monday evening, (7 days).
This whole ETC thing just happened to popup in the last 24hrs, and right now, I don't have any spare rigs to run a proper comparative test, (but I am starting to sketch out that test).

Clearly pools have a bunch of algorithms to divide up the work, load balance, and match reported hashing power to jobs, I wonder how well that scales.
Obviously not all pools do that the same way, and in fact, doing that well SHOULD be a selling point for them, secret as it may be.

I'm assuming ethermine use more or less the same mechanism on their ETH and ETC pools, (another test :-)

But I'm going to try a 1:1 and 8:1 side by side next week on the ETC pool.
Will share the findings for discussion.


Side note: ETC has indeed dropped 6hr average below local hash rate, 14:30-ish UTC.
Happy mining everyone.

[knohult]

Ok, afterburner.
Less than ideal to use that imho, any application can crash, what damage can happen if afterburner crashes? I'd rather not find that out the hard way.

Did you spot in 11.7, Nvidia temperature control is now supported?
 added temperature management and overclock support for recent Nvidia cards in Windows: "-tt", "-powlim", "-cclock", "-mclock", "-tt", "-fanmax", "-fanmin" options are supported for Nvidia too.

I'd suggest using it. That way, if claymore crashes, (no more work is pushed to GPUs), and at least your GPUs revert to bios control, cool down etc.
Right now, if your afterburner crashes, and claymore carries on, you're going to potentially cook those cards, or force them to their hardware trip point, (probably something scary like 100C plus).

Good  luck.

I didn´t see that. I can configure it without afterburner. The cards is set to be at maximum 60C now. But they live between 45-60C.
Afterburner have failed, the hashrate will be lower then and I have an alarm so I notice it but it would be nice to let the miner handle all insted. Thanks!

[BryanMeLee]

If someone uses new Ubuntu 18.04 LTS, claymore ends with an error message:

Code:

/usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found ...

To correct it, just install older version of curl library

Code:

sudo apt install libcurl3

But what if libcurl4 is required for other applications installed?  I don't have a dedicated mining rig.  I use my desktop during off-hours.

[iSuX]

Ethermine performance with Claymore.

Hello fellow miners.
I'm currently running some 10 day comparative testing, two identical rigs, identical hardware, same number of GPUs etc, (more on that later), but as it happened yesterday another GPU arrived, and it happened to bring the overall gpu count to an odd number.

So as I didn't want to upset the comparative test by having 1 more GPU running on one rig than the other, I decided to start a second instance of claymore, (using only this single GPU), and so as not to mess up the graphs at ethermine, I targeting this single GPU at ETC.

What is interesting is, after 24 hours, and allowing for the 6h average to normalise, this single instance, one GPU, is averaging above my local hash rate, while ETH is consistently lower.


Now, by no means can any conclusions be drawn at this stage, but it got me wondering....

So, for the next test, I'm going to configure 8 claymore instances, single GPU each, and go head to head with the other rig, running one claymore instance with 8 gpu.

I'm wondering if/how/what ethermine is doing differently, that single gpu instance is local hashing at 32.15, rock solid, but the @pool average in the last 12 hours, 35.25~33.6MH/s. (plus 7%!)

While the other rig, is running at -4%

Have any of you guys experienced something like this, or can point me to previous comparison tests?

Cheers

well, I already had my farm with more hashrate on 24 hours than supposed to. Wait another 24/48 hours to be sure it is not just randomness.

What are ou testing? pool or miner?

Yeah, I spotted that also. Actually I was testing against 2 different pools, that test will wrap next Monday evening, (7 days).
This whole ETC thing just happened to popup in the last 24hrs, and right now, I don't have any spare rigs to run a proper comparative test, (but I am starting to sketch out that test).

Clearly pools have a bunch of algorithms to divide up the work, load balance, and match reported hashing power to jobs, I wonder how well that scales.
Obviously not all pools do that the same way, and in fact, doing that well SHOULD be a selling point for them, secret as it may be.

I'm assuming ethermine use more or less the same mechanism on their ETH and ETC pools, (another test :-)

But I'm going to try a 1:1 and 8:1 side by side next week on the ETC pool.
Will share the findings for discussion.


Side note: ETC has indeed dropped 6hr average below local hash rate, 14:30-ish UTC.
For the conspiracy freaks, I wonder if pools give easy jobs to new miners, suck you in etc :-)
Then again, it could be learning if your advertised hash rate is realistic, or just luck.

Happy mining everyone.

[Changeyourcoin]

Well, I need to know how I can do to mine ethereum with nanopool and blake 2 with nicehash?

[janding]

This was posted by wtfonly16 on the Phoenix thread a few minutes ago:
It was NOT posted by me !!!

wtfonly16:

this have claymore source in it i found it. it a timebomb that will mess with Gpu voltage to Blowed it
there is no phoenix, this was made by claymore to further his Strength in claymore miner monopoly.
after he explode all gpu, no one will ever use any other miner but claymore.

i will release my proof in 48 hours.


Me:
Maybe Claymore might want to respond to him.

[Jamsan]

This was posted by wtfonly16 on the Phoenix thread a few minutes ago:
It was NOT posted by me !!!

wtfonly16:

this have claymore source in it i found it. it a timebomb that will mess with Gpu voltage to Blowed it
there is no phoenix, this was made by claymore to further his Strength in claymore miner monopoly.
after he explode all gpu, no one will ever use any other miner but claymore.

i will release my proof in 48 hours.


Me:
Maybe Claymore might want to respond to him.

That's not even logical. Claymore wants to blow up every single person's rig that is using Phoenix, just so he can get back them back to Claymore to pay 1% instead? If he really is behind Phoenix, he's better off taking 100% of the .65% for people that use Phoenix, instead of getting 1% of the 100% of people with blown cards who aren't mining anymore...

The logic behind that comment is really non-nonsensical.

[olexko]

Overclock in bat file.

EthDcrMiner64.exe -epool eth-eu.dwarfpool.com:8008 -ewal WALLET -eworker w3 -epsw x -mport 0 -tstop 80 -tt 50 -powlim -30 -cclock -400 -mclock +290

After close miner, claymore don't reset overclock.
Run afterburner & see.
https://i.imgur.com/jlw6bkM.jpg
Why -200 instead -400 in memory clock?

[rline]

ETH: 1 pool is specified
Main Ethereum pool is eu1.ethermine.org:4444
DCR: 0 pool is specified
AMD OpenCL platform not found
Be careful with overclocking, use default clocks for first tests
Press "s" for current statistics, "0".."9" to turn on/off cards, "r" to reload pools, "e" or "d" to select current pool, "x" to select GPU
CUDA initializing...

NVIDIA Cards available: 6
CUDA Driver Version/Runtime Version: 9.1/8.0
GPU #0: GeForce GTX 1060 6GB, 6144 MB available, 10 compute units, capability: 6.1  (pci bus 1:0:0)
GPU #1: GeForce GTX 1060 6GB, 6144 MB available, 10 compute units, capability: 6.1  (pci bus 3:0:0)
GPU #2: GeForce GTX 1060 6GB, 6144 MB available, 10 compute units, capability: 6.1  (pci bus 5:0:0)
GPU #3: GeForce GTX 1060 6GB, 6144 MB available, 10 compute units, capability: 6.1  (pci bus 6:0:0)
GPU #4: GeForce GTX 1060 6GB, 6144 MB available, 10 compute units, capability: 6.1  (pci bus 7:0:0)
GPU #5: GeForce GTX 1060 6GB, 6144 MB available, 10 compute units, capability: 6.1  (pci bus 8:0:0)
Total cards: 6
No pool specified for Decred! Ethereum-only mining mode is enabled
ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
ETH: eth-proxy stratum mode
Watchdog enabled
Remote management (READ-ONLY MODE) is enabled on port 3333

ETH: Stratum - connecting to 'eu1.ethermine.org' <91.121.167.111> port 4444 (unsecure)
ETH: Stratum - Connected (eu1.ethermine.org:4444) (unsecure)
ETH: Authorized
Setting DAG epoch #184...
Setting DAG epoch #184 for GPU1
Setting DAG epoch #184 for GPU3
Setting DAG epoch #184 for GPU0
Setting DAG epoch #184 for GPU4
Setting DAG epoch #184 for GPU2
Setting DAG epoch #184 for GPU5
Create GPU buffer for GPU3
Create GPU buffer for GPU1
Create GPU buffer for GPU0
Create GPU buffer for GPU4
Create GPU buffer for GPU5
Create GPU buffer for GPU2
CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
Setting DAG epoch #184 for GPU3
GPU 3 failed
GPU 5 failed
GPU 3, CUDA error 11 - cannot write buffer for DAG
Setting DAG epoch #184 for GPU5
GPU 4 failed
GPU 5, CUDA error 11 - cannot write buffer for DAG
Setting DAG epoch #184 for GPU4
GPU 4, CUDA error 11 - cannot write buffer for DAG
Setting DAG epoch #184 for GPU1
GPU 1 failed
GPU 1, CUDA error 11 - cannot write buffer for DAG
ETH: 05/03/18-10:30:56 - New job from eu1.ethermine.org:4444
ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
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
GPU 3 failed
GPU 5 failed
GPU 4 failed
GPU 1 failed


I have set my VM to 16000 issue still persists. Can I have some help please.

[janding]

This was posted by wtfonly16 on the Phoenix thread a few minutes ago:
It was NOT posted by me !!!

wtfonly16:

this have claymore source in it i found it. it a timebomb that will mess with Gpu voltage to Blowed it
there is no phoenix, this was made by claymore to further his Strength in claymore miner monopoly.
after he explode all gpu, no one will ever use any other miner but claymore.

i will release my proof in 48 hours.


Me:
Maybe Claymore might want to respond to him.

That's not even logical. Claymore wants to blow up every single person's rig that is using Phoenix, just so he can get back them back to Claymore to pay 1% instead? If he really is behind Phoenix, he's better off taking 100% of the .65% for people that use Phoenix, instead of getting 1% of the 100% of people with blown cards who aren't mining anymore...

The logic behind that comment is really non-nonsensical.

Agree.
What a moron

[ivanpop]

What page file size should I set for 13 gpu rig?

[jamfro]

Major problems with windows 1803 update.

All of my rigs use  570 or 580

After update.  I can't get any rig to have more than 6 gpus attached, 10 out of 12 I can only get 5 gpus working.
Takes a very long time to initialize claymore miner.
If I try to go past 5 or 6 gpus claymore timesout/reset after 5 min.
Everything was working fine before the 1803 update with latest claymore and amd latest drivers

basically i have the same problem as https://bitcointalk.org/index.php?topic=1433925.msg36032619#msg36032619

There is nothing useful in logs/debug.

[androstan1234]

It's never a good idea to immediately update windows on a mining rig.

[iRrromka]

What page file size should I set for 13 gpu rig?

as much as you can afford

[Vann]

Major problems with windows 1803 update.

All of my rigs use  570 or 580

After update.  I can't get any rig to have more than 6 gpus attached, 10 out of 12 I can only get 5 gpus working.
Takes a very long time to initialize claymore miner.
If I try to go past 5 or 6 gpus claymore timesout/reset after 5 min.
Everything was working fine before the 1803 update with latest claymore and amd latest drivers

basically i have the same problem as https://bitcointalk.org/index.php?topic=1433925.msg36032619#msg36032619

There is nothing useful in logs/debug.

It's not a good idea to update to a new major Windows feature update as soon as it's released, since they often break compatibility with drivers and programs. It's better to wait until the mainstream build is released. The current v1803 build is essentially a beta preview build so that vendors can update drivers and software to be compatible with the new build.

In the Windows 10 Pro Group Policy Editor you can set Windows to only upgrade to feature updates when there enter a final release build.

Enable this policy to specify the level of Preview Build or Feature Updates to receive, and when.

* Preview Build - Fast: Devices set to this level will be the first to receive new builds of Windows with features not yet available to the general public. Select Fast to participate in identifying and reporting issues to Microsoft, and provide suggestions on new functionality.
* Preview Build - Slow: Devices set to this level receive new builds of Windows before they are available to the general public, but at a slower cadence than those set to Fast, and with changes and fixes identified in earlier builds.
* Release Preview: Receive builds of Windows just before Microsoft releases them to the general public.
* Semi-Annual Channel (Targeted): Receive feature updates when they are released to the general public.
* Semi-Annual Channel: Feature updates will arrive when they are declared Semi-Annual Channel. This usually occurs about 4 months after Semi-Annual Channel (Targeted), indicating that Microsoft, Independent Software Vendors (ISVs), partners and customer believe that the release is ready for broad deployment.

gpedit ==> Administrative Templates ==> Windows Components ==> Windows Updates ==> Windows Update for Business ==> Select when Preview Builds and Feature Updates are Received ==> Set to 'enabled' and  in the drop down select 'Semi-Annual Channel'.

[AzzAz]

What page file size should I set for 13 gpu rig?

as much as you can afford

try 32000 or 13 x (size of card memory)

[4ward]

Check Forager - automatic profit switching miner with MSI Afterburner integration
[/end_shameless_ad]

[Bigdrago]

Major problems with windows 1803 update.

All of my rigs use  570 or 580

After update.  I can't get any rig to have more than 6 gpus attached, 10 out of 12 I can only get 5 gpus working.
Takes a very long time to initialize claymore miner.
If I try to go past 5 or 6 gpus claymore timesout/reset after 5 min.
Everything was working fine before the 1803 update with latest claymore and amd latest drivers

basically i have the same problem as https://bitcointalk.org/index.php?topic=1433925.msg36032619#msg36032619

There is nothing useful in logs/debug.

It's not a good idea to update to a new major Windows feature update as soon as it's released, since they often break compatibility with drivers and programs. It's better to wait until the mainstream build is released. The current v1803 build is essentially a beta preview build so that vendors can update drivers and software to be compatible with the new build.

In the Windows 10 Pro Group Policy Editor you can set Windows to only upgrade to feature updates when there enter a final release build.

Enable this policy to specify the level of Preview Build or Feature Updates to receive, and when.

* Preview Build - Fast: Devices set to this level will be the first to receive new builds of Windows with features not yet available to the general public. Select Fast to participate in identifying and reporting issues to Microsoft, and provide suggestions on new functionality.
* Preview Build - Slow: Devices set to this level receive new builds of Windows before they are available to the general public, but at a slower cadence than those set to Fast, and with changes and fixes identified in earlier builds.
* Release Preview: Receive builds of Windows just before Microsoft releases them to the general public.
* Semi-Annual Channel (Targeted): Receive feature updates when they are released to the general public.
* Semi-Annual Channel: Feature updates will arrive when they are declared Semi-Annual Channel. This usually occurs about 4 months after Semi-Annual Channel (Targeted), indicating that Microsoft, Independent Software Vendors (ISVs), partners and customer believe that the release is ready for broad deployment.

gpedit ==> Administrative Templates ==> Windows Components ==> Windows Updates ==> Windows Update for Business ==> Select when Preview Builds and Feature Updates are Received ==> Set to 'enabled' and  in the drop down select 'Semi-Annual Channel'.

1803 is major release to the public. Not beta.

[Vann]

I have the policy set to 'Semi-Annual Channel', as I mentioned and i'm not getting the update, so if it was just released to the pubic, I won't get it for another ~4 months until it's been thoroughly tested.