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

[faanigee]

You sir are a dickhole.

dont show off your self please...!!!

[Claymore]

Hi, Mr.Claymore
Please, make the "-minspeed" option understand, that there is no internet connection, so it doesn't actually mine. So, the reason of hitting "-minspeed" limit is not a hardware issue. So, I don't want the miner restarts (reboot the PC) in this case. You understand, that it triggers all other signaling like e-mail/messages "I have to reboot", "I have been rebooted" and so on from every miner affected.

I guess that there are people who need the opposite from what you describe (they need the -minspeed to get triggered from internet connection loss). I am not one of them but I am sure that there are cases where that makes sense.
I agree with you though on what you are saying. I would modify your request like this:
"Please add a flag that indicates whether internet connection loss will trigger -minspeed"

Ok I will add an option in next update so you can set if "-minspeed" should work if miner cannot reach pools or not.

[kkourmousis]

Great! Thanks a lot 

[MikeGR7]

Hi, Mr.Claymore
Please, make the "-minspeed" option understand, that there is no internet connection, so it doesn't actually mine. So, the reason of hitting "-minspeed" limit is not a hardware issue. So, I don't want the miner restarts (reboot the PC) in this case. You understand, that it triggers all other signaling like e-mail/messages "I have to reboot", "I have been rebooted" and so on from every miner affected.

I guess that there are people who need the opposite from what you describe (they need the -minspeed to get triggered from internet connection loss). I am not one of them but I am sure that there are cases where that makes sense.
I agree with you though on what you are saying. I would modify your request like this:
"Please add a flag that indicates whether internet connection loss will trigger -minspeed"

Ok I will add an option in next update so you can set if "-minspeed" should work if miner cannot reach pools or not.

Yes, the default behavior is exactly how i use this flag.

I am one of the users that suffer from the already reported problem:
Every 2- 3 days my internet connection drops and reconnects after 5 minutes.
After reconnection the cards work at a lower speed than normal almost half speed.
I can easily reproduce it with just unplugging and replugging the Ethernet cable.
Only solution was for me to manually close the miner and reopen it to regain full speed.

"-minspeed" option provided me a solution and when the internet reconnected, the miner detects the lower speed and restarts by itself and regains full speed.

If Claymore needs it, i can provide a video clip with this issue or whatever info he needs.

Thanks for development efforts either way!

[EthereumBa]

Hi guys. I'm getting this error since yesterday. Trying to fix it but no success for now. Any hints what could be a problem?

Photo: https://www.photobox.co.uk/my/photo/full?photo_id=21867640249

[vinkenzo]

hi everyone
i have 1 question for you
can you help me with -minspeed command ?
why there is not any example on that section ?

if i want claymore to restart when mines with low hash rate, how can i use this command?
is this correct format?
-minspeed 180

 or this one ?
 -minspeed 180MH/s

which one is correct ?

thanks

[MikeGR7]

-minspeed 180 is the correct one.

I place it before -dcri command which is the last command in my bat file.

[EthereumBa]

Hi guys. I'm getting this error since yesterday. Trying to fix it but no success for now. Any hints what could be a problem?

Photo: https://www.photobox.co.uk/my/photo/full?photo_id=21867640249

GPU1, GpuMiner cu_k01 failed 73, an illegal instruction was encountered
GPU4, GpuMiner kx failed 1
GPU1, GpuMiner kx failed 1
GPU 4 failed
GPU 1 failed
Setting DAG epoch #150 for GPU0
GPU0 failed
GPU0, CUDA error 73, cannot write buffer for DAG
GPU 0 failed
NVML: cannot get current temperature, error 999(an internal driver error occurred)
NVML: cannot get current temperature, error 999(an internal driver error occurred)
NVML: cannot get current temperature, error 999(an internal driver error occurred)
NVML: cannot get current temperature, error 999(an internal driver error occurred)
NVML: cannot get current temperature, error 999(an internal driver error occurred)
NVML: cannot get current temperature, error 999(an internal driver error occurred)
NVML: cannot get current temperature, error 999(an internal driver error occurred)
NVML: cannot get current temperature, error 999(an internal driver error occurred)
NVML: cannot get current temperature, error 999(an internal driver error occurred)
NVML: cannot get current temperature, error 999(an internal driver error occurred)
NVML: cannot get current temperature, error 999(an internal driver error occurred)
NVML: cannot get current temperature, error 999(an internal driver error occurred)
WATCHDOG: GPU error, you need to restart miner

