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

[Dzeronimo]

What version Claymore's runs the best with AMD rx 570 and 580 8gb cards and what driver should I install?

On Windows, I'd go with either the blockchain driver or something around 17.11 (whatever the first WQHL version is after they added "large page" support to the mainline drivers).

On LINUX, 17.50 seems a lot more stable than the blockchain drivers, but you have to modify one of the driver modules to get ANY support for undervolting or underclocking the core.

The latest Adrenalin driver works perfectly well for RX cards. It's pointless to intentionally install older drivers.

Does it work with BIOS modded cards?
I've seen conflicting info about which Adrenalin drivers do so and which don't.

That's also why Claymore's recommendation of 16.12.x made ZERO sense, as 16.11.x and up DISABLED support for BIOS modded cards while 16.9.x and 16.10.x DID work with them.

I'm using the latest AMD Adrenalin drivers and latest Claymore miner and they work perfectly on my RX570 with custom BIOS.

[1714149243]

1714149243

[1714149243]

1714149243

[1714149243]

1714149243

[1714149243]

1714149243

[nazarpechka]

>>>>>>>>>>LuckyPool<<<<<<<<<<
Get the profit you deserve!

Check out new awesome mining pool for Verge blake2s. This pool was made specially for people using Claymore Ethereum miner dual mode.

Our features:

- nice fee 1%
- fast dedicated server in Germany with low latency
- 99% uptime, stable mining
- WTM earnings (±10%)
- payout every 2 hours
- nice community in Telegram
- NEW: Telegram Bot to check balances and workers without viewing site

How to mine?

Code:

-dpool stratum+tcp://mine.luckypool.xyz:5766 -dwal WALLET -dpsw c=XVG.WORKER -dcoin blake2s -dcri 45 - VERGE

Here are examples of batch files for Claymore

Thanks for attention

[potificate]

Still learning here...

The first page still says "10xx cards in Windows 10 x64: just use latest 372.54 drivers from Nvidia website"

It appears that 372.54 is about a year and a half old. Is that really best or should I use the latest (which is now 391.35)?

Thanks!

373.06 is probably the best overall driver for anything before the 1070 ti - not sure on Windows for that GPU or the 1050/1050ti but LINUX mining likes 384.98 very well indeed and that version works stable with older cards as well.

Thanks! I'll give that a try... is it because it's simply stable or that one can overclock cards higher than when using newer drivers? (I have 1060 6GB cards)

[rufo28]

Hello Gents,

I would like to share my issue using claymore (new or old) versions.
My RIG consists of 3 AMD and 7 Nvidia (2x1080 and 5x1080Ti).
When i ran it for mining only Ethereum, there's a "Cuda error 11 - cannot write buffer for DAG".
I already put VM max to 16000MB , but still it will show this error.

Experiment 1 : I separate running my bat file for the 3 AMD ( -platform 1 , all are working and running ), then ran the 7 Nvidia bat file (-platform 2, 2-3 cards has this error)
Experiment 2 : I ran in one bat file (-platform 3) all AMD and Nvidia Cards, results still the same 2-3 cards has the error.
Experiment 3 : I ran in one bat file (-platform 3 , -di 01234567), AMD and Nvidia ( excluding 2 cards  - either AMD or Nvidia) it works fine and continuously running..

So , is there any limitation for the claymore miner in number of cards in RIG?

Thanks and much appreciated if you can clear this up..

[AzzAz]

Hello Gents,

I would like to share my issue using claymore (new or old) versions.
My RIG consists of 3 AMD and 7 Nvidia (2x1080 and 5x1080Ti).
When i ran it for mining only Ethereum, there's a "Cuda error 11 - cannot write buffer for DAG".
I already put VM max to 16000MB , but still it will show this error.

