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

[kgminer]

Hello,
Just set up Asus B250 board with 13 AMD RX 580's, this is my 4th miner and 2nd AMD rig exactly like this one.
Weird thing happening...when I start the CM miner, it gives me nothing past the start up screen:
Eth: 1 pool is specified
Main Ethereum pool is eth.suprnova.cc:5005
DCR: 0 pool is specified

Then after 5 minutes (apperently) it says:
Miner cannot initialize for 5 minutes, need to restart miner!

Here is command line:
ethdcrminer64.exe -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw ** -esm 3 -allpools 1 -dbg 1


I have a funny feeling it's to do with Windows Defender, because since I've been trying to get this thing working for the last few days, it never popped up and asked for me to Allow it through the firewall...but idk for sure. I shut it off and still no action.

I would post a pic to make it easier but I cannot figure out how to do that :-)

this is happening to me as well. Exactly same specs
Asus B250 board with 13 AMD RX 580's
Windows 10 version 1803 (build 17134.81), fully patched (patched yesterday)
16 GB minimum virtual RAM, 100 GB maximum
windows defender disabled



I installed windows, AMD drivers and one GPU(rx580), tested mining, it worked fine.

Now, I have added 5 more GPUs and then decided to test, the problem started
So far uninstalled and reinstalled AMD drivers
debug log doesn't say much
tried -di 0 (command) no luck
Not sure what's happening here

Okay, so I have managed to workaround the problem in Windows 1803 version, ASUS B250, AMD driver 18.3.4

1) Disabled Windows Firewall (disabled via service) and rebooted, this intermittently fixed the problem for me
2) Then I disabled "Intel onboard GPU (Yes driver of this GPU is up to date)" so now every time I start miner, it takes a bit of time to start but works fine.

I still believe it's problem with Windows 1803 version as my other rigs are working fine.

[kgminer]

this is happening to me as well. Exactly same specs
Asus B250 board with 13 AMD RX 580's
Windows 10 version 1803 (build 17134.81), fully patched (patched yesterday)
16 GB minimum virtual RAM, 100 GB maximum
windows defender disabled



I installed windows, AMD drivers and one GPU(rx580), tested mining, it worked fine.

Now, I have added 5 more GPUs and then decided to test, the problem started
So far uninstalled and reinstalled AMD drivers
debug log doesn't say much
tried -di 0 (command) no luck
Not sure what's happening here

Hi! I have the same issues with asrock h110 btc, sapphire rx580 (windows 10 1803, amd 18.5.1) it worked fine under smos, but started to crash.
With up to 5 cards everything works, but it starts to mine after 2-3 minutes

15:04:46:888   518   ETH: 1 pool is specified
15:04:46:899   518   Main Ethereum pool is eu1.ethermine.org:5555
>>>15:04:46:904   518   DCR: 0 pool is specified
15:05:17:117   1d44   
15:05:47:332   1d44   
15:06:17:602   1d44   
15:06:50:469   1d44   
15:07:22:741   1d44   
15:07:52:973   1d44   
>>>>15:08:01:117   518   OpenCL platform: AMD Accelerated Parallel Processing
15:08:01:163   518   OpenCL initializing...

15:08:01:167   518   AMD Cards available: 5


When i add more cards it freezes here “DCR: 0 pool is specified”

I had the same issue with RX580 card, read my previous post and try the workaround.

[kgminer]

Hi Everyone,

Is there a way to make Claymore's miner auto switch between 2 ETH wallet address ?  kinda like how the Devfee works ?

I'm helping my friend run & maintain his farm & for payment I can have all the miner mine to my wallet for 1 day every week, I wish to set every Sunday to mine to my wallet then after that it should auto switch back to my friends wallet.

For the time being I have to manually close & run between 2 .bat files, so i'm wondering is there anyway to make my life easier.

We're running on Windows 10, I'm not familiar with Linux at all.

Just install two instances of Claymore and have some GPUs mine for you

Hi, thanks for replying. If I install 2 instance of Claymore, then it would be mining all the time to both wallet, I just wish for the onwer's claymore to stop for 1 day every week. I have plans for the future that i might use that one day to mine something else other than ETH but for the time being its only ETH.

The farm has 40 over rigs, doing it manually is kinda tiring.  

if it is windows, you can try using windows task scheduler

run your customer's instance Monday to Sat and your instance on Sunday.

Thank you Jamsan & kgminer for the suggestion, the task scheduler trick works perfectly for me.  

I have some problem with most of the Nvidia rigs, you see after 30 minutes of mining, everything slows down & lags almost to a halt except for the Claymore miner, if i were to close the miner & start it up again, it won't run, the Claymore miner will stuck at scanning GPU. So what i normally did is to restart the rig manually then run the .bat files that i needed.  

All the AMD rigs doesn't have the windows lag issue. only half of the Nvidia rigs has this problem not all, i can't seem to solve it even if I clone the OS & settings over.

Even though I recommended you this workaround, but in the longer run, this would affect the stability of your clients' rigs. I have found if I leave rig untouched it works sweet, but if I had to kill or close the claymore process for an update or troubleshooting, it sometimes takes a bit of time again to stabilize the rigs.

[74hawksfan]

Hello,
Just set up Asus B250 board with 13 AMD RX 580's, this is my 4th miner and 2nd AMD rig exactly like this one.
Weird thing happening...when I start the CM miner, it gives me nothing past the start up screen:
Eth: 1 pool is specified
Main Ethereum pool is eth.suprnova.cc:5005
DCR: 0 pool is specified

Then after 5 minutes (apperently) it says:
Miner cannot initialize for 5 minutes, need to restart miner!

Here is command line:
ethdcrminer64.exe -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw ** -esm 3 -allpools 1 -dbg 1


I have a funny feeling it's to do with Windows Defender, because since I've been trying to get this thing working for the last few days, it never popped up and asked for me to Allow it through the firewall...but idk for sure. I shut it off and still no action.

I would post a pic to make it easier but I cannot figure out how to do that :-)

this is happening to me as well. Exactly same specs
Asus B250 board with 13 AMD RX 580's
Windows 10 version 1803 (build 17134.81), fully patched (patched yesterday)
16 GB minimum virtual RAM, 100 GB maximum
windows defender disabled



I installed windows, AMD drivers and one GPU(rx580), tested mining, it worked fine.

Now, I have added 5 more GPUs and then decided to test, the problem started
So far uninstalled and reinstalled AMD drivers
debug log doesn't say much
tried -di 0 (command) no luck
Not sure what's happening here

Okay, so I have managed to workaround the problem in Windows 1803 version, ASUS B250, AMD driver 18.3.4

1) Disabled Windows Firewall (disabled via service) and rebooted, this intermittently fixed the problem for me
2) Then I disabled "Intel onboard GPU (Yes driver of this GPU is up to date)" so now every time I start miner, it takes a bit of time to start but works fine.

I still believe it's problem with Windows 1803 version as my other rigs are working fine.

So...rookie mistake on my part...
I didn't go through and fully set up the bios after I flashed new bios, I forgot to enable CSM.  Enabled and all the sudden I was able to get OpenCL, which in turn gave me CM functionality.
Sorry guys, hope this at least helped in some way.
FYI, I'm on 1709 with no updates, newest AMD driver 15.5.1

[Jonet]

Tonight, I will go all the way back to 1709 with NO UPDATES, and see if it works.  If not, I will try 1607 with NO UPDATES and see if that works.  So bothersome :-)

If you install 1709 and set "feature updates" to be deferred for 365 days you will not get 1803. Windows Update - Advanced options.

[Claymore]

Anyway, I will release new version in a few days, Linux version will work properly in latest Ubuntu too.

how about that?

I will release new version in 1-3 days.

[sidaliroy]

Anyway, I will release new version in a few days, Linux version will work properly in latest Ubuntu too.

how about that?

I will release new version in 1-3 days.

Is there AMD's hashrate improvement on the new version?

[sedde]

Anyway, I will release new version in a few days, Linux version will work properly in latest Ubuntu too.

how about that?

I will release new version in 1-3 days.

Mr. Claymore,

dual mining keccak with my rx580's i have found something interesting.

While mining b2s the dcri has to go from 40-57 for max results and we had a lot of play for fine tuning, with keccak, i find that 8 is a bit too much on the power consuming, and 7 is a little bit to low.

Can i do something to alleviate that ? i dont think a 7,5 value will work right ?

[MrJaekin]

I'd LOVE to see a Wild Keccak miner from Claymore.   

[xunl]

Claymore 11.7 watchdog not working.

This is the 1st time ever happened to me. Normally, when gpu shows hashrate at 0.00 mh/s for about 1~2 minutes, watchdog would catch the crash and restart the miner by default.

Last night after epoch changed to 190, one of my GPU (RX580 8G) crashed during DAG generation. So the hashrate was 0.00 mh/s, the only difference this time was it stayed at 0.00 for 2.5 hours or so, watchdog never caught this crash even the hb time was 418109 (normally watchdog restart the miner when hb time > 20000). Eventually I caught the error and restart the miner on my own. Watchdog was very reliable in catching crash and restart miner in the past, but this time it failed. Why?

[adaseb]

Anyway, I will release new version in a few days, Linux version will work properly in latest Ubuntu too.

how about that?

I will release new version in 1-3 days.

Is there AMD's hashrate improvement on the new version?

There won't be any hash rate improvements on Dagger hashimoto ever most likely.

It's the way the algo is designed, there isn't room to improve it. The way that the ETH dev team designed it back in 2015 is the way it remains today.

Only improvements are usually in stability and the dual mining functionality.

Only way to improve speed is to get a better GPU or overclock your system.

[74hawksfan]

I don't see anything in the read me text, is there a command that will give me an average of hash rate versus just what it was most recently?  Seems like an average would be very useful when overclocking.

[Grumble Bumpkin]

