Only those who have an access to very cheap-to-free electricity are still mining.

Check this out:

How the Crypto Collapse is Hurting Nvidia

https://www.investopedia.com/news/how-crypto-collapse-hurting-nvidia/

Moreover, NVIDIA Stock has plummeted and wiped away 18 months of gains already within two days.

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.   

Thanks for your reply.
It's not a TI, it's a GTX 1080 (G1 Gaming-8GD) it's because i use the ETHlargement Tool.
On my AMD rigs i use the Crimson beta drivers still: https://support.amd.com/en-us/kb-articles/Pages/Radeon-Software-Crimson-ReLive-Edition-Beta-for-[Suspicious link removed]pute-Release-Notes.aspx
Exactly how i check my power usage? is there a tool for that? because i don't have a adapter that displays the power usage.
And yea my 580 rigs keeps running without a reboot or share warning in the .bat file.

Any toughts on my rigs?

RX 580
https://i.imgur.com/OFP14w6.jpg
Core Voltage -93
Power limit +0
Temp limit 90
Core Clock 1235
Mem Clock 2250
Fan Speed 70%

RX 570
https://i.imgur.com/pVbGo8F.jpg
Core Voltage -93
Power limit -7
Temp limit 76
Core Clock 1330
Mem Clock 2100
Fan Speed 80%

3 x GTX 1060 & 1 x GTX 1080
https://i.imgur.com/7NgC5xP.jpg

1060's
Core Voltage +0
Power limit 75
Temp limit 72
Core Clock -400
Mem Clock +1000
Fan Speed 35%

1080
Core Voltage +0
Power limit 80
Temp limit 74
Core Clock -400
Mem Clock +1000
Fan Speed 45%

Thoughts or ideas?

I do use Afterburner for these clocks and i close the program after adjusting, but i heard that Claymore doesn't Recognize Afterburner settings.
Is this true, is it better to edit the .bat file?

RX580 is not checked, but RX480 is, and needs the patch

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.

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.