Experiment 1 : I separate running my bat file for the 3 AMD ( -platform 1 , all are working and running ), then ran the 7 Nvidia bat file (-platform 2, 2-3 cards has this error)
Experiment 2 : I ran in one bat file (-platform 3) all AMD and Nvidia Cards, results still the same 2-3 cards has the error.
Experiment 3 : I ran in one bat file (-platform 3 , -di 01234567), AMD and Nvidia ( excluding 2 cards  - either AMD or Nvidia) it works fine and continuously running..

So , is there any limitation for the claymore miner in number of cards in RIG?

Thanks and much appreciated if you can clear this up..

Try VM 32000

[rufo28]

Hello Gents,

I would like to share my issue using claymore (new or old) versions.
My RIG consists of 3 AMD and 7 Nvidia (2x1080 and 5x1080Ti).
When i ran it for mining only Ethereum, there's a "Cuda error 11 - cannot write buffer for DAG".
I already put VM max to 16000MB , but still it will show this error.

Experiment 1 : I separate running my bat file for the 3 AMD ( -platform 1 , all are working and running ), then ran the 7 Nvidia bat file (-platform 2, 2-3 cards has this error)
Experiment 2 : I ran in one bat file (-platform 3) all AMD and Nvidia Cards, results still the same 2-3 cards has the error.
Experiment 3 : I ran in one bat file (-platform 3 , -di 01234567), AMD and Nvidia ( excluding 2 cards  - either AMD or Nvidia) it works fine and continuously running..

So , is there any limitation for the claymore miner in number of cards in RIG?

Thanks and much appreciated if you can clear this up..

Try VM 32000

Thanks for the response, i will try and check..
Will inform you..

[Premiermine]

https://premiumminer.com/images/advert.png

https://premiumminer.com/

0% FEE UNTIL BETA PERIOD - REAL 1% FEE AFTER BETA.
NO HIDDEN FEES
REGULAR PAYS - 2 HOURS

Claymore Dual Mining XVG-blake2s:
-o stratum+tcp://mine.premiumminer.com:5766 -dwal <WALLET_ADDRESS> -dpsw c=XVG

Thanks for joining.
[/quote]

[R0mi]

What version Claymore's runs the best with AMD rx 570 and 580 8gb cards and what driver should I install?

On Windows, I'd go with either the blockchain driver or something around 17.11 (whatever the first WQHL version is after they added "large page" support to the mainline drivers).

On LINUX, 17.50 seems a lot more stable than the blockchain drivers, but you have to modify one of the driver modules to get ANY support for undervolting or underclocking the core.

The latest Adrenalin driver works perfectly well for RX cards. It's pointless to intentionally install older drivers.

Does it work with BIOS modded cards?
I've seen conflicting info about which Adrenalin drivers do so and which don't.

That's also why Claymore's recommendation of 16.12.x made ZERO sense, as 16.11.x and up DISABLED support for BIOS modded cards while 16.9.x and 16.10.x DID work with them.

You will get much better performance, in my experience, from the latest Adrenaline drivers.

Here is the trick for modded bios files:  If these are fresh cards, apply the bios mods using ATIFlash, install the new driver but do not restart.

After installing the Adrenaline drivers on a rig whose cards have modded RX bios mods, run 1.4.6 of atikmdag-patcher.exe prior to restarting.  Then restart.  All should be good.

[rufo28]

Hello Gents,

I would like to share my issue using claymore (new or old) versions.
My RIG consists of 3 AMD and 7 Nvidia (2x1080 and 5x1080Ti).
When i ran it for mining only Ethereum, there's a "Cuda error 11 - cannot write buffer for DAG".
I already put VM max to 16000MB , but still it will show this error.

Experiment 1 : I separate running my bat file for the 3 AMD ( -platform 1 , all are working and running ), then ran the 7 Nvidia bat file (-platform 2, 2-3 cards has this error)
Experiment 2 : I ran in one bat file (-platform 3) all AMD and Nvidia Cards, results still the same 2-3 cards has the error.
Experiment 3 : I ran in one bat file (-platform 3 , -di 01234567), AMD and Nvidia ( excluding 2 cards  - either AMD or Nvidia) it works fine and continuously running..

