kantoi
Newbie
 Offline
Activity: 84
Merit: 0
|
 |
July 25, 2018, 06:10:27 PM |
|
I just tried the EWBF miner and I really like it - works stable and I am getting good hasrates: My standard 1070 gets around 19.4 KSol/s with 96.5 algo on the pool side and it is throttled down to 90% power which keeps it cool...
|
|
|
|
|
Eeroz
Newbie
Offline
Activity: 19
Merit: 0
|
|
July 25, 2018, 06:40:11 PM
Last edit: July 25, 2018, 11:58:53 PM by Eeroz |
|
My miner sometimes crashes with this error and does not recover: I have to exit/close the miner and restart it. This seems to happen randomly. Could you add an argument/switch that closes the miner when this error occurs, so my script would restart it? ...
25.07.2018 18:39:22 Total speed: 442 Sol/s
25.07.2018 18:39:23 INFO: GPU5 Accepted share 47ms [A:1042, R:1]
25.07.2018 18:39:34 INFO: GPU9 Accepted share 47ms [A:969, R:1]
25.07.2018 18:39:40 INFO: GPU9 Accepted share 63ms [A:970, R:1]
25.07.2018 18:39:50 INFO: GPU5 Accepted share 63ms [A:1043, R:1]
25.07.2018 18:39:50 INFO: GPU7 Accepted share 63ms [A:1004, R:0]
25.07.2018 18:39:53 Temp: GPU0 57C GPU1 56C GPU2 60C GPU3 62C GPU4 62C GPU5 59C GPU6 60C GPU7 59C GPU8 64C GPU9 61C GPU10 59C GPU11 64C GPU12 65C
25.07.2018 18:39:53 GPU0: 34 Sol/s GPU1: 35 Sol/s GPU2: 34 Sol/s GPU3: 32 Sol/s GPU4: 34 Sol/s GPU5: 35 Sol/s GPU6: 34 Sol/s GPU7: 36 Sol/s GPU8: 31 Sol/s GPU9: 34 Sol/s GPU10: 35 Sol/s GPU11: 33 Sol/s GPU12: 35 Sol/s
25.07.2018 18:39:53 Total speed: 442 Sol/s
25.07.2018 18:39:56 INFO: GPU4 Accepted share 62ms [A:960, R:0]
25.07.2018 18:40:00 INFO: GPU5 Accepted share 62ms [A:1044, R:1]
25.07.2018 18:40:23 CUDA: Device: 2 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 6 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 12 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 5 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 1 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 4 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 9 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 10 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 3 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 0 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 7 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 8 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 11 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 Temp: GPU0 56C GPU1 55C GPU2 58C GPU3 62C GPU4 62C GPU5 59C GPU6 58C GPU7 58C GPU8 63C GPU9 60C GPU10 59C GPU11 64C GPU12 63C
25.07.2018 18:40:23 GPU0: 36 Sol/s GPU1: 34 Sol/s GPU2: 32 Sol/s GPU3: 36 Sol/s GPU4: 33 Sol/s GPU5: 35 Sol/s GPU6: 35 Sol/s GPU7: 35 Sol/s GPU8: 35 Sol/s GPU9: 35 Sol/s GPU10: 34 Sol/s GPU11: 36 Sol/s GPU12: 35 Sol/s
25.07.2018 18:40:23 Total speed: 451 Sol/s
25.07.2018 18:40:23 WARNING: Looks like GPU0 are stopped. Restarting...
25.07.2018 18:40:23 INFO: GPU0 are restarted.
25.07.2018 18:40:23 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:23 WARNING: Looks like GPU1 are stopped. Restarting...
25.07.2018 18:40:23 INFO: GPU1 are restarted.
25.07.2018 18:40:24 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU2 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU2 are restarted.
25.07.2018 18:40:24 CUDA: Device: 2 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU3 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU3 are restarted.
25.07.2018 18:40:24 CUDA: Device: 3 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU4 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU4 are restarted.
25.07.2018 18:40:24 CUDA: Device: 4 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU5 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU5 are restarted.
25.07.2018 18:40:24 CUDA: Device: 5 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU6 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU6 are restarted.
25.07.2018 18:40:25 CUDA: Device: 6 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU7 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU7 are restarted.
25.07.2018 18:40:25 CUDA: Device: 7 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU8 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU8 are restarted.
25.07.2018 18:40:25 CUDA: Device: 8 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU9 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU9 are restarted.
25.07.2018 18:40:25 CUDA: Device: 9 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU10 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU10 are restarted.
25.07.2018 18:40:25 CUDA: Device: 10 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU11 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU11 are restarted.
25.07.2018 18:40:26 CUDA: Device: 11 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:26 WARNING: Looks like GPU12 are stopped. Restarting...
25.07.2018 18:40:26 INFO: GPU12 are restarted.
25.07.2018 18:40:26 CUDA: Device: 12 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:27 WARNING: Looks like GPU0 are stopped. Restarting...
25.07.2018 18:40:27 INFO: GPU0 are restarted.
25.07.2018 18:40:27 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:27 WARNING: Looks like GPU1 are stopped. Restarting...
25.07.2018 18:40:27 INFO: GPU1 are restarted.
25.07.2018 18:40:27 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:27 WARNING: Looks like GPU2 are stopped. Restarting...
25.07.2018 18:40:27 INFO: GPU2 are restarted.
...
More info 13x EVGA 1070 Pool: https://btg.2miners.comCommand line options: miner.exe --algo 144_5 --pers BgoldPoW --server btg.2miners.com --port 4040 --user <address>.rig1 --pass x Power limit: 75% Mem OC: 0 Core OC: 0 Virtual mem: 170GB Miner: v0.4 This rig has worked almost flawlessly with DSTM's equihash miner. The only occassional hiccups have been due to previous OC settings. |
|
|
|
|
R00d
Newbie
Offline
Activity: 13
Merit: 0
|
|
July 25, 2018, 07:32:44 PM |
|
please work your maigc for a fully functional amd miner....
|
|
|
|
|
minefarmbuy
Full Member
Offline
Activity: 1022
Merit: 225
We are not retail.
|
|
July 26, 2018, 05:15:03 AM |
|
Pretty stable close to 24 hour mark. all nivida
60 / 150 / 580-740
One crash in 12 hour span, still not able to run a bat file specifically.
|
|
|
|
alinturbut
Newbie
Offline
Activity: 1
Merit: 0
|
|
July 26, 2018, 08:43:43 AM |
|
=== ONLY RELATED TO AION == Hi guys, I've noticed that your miner submits lots of low difficulty shares on the AION pool. I have opened an issue here: https://github.com/nanopool/ewbf-miner/issues/88Can you please check? Also, let me know in case you need any additional assistance. Last, but not least, thank you for your work. Regards |
|
|
|
|
|
EWBF_ (OP)
|
|
July 26, 2018, 01:34:33 PM |
|
=== ONLY RELATED TO AION == Hi guys, I've noticed that your miner submits lots of low difficulty shares on the AION pool. I have opened an issue here: https://github.com/nanopool/ewbf-miner/issues/88Can you please check? Also, let me know in case you need any additional assistance. Last, but not least, thank you for your work. Regards Yes, I know about this, it will be fixed in the next release. |
|
|
|
|
|
EWBF_ (OP)
|
|
July 26, 2018, 01:36:33 PM |
|
please work your maigc for a fully functional amd miner....
I thought about it, but right now I do not have time for it, maybe later. |
|
|
|
|
|
EWBF_ (OP)
|
|
July 26, 2018, 01:42:44 PM |
|
My miner sometimes crashes with this error and does not recover: I have to exit/close the miner and restart it. This seems to happen randomly. Could you add an argument/switch that closes the miner when this error occurs, so my script would restart it? ...
25.07.2018 18:39:22 Total speed: 442 Sol/s
25.07.2018 18:39:23 INFO: GPU5 Accepted share 47ms [A:1042, R:1]
25.07.2018 18:39:34 INFO: GPU9 Accepted share 47ms [A:969, R:1]
25.07.2018 18:39:40 INFO: GPU9 Accepted share 63ms [A:970, R:1]
25.07.2018 18:39:50 INFO: GPU5 Accepted share 63ms [A:1043, R:1]
25.07.2018 18:39:50 INFO: GPU7 Accepted share 63ms [A:1004, R:0]
25.07.2018 18:39:53 Temp: GPU0 57C GPU1 56C GPU2 60C GPU3 62C GPU4 62C GPU5 59C GPU6 60C GPU7 59C GPU8 64C GPU9 61C GPU10 59C GPU11 64C GPU12 65C
25.07.2018 18:39:53 GPU0: 34 Sol/s GPU1: 35 Sol/s GPU2: 34 Sol/s GPU3: 32 Sol/s GPU4: 34 Sol/s GPU5: 35 Sol/s GPU6: 34 Sol/s GPU7: 36 Sol/s GPU8: 31 Sol/s GPU9: 34 Sol/s GPU10: 35 Sol/s GPU11: 33 Sol/s GPU12: 35 Sol/s
25.07.2018 18:39:53 Total speed: 442 Sol/s
25.07.2018 18:39:56 INFO: GPU4 Accepted share 62ms [A:960, R:0]
25.07.2018 18:40:00 INFO: GPU5 Accepted share 62ms [A:1044, R:1]
25.07.2018 18:40:23 CUDA: Device: 2 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 6 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 12 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 5 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 1 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 4 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 9 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 10 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 3 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 0 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 7 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 8 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 CUDA: Device: 11 Thread exited with message: "unspecified launch failure"
25.07.2018 18:40:23 Temp: GPU0 56C GPU1 55C GPU2 58C GPU3 62C GPU4 62C GPU5 59C GPU6 58C GPU7 58C GPU8 63C GPU9 60C GPU10 59C GPU11 64C GPU12 63C
25.07.2018 18:40:23 GPU0: 36 Sol/s GPU1: 34 Sol/s GPU2: 32 Sol/s GPU3: 36 Sol/s GPU4: 33 Sol/s GPU5: 35 Sol/s GPU6: 35 Sol/s GPU7: 35 Sol/s GPU8: 35 Sol/s GPU9: 35 Sol/s GPU10: 34 Sol/s GPU11: 36 Sol/s GPU12: 35 Sol/s
25.07.2018 18:40:23 Total speed: 451 Sol/s
25.07.2018 18:40:23 WARNING: Looks like GPU0 are stopped. Restarting...
25.07.2018 18:40:23 INFO: GPU0 are restarted.
25.07.2018 18:40:23 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:23 WARNING: Looks like GPU1 are stopped. Restarting...
25.07.2018 18:40:23 INFO: GPU1 are restarted.
25.07.2018 18:40:24 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU2 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU2 are restarted.
25.07.2018 18:40:24 CUDA: Device: 2 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU3 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU3 are restarted.
25.07.2018 18:40:24 CUDA: Device: 3 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU4 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU4 are restarted.
25.07.2018 18:40:24 CUDA: Device: 4 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU5 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU5 are restarted.
25.07.2018 18:40:24 CUDA: Device: 5 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:24 WARNING: Looks like GPU6 are stopped. Restarting...
25.07.2018 18:40:24 INFO: GPU6 are restarted.
25.07.2018 18:40:25 CUDA: Device: 6 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU7 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU7 are restarted.
25.07.2018 18:40:25 CUDA: Device: 7 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU8 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU8 are restarted.
25.07.2018 18:40:25 CUDA: Device: 8 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU9 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU9 are restarted.
25.07.2018 18:40:25 CUDA: Device: 9 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU10 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU10 are restarted.
25.07.2018 18:40:25 CUDA: Device: 10 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:25 WARNING: Looks like GPU11 are stopped. Restarting...
25.07.2018 18:40:25 INFO: GPU11 are restarted.
25.07.2018 18:40:26 CUDA: Device: 11 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:26 WARNING: Looks like GPU12 are stopped. Restarting...
25.07.2018 18:40:26 INFO: GPU12 are restarted.
25.07.2018 18:40:26 CUDA: Device: 12 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:27 WARNING: Looks like GPU0 are stopped. Restarting...
25.07.2018 18:40:27 INFO: GPU0 are restarted.
25.07.2018 18:40:27 CUDA: Device: 0 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:27 WARNING: Looks like GPU1 are stopped. Restarting...
25.07.2018 18:40:27 INFO: GPU1 are restarted.
25.07.2018 18:40:27 CUDA: Device: 1 Thread exited with message: "all CUDA-capable devices are busy or unavailable"
25.07.2018 18:40:27 WARNING: Looks like GPU2 are stopped. Restarting...
25.07.2018 18:40:27 INFO: GPU2 are restarted.
...
More info 13x EVGA 1070 Pool: https://btg.2miners.comCommand line options: miner.exe --algo 144_5 --pers BgoldPoW --server btg.2miners.com --port 4040 --user <address>.rig1 --pass x Power limit: 75% Mem OC: 0 Core OC: 0 Virtual mem: 170GB Miner: v0.4 This rig has worked almost flawlessly with DSTM's equihash miner. The only occassional hiccups have been due to previous OC settings. Yes, this is a common problem, on the miner's side I will do everything possible to fix it. |
|
|
|
|
|
|
minefarmbuy
Full Member
Offline
Activity: 1022
Merit: 225
We are not retail.
|
|
July 26, 2018, 03:04:28 PM |
|
Yes, this is a common problem, on the miner's side I will do everything possible to fix it.
Yea, this the error I'm getting as well. 2 crashes of this type in a day and a half (second one over night). |
|
|
|
Overdrive5
Member
Offline
Activity: 114
Merit: 14
|
|
July 26, 2018, 04:08:25 PM |
|
Yes, this is a common problem, on the miner's side I will do everything possible to fix it.
Yea, this the error I'm getting as well. 2 crashes of this type in a day and a half (second one over night). FWIW, I am not seeing this nor am I receiving any reports from my Linux users in ZhashOS using the cuda 8 binary. So this might be a cuda 9.1 and/or windows issue. |
|
|
|
|
minefarmbuy
Full Member
Offline
Activity: 1022
Merit: 225
We are not retail.
|
|
July 27, 2018, 03:25:46 AM |
|
Yes, winx here and latest drivers. Been looking at a roll back but been super busy with LN and BTCpay . And remote connection is helping uptime currently.
|
|
|
|
minefarmbuy
Full Member
Offline
Activity: 1022
Merit: 225
We are not retail.
|
|
July 27, 2018, 05:31:08 AM |
|
So far single cards work best. Going to try running separate batch files for each card over night (6 hours approx) and see how it fairs. Seems to be a strong miner for nivida though when it's hashing.
|
|
|
|
Morama
Member
Offline
Activity: 104
Merit: 44
|
|
July 27, 2018, 07:35:35 AM |
|
0.4 works fine and stable for me on 3 PCs. Algo is Equihash 144.5
6x 1060 - 3 & 6 GB mixed (Power 68, Core +120, Mem +500) - Win 10 - Nvidia 398.36
1x 1080 Ti - OC-Version +100 Core default! (Power 65, Core +70, Mem +600) - Win 10 - Nvidia 398.36
2x 1080 (Power 65, Core +120, Mem +500) - Win 10 - Nvidia 398.36
|
|
|
|
|
minefarmbuy
Full Member
Offline
Activity: 1022
Merit: 225
We are not retail.
|
|
July 27, 2018, 03:25:26 PM |
|
Finally got a batch file to run, and run stable with four 1070's. Hashing all night about 5 hours.
So far my clock are the same as posted before. 1080 ti is maxed I feel with 60 pwr / 150 core / 780 mem, haven't checked the draw but it's hopefully around 150w estimated.
I feel I can get more out the 1070's once stability is reached on my end.
(Note: one is a hobby rig and the other gaming desktop. Not much time for gaming lately .. .)
|
|
|
|
SchroedingerC
Newbie
Offline
Activity: 47
Merit: 0
|
|
July 27, 2018, 04:14:23 PM |
|
Why everybody overclocking MEM on 144 one? It works with deafult equihash but it seems that "144" mode is MEM-independent...
My 1070th work at 2025MHz/950mV (some of them need 975mV, and 2 of 15 need above 1000mV) with -200 on memory and give about 36~38 each.
1070ti (bought one recently) with same settings gives 40~41.
1080s (not "ti") work at 2050MHz/1025mV (and -200 on MEM) give about 43~44 each.
Why overclock memory then?..
|
|
|
|
|
rgzrgz
Member
Offline
Activity: 151
Merit: 10
|
|
July 27, 2018, 04:23:12 PM |
|
Give me Readme.txt please!
|
|
|
|
|
Overdrive5
Member
Offline
Activity: 114
Merit: 14
|
|
July 27, 2018, 05:34:38 PM |
|
Why everybody overclocking MEM on 144 one? It works with deafult equihash but it seems that "144" mode is MEM-independent...
My 1070th work at 2025MHz/950mV (some of them need 975mV, and 2 of 15 need above 1000mV) with -200 on memory and give about 36~38 each.
1070ti (bought one recently) with same settings gives 40~41.
1080s (not "ti") work at 2050MHz/1025mV (and -200 on MEM) give about 43~44 each.
Why overclock memory then?..
What is your power setting (watts/TDP) for those numbers? Do you monitor Sols/W? I have found at higher power settings, memory O/C has little affect on Sol/s. However when you lower power settings, memory O/C then becomes somewhat more effective. It is hot summer here so I am running @104 watts (58% TDP) to keep the GPU temps below 63c without running AC in the room. I usually adjust power first, core second and then memory last. |
|
|
|
|
SchroedingerC
Newbie
Offline
Activity: 47
Merit: 0
|
|
July 27, 2018, 06:31:29 PM
Last edit: July 27, 2018, 09:37:58 PM by SchroedingerC |
|
I lock voltage so there's no point for me to use PL, 'cause it does almost the same thing (limits top voltage of your f/v curve but leaves it unstable on under limit levels). So I prefer voltage locking instead of PL.
At "144" mode average S/W of my GPUs are about 0.27~0.32. Not the best maybe, but electricity costs only 0.03$/kWh for me... almost doesn't matter.
Only one of all my GPUs get higher than 65 Celsius (lucky me! this summer leaves RIG room's temperature slightly below 35 Celsius — when all GPUs turned off).
My hottest ones (right now, at night, when every card is 3~4C cooler): 1070 HoF KFA2 (61C), 1070 ASUS Dual (60C) and 1070 ZOTAC Amp! edition(63C). But they all need just a thermal grease change I think.
P.S.
At first my mem was like +200 ... +400 (+600 on palit jetstream) and temps of all GPUs were much higher.
upd: I cleaned my RIG
all GPUs are lower than 60C now
except that asus (I bet thermal grease change will change it))
|
|
|
|
|
Overdrive5
Member
Offline
Activity: 114
Merit: 14
|
|
July 27, 2018, 08:06:15 PM |
|
I lock voltage so there's no point for me to use PL, 'cause it does almost the same thing (limits top voltage of your f/v curve but leaves it unstable on under limit levels). So I prefer voltage locking instead of PL.
At "144" mode average S/W of my GPUs are about 0.27~0.32. Not the best maybe, but electricity costs only 0.03$/kWh for me... almost doesn't matter.
Only one of all my GPUs get higher than 65 Celsius (lucky me! this summer leaves RIG room's temperature slightly below 35 Celsius — when all GPUs turned off).
My hottest ones (right now, at night, when every card is 3~4C cooler): 1070 HoF KFA2 (61C), 1070 ASUS Dual (60C) and 1070 ZOTAC Amp! edition(63C). But they all need just a thermal grease change I think.
P.S.
At first my mem was like +200 ... +400 (+600 on palit jetstream) and temps of all GPUs were much higher.
Wow! 0.03$/kWh! How did you manage that? |
|
|
|
|
|
