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

[Mannyx101]

Hello. I am trying to set up a miner as a work project. The main goal isnt to make money, its just to say that I know how to set up a miner. The work computer has a radeon rx 560 2gb card. I was wondering if the program would let me run the miner with this card. Thanks.

[Raja_MBZ]

Hello. I am trying to set up a miner as a work project. The main goal isnt to make money, its just to say that I know how to set up a miner. The work computer has a radeon rx 560 2gb card. I was wondering if the program would let me run the miner with this card. Thanks.

Hello! Yes, it should work. Give it a try.

[Privatoria]

As I read in the news, there will be new update of Ethereum in few months related to Constantinople hard fork. Dear Claymore! I think that you have to update your program to be ready for it.

[Call_Me_Bambi]

Hello. I am trying to set up a miner as a work project. The main goal isnt to make money, its just to say that I know how to set up a miner. The work computer has a radeon rx 560 2gb card. I was wondering if the program would let me run the miner with this card. Thanks.

This will show you what you can mine with a 2GB card "Current DAG Size" is what you want to look at.
https://investoon.com/tools/dag_size

[chinh.daongoc]

Hello Claymore

Could you add switch pool function to Remote Manager? I think it should be very useful

Thank you

[Ursul0]

@Claymore
It seems there's a correlation between using temps/fan control from the miner and "NVML: cannot get fan speed, error 999 (an internal driver error occurred)" errors, causing application restart (worker restart in my case)
The rig is Win10 with 10*1060*6gb and and latest drivers. I'm using -mclock and -pwlim with no issues running v11.9, but as soon as I set -tt into anything it will lead to the error above within minutes.

[AzzAz]

@Claymore
It seems there's a correlation between using temps/fan control from the miner and "NVML: cannot get fan speed, error 999 (an internal driver error occurred)" errors, causing application restart (worker restart in my case)
The rig is Win10 with 10*1060*6gb and and latest drivers. I'm using -mclock and -pwlim with no issues running v11.9, but as soon as I set -tt into anything it will lead to the error above within minutes.

I have better results with MSI AB than Claymore on Nvidia

[XiXiMios]

If you could create something that can push the data from the rigs to your server and then to the app on my iPhone, that would be awesome.  Realtime stats on all rigs.  Click on a rig name to get detailed stats on that particular machine.  Group/individual config for pools. etc etc.

[javilee94]

Hello guys,

Today I started having problems with my mining rig.

This is the problem I'm encountering

Once Claymore starts, after few minutes, this message appears:

WATCHDOG: GPU 1 hang in OpenCL call, exit
WATCHDOG: GPU 1 hang in OpenCL call, exit

Quit, please wait..

Restarting OK, exit...

Then my rig freezes..

I would appreciate some help.

Thanks

[Ursul0]

@Claymore
It seems there's a correlation between using temps/fan control from the miner and "NVML: cannot get fan speed, error 999 (an internal driver error occurred)" errors, causing application restart (worker restart in my case)
The rig is Win10 with 10*1060*6gb and and latest drivers. I'm using -mclock and -pwlim with no issues running v11.9, but as soon as I set -tt into anything it will lead to the error above within minutes.

I have better results with MSI AB than Claymore on Nvidia

Well... and my conclusion from the experience with MSI AB: do anything you must in order to avoid installing AB on your workers.

Anyways I had serious stability issues with this 10*1060 rig (lately it never held over 5-6 hours of constant work) , it was behaving like it had some problems with electricity/raisers/contacts.
It was constantly restarting/and occasionally hung in a way that only power down/up would make it recover. Reset wasn't doing the trick.

Fresh system image and NO AB install and now I have it running stable at 24.1MH at actually higher mclock than it was before and no issues whatsoever for 21+ hours.

[Indi27]

Any chance for zhash miner?

[leonix007]

Any chance for zhash miner?

you are in Ethash algo thread

Zhash is a hardened Equihash algorithm you might want to search on this threads

https://bitcointalk.org/index.php?topic=4466962.0

https://bitcointalk.org/index.php?topic=2021765.3300

https://bitcointalk.org/index.php?topic=2519271.880

[tg88]

Once Claymore starts, after few minutes, this message appears:

WATCHDOG: GPU 1 hang in OpenCL call, exit
WATCHDOG: GPU 1 hang in OpenCL call, exit

Quit, please wait..

Restarting OK, exit...

I would test this sequence:

- Install new Riser on GPU1.
- Check if you did not overclock or undervolt too much.
- Perform a test with another PSU.

[bitgameSolo]

@Claymore
It seems there's a correlation between using temps/fan control from the miner and "NVML: cannot get fan speed, error 999 (an internal driver error occurred)" errors, causing application restart (worker restart in my case)
The rig is Win10 with 10*1060*6gb and and latest drivers. I'm using -mclock and -pwlim with no issues running v11.9, but as soon as I set -tt into anything it will lead to the error above within minutes.

I have better results with MSI AB than Claymore on Nvidia

Well... and my conclusion from the experience with MSI AB: do anything you must in order to avoid installing AB on your workers.