I have an 6x GTX1070 STRIX miner. Core clock +99, Memory clock +600. Tried to decrease it, but no effect for now. Running 10.0 Claymore Dual eth+sia. Power is on 90% for now. Tried to change it but also no effect.

[ffthomas]

hi,

ethermine.org pool is down for ~30 minutes, do you know anything about that issue?

I am not certain about that issue mate, but first thing to do is you must first check you cooling systems and other hardware. I've also encountered overheating but not like that pool is being downed. To determine that you must always back to basic so that with step by step troubleshooting you will eventually solve that problem with no hassle, and lesser time so you can continue the operation again.

If you go to Pool Ethermine website ( https://ethermine.org/ )you will see that last block was mined 4h ago... so I do not think it is the miner "cooling systems and other hardware"

It caused by a datacenter-issue. Great respect to Ethermine.org as how they managed this server-outage: https://medium.com/@bitfly/eu-stratum-mining-server-outage-postmortem-60f00e4c4411

[Delija93]

Please HELP ME!!
i have ASUS RADEON RX 580 8GB OC Editio ..
I mining with "Claymore's Dual Ethereum+Decred_Siacoin_Lbry AMD+NVIDIA GPU Miner v7.4"

For now i bought that one card, and when start to mining write "GPU #0 recognized ad Radeon RX 480"

Why ?? And with this card i mining 20.3 Mh/s .. Is that low or ?
Sorry for my bad English.. i need a help :/

[Flickspeed]

@Claymore

I am noticing strange behavior on one of the rigs with 6x 1080 Ti mining Ethereum with Claymore.

The cards starts mining at 36.1 MH/s and the do fine until there is a problem with the network connection either an actual loss of ping with the pool or a manual cable disconnect. Once the connection is reestablished the cards resume hashing at 35 MH/s instead of 36.1 MH/s. Upgraded to version 10.1 and the behavior persisted.

[heavyarms1912]

Please HELP ME!!
i have ASUS RADEON RX 580 8GB OC Editio ..
I mining with "Claymore's Dual Ethereum+Decred_Siacoin_Lbry AMD+NVIDIA GPU Miner v7.4"

For now i bought that one card, and when start to mining write "GPU #0 recognized ad Radeon RX 480"

Why ?? And with this card i mining 20.3 Mh/s .. Is that low or ?
Sorry for my bad English.. i need a help :/

version 7.4?  That's really old one.  Update to v10 or v10.1 (first post in the thread).
You're probably using the claymore version before RX 580 was even launched.

[Flickspeed]

Is there a way to lower the power limit below the minimal 50% on Nvidia cards?

[MikeGR7]

@Claymore

I am noticing strange behavior on one of the rigs with 6x 1080 Ti mining Ethereum with Claymore.

The cards starts mining at 36.1 MH/s and the do fine until there is a problem with the network connection either an actual loss of ping with the pool or a manual cable disconnect. Once the connection is reestablished the cards resume hashing at 35 MH/s instead of 36.1 MH/s. Upgraded to version 10.1 and the behavior persisted.

I just posted the same error in the previous page!

It is a known problem that a ton of us have. ( After network loss, the cards mine at lower speed when the network connection is restored ).

Claymore propably can't reproduce the issue so we may have to live with it.

Temporary Workarounds:

1.Close and restart the miner manually when network connection is restored.

or

2. Add -minspeed in your .bat file so that the miner restarts itself when it detects a lower then normal mining speed.

[MikeGR7]

Is there a way to lower the power limit below the minimal 50% on Nvidia cards?

Not through software man.


Either way i advice against it since around the -30%, the speed slowdown counters any gains from the power efficiency.

[Flickspeed]

Is there a way to lower the power limit below the minimal 50% on Nvidia cards?

Not through software man.


Either way i advice against it since around the -30%, the speed slowdown counters any gains from the power efficiency.

There are some 1060 cards with power limit way above what it should be and even setting 50% doesn't allow to get anything below 1.0 volts I then used the temp limit to operate them at 750mV and around 1500 MHz... This kept the speed same in ETH especially on micron chips those cards cant go beyond 23 MHs so they dont need any core power at all.

Wonderif we can trick the card somehow to use low voltage

[TigTex]

Recently, I was hacked using a bruteforce attack.

Somehow, someone found my ddns, my remote management port (it's not the default one) and he was able to bruteforce the password until he succeeded. The hacker was able to upload a epools dpools and custom config.txt file and restart the miner. A couple of minutes after, I noticed the hack and quickly erased those files because I don't use any of them and I've also disabled the remote management feature.
@Claymore, are there any anti-bruteforce measures implemented on your miner? If not, consider adding something like a lockdown after "x" invalid login attempts.
Also, it's possible to flood the miner if you start refreshing the rig stats too often. You can send http requests as many times as you want and that creates an overflow of refreshes on the miner stats. It's basically a DoS attack. It floods the log file, uses CPU time on the miner and some bandwidth. Consider adding an http login feature so that you can't check your miner's stats on your browser without the correct user/password combo.

Thanks

[blackhwk77]

Use a vpn and don't expose that port to the internet.

Recently, I was hacked using a bruteforce attack.

Somehow, someone found my ddns, my remote management port (it's not the default one) and he was able to bruteforce the password until he succeeded. The hacker was able to upload a epools dpools and custom config.txt file and restart the miner. A couple of minutes after, I noticed the hack and quickly erased those files because I don't use any of them and I've also disabled the remote management feature.
@Claymore, are there any anti-bruteforce measures implemented on your miner? If not, consider adding something like a lockdown after "x" invalid login attempts.
Also, it's possible to flood the miner if you start refreshing the rig stats too often. You can send http requests as many times as you want and that creates an overflow of refreshes on the miner stats. It's basically a DoS attack. It floods the log file, uses CPU time on the miner and some bandwidth. Consider adding an http login feature so that you can't check your miner's stats on your browser without the correct user/password combo.

Thanks

[edin_tam]

Hello everyone

I have a rig with 4x ASUS RX470 4G and used to get 85+MH/s but with the time the hashrate got lower and lower and I thought it is because the difficulty is increasing.
But then the diff dropped and my hashrate continued to decrease, so now is ~75MH/s. I know my cards are not the best for this job  but still.. Also now they keep lower temperatures (54-57C).
Someone please explain to me what am I missing. Thanks

[MikeGR7]

Hello everyone

I have a rig with 4x ASUS RX470 4G and used to get 85+MH/s but with the time the hashrate got lower and lower and I thought it is because the difficulty is increasing.
But then the diff dropped and my hashrate continued to decrease, so now is ~75MH/s. I know my cards are not the best for this job  but still.. Also now they keep lower temperatures (54-57C).
Someone please explain to me what am I missing. Thanks

You are missing a lot brother.

Here is what you must do:

1. If you are using Windows 10, then go at AMD website, you will see a search box on the upper right corner, type " Blockchain".

2. First result is a driver, download it, uninstall your old gpu driver and install the new one, also make sure to use latest miner 10.1.

3. Problem solved, still use google in your free time and search "AMD DAG problem". You will now know what got you into all this.

Have a beer haha