 Show Posts
|
|
Pages: [1]
|
|
Hi Cracfoo,
Nist5 connection refusing for 15 minutes by now:
"Stratum connection failed: Failed to connect to mine.zpool.ca port 3833: Connection refused"
|
|
|
|
Looks like your settings are too aggressive, try if you can run the algorithm stable by lowering overclock and power settings. Once you can run lyra2re2 stable delete Stats\[file for alexis78 lyra2re2] You can remove lyra2re2 from the algorithm list while you work on figuring out the issue. You can also check if running d=1 will run correctly, this would be a good test to see if your power supply is running short. WTF? 2x1070 GTX, NemosMiner-v2.2, zpool.ca When I set to mining lyra2re2 the speed detecting incorrect Type: NVIDIA
Miner Algorithm Speed BTC/Day BTC/GH/Day Pool
----- --------- ----- ------- ---------- ----
ccminerAlexis78 Lyra2RE2 518,26 MH/s 0,00539 0,01040 zpoollive-
ccminerAlexis78 C11 36,06 MH/s 0,00102 0,02842 zpoollive-
CcminerTpruvot Tribus 79,49 MH/s 0,00097 0,01222 zpoollive-
...
... but [2017-10-06 18:14:13] [S/A/T]: 0/21/21, diff: 0.318, 85.52MH/s yes!
[2017-10-06 18:14:18] [S/A/T]: 0/22/22, diff: 2.573, 85.64MH/s yes!
[2017-10-06 18:14:26] [S/A/T]: 0/23/23, diff: 0.641, 85.56MH/s yes!
[2017-10-06 18:14:32] [S/A/T]: 0/24/24, diff: 0.502, 85.53MH/s yes!
[2017-10-06 18:15:10] GPU#1:GeForce GTX 1070, 44.07MH/s
[2017-10-06 18:15:19] GPU#0:GeForce GTX 1070, 43.45MH/s wrong definition of speed and therefore I mining ONLY lyra2re2. And after some time I see that [2017-10-06 18:28:47] GPU#1:an illegal memory access was encountered
[2017-10-06 18:28:47] GPU#0:an illegal memory access was encountered
[2017-10-06 18:28:47] GPU#1:an illegal memory access was encountered
[2017-10-06 18:28:47] GPU#0:an illegal memory access was encountered
[2017-10-06 18:28:47] GPU#1:an illegal memory access was encountered
[2017-10-06 18:28:47] GPU#1:an illegal memory access was encountered What I do wrong? |
|
|
|
|
Need help from someone who understands windows scripts better:
My machine has problems with one algorithm when pool asks for stats, I can see that in the logs. If I manually run that algorithm by itself without stats i.e. with "-p ID=NemosMiner-v2.1,c=BTC" it works stable for a long time.
$workerName, currency and ,stats is concatenated to form the below in the commandline somewhere in the scripts but I could not locate any such usage of workername or currecny or a literal stats.
-p ID=NemosMiner-v2.1,c=BTC,stats
I am running recent download of 2.2. code. NemosMiner-v2.1.ps has a call to Start-Subprocess with the Aruguments. That is defined in Include.ps1.
individual miner fils seem to construct what goes into -p with this:
"-p $($Pools.(Get-Algorithm($_)).Pass)" but I cant see how that is made from combining $workername, c=$Currency and ,stats.
|
|
|
|
|
"Insert Quote
Again for several hours the sigt pool hashrate is 50-100Mh/s. My H/s was reported as 0.67Mh while it is 200."
On sigt I see quite odd numbers reported but the payments are coming along without issue is my summary if I reconcile the below:
* The pool luck is 10-50x better than normal for several hours
* Blocks are actually found
* Pool total hash and reported hash for my worker are extra low
* Overall daily earnings are reasonable for me despite weird hash stats past 3-4 hours.
|
|
|
|
chainworks reports latency. Check if it is going up and down when you have poor poolside hash. Mine was doubling frequently when I had poor results. Statistics->graph on pool's gui looks reasonably healthy today. This can be your internet provider is my best guess, I could not fully rootcause it when mine degraded out of the blue. Anybody else getting like 50% of their hashrates on all the pools right now?
I have 6 cards 4 in 1 right 2 XFX 480 8GB and 2 GTX 1060 in the other another 2 480 8GB XFX
I should be getting 99MH/s but get nowhere near that. I even had one pool get me down to 8MH/s which is like more than 10X less what my power actually is.
Does anybody know whats happening?
My theory so far is the blocks are moving too fast for me to report a share.
For anyone that might be reading my Chainworks pool improved greatly but was doing the same thing as MN and Suprnova almost worse for a bit. Can say after trying each tho somehow the Chainworks is correcting itself a bit but still lower mostly like I mentioned but not quite as low and I've actually seen it hit 99MH/s for the first time out of all the pools I tried for 24 hours |
|
|
|
I have caught moments when my latency goes up from 150-160ms range to over 300ms, that may be enough to explain dips in my poolside numbers. I believe there is some kind of new problem with my internet, for the month before it poolside rate was quite steady. restarts/reboots etc had not generally made a difference though past 2 days is somewhere in the middle. [You just read marketing for cwi miner having the rare feature of showing live latency to pool  ] |
|
|
|
|
Past 5 hours my poolside hash rate for sigt is 60% of what it has historically been, when I look at the statistics graph there is clear change.
There is no errors or change on the miner machine. Anyone else seeing this? It does not drop to zero for me.
|
|
|
|
This has given me the most stable results so far, especially if I compare final hash rate on pool side ... the one under statistics->graph shows you what your pool side average is visually, while any pool will have momentary numbers go up and down. Every miner with every particular card has a different maximum, same miner different algorithms will also have a different limit for overclocking. You look for that limit, than back off some to give it breathing room. By example: When I was testing the limits with CWI I saw the same failure mode 2-3 times around +125 core -1000 memory 88% power, -i 26.5 with my cards (works for a few minutes, I believe when the cards warm up it starts failing). I get "invalid nonce" in a loop, estimated coins goes into millions With the +121 core -1000 memory 88% power, -i 26.5 I was stable for a few hours. I notched down to -i 26 +120 core for some breathing room and have not had problems with my 1080 ti cards within past day. How to get rid of this error?   Overclocking too much. Try dropping down core clocks slowly until it's stable. its only +150 on core, and they're stable on other miner, i tried to lower my intensity but still getting that error, its only on my 1060s, my 1070 is stable. What's your OC setting? PL 70, core +150, mem -502, fan 75, intensity 24 but why on other miner they're stable? And what is in your batch file? cwigm -c sigt -u myusername.myworker -p x -i 23 --lodiff --max-temp=70 Try use intesnity 22 and if it still occurs try lower the core slowly until it will work fine. I also lowered my core from 95 to 90 when i seen few ounce messages during mining. Seems ok now. I had several in 5 hours but maybe this helps and give extra profit in long run. ok,thanks!i will try this, but im only wondering, it's stable with spmod3  |
|
|
|
My results were about 6% better than palgin 1.1 on 1080 tis, similar to other 1080ti numbers here. That was also about 5% better than the klxr (spelling?) source code based x86 compile I made myself. I have not had to tweak anything to make it go, and it never had a crash/pause/confusion/questionable result. Pool side numbers make more sense than other pools, I pay attention to those. High quality stable experience . to answer question above: This line in local text output of miner shows it correctly picks up the 1250/block reward after halving. Coin:signatum | POW: 1250 | Estimated coins/day: 210.961 This miner side per day estimate that follows looks about right for me after running overnight, compared to actual earnings, it ramped up within the first hour, dont get put off with low numbers in the first few minutes. One can not judge this too quickly when blocks take 30-80 minutes. The server side gui has an estimate that is a bit diffrent, all mpos guis seem to have some similar estimate possibly same code. These are hardly ever accurate, especially hard on a coin where difficulty is moving up and down very fast, network has is all over the place and the past day included a halving, Liking it so far, just got my smallest rig set up for testing purposes. Currently running well and testing the max I can produce.
One question - the program says I will currently generate 200+ coins per day yet WTM says I will produce only 100. Is the software not correctly picking up the BR halving?
|
|
|
|
|
I compiled my own.
VS 2017 community does not work.
VS 2013 community works.
I reinstalled cuda 8.0 after vs2013, it would not work if cuda is installed before, in my case after vs2017. It looks for whitelisted VS versions.
Debug build was default and broken for me (was too old compute model wise I believe given it kept running out of memory), choosing "release" "win32" from main window's drop down worked.
I get very close numbers , ~0.5% more than palgin with 1080 tis the way I run them. For me it was not worth the effort for the minor result improvement, I do prefer to use a binary I know is clean.
Can cuda 7.5 coexist with 8.0 installation? I can attempt that also.
|
|
|
|
|
