trexminer:
Issue of trex crashing after mining dev fee still exists in 0.7.3:
Thanks. This issue has just been identified and fixed. 0.7.4 will contain the fix Works as advertised now, thanks |
|
|
|
trexminer: Issue of trex crashing after mining dev fee still exists in 0.7.3: 20181107 19:34:46 [ OK ] 210/210 - 4903.21 kH/s, 10ms
20181107 19:34:46 GPU #1: Zotac GTX 1050 Ti - 4903.21 kH/s, [T:54C, F:56%]
20181107 19:34:46 Uptime: 55 mins 46 secs
20181107 19:35:22 [ OK ] 211/211 - 4905.11 kH/s, 12ms
20181107 19:35:26 Started mining dev fee
20181107 19:36:26 Done mining dev fee
20181107 19:36:46 [ OK ] 212/212 - 4903.78 kH/s, 10ms
20181107 19:36:46 WARN: Messy shutdown...
20181107 19:36:47 Main loop finished.
20181107 19:36:47 ApiServer: stopped listening on 0.0.0.0:4067
20181107 19:36:47 ApiServer: stopped listening on 0.0.0.0:4068
Waiting for 0 seconds, press a key to continue ...
20181107 19:36:53 T-Rex NVIDIA GPU miner v0.7.3 - [CUDA v9.20]
20181107 19:36:53
20181107 19:36:53 NVIDIA Driver v416.16
20181107 19:36:53 CUDA devices available: 2
|
|
|
|
Trexminer :
0.7.1 and 0.7.2 seem to crash after mining the dev fee - 0.7.0 was fine
Give please some info about cuda version, Windows version ( which updates installed too ) ... Note- this is not limited to Windows, it also happens on Linux with CUDA 9.1 : Thanks nazzer, we'll look into it. Thanks - I've reverted back to 0.7.0 now, for stable x16r hashing |
|
|
|
Trexminer :
0.7.1 and 0.7.2 seem to crash after mining the dev fee - 0.7.0 was fine
Give please some info about cuda version, Windows version ( which updates installed too ) Logs - from Windows:
Windows 10 1803
UpdateCUDA / Driver:
20181028 07:54:50 T-Rex NVIDIA GPU miner v0.7.2 - [CUDA v10.0]
20181028 07:54:50
20181028 07:54:50 NVIDIA Driver v416.16
20181028 07:53:05 [ OK ] 273/273 - 14.90 MH/s, 12ms
20181028 07:53:11 [ OK ] 274/274 - 14.92 MH/s, 10ms
20181028 07:53:17 WARN: 2 shares found
20181028 07:53:17 [ OK ] 275/275 - 14.77 MH/s, 11ms
20181028 07:53:17 GPU #0: Zotac GTX 1070 - 10.70 MH/s, [T:73C, P:98W, F:53%, E:104kH/W]
20181028 07:53:17 GPU #1: Zotac GTX 1050 Ti - 4070.12 kH/s, [T:55C, F:56%]
20181028 07:53:17 Uptime: 34 mins 17 secs
20181028 07:53:18 [ OK ] 276/276 - 14.77 MH/s, 59ms
20181028 07:53:23 Started mining dev fee
20181028 07:54:03 x16r block 423144, diff 85216.305
20181028 07:54:14 x16r block 423145, diff 85059.350
20181028 07:54:23 Done mining dev fee
20181028 07:54:25 [ OK ] 277/277 - 16.88 MH/s, 11ms
20181028 07:54:33 [ OK ] 278/278 - 18.26 MH/s, 10ms
20181028 07:54:43 WARN: Messy shutdown...
20181028 07:54:43 Main loop finished.
20181028 07:54:43 ApiServer: stopped listening on 0.0.0.0:4067
20181028 07:54:43 ApiServer: stopped listening on 0.0.0.0:4068
Note- this is not limited to Windows, it also happens on Linux with CUDA 9.1 : 20181028 07:23:06 Uptime: 1 hour 19 mins 51 secs
20181028 07:23:19 [ OK ] 411/421 - 60.31 MH/s, 12ms
20181028 07:23:49 x16r block 423119, diff 90213.867
20181028 07:23:49 Hash order B4C811FCA4BAD9A5
20181028 07:23:49 HamKckFugShvBmwBmwShaFugEchKckHamEchShbSmdEchSke
20181028 07:23:54 [ OK ] 412/422 - 63.80 MH/s, 12ms
20181028 07:24:07 [ OK ] 413/423 - 73.25 MH/s, 13ms
20181028 07:24:09 Started mining dev fee
20181028 07:25:09 Done mining dev fee
20181028 07:25:11 [ OK ] 414/424 - 80.07 MH/s, 14ms
20181028 07:25:16 x16r block 423120, diff 92111.904
20181028 07:25:16 Hash order 64D95ED776FA511C
20181028 07:25:16 LufKckShbSmdSkeWrlShbCubCubLufShaEchSkeBmwBmwFug
20181028 07:25:22 [ OK ] 415/425 - 83.63 MH/s, 13ms
20181028 07:25:22 GPU #0: Zotac GTX 1070 - 13.67 MH/s, [T:57C, P:99W, F:100%, E:147kH/W]
20181028 07:25:22 GPU #1: Zotac GTX 1070 - 13.55 MH/s, [T:66C, P:91W, F:100%, E:161kH/W]
20181028 07:25:22 GPU #2: GTX 1070 - 14.01 MH/s, [T:63C, P:90W, F:100%, E:156kH/W]
20181028 07:25:22 GPU #3: GTX 1070 - 13.96 MH/s, [T:64C, P:94W, F:80%, E:144kH/W]
20181028 07:25:22 GPU #4: GTX 1070 - 14.12 MH/s, [T:62C, P:85W, F:100%, E:168kH/W]
20181028 07:25:22 GPU #5: GTX 1070 - 14.32 MH/s, [T:59C, P:71W, F:80%, E:161kH/W]
20181028 07:25:22 Uptime: 1 hour 22 mins 7 secs
20181028 07:25:29 [ OK ] 416/426 - 87.84 MH/s, 16ms
20181028 07:25:29 WARN: Messy shutdown...
20181028 07:25:29 Main loop finished.
20181028 07:25:29 ApiServer: stopped listening on 0.0.0.0:4067
20181028 07:25:29 ApiServer: stopped listening on 192.168.1.224:4068
20181028 07:25:29 [ OK ] 417/427 - 0.00 H/s, 12ms
./miner2_x16r_ahashpool.sh: line 12: 32641 Killed
~/trex/t-rex -r 0 -a x16r -o stratum+tcp://x16r.mine.ahashpool.com:3636
-u REMOVED p c=BTC,d=48 -b 192.168.1.224:4068 -J -i 19.5
20181028 07:25:36 T-Rex NVIDIA GPU miner v0.7.2 - [CUDA v9.10]
20181028 07:25:36
20181028 07:25:36 NVIDIA Driver v390.30
20181028 07:25:36 CUDA devices available: 6
|
|
|
|
|
Trexminer :
0.7.1 and 0.7.2 seem to crash after mining the dev fee - 0.7.0 was fine
|
|
|
|
Bittersweet Block day for me ... what with the 14% difficulty increase and the huge selloff in the past few hours, I've now switched off all my miners as they've gone below breakeven on electricity for me.
Last two blocks averaged 110TH for me as I also had to switch a few off prior due to electrical issues.
Oh, wow... Sorry to hear. I've been kicking around some 'what to dos' myself with a potential upgrade, keep the old one running at a loss, etc. but nowhere near the scale you guys are operating on, for sure. Mine is essentially $75 more in electric each month; nothing compared to the $750 more in electric you guys are dealing with. Too bad electric companies don't accept BTC.  Got a bit of good news after I posted that, my friend's managed to sort out a new hosting site at 50% of the current electricity cost, so all is not lost yet ! |
|
|
|
|
Bittersweet Block day for me ... what with the 14% difficulty increase and the huge selloff in the past few hours, I've now switched off all my miners as they've gone below breakeven on electricity for me.
Last two blocks averaged 110TH for me as I also had to switch a few off prior due to electrical issues.
|
|
|
|
|
A few more through the weekend would be excellent ...
|
|
|
|
|
Oh hey weekend started early!
|
|
|
|
|
Ouch, 14% diff change hit like a rock
|
|
|
|
Kano - could I have the link to the mining calculator again? Always can't seem to find it in the thread ... Edit: nevermind found it  http://tradebtc.net/bitcalc.php |
|
|
|
|
Another hit by Sidewinder! Woot!
|
|
|
|
Just got this scam PM: [quote author=rao916 link=action=profile;u=1888646 date=1527860489]
Now GH is activated on kano yooopyyy! :D
[url=http://maxpara.vn/index/Register/?=1]
https://kano.is/index.php?mine=Gh
[/url]
[/quote]
Be wary please |
|
|
|
|
Woo-hoo! Thanks Sidewinder!
|
|
|
|
Cool, yet another one - by Men38 this time  Another one today would be great |
|
|
|
A couple more today and we’ll be on target for May |
|
|
|
BTClock! Thanks Cryptostarusa!
I'm really grateful for the 5Nd ... doesn't feel like my speed diminished much after losing 1 S9 for 10 hours
Yeah, it's not that you don't lose an amount of mining, if you are off for 10 hours then you expect to lose 10 hours worth of mining, but it's that it is spread out over 5Nd so the variance effect is VERY low vs what your reward should be minus 10 hours. If instead the N was only 1 hour, the variance effect is actually VERY high, i.e. your chance of getting less or more than your expected reward, is a lot higher. So as long as your hardware DOES fail a REAL lot on that other pool, it's expected to even out OK eventually. If being offline is a rare event, then you may win some and may lose some, but if you are in the 50% that loses, you don't expect to get it back. But again, it's yet another one of those things that a lot of people on other pools don't notice or don't understand 10 hours spread over 5 days is basically my "normal" variance of all the S9's over a given shift Edit: more like variance for each block, but who's counting  |
|
|
|
|
BTClock! Thanks Cryptostarusa!
I'm really grateful for the 5Nd ... doesn't feel like my speed diminished much after losing 1 S9 for 10 hours
|
|
|
|
Guys some suggestions please, should i mine to my trezor or desktop bitcoin core or brd wallet?
I am using Exodus I have no complains its very easy to use. how is trezor?? Trezor gets angry when you make it receive lots of small payments. It does work but it starts warning you that it's resources are getting sucked up and your acct takes a long time to load. I use a core desktop wallet as my own little clearing house to accumulate mining payouts, then consolidate those UTXOs to trezor at regular intervals. Use the "replace by fee" feature and set the fees to the minimum allowed. Time is not much of a factor when you are just moving money from one of your pockets to another. It only took me 3 months of mining to figure this out. If you are the type who really values privacy, running a core node wallet on a desktop has serious privacy advantages over spv wallets. I'm not that paranoid...but it can't hurt I mine to my Trezor address, and use Electrum to manage the it rather than the web interface. I consolidate everything to a separate hardware wallet when I get too many coin transactions. --- On S9's - one of my S9's went into thermal shutdown, I've replaced it with my spare S9 (yes I have a spare S9, due to power constraints) - haven't had time to diagnose the issue but it's likely the fan. S9 no 11 now pressed into service Thankfully, noticed it in the morning - only ~10.5 hours offline on one machine. I'm considering expanding with 841's next. |
|
|
|
|
Show Posts
