hello! i am writing here as theres no hashrefinery official thread anywhere i could find. in the last few days i've noticed some strange things. sometimes my hashrate does not get registered at all or sometimes it does get registered but i do not get paid. i would say either they've been hacked or they're stealing hashpower. you can see it in this screenshot. for the last 4 hours of mining x17 i've got nothing:
https://imgur.com/6aAdJur also ahashpool is becoming quite suspicious as well i would say as my earnings have dropped dramatically lately and i get maybe about a half of whats reported in nemosminer.
Topic: [NemosMiner] multi algo profit switching NVIDIA/CPU miner - page 101. (Read 289464 times)
7x 1070 what psu you using could be anything dogey riser insufficient psu.... if your other rigs are running fine an it is just this one i would pull it apart start with one card and one riser install test then add another card keep doing that... that why you can test each riser / gpu and find the problem...
Hope that helped...
Regards
Nemo
P.S looking at the data you provided above:
GPU0 59C Sol/s: 331.3 Sol/W: 3.11 Avg: 331.1 I/s: 176.1 Sh: 0.00 . .
GPU1 61C Sol/s: 440.5 Sol/W: 3.95 Avg: 445.1 I/s: 238.0 Sh: 0.19 1.00 76
GPU2 55C Sol/s: 467.7 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.56 1.00 80
GPU3 58C Sol/s: 446.8 Sol/W: 3.99 Avg: 445.6 I/s: 238.1 Sh: 0.00 . .
GPU4 59C Sol/s: 455.9 Sol/W: 4.03 Avg: 454.3 I/s: 241.9 Sh: 0.00 . .
GPU5 57C Sol/s: 440.0 Sol/W: 3.96 Avg: 446.3 I/s: 238.5 Sh: 0.00 . .
> GPU6 63C Sol/s: 482.2 Sol/W: 3.58 Avg: 481.1 I/s: 256.2 Sh: 0.19 1.00 74
========== Sol/s: 3064.5 Sol/W: 3.82 Avg: 3068.9 I/s: 1637.7 Sh: 0.94 1.00 76
> GPU0 60C Sol/s: 335.7 Sol/W: 3.11 Avg: 331.4 I/s: 179.0 Sh: 0.00 . .
> GPU1 61C Sol/s: 438.4 Sol/W: 3.94 Avg: 444.7 I/s: 237.9 Sh: 0.35 1.00 79 +
> GPU2 55C Sol/s: 465.6 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.53 1.00 80
gpu_id 1 71 2 unspecified launch failure
gpu 1 unresponsive - check overclocking
gpu_id 5 66 3 unspecified launch failure
cudaMemcpy 1 failed
gpu 5 unresponsive - check overclocking
cudaMemcpy 1 failed
something seems to be wrong with GPU 0... Sol/s: 331.3 335.7 is over 100 sols short of what the other 6 1070's are doing may won't to start there...
you may won't to check your OC setting also...
i run my g1 Gaming 1070's at 70%tdp (120-125)watt +75 core +505mem
Hope that helped...
Regards
Nemo
P.S looking at the data you provided above:
GPU0 59C Sol/s: 331.3 Sol/W: 3.11 Avg: 331.1 I/s: 176.1 Sh: 0.00 . .
GPU1 61C Sol/s: 440.5 Sol/W: 3.95 Avg: 445.1 I/s: 238.0 Sh: 0.19 1.00 76
GPU2 55C Sol/s: 467.7 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.56 1.00 80
GPU3 58C Sol/s: 446.8 Sol/W: 3.99 Avg: 445.6 I/s: 238.1 Sh: 0.00 . .
GPU4 59C Sol/s: 455.9 Sol/W: 4.03 Avg: 454.3 I/s: 241.9 Sh: 0.00 . .
GPU5 57C Sol/s: 440.0 Sol/W: 3.96 Avg: 446.3 I/s: 238.5 Sh: 0.00 . .
> GPU6 63C Sol/s: 482.2 Sol/W: 3.58 Avg: 481.1 I/s: 256.2 Sh: 0.19 1.00 74
========== Sol/s: 3064.5 Sol/W: 3.82 Avg: 3068.9 I/s: 1637.7 Sh: 0.94 1.00 76
> GPU0 60C Sol/s: 335.7 Sol/W: 3.11 Avg: 331.4 I/s: 179.0 Sh: 0.00 . .
> GPU1 61C Sol/s: 438.4 Sol/W: 3.94 Avg: 444.7 I/s: 237.9 Sh: 0.35 1.00 79 +
> GPU2 55C Sol/s: 465.6 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.53 1.00 80
gpu_id 1 71 2 unspecified launch failure
gpu 1 unresponsive - check overclocking
gpu_id 5 66 3 unspecified launch failure
cudaMemcpy 1 failed
gpu 5 unresponsive - check overclocking
cudaMemcpy 1 failed
something seems to be wrong with GPU 0... Sol/s: 331.3 335.7 is over 100 sols short of what the other 6 1070's are doing may won't to start there...
you may won't to check your OC setting also...
i run my g1 Gaming 1070's at 70%tdp (120-125)watt +75 core +505mem
Nemo the gpu0 goes down 100 sols/s after I log into the rig. It gives that power to the display when I log into it:
========== Sol/s: 3163.5 Sol/W: 3.89 Avg: 3133.2 I/s: 1688.1 Sh: 3.30 1.00 78
> GPU4 60C Sol/s: 449.4 Sol/W: 4.00 Avg: 451.1 I/s: 241.9 Sh: 0.50 1.00 78
GPU1 61C Sol/s: 441.7 Sol/W: 3.93 Avg: 442.7 I/s: 237.6 Sh: 0.56 1.00 78
GPU2 56C Sol/s: 464.5 Sol/W: 4.09 Avg: 457.7 I/s: 246.6 Sh: 0.49 1.00 78
GPU5 58C Sol/s: 447.8 Sol/W: 3.95 Avg: 445.2 I/s: 238.2 Sh: 0.40 1.00 78
GPU3 59C Sol/s: 442.9 Sol/W: 3.93 Avg: 438.4 I/s: 236.0 Sh: 0.47 1.00 78
GPU0 63C Sol/s: 441.1 Sol/W: 3.77 Avg: 421.1 I/s: 233.9 Sh: 0.42 1.00 78
GPU6 64C Sol/s: 486.9 Sol/W: 3.55 Avg: 477.3 I/s: 255.8 Sh: 0.42 1.00 78
========== Sol/s: 3174.1 Sol/W: 3.89 Avg: 3133.5 I/s: 1690.0 Sh: 3.28 1.00 78
GPU4 60C Sol/s: 447.6 Sol/W: 4.00 Avg: 451.0 I/s: 241.8 Sh: 0.49 1.00 78
GPU1 61C Sol/s: 440.8 Sol/W: 3.93 Avg: 442.7 I/s: 237.5 Sh: 0.58 1.00 78 +
GPU2 56C Sol/s: 454.9 Sol/W: 4.09 Avg: 457.7 I/s: 245.6 Sh: 0.51 1.00 79 +
GPU5 58C Sol/s: 440.6 Sol/W: 3.95 Avg: 445.2 I/s: 238.4 Sh: 0.42 1.00 78 +
GPU3 59C Sol/s: 445.1 Sol/W: 3.93 Avg: 438.4 I/s: 235.0 Sh: 0.47 1.00 78
GPU6 64C Sol/s: 473.3 Sol/W: 3.55 Avg: 477.2 I/s: 256.0 Sh: 0.42 1.00 78
========== Sol/s: 3143.3 Sol/W: 3.89 Avg: 3133.4 I/s: 1688.2 Sh: 3.32 1.00 78
GPU0 63C Sol/s: 438.5 Sol/W: 3.77 Avg: 421.2 I/s: 234.1 Sh: 0.42 1.00 78
# server set difficulty to: 00009e842444b57508000000...
> GPU4 60C Sol/s: 456.1 Sol/W: 4.00 Avg: 451.1 I/s: 242.0 Sh: 0.49 1.00 78
> GPU1 61C Sol/s: 444.9 Sol/W: 3.93 Avg: 442.7 I/s: 237.0 Sh: 0.58 1.00 78
> GPU2 56C Sol/s: 454.4 Sol/W: 4.08 Avg: 457.7 I/s: 244.3 Sh: 0.51 1.00 79
> GPU5 58C Sol/s: 447.1 Sol/W: 3.95 Avg: 445.2 I/s: 237.3 Sh: 0.42 1.00 78
> GPU3 59C Sol/s: 446.8 Sol/W: 3.93 Avg: 438.5 I/s: 234.5 Sh: 0.46 1.00 78
> GPU0 62C Sol/s: 382.5 Sol/W: 3.77 Avg: 420.9 I/s: 207.6 Sh: 0.42 1.00 78
> GPU6 64C Sol/s: 481.5 Sol/W: 3.55 Avg: 477.3 I/s: 255.3 Sh: 0.42 1.00 78
========== Sol/s: 3169.3 Sol/W: 3.89 Avg: 3133.7 I/s: 1684.5 Sh: 3.30 1.00 78
I dont think there is a hardware issue as there have been times it ran for over 24 hours without any issues. Its going on almost 5 hours now and no errors dished out. Fingers crossed.
7x 1070 what psu you using could be anything dogey riser insufficient psu.... if your other rigs are running fine an it is just this one i would pull it apart start with one card and one riser install test then add another card keep doing that... that why you can test each riser / gpu and find the problem...
Hope that helped...
Regards
Nemo
P.S looking at the data you provided above:
GPU0 59C Sol/s: 331.3 Sol/W: 3.11 Avg: 331.1 I/s: 176.1 Sh: 0.00 . .
GPU1 61C Sol/s: 440.5 Sol/W: 3.95 Avg: 445.1 I/s: 238.0 Sh: 0.19 1.00 76
GPU2 55C Sol/s: 467.7 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.56 1.00 80
GPU3 58C Sol/s: 446.8 Sol/W: 3.99 Avg: 445.6 I/s: 238.1 Sh: 0.00 . .
GPU4 59C Sol/s: 455.9 Sol/W: 4.03 Avg: 454.3 I/s: 241.9 Sh: 0.00 . .
GPU5 57C Sol/s: 440.0 Sol/W: 3.96 Avg: 446.3 I/s: 238.5 Sh: 0.00 . .
> GPU6 63C Sol/s: 482.2 Sol/W: 3.58 Avg: 481.1 I/s: 256.2 Sh: 0.19 1.00 74
========== Sol/s: 3064.5 Sol/W: 3.82 Avg: 3068.9 I/s: 1637.7 Sh: 0.94 1.00 76
> GPU0 60C Sol/s: 335.7 Sol/W: 3.11 Avg: 331.4 I/s: 179.0 Sh: 0.00 . .
> GPU1 61C Sol/s: 438.4 Sol/W: 3.94 Avg: 444.7 I/s: 237.9 Sh: 0.35 1.00 79 +
> GPU2 55C Sol/s: 465.6 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.53 1.00 80
gpu_id 1 71 2 unspecified launch failure
gpu 1 unresponsive - check overclocking
gpu_id 5 66 3 unspecified launch failure
cudaMemcpy 1 failed
gpu 5 unresponsive - check overclocking
cudaMemcpy 1 failed
something seems to be wrong with GPU 0... Sol/s: 331.3 335.7 is over 100 sols short of what the other 6 1070's are doing may wan't to start there...
you may wan't to check your OC setting also...
i run my g1 Gaming 1070's at 70%tdp (120-125)watt +75 core +505mem
Hope that helped...
Regards
Nemo
P.S looking at the data you provided above:
GPU0 59C Sol/s: 331.3 Sol/W: 3.11 Avg: 331.1 I/s: 176.1 Sh: 0.00 . .
GPU1 61C Sol/s: 440.5 Sol/W: 3.95 Avg: 445.1 I/s: 238.0 Sh: 0.19 1.00 76
GPU2 55C Sol/s: 467.7 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.56 1.00 80
GPU3 58C Sol/s: 446.8 Sol/W: 3.99 Avg: 445.6 I/s: 238.1 Sh: 0.00 . .
GPU4 59C Sol/s: 455.9 Sol/W: 4.03 Avg: 454.3 I/s: 241.9 Sh: 0.00 . .
GPU5 57C Sol/s: 440.0 Sol/W: 3.96 Avg: 446.3 I/s: 238.5 Sh: 0.00 . .
> GPU6 63C Sol/s: 482.2 Sol/W: 3.58 Avg: 481.1 I/s: 256.2 Sh: 0.19 1.00 74
========== Sol/s: 3064.5 Sol/W: 3.82 Avg: 3068.9 I/s: 1637.7 Sh: 0.94 1.00 76
> GPU0 60C Sol/s: 335.7 Sol/W: 3.11 Avg: 331.4 I/s: 179.0 Sh: 0.00 . .
> GPU1 61C Sol/s: 438.4 Sol/W: 3.94 Avg: 444.7 I/s: 237.9 Sh: 0.35 1.00 79 +
> GPU2 55C Sol/s: 465.6 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.53 1.00 80
gpu_id 1 71 2 unspecified launch failure
gpu 1 unresponsive - check overclocking
gpu_id 5 66 3 unspecified launch failure
cudaMemcpy 1 failed
gpu 5 unresponsive - check overclocking
cudaMemcpy 1 failed
something seems to be wrong with GPU 0... Sol/s: 331.3 335.7 is over 100 sols short of what the other 6 1070's are doing may wan't to start there...
you may wan't to check your OC setting also...
i run my g1 Gaming 1070's at 70%tdp (120-125)watt +75 core +505mem
I don't know if this has been mentioned before but zm.exe keeps crashing on random gpu's for only one of my rigs:
========== Sol/s: 3055.0 Sol/W: 3.82 Avg: 3069.2 I/s: 1634.2 Sh: 1.00 1.00 76
GPU0 59C Sol/s: 331.3 Sol/W: 3.11 Avg: 331.1 I/s: 176.1 Sh: 0.00 . .
GPU1 61C Sol/s: 440.5 Sol/W: 3.95 Avg: 445.1 I/s: 238.0 Sh: 0.19 1.00 76
GPU2 55C Sol/s: 467.7 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.56 1.00 80
GPU3 58C Sol/s: 446.8 Sol/W: 3.99 Avg: 445.6 I/s: 238.1 Sh: 0.00 . .
GPU4 59C Sol/s: 455.9 Sol/W: 4.03 Avg: 454.3 I/s: 241.9 Sh: 0.00 . .
GPU5 57C Sol/s: 440.0 Sol/W: 3.96 Avg: 446.3 I/s: 238.5 Sh: 0.00 . .
> GPU6 63C Sol/s: 482.2 Sol/W: 3.58 Avg: 481.1 I/s: 256.2 Sh: 0.19 1.00 74
========== Sol/s: 3064.5 Sol/W: 3.82 Avg: 3068.9 I/s: 1637.7 Sh: 0.94 1.00 76
> GPU0 60C Sol/s: 335.7 Sol/W: 3.11 Avg: 331.4 I/s: 179.0 Sh: 0.00 . .
> GPU1 61C Sol/s: 438.4 Sol/W: 3.94 Avg: 444.7 I/s: 237.9 Sh: 0.35 1.00 79 +
> GPU2 55C Sol/s: 465.6 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.53 1.00 80
gpu_id 1 71 2 unspecified launch failure
gpu 1 unresponsive - check overclocking
gpu_id 5 66 3 unspecified launch failure
cudaMemcpy 1 failed
gpu 5 unresponsive - check overclocking
cudaMemcpy 1 failed
++++++++++++++++++++++++++++
I have multiple other rigs running nemos and they are going strong for weeks now. This one machine is causing problems.
x7 GeForce GTX 1070: OC: 75%pwr, CC +130, MC +560
3 of my rigs running driver version 390.65 and are on the same hardware. This is the only one crashing. Is there something that can be done for this? I've reset the OC settings to stock and its still doing this. Crashes every 4-5 minutes of running.
========== Sol/s: 3055.0 Sol/W: 3.82 Avg: 3069.2 I/s: 1634.2 Sh: 1.00 1.00 76
GPU0 59C Sol/s: 331.3 Sol/W: 3.11 Avg: 331.1 I/s: 176.1 Sh: 0.00 . .
GPU1 61C Sol/s: 440.5 Sol/W: 3.95 Avg: 445.1 I/s: 238.0 Sh: 0.19 1.00 76
GPU2 55C Sol/s: 467.7 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.56 1.00 80
GPU3 58C Sol/s: 446.8 Sol/W: 3.99 Avg: 445.6 I/s: 238.1 Sh: 0.00 . .
GPU4 59C Sol/s: 455.9 Sol/W: 4.03 Avg: 454.3 I/s: 241.9 Sh: 0.00 . .
GPU5 57C Sol/s: 440.0 Sol/W: 3.96 Avg: 446.3 I/s: 238.5 Sh: 0.00 . .
> GPU6 63C Sol/s: 482.2 Sol/W: 3.58 Avg: 481.1 I/s: 256.2 Sh: 0.19 1.00 74
========== Sol/s: 3064.5 Sol/W: 3.82 Avg: 3068.9 I/s: 1637.7 Sh: 0.94 1.00 76
> GPU0 60C Sol/s: 335.7 Sol/W: 3.11 Avg: 331.4 I/s: 179.0 Sh: 0.00 . .
> GPU1 61C Sol/s: 438.4 Sol/W: 3.94 Avg: 444.7 I/s: 237.9 Sh: 0.35 1.00 79 +
> GPU2 55C Sol/s: 465.6 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.53 1.00 80
gpu_id 1 71 2 unspecified launch failure
gpu 1 unresponsive - check overclocking
gpu_id 5 66 3 unspecified launch failure
cudaMemcpy 1 failed
gpu 5 unresponsive - check overclocking
cudaMemcpy 1 failed
++++++++++++++++++++++++++++
I have multiple other rigs running nemos and they are going strong for weeks now. This one machine is causing problems.
x7 GeForce GTX 1070: OC: 75%pwr, CC +130, MC +560
3 of my rigs running driver version 390.65 and are on the same hardware. This is the only one crashing. Is there something that can be done for this? I've reset the OC settings to stock and its still doing this. Crashes every 4-5 minutes of running.
these are the specs for my cards:
GPU#0: ASUS GTX 1070
GPU#1: ASUS GTX 1070
GPU#2: EVGA GTX 1070
GPU#3: ASUS GTX 1070
GPU#4: ASUS GTX 1070
GPU#5: ASUS GTX 1070
GPU#6: Gigabyte GTX 1070
Is there something that needs to be added to DSTM.PS1 file for it to prevent from zm.exe from crashing? Every time it becomes unresponsive, I need to click the OK button on the error message for the miner to resume operations.
Update: Restarted the rig at noon my time (PST -8) and ran the miner. Has been stable for the past 4 hours without any hiccups. Been monitoring it off and on and the miner is switching between DSTM and CCminer over and over again without any issues. What could be causing this problem when it starts to crash? My virt mem is set at 64 gigs max, all sleep mode crap is disabled, bios sees all card fine. All in all like I mentioned, I have other rigs identical to this running without any issues for many days now.
nicehash ok i'll add workername for you shortly sorry havn't used nicehash for a while... just testing through nicehash atm your right there is no workername just -p x
Regards
Nemo
Regards
Nemo
Thanks!
It's not just the batch file that needs to be fixed. It's function was removed elsewhere too.
done : ) https://github.com/nemosminer/NemosMiner-v2.3/issues/177
Best Regards
Nemo
nicehash ok i'll add workername for you shortly sorry havn't used nicehash for a while... just testing through nicehash atm your right there is no workername just -p x
Regards
Nemo
Regards
Nemo
I'm getting a "Duplicate Share" error when running palgin (neoscrypt). I'm unable to do a screenshot since it freezes until the miner closes for some reason. I'll try to take a photo using my phone later when I get home.
Nemos,
Is there a specific instruction on how these batch files are being run? "restart.bat, stop.bat, miner.bat". I tried changing my interval from the new default of 30 to 900 as to let the miners get into the correct hashrates but for some reason, I think it's restarting my computer (not sure since I'm remotely connected to it).
Nemos,
Is there a specific instruction on how these batch files are being run? "restart.bat, stop.bat, miner.bat". I tried changing my interval from the new default of 30 to 900 as to let the miners get into the correct hashrates but for some reason, I think it's restarting my computer (not sure since I'm remotely connected to it).
Need a lil help with the new version @Nemos
try not changing any intervals just run as is... (note:1st benchmarks will take 12mins per algo)
just change your btc address or user name for miningpool hub
you don't run restart.bat, stop.bat, miner.bat etc...
you should still be running eg. startzpool.bat startahashpool.bat startminingpoolhub.bat etc (same as previous versions)
Regards
Nemo
Thanks, the only change I did was for the interval. I restored it to default which is 30. It works up to a certain point then restarts my computer for some reason. No problems with the 2.3c version (keeping it in cases like these). So is the restart,stop,and miner batch files are being used with the 2.3 version?
As for benchmarking neoscrypt, I'm getting a duplicate share issue. Not sure what it is and I would like to figure that out but with this restart problem I might not be able to do that. I have removed neoscrypt for now.
Thanks again Nemos. I wanted to troubleshoot this myself but got lost so divine intervention is needed
there is something wrong with your rig... your rig/pc should not restart.... also i have run latest code through serval rigs now (6x1070 & 6x1080ti)PalginsHSR is working correctly im not getting any "duplicate share issue"
use latest release 2.3c-beta if it is working well for you...
Latest (Fully Tested) Release NemosMiner-v2.3c-beta.zip : https://github.com/nemosminer/NemosMiner-v2.3/releases/download/NemosMiner-v2.3c-beta/NemosMiner-v2.3c-beta.zip
im still testing the new master code atm it is not ready for release yet... NemosMiner-v2.3+(PalginHSR,XMrig) https://github.com/nemosminer/NemosMiner-v2.3/archive/master.zip
Best Regards
Nemo
try not changing any intervals just run as is... (note:1st benchmarks will take 12mins per algo)
just change your btc address or user name for miningpool hub
you don't run restart.bat, stop.bat, miner.bat etc...
you should still be running eg. startzpool.bat startahashpool.bat startminingpoolhub.bat etc (same as previous versions)
Regards
Nemo
Thank you for your answer.just change your btc address or user name for miningpool hub
you don't run restart.bat, stop.bat, miner.bat etc...
you should still be running eg. startzpool.bat startahashpool.bat startminingpoolhub.bat etc (same as previous versions)
Regards
Nemo
Maybe I missed something and how to to that, but is it possible to monitor 2 different pool ? I would like to use ahashpool, and zpool for equihash. Which do I need to edit or launch to to use/monitor both pools ?
Thank you !
I'm getting a "Duplicate Share" error when running palgin (neoscrypt). I'm unable to do a screenshot since it freezes until the miner closes for some reason. I'll try to take a photo using my phone later when I get home.
Nemos,
Is there a specific instruction on how these batch files are being run? "restart.bat, stop.bat, miner.bat". I tried changing my interval from the new default of 30 to 900 as to let the miners get into the correct hashrates but for some reason, I think it's restarting my computer (not sure since I'm remotely connected to it).
Nemos,
Is there a specific instruction on how these batch files are being run? "restart.bat, stop.bat, miner.bat". I tried changing my interval from the new default of 30 to 900 as to let the miners get into the correct hashrates but for some reason, I think it's restarting my computer (not sure since I'm remotely connected to it).
Need a lil help with the new version @Nemos
try not changing any intervals just run as is... (note:1st benchmarks will take 12mins per algo)
just change your btc address or user name for miningpool hub
you don't run restart.bat, stop.bat, miner.bat etc...
you should still be running eg. startzpool.bat startahashpool.bat startminingpoolhub.bat etc (same as previous versions)
Regards
Nemo
Thanks, the only change I did was for the interval. I restored it to default which is 30. It works up to a certain point then restarts my computer for some reason. No problems with the 2.3c version (keeping it in cases like these). So is the restart,stop,and miner batch files are being used with the 2.3 version?
As for benchmarking neoscrypt, I'm getting a duplicate share issue. Not sure what it is and I would like to figure that out but with this restart problem I might not be able to do that. I have removed neoscrypt for now.
Thanks again Nemos. I wanted to troubleshoot this myself but got lost so divine intervention is needed
I'm getting a "Duplicate Share" error when running palgin (neoscrypt). I'm unable to do a screenshot since it freezes until the miner closes for some reason. I'll try to take a photo using my phone later when I get home.
Nemos,
Is there a specific instruction on how these batch files are being run? "restart.bat, stop.bat, miner.bat". I tried changing my interval from the new default of 30 to 900 as to let the miners get into the correct hashrates but for some reason, I think it's restarting my computer (not sure since I'm remotely connected to it).
Nemos,
Is there a specific instruction on how these batch files are being run? "restart.bat, stop.bat, miner.bat". I tried changing my interval from the new default of 30 to 900 as to let the miners get into the correct hashrates but for some reason, I think it's restarting my computer (not sure since I'm remotely connected to it).
Need a lil help with the new version @Nemos
try not changing any intervals just run as is... (note:1st benchmarks will take 12mins per algo)
just change your btc address or user name for miningpool hub
you don't run restart.bat, stop.bat, miner.bat etc...
you should still be running eg. startzpool.bat startahashpool.bat startminingpoolhub.bat etc (same as previous versions)
Regards
Nemo
Any reason why the -WorkerName switch was removed? I noticed this back when you had the palgin fork, but now the change is in master as well.
I know you have a lot of recent commits, so not sure if this is temporary, or a permanent. But I find the workername important for monitoring workers.
I posted a page or so back, but not sure it got lost in the sea of posts, so figured I'd post again.
its not removed....
https://imgur.com/a/dOMvo
https://imgur.com/a/Snuke
what pool are you running?
Regards Nemo
I'm getting a "Duplicate Share" error when running palgin (neoscrypt). I'm unable to do a screenshot since it freezes until the miner closes for some reason. I'll try to take a photo using my phone later when I get home.
Nemos,
Is there a specific instruction on how these batch files are being run? "restart.bat, stop.bat, miner.bat". I tried changing my interval from the new default of 30 to 900 as to let the miners get into the correct hashrates but for some reason, I think it's restarting my computer (not sure since I'm remotely connected to it).
Nemos,
Is there a specific instruction on how these batch files are being run? "restart.bat, stop.bat, miner.bat". I tried changing my interval from the new default of 30 to 900 as to let the miners get into the correct hashrates but for some reason, I think it's restarting my computer (not sure since I'm remotely connected to it).
Need a lil help with the new version @Nemos
try not changing any intervals just run as is... (note:1st benchmarks will take 12mins per algo)
just change your btc address or user name for miningpool hub
you don't run restart.bat, stop.bat, miner.bat etc...
you should still be running eg. startzpool.bat startahashpool.bat startminingpoolhub.bat etc (same as previous versions)
Regards
Nemo
I'm getting a "Duplicate Share" error when running palgin (neoscrypt). I'm unable to do a screenshot since it freezes until the miner closes for some reason. I'll try to take a photo using my phone later when I get home.
Nemos,
Is there a specific instruction on how these batch files are being run? "restart.bat, stop.bat, miner.bat". I tried changing my interval from the new default of 30 to 900 as to let the miners get into the correct hashrates but for some reason, I think it's restarting my computer (not sure since I'm remotely connected to it).
Nemos,
Is there a specific instruction on how these batch files are being run? "restart.bat, stop.bat, miner.bat". I tried changing my interval from the new default of 30 to 900 as to let the miners get into the correct hashrates but for some reason, I think it's restarting my computer (not sure since I'm remotely connected to it).
Need a lil help with the new version @Nemos
I don't know if this has been mentioned before but zm.exe keeps crashing on random gpu's for only one of my rigs:
========== Sol/s: 3055.0 Sol/W: 3.82 Avg: 3069.2 I/s: 1634.2 Sh: 1.00 1.00 76
GPU0 59C Sol/s: 331.3 Sol/W: 3.11 Avg: 331.1 I/s: 176.1 Sh: 0.00 . .
GPU1 61C Sol/s: 440.5 Sol/W: 3.95 Avg: 445.1 I/s: 238.0 Sh: 0.19 1.00 76
GPU2 55C Sol/s: 467.7 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.56 1.00 80
GPU3 58C Sol/s: 446.8 Sol/W: 3.99 Avg: 445.6 I/s: 238.1 Sh: 0.00 . .
GPU4 59C Sol/s: 455.9 Sol/W: 4.03 Avg: 454.3 I/s: 241.9 Sh: 0.00 . .
GPU5 57C Sol/s: 440.0 Sol/W: 3.96 Avg: 446.3 I/s: 238.5 Sh: 0.00 . .
> GPU6 63C Sol/s: 482.2 Sol/W: 3.58 Avg: 481.1 I/s: 256.2 Sh: 0.19 1.00 74
========== Sol/s: 3064.5 Sol/W: 3.82 Avg: 3068.9 I/s: 1637.7 Sh: 0.94 1.00 76
> GPU0 60C Sol/s: 335.7 Sol/W: 3.11 Avg: 331.4 I/s: 179.0 Sh: 0.00 . .
> GPU1 61C Sol/s: 438.4 Sol/W: 3.94 Avg: 444.7 I/s: 237.9 Sh: 0.35 1.00 79 +
> GPU2 55C Sol/s: 465.6 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.53 1.00 80
gpu_id 1 71 2 unspecified launch failure
gpu 1 unresponsive - check overclocking
gpu_id 5 66 3 unspecified launch failure
cudaMemcpy 1 failed
gpu 5 unresponsive - check overclocking
cudaMemcpy 1 failed
++++++++++++++++++++++++++++
I have multiple other rigs running nemos and they are going strong for weeks now. This one machine is causing problems.
x7 GeForce GTX 1070: OC: 75%pwr, CC +130, MC +560
3 of my rigs running driver version 390.65 and are on the same hardware. This is the only one crashing. Is there something that can be done for this? I've reset the OC settings to stock and its still doing this. Crashes every 4-5 minutes of running.
========== Sol/s: 3055.0 Sol/W: 3.82 Avg: 3069.2 I/s: 1634.2 Sh: 1.00 1.00 76
GPU0 59C Sol/s: 331.3 Sol/W: 3.11 Avg: 331.1 I/s: 176.1 Sh: 0.00 . .
GPU1 61C Sol/s: 440.5 Sol/W: 3.95 Avg: 445.1 I/s: 238.0 Sh: 0.19 1.00 76
GPU2 55C Sol/s: 467.7 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.56 1.00 80
GPU3 58C Sol/s: 446.8 Sol/W: 3.99 Avg: 445.6 I/s: 238.1 Sh: 0.00 . .
GPU4 59C Sol/s: 455.9 Sol/W: 4.03 Avg: 454.3 I/s: 241.9 Sh: 0.00 . .
GPU5 57C Sol/s: 440.0 Sol/W: 3.96 Avg: 446.3 I/s: 238.5 Sh: 0.00 . .
> GPU6 63C Sol/s: 482.2 Sol/W: 3.58 Avg: 481.1 I/s: 256.2 Sh: 0.19 1.00 74
========== Sol/s: 3064.5 Sol/W: 3.82 Avg: 3068.9 I/s: 1637.7 Sh: 0.94 1.00 76
> GPU0 60C Sol/s: 335.7 Sol/W: 3.11 Avg: 331.4 I/s: 179.0 Sh: 0.00 . .
> GPU1 61C Sol/s: 438.4 Sol/W: 3.94 Avg: 444.7 I/s: 237.9 Sh: 0.35 1.00 79 +
> GPU2 55C Sol/s: 465.6 Sol/W: 4.14 Avg: 465.4 I/s: 248.7 Sh: 0.53 1.00 80
gpu_id 1 71 2 unspecified launch failure
gpu 1 unresponsive - check overclocking
gpu_id 5 66 3 unspecified launch failure
cudaMemcpy 1 failed
gpu 5 unresponsive - check overclocking
cudaMemcpy 1 failed
++++++++++++++++++++++++++++
I have multiple other rigs running nemos and they are going strong for weeks now. This one machine is causing problems.
x7 GeForce GTX 1070: OC: 75%pwr, CC +130, MC +560
3 of my rigs running driver version 390.65 and are on the same hardware. This is the only one crashing. Is there something that can be done for this? I've reset the OC settings to stock and its still doing this. Crashes every 4-5 minutes of running.
these are the specs for my cards:
GPU#0: ASUS GTX 1070
GPU#1: ASUS GTX 1070
GPU#2: EVGA GTX 1070
GPU#3: ASUS GTX 1070
GPU#4: ASUS GTX 1070
GPU#5: ASUS GTX 1070
GPU#6: Gigabyte GTX 1070
Is there something that needs to be added to DSTM.PS1 file for it to prevent from zm.exe from crashing? Every time it becomes unresponsive, I need to click the OK button on the error message for the miner to resume operations.
Same for me. I stopped using Nemosminer and Sniffdog because of that. I don't know why the damn things keep crashing, I suppose it's either intensity or clocks related for some specific algos or miners... But then again nothing's for sure. Some algos I can mine for days without a hickup, others will crash within minutes. Profit-switching programs just exacerbate the issue. 
Sad to hear that... Been using Sniff and Nemos for months.. Never had one issue.
also sad to hear i have 7 different rigs all running Latest Build of NemosMiner....
been running since i started this project almost a year ago now i have 2 6x10603g / 1 6x1080ti / 2 6x1070ti / 2 6x1070 i have no crashes and is running very stable
i usually run ahashpool lately but when i test i use miningpool hub and ahashpool and i don't get any crashes there is nothing wrong with intensity...
my 6x1070 test rig running latest code: https://github.com/nemosminer/NemosMiner-v2.3/archive/master.zip (has been running for over 24hours now...)
Best Regards
Nemo
Hi Nemo,
Could you tell me bit more about the hardware you are using, which motherboard and risers for example?
Which version (build) of Windows. Any special tweaks? I`m facing problems. Like the PalginHSR miner is Benchmarking for ever. Using newest version...
6X1080Ti 70GB Virtual Memory. Win10 X64 Pro latest updates and drivers installed.
6X1080Ti 70GB Virtual Memory. Win10 X64 Pro latest updates and drivers installed.
Same here....benchmark PalginHSR doesn't stop.
Fixed:
Palgin HSR-Neoscrypt has now been added and is running and benchmarking correctly you can test for your self here, have also added XMRig for cryptonight
NemosMiner-v2.3 + Palgin Neoscrypt + XMRig
https://github.com/nemosminer/NemosMiner-v2.3/archive/master.zip
Tested on MiningPoolhub and Ahashpool with a 6x1070 rig (i will test it through my 6x1060 3gb and 6x1080ti rigs 2moro)
Best Regards
Nemo
Your miner works fine here on multiple GTX 1080 ti.
I just registered here to thank you !
Much Appreciated (i'll be testing on my own 6x1080ti rig today)
Best Regards
Nemo
Same for me. I stopped using Nemosminer and Sniffdog because of that. I don't know why the damn things keep crashing, I suppose it's either intensity or clocks related for some specific algos or miners... But then again nothing's for sure. Some algos I can mine for days without a hickup, others will crash within minutes. Profit-switching programs just exacerbate the issue.
Sad to hear that... Been using Sniff and Nemos for months.. Never had one issue.
also sad to hear i have 7 different rigs all running Latest Build of NemosMiner....
been running since i started this project almost a year ago now i have 2 6x10603g / 1 6x1080ti / 2 6x1070ti / 2 6x1070 i have no crashes and is running very stable
i usually run ahashpool lately but when i test i use miningpool hub and ahashpool and i don't get any crashes there is nothing wrong with intensity...
my 6x1070 test rig running latest code: https://github.com/nemosminer/NemosMiner-v2.3/archive/master.zip (has been running for over 24hours now...)
Best Regards
Nemo
I have almost same issue as some others. But my miner does not crash, it just lag whole computer and everything is really really slow, hashes drops under half of full speed and only pc restart help. This happen mostly on miningpoolhub and few times a day. I tried to set lower clocks because it looks like it set very high clock and then everything is slow, but it doesnt help.
Zikkson that slowdown sounds like a Virtual Memory issue. Try to set it at min 16gigs max 64 gigs.
COMPARISON TESTING POOLS!!!!
As some of you know I have 2 identical (1070ti x 6) rigs mining in a test. I've originally tested ahashpool vs ahashpool24 and found ahashpool after 17.5 days was a little more profitable (at least period 12/27-1/14)
After finding this out, I switched the two rigs to mine two different pools. I'm comparing ahashpool (who lists better profits and lower fees) vs zpool. So far
27.5 hrs in - Ahashpool 0.00295502 vs Zpool 0.00261868
At current value of $14,000, we have earned $41.37 from AHashPool vs $36.66 from Zpool in a 27.5 hour period!
I kinda like making $5 more per rig per day We'll see if this holds true over the coming weeks...
As some of you know I have 2 identical (1070ti x 6) rigs mining in a test. I've originally tested ahashpool vs ahashpool24 and found ahashpool after 17.5 days was a little more profitable (at least period 12/27-1/14)
After finding this out, I switched the two rigs to mine two different pools. I'm comparing ahashpool (who lists better profits and lower fees) vs zpool. So far
27.5 hrs in - Ahashpool 0.00295502 vs Zpool 0.00261868
At current value of $14,000, we have earned $41.37 from AHashPool vs $36.66 from Zpool in a 27.5 hour period!
I kinda like making $5 more per rig per day
We'll see if this holds true over the coming weeks...Fixed:
Palgin HSR-Neoscrypt has now been added and is running and benchmarking correctly you can test for your self here, have also added XMRig for cryptonight
NemosMiner-v2.3 + Palgin Neoscrypt + XMRig
https://github.com/nemosminer/NemosMiner-v2.3/archive/master.zip
Tested on MiningPoolhub and Ahashpool with a 6x1070 rig (i will test it through my 6x1060 3gb and 6x1080ti rigs 2moro)
Best Regards
Nemo
Palgin HSR-Neoscrypt has now been added and is running and benchmarking correctly you can test for your self here, have also added XMRig for cryptonight
NemosMiner-v2.3 + Palgin Neoscrypt + XMRig
https://github.com/nemosminer/NemosMiner-v2.3/archive/master.zip
Tested on MiningPoolhub and Ahashpool with a 6x1070 rig (i will test it through my 6x1060 3gb and 6x1080ti rigs 2moro)
Best Regards
Nemo
Thanks, but the issue regarding wrong reported hashrate as mentioned here still persist on my end.
I think Palgin miner report wrong speed back to Nemos:P
I got reported 165Mh/s.
I think the miner itself showed 1700Kh/s when the benchmark was active.
I got reported 165Mh/s.
I think the miner itself showed 1700Kh/s when the benchmark was active.
At the moment which is better to Zpool or Ahashpool I am testing with the following scenario
:
3 1080p GPU, both of us in both zpool and ahashpool show above 30U $ but the reality is less than 25U $ what's up?
Algorithm equihash, Lyra2RE2, neoscrypt
U can add both Ahashpool and Zpool to the bat file and NemosMiner will automatically use the most profitable one. Though its gonna be Ahashpool most of the time. :
3 1080p GPU, both of us in both zpool and ahashpool show above 30U $ but the reality is less than 25U $ what's up?
Algorithm equihash, Lyra2RE2, neoscrypt
Jump to: