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

[Vann]

Try resetting the GPU's by shutting down the rig and cutting the power to the PSU with the switch on the back. Then press the power on button until the power drains from the system and then turn the rig back on.

[1714092274]

1714092274

[kenron]

now only 2 of the cards still is at 18mhs,  ill try once more

[kenron]

looks like second reset did it B-) thanx for tip

[lostprophet007]

I have a rig with 4 GPU.
Is it possible to activate solo mining ETH only on 1 out of 4?

From first page,

mode   Select mining mode:
   "-mode 0" (default) means dual Ethereum + Decred/Siacoin/Lbry mining mode.
   "-mode 1" means Ethereum-only mining mode. You can set this mode for every card individually, for example, "-mode 1-02" will set mode "1" for first and third GPUs (#0 and #2).
   For systems with more than 10 GPUs: use letters to specify indexes more than 9, for example, "a" means index 10, "b" means index 11, etc.

Thanks!

[JDLSantos]

Same problem here!
I tried deferent options on the command in the .bat file, but still crashing

any ideas? something change in the pool, that is making miner crash during the DAG open?
thanks

Hi everyone, my miner has been working fine for several days in a row, until all of a sudden it has started mining at 0.000 MH/s, just after switching from Dev mining fee (which is not actually mined but still appear) to the pool where I am mining.

It was really weird as it kept mining for a good 15 minutes at 0.000 Mh/s without restarting or stopping, and even closing and restarting Claymore's software it was still mining at 0.000 Mh/s, while after restarting the miner itself it has started working normally again.

I have searched but it looks like no one has got this issue? All I could see online was people having one GPU going to 0, but not all 6 GPU and the software still going.

Any idea why this happened?

Any help is appreciated, thanks.

My rig is made of 5x XFXrx480 8GB GPUs + 1x rx480Nitro 8GB and the batch file is the standard one, as recommended in Claymore's readme.

[potificate]

Hey all... I'm getting the "NVML: cannot get fan speed, error 999 (an internal driver error occurred)" error... cannot isolate it to one card (all 1060 6GB, but of different makes). Every time I take one suspected card out and put it to a separate instance, the main group still throws this error. I add another to the suspect group and still an error.... and so forth until I can fairly say that no one card is at fault. All but two risers are powered by PCIe, the other two are molex,  but on separate cables. Total power usage of the PSU is no more than 80% at any time. I _think_ I'm doing everything right. I've even tried saving the OCs so that when I quit Afterburner, they still hold. (Thought it might be AB's monitoring that was interfering.)

Here's the thing, though... unlike other people, this error does _not_ cause the miner to restart nor does it cause anything like windows to freeze or restart. Plus this error does not show up in the logs straight away, it typically takes 4-6 hours.

Now I know what some might say... "if it isn't crashing, don't worry." But I can't help but think that if this error is being reported, it's for a reason (a hit on number of shares earned, bad connection somewhere, impending doom ;-) ) ... or there could simply be a bug in the program.

Thanks for any hints as to what might be going on.

potificate

P.S. I am using 11.6 and 391.35 and did not have this issue when running 1050Ti's on the same rig.

[project01uk]

Hello,

I'm having a very strange issue, never came across it before, any help or suggestions will be greatly appreciated.

I'm mining Ethereum and one day I have noticed that every GPU on my rig slowed down - instead of usual 30mh/s I'm getting only 17mh/s now! I have tried different pools, servers, Claymore versions and even different miners altogether including Phoenix and Ethminer... same effect, I can only get 17mh/s. The weird thing is that other Ethash coins will mine at 30mh/s! So Pirl, Musicoin, Ellaism coin they all mine at 30mh/s, only ETH stuck at 17mh/s. Any suggestions please?

Thanks! 

[leonix007]

Hello,

I'm having a very strange issue, never came across it before, any help or suggestions will be greatly appreciated.

I'm mining Ethereum and one day I have noticed that every GPU on my rig slowed down - instead of usual 30mh/s I'm getting only 17mh/s now! I have tried different pools, servers, Claymore versions and even different miners altogether including Phoenix and Ethminer... same effect, I can only get 17mh/s. The weird thing is that other Ethash coins will mine at 30mh/s! So Pirl, Musicoin, Ellaism coin they all mine at 30mh/s, only ETH stuck at 17mh/s. Any suggestions please?

Thanks! 

Might be a DAG and driver issue, what's your driver installed?

are you in win 10? ensure you're driver that are in compute mode

[tg88]

Hello,

I'm having a very strange issue, never came across it before, any help or suggestions will be greatly appreciated.

I'm mining Ethereum and one day I have noticed that every GPU on my rig slowed down - instead of usual 30mh/s I'm getting only 17mh/s now! I have tried different pools, servers, Claymore versions and even different miners altogether including Phoenix and Ethminer... same effect, I can only get 17mh/s. The weird thing is that other Ethash coins will mine at 30mh/s! So Pirl, Musicoin, Ellaism coin they all mine at 30mh/s, only ETH stuck at 17mh/s. Any suggestions please?

Thanks! 

By reporting the driver is not in compute mode, use this tool and solve your problem:

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

[project01uk]

Thanks,

I'm using Windows 10 (64), RX580 4GB with the blockchain driver 17.30.1091 and everything was fine for many months previously. Thank you for your suggestion about switching them to compute mode, I did the switch but nothing has changed unfortunately.

Other Ethash coins still mine at 30mh/s

[therock11]

Thanks,

I'm using Windows 10 (64), RX580 4GB with the blockchain driver 17.30.1091 and everything was fine for many months previously. Thank you for your suggestion about switching them to compute mode, I did the switch but nothing has changed unfortunately.

Other Ethash coins still mine at 30mh/s

This is due to the recent changes in Windows 10 from feature release 1709.  I haven't found a fix for it either.  I was getting 32mh/s per card and now I'm  getting 16mh/s.  I'd love to see a fix for this.  I'm going to try and rollback the update.

[project01uk]

I've just reinstalled drivers and it worked! I'm back at 30mh/s, very strange as I did re-install drivers previously without success, this time it worked though

Thank you all!

[jackbox]

I've just reinstalled drivers and it worked! I'm back at 30mh/s, very strange as I did re-install drivers previously without success, this time it worked though

Thank you all!

Make sure you go into the settings app and change all the cards to compute mode in the driver also. Should get you some more speed if you have not done that already.

[project01uk]

I've used the AMD switcher app to do that because I don't seem to have that option in AMD settings.

[troner8x]

The version of Windows 7 or 10, is important for the volume of coin mining ?

Mining - what coins does the processor use less ?

[janding]

The version of Windows 7 or 10, is important for the volume of coin mining ?

Mining - what coins does the processor use less ?

You should load the latest Windows 10, 64 bit, although some do mine with Windows 7.
The computer CPU is not important, the mining process uses very little of the computers CPU.
The computing and work is done mainly on the GPU's you install.

Just make sure your system has a PSU with enough power to easily support the amount of GPU's you install.
I would use a power supply that can supply you with at least 250 watts for every card you install, that should
comfortably give you enough power for all the cards and the computer + accessories.

I see lots of issues on these threads with systems that are on the edge of not having enough power for
the amount of work that are asked to do.

[xunl]

What is the difference among 3 intensity setting flag?
-li
-ethi
-dcri

I can see
-dcri adjust intensity w/o change hashrate
-ethi adjust hashrate
-li seems similar to ethi, is there any differnce?
-ttli apply li when temperature threshold is reached.

[xunl]

Hey all... I'm getting the "NVML: cannot get fan speed, error 999 (an internal driver error occurred)" error... cannot isolate it to one card (all 1060 6GB, but of different makes). Every time I take one suspected card out and put it to a separate instance, the main group still throws this error. I add another to the suspect group and still an error.... and so forth until I can fairly say that no one card is at fault. All but two risers are powered by PCIe, the other two are molex,  but on separate cables. Total power usage of the PSU is no more than 80% at any time. I _think_ I'm doing everything right. I've even tried saving the OCs so that when I quit Afterburner, they still hold. (Thought it might be AB's monitoring that was interfering.)

Here's the thing, though... unlike other people, this error does _not_ cause the miner to restart nor does it cause anything like windows to freeze or restart. Plus this error does not show up in the logs straight away, it typically takes 4-6 hours.

Now I know what some might say... "if it isn't crashing, don't worry." But I can't help but think that if this error is being reported, it's for a reason (a hit on number of shares earned, bad connection somewhere, impending doom ;-) ) ... or there could simply be a bug in the program.

Thanks for any hints as to what might be going on.

potificate

P.S. I am using 11.6 and 391.35 and did not have this issue when running 1050Ti's on the same rig.

Error 999 is for nVidia Card and generally are not critical. The root cause can be riser, cable, loose connection, etc. I used to worry about crash after I saw error 999 so I reboot the rig. But since 11.2, I have continued runing w/o any action if it only misses fan info (since I set fan at constant via afterburn). It runs anytime between 1~17 more days until a new issue cause the rig to hang (none of them is related to the GPU showing error 999 initially). If it misses temperature, then I would have to restart or reboot to fix the issue right away.

6 things through my observations:
1) If error 15 arise after error 999, your rig might hang
2) If the initial GPU showing error 999 crashes, the afterburner OC setting might reset to default (slow hashrate, higher power comsuption, much higher temperature)
3) If 2) occurs, the error 999 might spread out to other nVidia cards like a virus.
4) If you use UPS, another power outage might trigger error 999 (initially missing fan setting, now missing both fan and temp)
5) missing fan info is not as critical as missing temp
6) sometimes when you close the miner that GPU show error 999, afterburn will not start (nvdia driver issue)

[potificate]

Error 999 is for nVidia Card and generally are not critical.

Okay, so unless I'm getting actual crashes or miner resets, I needn't freak so much... I just _hate_ error messages though :-)

Thank you for your reassurance.
potificate

[janding]

What is the difference among 3 intensity setting flag?
-li
-ethi
-dcri

I can see
-dcri adjust intensity w/o change hashrate
-ethi adjust hashrate
-li seems similar to ethi, is there any differnce?
-ttli apply li when temperature threshold is reached.

Actually, all these settings will increase or decrease the mining intensity, but in different ways depending on how you want to use them.


-dcri  Used for individual tuning of each GPU for maximum hash rate.
         It will definitely increase or decrease your hash rate depending on how well it is tuned.
         If it is tuned badly then the intensity is actually lower and you will get less hash rate
         but lower temp on that GPU. Tuned well and the hash rate goes up and also the temp. You want this
         tuned to the highest hash rate on each card.

-ethi  Used to set the Max intensity per card. If you set this to the max allowed your cards
         will mine to the maximum intensity allowed by the miner. However, if you have badly
         tuned the -dcri then that card will still not be getting you the maximum intensity.
         Also, the -li if used will lower the intensity if you have it set. And of course  the -ttli will
         also cause the card to use a lower intensity if the temp you have specified is reached.
      
-li      Used if you’re having a heat problem with a card. It basically decreases the
         intensity of the GPU therefore lowering the heat.

-ttli    Automatically decreases the intensity for a card if the temp you specify is exceeded, that lowers the temp of that card.


Here is the way I think these setting should be used. It is how I do them and I have no issues.
If anyone else has a better or different method I would like to know what it is please.

1st:
-ethi
Set this to maximum value to get the most mining intensity and the highest hash rates.

2nd:
-dcri
Tune your cards to get the maximum hash rate on each card. Each card will probably have a different setting.

3rd:
-ttli
I set this to a temp that I don't want my cards to go above at any time.
I set mine to 75. I don't want any of my cards to go above 75. If for some reason they do
then the miner will automatically reduce the intensity on that card and lower the temp for me.
If this happens you can see it in the logs. Then you can set the -li for that card only to lower
it's intensity so that it doesn't happen again.

4th:
-li
I would only use this to reduce the intensity on a card that was giving me a temp issue
that the other settings did not handle.

If all your cards have slightly high temps after doing this, then the best thing to do is
use the -ethi and lower that number for all the cards. All cards will then mine at a lower intensity
and the temp will be dropped on them all.

These are my opinions and experience of how these setting work.


Edit: Note

All this assumes that you have not overclocked to a point where increasing the intensity will cause you a stability issue.