So , is there any limitation for the claymore miner in number of cards in RIG?

Thanks and much appreciated if you can clear this up..

Try VM 32000

Thanks for the response, i will try and check..
Will inform you..

@AzzAz , Many thanks for your suggestion... currently after changing it to 32000 it run successfully for few minutes now.
I will observed further...

[janding]

The E3 is NOT going to "spike" the total network hashrate for Ethereum or the other ethash coins.

It will take about 2 MILLION of those units built and operating JUST TO MATCH THE EXISTING HASHRATE.

They aren't shipping 'till mid-July timeframe.

In the almost 2 YEARS since Bitmain introduced the S9 (which was a LOT more efficient than anything else available for months, and STILL is the most efficient SHA256 miner that is shipping) they might have sold a little over ONE MILLION of them (total SHA256 network hashrate says up to 2 million, but you also have to factor in the Avalon 721/741 sales, the eBang sales, sales of whatever miners with Bitfury chips have been built, however much hashrate LW.COM has on it's internally-built miners, and at least one "smaller fry" mining operation I know of that is using their own chip).

The E3 will push network hashrate - but it's NOT going to be a "spike", there is too much EXISTING hashrate from mining rigs that are the SAME OR BETTER efficiency than the E3 announced specs.


It's a lot closer to the situation in Scrypt mining when Bitmain introduced the L3 - which STILL hasn't managed to push all "older rigs" out of profitable service if you have cheap enough electric and has a LOT of competition helping it TRY to push A2/Titan/Alcheminers out of profitability.

Thanks for that information.  
It’s refreshing to see an intelligent and informative comment.
We need more of that.

[gt_addict]

Just a query if anyone can help. I keep getting a “socket was closed remotely (by pool)” message come up since i restarted my rig. I havent changed any settings and my internet connection is working fine. I have contacted the pool (ethermine) but no response yet. Just wondered if anyone else has experienced this problem lately?

Also shares seem to be in the 1500-2000ms+ range now rather than <100ms it was before.

[AzzAz]

Hello Gents,

I would like to share my issue using claymore (new or old) versions.
My RIG consists of 3 AMD and 7 Nvidia (2x1080 and 5x1080Ti).
When i ran it for mining only Ethereum, there's a "Cuda error 11 - cannot write buffer for DAG".
I already put VM max to 16000MB , but still it will show this error.

Experiment 1 : I separate running my bat file for the 3 AMD ( -platform 1 , all are working and running ), then ran the 7 Nvidia bat file (-platform 2, 2-3 cards has this error)
Experiment 2 : I ran in one bat file (-platform 3) all AMD and Nvidia Cards, results still the same 2-3 cards has the error.
Experiment 3 : I ran in one bat file (-platform 3 , -di 01234567), AMD and Nvidia ( excluding 2 cards  - either AMD or Nvidia) it works fine and continuously running..

So , is there any limitation for the claymore miner in number of cards in RIG?

Thanks and much appreciated if you can clear this up..

Try VM 32000

Thanks for the response, i will try and check..
Will inform you..

@AzzAz , Many thanks for your suggestion... currently after changing it to 32000 it run successfully for few minutes now.
I will observed further...

What drivers ( AMD & NVIDIA) are you using?

[Aziat]

Two cards in the system 5870 6870 produces this error "No ASM binary found for GPU".
On xmr-stak, everything works but the hashreid is much smaller. 9.7 also works . 270 in another assembly, too, works.

[big_daddy]

I'm dualmining on cryptocartel.one, I am getting only 34 XVG a day with 20Gh
according to whattomine I can mine around 90-100 XVGs a day

can someone share here some other results from other pool please

[QuintLeo]

Just a query if anyone can help. I keep getting a “socket was closed remotely (by pool)” message come up since i restarted my rig. I havent changed any settings and my internet connection is working fine. I have contacted the pool (ethermine) but no response yet. Just wondered if anyone else has experienced this problem lately?

Haven't ever seen it on ethermine, but I've seen it occasionally on nicehash when first starting up - seems to be a temporary "pool overloading on making new connections" issue, as it normally resolves itself in a few minutes.

Dropping the wait time down from the default 20 secs to 10 secs seemed to help a little, but that might have been a coincidence as I only tried that once.


I'm think Claymore dropped support for pre-GCN AMD cards somewhere along the line - he definitely has NOT added and has stated he has no plans TO add -asm cores for older cards so you might just need to reconfigure to "don't use ASM" on those.

[gt_addict]

Just a query if anyone can help. I keep getting a “socket was closed remotely (by pool)” message come up since i restarted my rig. I havent changed any settings and my internet connection is working fine. I have contacted the pool (ethermine) but no response yet. Just wondered if anyone else has experienced this problem lately?

Haven't ever seen it on ethermine, but I've seen it occasionally on nicehash when first starting up - seems to be a temporary "pool overloading on making new connections" issue, as it normally resolves itself in a few minutes.

Dropping the wait time down from the default 20 secs to 10 secs seemed to help a little, but that might have been a coincidence as I only tried that once.


I'm think Claymore dropped support for pre-GCN AMD cards somewhere along the line - he definitely has NOT added and has stated he has no plans TO add -asm cores for older cards so you might just need to reconfigure to "don't use ASM" on those.

Thank for the reply QuintLeo, im using 1070’s so havent got to worry about the AMD thing. Ive restarted the router, updated drivers to the wireless card and tried the US pool address aswell. Still the same problem. It means its registering 207mh but because of the connection issues its paying out for only 150mh effective hashrate.

[weigh2634]

i would like use Email Notifications in Remote manager, but it alway sending email ERROR, how do i fix it? thanks a lot.

ERROR:Error connecting with SSL.
Error connecting with SSL.
error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number

https://i.imgur.com/EpcVmXJ.png

[Digital_Seytan]

Hello Claymoreminers, I have a question among the users who have experience with this farmbatchbot download link: https://github.com/Undertrey/FarmWatchBot/releases
have used these with Claymoreminer 11.6   ---->> please share.

[gt_addict]

Just a query if anyone can help. I keep getting a “socket was closed remotely (by pool)” message come up since i restarted my rig. I havent changed any settings and my internet connection is working fine. I have contacted the pool (ethermine) but no response yet. Just wondered if anyone else has experienced this problem lately?

Haven't ever seen it on ethermine, but I've seen it occasionally on nicehash when first starting up - seems to be a temporary "pool overloading on making new connections" issue, as it normally resolves itself in a few minutes.

Dropping the wait time down from the default 20 secs to 10 secs seemed to help a little, but that might have been a coincidence as I only tried that once.


I'm think Claymore dropped support for pre-GCN AMD cards somewhere along the line - he definitely has NOT added and has stated he has no plans TO add -asm cores for older cards so you might just need to reconfigure to "don't use ASM" on those.

Thank for the reply QuintLeo, im using 1070’s so havent got to worry about the AMD thing. Ive restarted the router, updated drivers to the wireless card and tried the US pool address aswell. Still the same problem. It means its registering 207mh but because of the connection issues its paying out for only 150mh effective hashrate.

I have seen the same issue with ethermine, and only on a wireless connection using SSL.  Once I switch over to NON-SSL, I no longer get that issue.  I noticed this because my one rigs was sending a ton of stale shares to the pool, but my other rig wasn't (wired rig) and I assumed it was a specific rig issue with wireless connectivity since it was only one rig but both are on the same internet connection.  But switching back to NON-SSL should solve it until ethermine gets back to you.  On occasion I would notice the discnnect message also when using SSL on any ethermine server.

Thanks man. Ill give it a try later and see how i get on.

[gt_addict]

Managed to remote in and change it but still the same