Anyways I had serious stability issues with this 10*1060 rig (lately it never held over 5-6 hours of constant work) , it was behaving like it had some problems with electricity/raisers/contacts.
It was constantly restarting/and occasionally hung in a way that only power down/up would make it recover. Reset wasn't doing the trick.

Fresh system image and NO AB install and now I have it running stable at 24.1MH at actually higher mclock than it was before and no issues whatsoever for 21+ hours.

I also have a couple rigs that restart every 4-6 hours. Is there a log file in win7 that would give insight as to whether specifically AB or other driver was at fault? I've been assuming it was just an OC/ temp thing, but hard to figure out which card is at fault so I end up lowering OC on all of them.

[jackbox]

@Claymore
It seems there's a correlation between using temps/fan control from the miner and "NVML: cannot get fan speed, error 999 (an internal driver error occurred)" errors, causing application restart (worker restart in my case)
The rig is Win10 with 10*1060*6gb and and latest drivers. I'm using -mclock and -pwlim with no issues running v11.9, but as soon as I set -tt into anything it will lead to the error above within minutes.

I have better results with MSI AB than Claymore on Nvidia

Well... and my conclusion from the experience with MSI AB: do anything you must in order to avoid installing AB on your workers.

Anyways I had serious stability issues with this 10*1060 rig (lately it never held over 5-6 hours of constant work) , it was behaving like it had some problems with electricity/raisers/contacts.
It was constantly restarting/and occasionally hung in a way that only power down/up would make it recover. Reset wasn't doing the trick.

Fresh system image and NO AB install and now I have it running stable at 24.1MH at actually higher mclock than it was before and no issues whatsoever for 21+ hours.

I also have a couple rigs that restart every 4-6 hours. Is there a log file in win7 that would give insight as to whether specifically AB or other driver was at fault? I've been assuming it was just an OC/ temp thing, but hard to figure out which card is at fault so I end up lowering OC on all of them.

Have you looked at the Claymore log files to see what is causing the issues? Claymore log files are very detailed.

[adaseb]

Any of you guys running the old Radeon R9 290 Reference GPUs?

I've noticed that on stock settings (947/1250) the hashrate has decreased from 26.3Mhs to like 25Mhs.


Wondering if this is due to the DAG thrashing bug found on the older 280X GPUs.

[Ursul0]

@Claymore
It seems there's a correlation between using temps/fan control from the miner and "NVML: cannot get fan speed, error 999 (an internal driver error occurred)" errors, causing application restart (worker restart in my case)
The rig is Win10 with 10*1060*6gb and and latest drivers. I'm using -mclock and -pwlim with no issues running v11.9, but as soon as I set -tt into anything it will lead to the error above within minutes.

I have better results with MSI AB than Claymore on Nvidia

Well... and my conclusion from the experience with MSI AB: do anything you must in order to avoid installing AB on your workers.

Anyways I had serious stability issues with this 10*1060 rig (lately it never held over 5-6 hours of constant work) , it was behaving like it had some problems with electricity/raisers/contacts.
It was constantly restarting/and occasionally hung in a way that only power down/up would make it recover. Reset wasn't doing the trick.

Fresh system image and NO AB install and now I have it running stable at 24.1MH at actually higher mclock than it was before and no issues whatsoever for 21+ hours.

I also have a couple rigs that restart every 4-6 hours. Is there a log file in win7 that would give insight as to whether specifically AB or other driver was at fault? I've been assuming it was just an OC/ temp thing, but hard to figure out which card is at fault so I end up lowering OC on all of them.

Have you looked at the Claymore log files to see what is causing the issues? Claymore log files are very detailed.

speaking of logs- mine were unclear. mostly it looked like power failure - normal operations and then sudden restart/end of log. it was likely a combination of driver, temps control, AB OC profiles issues. also 10 nvidia gpus is a factor, there were various scenarios that would slow down the machine or make logonui 50% (100% of one of the two 1151 celeron cores) or hung on reboot (low level driver issues).
now without AB with plim -35 and mem +750 set in claymore it had 0 restarts past two days.
Note: setting -tt to any value produces driver error something about failure to read temps, but with stock settings its doing fine, the temps are a bit higher than my target of 70C though...



edit: AB is bad, just as it always was. cleaning up the mess it may create could be tough, better never to install it on a worker at all.

[JFoxOne]

Claymore dual miner is minerstat's default client on both Windows node and Linux mining OS. Also included in profit-switch option.

[Bael]

Hi

I am using Claymore 11.9 and windows 1803 in a rig, if I disconnect the monitor Claymore rig does not start, when I connect the monitor starts just at that time.

Is it something that is documented?

With windows 1709 I do not have this problem, but it is a rig of 12 gpus and I'm kind of lazy to reinstall everything for this problem.

Please if anyone knows if you could fix it using win 1803 (without reinstalling 1709) I would be very grateful for your help.

regards!

[crairezx20]

Guys, can you help me how to set the claymore to SSL?
I'm trying to change the stratum pool into ssl but it doesn't work on claymore I hope some can help because i'm frustrated setting up my claymore to SSL pool connection.
Unlike Phoenix that It works easily but my problem using Phoenix, it seems my hashrate dropping lately.