miniZ (OP)
|
|
August 15, 2019, 04:45:24 PM |
|
Mode=10 do nothing for me.
Same here Hi RelaxedCrypto, MineOrDie, Apparently our solver has not shrink enough to fit in your cards. We keep trying to improve this for the next version. Cheers
|
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter
|
|
|
2h4u
Newbie
Offline
Activity: 55
Merit: 0
|
|
August 15, 2019, 07:30:38 PM |
|
Our solver for 150,5,3 (Beam2) requires less memory than the 150,5 , but it will not fit on 3GB GPU Windows 10.
I do confirm--150,5,3 works brilliant under HiveOS.
|
|
|
|
Divinity666
Jr. Member
Offline
Activity: 312
Merit: 2
|
|
August 15, 2019, 07:31:42 PM |
|
Hi Divinity666, we did not make modifications to 144,5. Performance should be the same as the previous version. Could you let us know what miniZ cuda version are you using (8 or 10)? Also which OS are you using and which nvidia driver version? Thanks Cheers
cuda10, 419.35, win10
|
|
|
|
miniZ (OP)
|
|
August 15, 2019, 08:12:38 PM |
|
Hi Divinity666, we did not make modifications to 144,5. Performance should be the same as the previous version. Could you let us know what miniZ cuda version are you using (8 or 10)? Also which OS are you using and which nvidia driver version? Thanks Cheers
cuda10, 419.35, win10 Hi Divinity666, thanks, we will have a look. We would like to ask you one more thing, could you paste here the output of Cheers
|
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter
|
|
|
miniZ (OP)
|
|
August 15, 2019, 08:14:59 PM |
|
Our solver for 150,5,3 (Beam2) requires less memory than the 150,5 , but it will not fit on 3GB GPU Windows 10.
I do confirm--150,5,3 works brilliant under HiveOS. Hi 2h4u, this is good to know. Thanks for reporting Cheers
|
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter
|
|
|
Divinity666
Jr. Member
Offline
Activity: 312
Merit: 2
|
|
August 15, 2019, 09:43:57 PM |
|
Hi Divinity666, thanks, we will have a look. We would like to ask you one more thing, could you paste here the output of Cheers I rolled back to 1.3n5, so I dunno if there is a point? But like I said it's last release (miniZ v1.5p), h\r dropped by ~1.5% btw, its not critical, but still no point in upgrading if u mine 144.5.
|
|
|
|
topteam
Newbie
Offline
Activity: 157
Merit: 0
|
|
August 15, 2019, 10:20:11 PM |
|
for me miniZ have less CPU utilisation on 12x1070 CPU3930 4Gb ubuntu 16 cuda 9.2
Hi topteam, thank you for letting us know. Which nvidia driver version are you using? Cheers Driver Version: 396.82
|
|
|
|
miniZ (OP)
|
|
August 15, 2019, 10:59:03 PM |
|
Hi Divinity666, thanks, we will have a look. We would like to ask you one more thing, could you paste here the output of Cheers I rolled back to 1.3n5, so I dunno if there is a point? But like I said it's last release (miniZ v1.5p), h\r dropped by ~1.5% btw, its not critical, but still no point in upgrading if u mine 144.5. Hi Divinity666, in general it is advisable to use the latest version because we correct bugs that may affect all algos. Because we want to solve this, it would still be helpfull to know the output of miniZ.exe --version. (you can just run it where you have the miniZ.exe file, no need to stop the miner) Also, why did you went back to v1.3n5, and not the previous one v1.4o? Thanks. Cheers
|
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter
|
|
|
miniZ (OP)
|
|
August 15, 2019, 10:59:37 PM |
|
for me miniZ have less CPU utilisation on 12x1070 CPU3930 4Gb ubuntu 16 cuda 9.2
Hi topteam, thank you for letting us know. Which nvidia driver version are you using? Cheers Driver Version: 396.82 Hi topteam, thanks for the info. Cheers
|
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter
|
|
|
ar_computers
Newbie
Offline
Activity: 2
Merit: 0
|
|
August 16, 2019, 05:04:53 AM |
|
Hi good morning. Working with beamV2 in nicehash stratum pool? Any example or bat if is correct? Appreciate your help Best regards
|
|
|
|
rgzrgz
Member
Offline
Activity: 151
Merit: 10
|
|
August 16, 2019, 07:46:32 AM |
|
Hi good morning. Working with beamV2 in nicehash stratum pool? Any example or bat if is correct? Appreciate your help Best regards
See .bat files here: https://bytwork.com/news/nayshesh-add-beam
|
|
|
|
Divinity666
Jr. Member
Offline
Activity: 312
Merit: 2
|
|
August 16, 2019, 02:51:03 PM |
|
Hi Divinity666, in general it is advisable to use the latest version because we correct bugs that may affect all algos. Because we want to solve this, it would still be helpfull to know the output of miniZ.exe --version. (you can just run it where you have the miniZ.exe file, no need to stop the miner) Also, why did you went back to v1.3n5, and not the previous one v1.4o? Thanks. Cheers v1.4o = v1.3n5 in 144.5 h\r, so no difference from that point.
|
|
|
|
miniZ (OP)
|
|
August 16, 2019, 11:39:11 PM |
|
Hi good morning. Working with beamV2 in nicehash stratum pool? Any example or bat if is correct? Appreciate your help Best regards
Hi ar_computers, we have updated the FAQ How to mine with miniZ on NiceHash?. Example: miniZ.exe --url=YourBitcoinAddress.RigID@beamv2.eu-new.nicehash.com:3378 --pass x --pers auto Also, on Download you can find an updated miniZ_batfiles.zip. We added a few examples for NiceHash. Additionally, there is a new FAQ with some information on how to create a .bat file. We hope this can help. Cheers
|
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter
|
|
|
miniZ (OP)
|
|
August 16, 2019, 11:41:02 PM |
|
Hi rgzrgz, thank you for your answer with useful information for miners. Could you please add a link for miniZ miner on the list of miners the top of your page? Cheers
|
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter
|
|
|
miniZ (OP)
|
|
August 16, 2019, 11:42:02 PM |
|
Hi Divinity666, in general it is advisable to use the latest version because we correct bugs that may affect all algos. Because we want to solve this, it would still be helpfull to know the output of miniZ.exe --version. (you can just run it where you have the miniZ.exe file, no need to stop the miner) Also, why did you went back to v1.3n5, and not the previous one v1.4o? Thanks. Cheers v1.4o = v1.3n5 in 144.5 h\r, so no difference from that point. Hi Divinity666, thanks for the information! We are looking into it. Cheers
|
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter
|
|
|
2h4u
Newbie
Offline
Activity: 55
Merit: 0
|
|
August 17, 2019, 05:19:28 PM |
|
Dear miniz, that information is greatly outdated. Nowadays, you don't have to use that super awkward Custom miner scheme because your miner is in stock. Just create Flight Sheet and voila! your miner already is in the list--all versions for all CUDAs.
|
|
|
|
2h4u
Newbie
Offline
Activity: 55
Merit: 0
|
|
August 17, 2019, 05:39:43 PM |
|
Some weird behavior with BeamhashII mining. First 5-6 minutes of any mining session the GPU0 and GPU1 don't hash. Tested on 4 rigs, all the same result. Watch this: [ 0d 0h 5m57s|00:29:39 18/08/2019] S:146/0 164(164.2)Sol/s 385(385.4)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 97ms (94.2%) (5.8%) 0>GTX 1070 Ti `S: 2/0 [48°C/35%] 0.00 I/s 0.0( 0.0)Sol/s 34( 34.3)W clk=1607MHz mclk=4536MHz Sol/W=0.00 1>P106-100 `S: 0/0 [46°C/37%] 0.00 I/s 0.0( 0.0)Sol/s 30( 29.5)W clk=1506MHz mclk=4665MHz Sol/W=0.00 2>P106-100 `S: 16/0 [58°C/58%]*10.55 I/s 20.5(20.5)Sol/s 33( 33.3)W clk=1733MHz mclk=4738MHz Sol/W=0.62 3>P106-100 `S: 15/0 [57°C/63%] 10.27 I/s 19.8(19.8)Sol/s 24( 24.3)W clk=1506MHz mclk=4437MHz Sol/W=0.82 4>GTX 1060 6GB `S: 28/0 [55°C/66%] 12.85 I/s 25.5(25.6)Sol/s 28( 28.2)W clk=1544MHz mclk=4363MHz Sol/W=0.91 5>GTX 1060 6GB `S: 24/0 [54°C/68%] 13.23 I/s 26.0(26.0)Sol/s 29( 28.7)W clk=1594MHz mclk=4437MHz Sol/W=0.91 6>GTX 1060 6GB `S: 20/0 [57°C/62%]*12.58 I/s 25.0(25.1)Sol/s 30( 29.6)W clk=1594MHz mclk=4404MHz Sol/W=0.85 7>GTX 1060 6GB `S: 21/0 [57°C/62%] 11.10 I/s 22.1(22.1)Sol/s 27( 27.5)W clk=1544MHz mclk=4568MHz Sol/W=0.80 8>GTX 1050 Ti `S: 6/0 [48°C/46%] 6.19 I/s 12.1(12.1)Sol/s 75( 75.0)W clk=1290MHz mclk=4058MHz Sol/W=0.16 9>GTX 1050 Ti `S: 14/0 [43°C/36%] 6.61 I/s 13.2(13.2)Sol/s 75( 75.0)W clk=1290MHz mclk=4381MHz Sol/W=0.18 [ 0d 0h 6m07s|00:29:49 18/08/2019] S:147/0 164(164.1)Sol/s 385(385.4)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 96ms (94.3%) (5.7%) 0>GTX 1070 Ti `S: 2/0 [48°C/35%] 0.00 I/s 0.0( 0.0)Sol/s 34( 34.3)W clk=1607MHz mclk=4536MHz Sol/W=0.00 1>P106-100 `S: 0/0 [46°C/37%] 0.00 I/s 0.0( 0.0)Sol/s 30( 29.5)W clk=1506MHz mclk=4665MHz Sol/W=0.00 2>P106-100 `S: 16/0 [58°C/58%] 10.55 I/s 20.7(20.6)Sol/s 33( 33.3)W clk=1733MHz mclk=4738MHz Sol/W=0.62 3>P106-100 `S: 15/0 [57°C/63%] 10.27 I/s 20.1(20.0)Sol/s 24( 24.3)W clk=1506MHz mclk=4437MHz Sol/W=0.82 4>GTX 1060 6GB `S: 28/0 [55°C/66%] 12.85 I/s 25.6(25.6)Sol/s 28( 28.2)W clk=1544MHz mclk=4363MHz Sol/W=0.91 5>GTX 1060 6GB `S: 24/0 [54°C/68%] 13.23 I/s 26.1(26.0)Sol/s 29( 28.7)W clk=1594MHz mclk=4437MHz Sol/W=0.91 6>GTX 1060 6GB `S: 20/0 [57°C/62%] 12.58 I/s 25.1(25.1)Sol/s 30( 29.6)W clk=1594MHz mclk=4404MHz Sol/W=0.85 7>GTX 1060 6GB `S: 22/0 [57°C/62%]*11.09 I/s 22.0(22.0)Sol/s 27( 27.5)W clk=1544MHz mclk=4568MHz Sol/W=0.80 8>GTX 1050 Ti `S: 6/0 [48°C/46%] 6.19 I/s 11.8(11.9)Sol/s 75( 75.0)W clk=1290MHz mclk=4058MHz Sol/W=0.16 9>GTX 1050 Ti `S: 14/0 [43°C/36%] 6.61 I/s 13.2(13.2)Sol/s 75( 75.0)W clk=1290MHz mclk=4381MHz Sol/W=0.18 [ 0d 0h 6m17s|00:29:59 18/08/2019] S:147/0 165(164.7)Sol/s 1083(761.1)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 96ms (94.4%) (5.6%) 0>GTX 1070 Ti `S: 2/0 [45°C/35%] 0.01 I/s 0.0( 0.0)Sol/s 34( 33.9)W clk=1607MHz mclk=4536MHz Sol/W=0.00 1>P106-100 `S: 0/0 [43°C/36%] 0.01 I/s 0.0( 0.0)Sol/s 127( 81.9)W clk=1657MHz mclk=4665MHz Sol/W=0.00 2>P106-100 `S: 16/0 [65°C/47%] 10.55 I/s 20.7(20.6)Sol/s 109( 74.4)W clk=1506MHz mclk=4738MHz Sol/W=0.28 3>P106-100 `S: 15/0 [65°C/60%] 10.27 I/s 20.1(20.0)Sol/s 105( 67.7)W clk=1430MHz mclk=4437MHz Sol/W=0.29 4>GTX 1060 6GB `S: 28/0 [65°C/59%] 12.85 I/s 25.5(25.6)Sol/s 184(112.4)W clk=1873MHz mclk=4363MHz Sol/W=0.23 5>GTX 1060 6GB `S: 24/0 [64°C/62%] 13.23 I/s 25.9(25.9)Sol/s 105( 69.7)W clk=1974MHz mclk=4437MHz Sol/W=0.37 6>GTX 1060 6GB `S: 20/0 [65°C/57%] 12.57 I/s 24.8(25.0)Sol/s 149( 94.0)W clk=1822MHz mclk=4404MHz Sol/W=0.27 7>GTX 1060 6GB `S: 22/0 [65°C/53%] 11.09 I/s 22.2(22.1)Sol/s 120( 77.1)W clk=1594MHz mclk=4568MHz Sol/W=0.29 8>GTX 1050 Ti `S: 6/0 [63°C/35%] 6.19 I/s 12.1(12.1)Sol/s 75( 75.0)W clk=1873MHz mclk=4058MHz Sol/W=0.16 9>GTX 1050 Ti `S: 14/0 [54°C/35%] 6.61 I/s 13.1(13.1)Sol/s 75( 75.0)W clk=1835MHz mclk=4381MHz Sol/W=0.18 [ 0d 0h 6m27s|00:30:09 18/08/2019] S:150/0 172(168.1)Sol/s 977(766.8)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 100ms (94.6%) (5.4%) 0>GTX 1070 Ti `S: 3/0 [51°C/37%]*20.48 I/s 40.9(40.9)Sol/s 77( 38.3)W clk=1847MHz mclk=4536MHz Sol/W=1.07 1>P106-100 `S: 0/0 [50°C/40%] 12.03 I/s 25.8(25.8)Sol/s 109( 82.4)W clk=1835MHz mclk=4665MHz Sol/W=0.31 2>P106-100 `S: 16/0 [65°C/46%] 10.55 I/s 20.6(20.6)Sol/s 91( 74.3)W clk=1506MHz mclk=4738MHz Sol/W=0.28 3>P106-100 `S: 15/0 [64°C/60%] 10.26 I/s 20.2(20.0)Sol/s 85( 67.7)W clk=1506MHz mclk=4437MHz Sol/W=0.30 4>GTX 1060 6GB `S: 28/0 [65°C/59%] 12.85 I/s 25.3(25.5)Sol/s 137(111.2)W clk=1936MHz mclk=4363MHz Sol/W=0.23 5>GTX 1060 6GB `S: 24/0 [64°C/62%] 13.23 I/s 25.9(25.9)Sol/s 109( 71.9)W clk=1949MHz mclk=4437MHz Sol/W=0.36 6>GTX 1060 6GB `S: 21/0 [65°C/56%]*12.57 I/s 24.9(25.0)Sol/s 123( 94.1)W clk=1822MHz mclk=4404MHz Sol/W=0.27 7>GTX 1060 6GB `S: 23/0 [65°C/53%]*11.09 I/s 22.2(22.1)Sol/s 96( 76.9)W clk=1594MHz mclk=4568MHz Sol/W=0.29 8>GTX 1050 Ti `S: 6/0 [64°C/35%] 6.19 I/s 12.1(12.0)Sol/s 75( 75.0)W clk=1873MHz mclk=4058MHz Sol/W=0.16 9>GTX 1050 Ti `S: 14/0 [54°C/35%] 6.61 I/s 13.1(13.1)Sol/s 75( 75.0)W clk=1809MHz mclk=4381MHz Sol/W=0.17
|
|
|
|
miniZ (OP)
|
|
August 18, 2019, 12:08:02 AM |
|
Dear miniz, that information is greatly outdated. Nowadays, you don't have to use that super awkward Custom miner scheme because your miner is in stock. Just create Flight Sheet and voila! your miner already is in the list--all versions for all CUDAs. Some weird behavior with BeamhashII mining. First 5-6 minutes of any mining session the GPU0 and GPU1 don't hash. Tested on 4 rigs, all the same result. Watch this:
Hi 2h2u, We just give the info because some people may want to try it out before the HiveOS update But you are right we need to update the post and inform that Hives OS has added miniZ already and people should give preference to the standard miner setup. Regarding miniZ behaviour, does this happen always? Also, does it happen with all algorithms? Could you also confirm that you are using Hive OS? Thanks for reporting back. Cheers
|
miniZ is a fast and friendly Equihash & ProgPoW Cuda miner. Equihash algorithms: <144,5>, <144,5s> - BeamHash III, <125,4> <192,7> <210,9> <150,5> <96,5>. Ethash and Etchash. ProgPoW (KawPoW, ProgPoWZ, vProgPoW) More information: miniz.cc * Follow us: bitcointalk.org ~ Twitter
|
|
|
2h4u
Newbie
Offline
Activity: 55
Merit: 0
|
|
August 18, 2019, 04:20:10 AM |
|
Regarding miniZ behaviour, does this happen always? Also, does it happen with all algorithms? Could you also confirm that you are using Hive OS?
I have just overview all the logs and can tell this does happen like in 19 out of 20 cases. Average time before full power hashing is 3 minutes. Didn't test other algos. HiveOS, miniz 1.5p cuda 100. Driver version doesn't matter, I have 418.43, 430.14 and 418.56, all the same behaviour. Oh, by the way, it's not only GPU0 and GPU1. In most cases it is, but sometimes it's another two (rarely 1 or 3) gpus. Something wrong with scheduler?
|
|
|
|
2h4u
Newbie
Offline
Activity: 55
Merit: 0
|
|
August 18, 2019, 04:59:17 AM |
|
Another example. Note the temps/fans. Every other miner (gminer, cryptodredge, ethminer) does work without a glitch. [ 0d 0h 6m24s|11:54:12 18/08/2019] S:141/0 143(143.0)Sol/s 128(128.0)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 95ms (94.1%) (5.9%) 0>GTX 1050 Ti `S: 16/0 [43°C/50%] 6.62 I/s 12.8(12.8)Sol/s 64( 64.0)W clk=1290MHz mclk=4399MHz Sol/W=0.20 1>GTX 1050 Ti `S: 9/0 [37°C/50%] 6.49 I/s 12.9(13.0)Sol/s 64( 64.0)W clk=1290MHz mclk=4471MHz Sol/W=0.20 2>GTX 1050 Ti `S: 0/0 [0°C/ 0%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=-nan 3>GTX 1050 Ti `S: 0/0 [0°C/ 0%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=-nan 4>GTX 1050 Ti `S: 18/0 [0°C/ 0%]* 6.63 I/s 12.9(13.1)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 5>GTX 1050 Ti `S: 11/0 [0°C/ 0%] 6.37 I/s 12.8(12.7)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 6>GTX 1050 Ti `S: 8/0 [0°C/ 0%] 6.55 I/s 12.8(12.8)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 7>GTX 1050 Ti `S: 12/0 [0°C/ 0%] 6.52 I/s 12.9(12.8)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 8>GTX 1050 Ti `S: 14/0 [0°C/ 0%] 6.61 I/s 13.2(13.3)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 9>GTX 1050 Ti `S: 19/0 [0°C/ 0%]* 6.53 I/s 13.0(13.0)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 10>GTX 1050 Ti `S: 6/0 [0°C/ 0%] 6.63 I/s 13.5(13.5)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 11>GTX 1050 Ti `S: 18/0 [0°C/ 0%] 6.49 I/s 13.0(12.9)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 12>GTX 1050 Ti `S: 10/0 [0°C/ 0%] 6.59 I/s 13.1(13.1)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf [ 0d 0h 6m34s|11:54:22 18/08/2019] S:142/0 144(143.3)Sol/s 128(128.0)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 95ms (94.2%) (5.8%) 0>GTX 1050 Ti `S: 17/0 [43°C/50%]* 6.62 I/s 13.1(13.0)Sol/s 64( 64.0)W clk=1290MHz mclk=4399MHz Sol/W=0.20 1>GTX 1050 Ti `S: 9/0 [37°C/50%] 6.49 I/s 13.1(13.1)Sol/s 64( 64.0)W clk=1290MHz mclk=4471MHz Sol/W=0.21 2>GTX 1050 Ti `S: 0/0 [0°C/ 0%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=-nan 3>GTX 1050 Ti `S: 0/0 [0°C/ 0%] 0.00 I/s 0.0( 0.0)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=-nan 4>GTX 1050 Ti `S: 18/0 [0°C/ 0%] 6.63 I/s 13.0(13.2)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 5>GTX 1050 Ti `S: 11/0 [0°C/ 0%] 6.37 I/s 12.7(12.7)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 6>GTX 1050 Ti `S: 8/0 [0°C/ 0%] 6.55 I/s 12.9(12.9)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 7>GTX 1050 Ti `S: 12/0 [0°C/ 0%] 6.52 I/s 13.0(12.8)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 8>GTX 1050 Ti `S: 14/0 [0°C/ 0%] 6.61 I/s 13.0(13.2)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 9>GTX 1050 Ti `S: 19/0 [0°C/ 0%] 6.52 I/s 13.1(13.1)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 10>GTX 1050 Ti `S: 6/0 [0°C/ 0%] 6.63 I/s 13.5(13.5)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 11>GTX 1050 Ti `S: 18/0 [0°C/ 0%] 6.49 I/s 13.0(12.8)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf 12>GTX 1050 Ti `S: 10/0 [0°C/ 0%] 6.59 I/s 13.2(13.1)Sol/s 0( 0.0)W clk=0MHz mclk=0MHz Sol/W=inf [ 0d 0h 6m45s|11:54:32 18/08/2019] S:143/0 145(143.9)Sol/s 832(832.0)W [beamv2.eu-new.nicehash.com,Beam-PoW]- 95ms (94.3%) (5.7%) 0>GTX 1050 Ti `S: 17/0 [43°C/50%] 6.62 I/s 13.0(12.9)Sol/s 64( 64.0)W clk=1290MHz mclk=4399MHz Sol/W=0.20 1>GTX 1050 Ti `S: 9/0 [37°C/50%] 6.49 I/s 13.0(13.1)Sol/s 64( 64.0)W clk=1290MHz mclk=4471MHz Sol/W=0.20 2>GTX 1050 Ti `S: 0/0 [38°C/35%] 6.59 I/s 13.4(13.4)Sol/s 64( 64.0)W clk=1290MHz mclk=4360MHz Sol/W=0.21 3>GTX 1050 Ti `S: 0/0 [38°C/35%] 6.51 I/s 13.2(13.2)Sol/s 64( 64.0)W clk=1290MHz mclk=4477MHz Sol/W=0.21 4>GTX 1050 Ti `S: 18/0 [60°C/36%] 6.63 I/s 13.1(13.2)Sol/s 64( 64.0)W clk=1822MHz mclk=4398MHz Sol/W=0.21 5>GTX 1050 Ti `S: 11/0 [50°C/35%] 6.37 I/s 12.7(12.7)Sol/s 64( 64.0)W clk=1695MHz mclk=4404MHz Sol/W=0.20 6>GTX 1050 Ti `S: 8/0 [59°C/36%] 6.55 I/s 13.0(12.9)Sol/s 64( 64.0)W clk=1847MHz mclk=4318MHz Sol/W=0.20 7>GTX 1050 Ti `S: 12/0 [50°C/35%] 6.52 I/s 13.0(12.8)Sol/s 64( 64.0)W clk=1695MHz mclk=4468MHz Sol/W=0.20 8>GTX 1050 Ti `S: 15/0 [61°C/36%]* 6.61 I/s 13.0(13.1)Sol/s 64( 64.0)W clk=1809MHz mclk=4376MHz Sol/W=0.21 9>GTX 1050 Ti `S: 19/0 [53°C/35%] 6.52 I/s 13.2(13.1)Sol/s 64( 64.0)W clk=1670MHz mclk=4485MHz Sol/W=0.20 10>GTX 1050 Ti `S: 6/0 [61°C/35%] 6.63 I/s 13.5(13.5)Sol/s 64( 64.0)W clk=1847MHz mclk=4378MHz Sol/W=0.21 11>GTX 1050 Ti `S: 18/0 [54°C/35%] 6.49 I/s 12.9(12.8)Sol/s 64( 64.0)W clk=1670MHz mclk=4478MHz Sol/W=0.20 12>GTX 1050 Ti `S: 10/0 [55°C/35%] 6.59 I/s 13.2(13.1)Sol/s 64( 64.0)W clk=1898MHz mclk=4358MHz Sol/W=0.20
|
|
|
|
|