I have a strange problem with my miner since Windows 10 1803 and I wonder if any of you have had similar issues that you've solved. The rig is a tiny hobby system: a B250 Mining Expert with four RX580's of varying brands. All cards have modded BIOSs, and I overclock using my start.bat options.

I looked back through the mining logs from Claymore (11.2 at the time) to see that before the update restart, all cards were going at near 31 Mh/s, a rate that it had been maintaining for months with no problem. After the update, all cards were running at 18.5 Mh/s.

When I noticed, I updated my AMD drivers to 18.5.1 and set it to compute mode, and updated Claymore to 11.7. At that point, one of my four cards was back to 30 Mh/s, all the rest remained at 18.5 Mh/s. I've checked my VM, which is at 48000 MB, so I doubt that's an issue. I haven't managed to locate anyone else on here reporting a similar issue, so I'm wondering if any of you have dealt with this and if so, how?

Thanks!

[adaseb]

Is there anyway to get the Claymore to manage the core and memory clock under Linux ?

When I specific a fan speed, mclock or cclock nothing happens when it loads.

When ethdcrminer first starts it gives an error that the AMD ADL drivers are missing.

I tried searching and googling and none of those results are working. It seems the only method is to do a vbios mod in windows and flash it.

Really surprised there is no software like MSIAfterburner for this.

[74hawksfan]

I have a strange problem with my miner since Windows 10 1803 and I wonder if any of you have had similar issues that you've solved. The rig is a tiny hobby system: a B250 Mining Expert with four RX580's of varying brands. All cards have modded BIOSs, and I overclock using my start.bat options.

I looked back through the mining logs from Claymore (11.2 at the time) to see that before the update restart, all cards were going at near 31 Mh/s, a rate that it had been maintaining for months with no problem. After the update, all cards were running at 18.5 Mh/s.

When I noticed, I updated my AMD drivers to 18.5.1 and set it to compute mode, and updated Claymore to 11.7. At that point, one of my four cards was back to 30 Mh/s, all the rest remained at 18.5 Mh/s. I've checked my VM, which is at 48000 MB, so I doubt that's an issue. I haven't managed to locate anyone else on here reporting a similar issue, so I'm wondering if any of you have dealt with this and if so, how?

Thanks!

That's really interesting, I have 13 cards on same board, and I just added one of them to the system. Should be the best one for mining but it's running at 18 mh/s and all others 25+.
Love to know what's going on there, I'm in newest CM and newest driver as well, Win10 1709

[Jonet]

I have a strange problem with my miner since Windows 10 1803 and I wonder if any of you have had similar issues that you've solved. The rig is a tiny hobby system: a B250 Mining Expert with four RX580's of varying brands. All cards have modded BIOSs, and I overclock using my start.bat options.

I looked back through the mining logs from Claymore (11.2 at the time) to see that before the update restart, all cards were going at near 31 Mh/s, a rate that it had been maintaining for months with no problem. After the update, all cards were running at 18.5 Mh/s.

When I noticed, I updated my AMD drivers to 18.5.1 and set it to compute mode, and updated Claymore to 11.7. At that point, one of my four cards was back to 30 Mh/s, all the rest remained at 18.5 Mh/s. I've checked my VM, which is at 48000 MB, so I doubt that's an issue. I haven't managed to locate anyone else on here reporting a similar issue, so I'm wondering if any of you have dealt with this and if so, how?

Thanks!

That's really interesting, I have 13 cards on same board, and I just added one of them to the system. Should be the best one for mining but it's running at 18 mh/s and all others 25+.
Love to know what's going on there, I'm in newest CM and newest driver as well, Win10 1709

Did you set all GPUs to compute? It is a setting in the registry under each GPU. With AMD settings software you have to set them one by one. CM with Y or AMD-Compute-Swithcer will set all installed GPUs to compute, but when you add GPUs after that, they will not be set to compute by default. Sorry if you already knew this.

[oup59]

Do u still dual mine? Look like most of dual  mineable alts got ASICS treatment.

[sw00rdfish]

Anyway, I will release new version in a few days, Linux version will work properly in latest Ubuntu too.

how about that?

I will release new version in 1-3 days.

Claymore v11.7 dual mine keccak it easily hit -tstop 70 in 10-15 minutes whilst been fine tuning -mclock from 2130 down to 1900 without luck. Mining with DCR was not an issue though. Is this a bug?

[kgminer]

Do u still dual mine? Look like most of dual  mineable alts got ASICS treatment.

yes I do, but you gotta keep an eye on the market and switch to low difficulty coins

[kgminer]

Anyway, I will release new version in a few days, Linux version will work properly in latest Ubuntu too.

how about that?

I will release new version in 1-3 days.

Claymore v11.7 dual mine keccak it easily hit -tstop 70 in 10-15 minutes whilst been fine tuning -mclock from 2130 down to 1900 without luck. Mining with DCR was not an issue though. Is this a bug?

What is dcri value are you using?
what is minimum and max fan speed?
I mine using Keccak, 6 or 7 dcri value and 60% max speed works fine for me
My temp range 60-67
if you are located in a hotter place, change max fan speed to 80 or 90%