[NemosMiner] multi algo profit switching NVIDIA/CPU miner

[primo1983]

I noticed this screen that is attached, so I understand he is stopping my mining and back some minutes later, is that a problem?

Well I realized that in 24 hours you are saying that I get 45 U $ but the reality is 25 U $ I do not know if the cause can be this screen
https://prnt.sc/i0hl4z

[millsys]

I noticed this screen that is attached, so I understand he is stopping my mining and back some minutes later, is that a problem?

Well I realized that in 24 hours you are saying that I get 45 U $ but the reality is 25 U $ I do not know if the cause can be this screen

you are missing a SPACE -i

modify CcminerKlaust.ps1
"neoscrypt" = " -i 15 -d $SelGPUCC" #NeoScrypt

[primo1983]

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

[yashart]

Anyone know what might cause the reject rate to increase so drastically? I am seeing 27% rejection rate... Not entirely sure why though.  

[minerx117]

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.

Same here....benchmark PalginHSR doesn't stop.

Temporary solution would be is to create PalginHSR_NeoScrypt_HashRate.txt file in stats folder, input there whatever hashrate u had and make it read only.
for example 1.4 mhs

Code:

{
    "Live":  1412920,
    "Minute":  1412920,
    "Minute_Fluctuation":  0,
    "Minute_5":  1412920,
    "Minute_5_Fluctuation":  0,
    "Minute_10":  1412920,
    "Minute_10_Fluctuation":  0,
    "Hour":  1412920,
    "Hour_Fluctuation":  0,
    "Day":  1412920,
    "Day_Fluctuation":  0,
    "Week":  1412920,
    "Week_Fluctuation":  0,
    "Updated":  "\/Date(1515611652775)\/"
}

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

 

[cryptomoblo]

hi Nemosminers,

I'm running a 6x 1070 rig for 1,5 week now. And my rig keeps crashing once or twice a day, seems to happen when its running the x17 algo.

Powerlevel is set to 85, with 200 mem overclock in MSI afterburner.

 I already lowered the intensity from 21 to 19. Virtual memory minimum is 16000 max 64000. Still not stable. Any thoughts what to do?

EDIT: Actually seems to crash on other algo's as well. Just tested with neoscrypt. Will try running with everything on stock settings.

[bk2000]

Great tool so far - really like the stability too.  Less crashes than with other mining programs. 

Question - any thoughts of adding CPU algos?  I run cpuminer on the side to squeeze a few extra dollars / month out - would be nice to integrate into nemosminer!

[goldren]

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

 

Oh my!!! i am really rich! =)

https://i.imgur.com/POVjMwM.jpg

[primo1983]

how do I mine comment 0.008 in ashpool, since I want to change pool after giving 0.008, is there any configuration for this

[Lubrifiant]

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.

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

 

Thank you for your job.

Your miner works fine here on multiple GTX 1080 ti.
I just registered here to thank you !

[cable_loco]

Enhancement request:

Please add support for Excavator
https://github.com/MultiPoolMiner/MultiPoolMiner/blob/master/Miners/ExcavatorNvidia1.ps1

Please add support for FireiceNvidia
https://github.com/MultiPoolMiner/MultiPoolMiner/blob/master/Miners/FireiceNvidia.ps1

Thanks !

[micha_b]

I have several ASICs running and control them via Awesome Miner. The GUI gives me a good overview over Temps, Algos and Earnings.
For all Rigs I use Nemosminer.

Is there a possibility to track Nemosminer via Awesome Miner? At the moment I have to view each Rig via teamviewer one after the other to get all these information.

@Nemo: Good work, clean and efficient. Already put my donate to 10.

[dragonmike]

hi Nemosminers,

I'm running a 6x 1070 rig for 1,5 week now. And my rig keeps crashing once or twice a day, seems to happen when its running the x17 algo.

Powerlevel is set to 85, with 200 mem overclock in MSI afterburner.

 I already lowered the intensity from 21 to 19. Virtual memory minimum is 16000 max 64000. Still not stable. Any thoughts what to do?

EDIT: Actually seems to crash on other algo's as well. Just tested with neoscrypt. Will try running with everything on stock settings.

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.

[newgameos]

hi Nemosminers,

I'm running a 6x 1070 rig for 1,5 week now. And my rig keeps crashing once or twice a day, seems to happen when its running the x17 algo.

Powerlevel is set to 85, with 200 mem overclock in MSI afterburner.

 I already lowered the intensity from 21 to 19. Virtual memory minimum is 16000 max 64000. Still not stable. Any thoughts what to do?

EDIT: Actually seems to crash on other algo's as well. Just tested with neoscrypt. Will try running with everything on stock settings.

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.

Having the same problem - sometimes all algos working ok, but most of the time neoscrypt, x17 and nist5 are crashing within one minute, and when i have interval set to 900 for the next 13-14 minutes nothing is mining. At this moment i'm trying older versions of nemosminer, and at version 2.3 disabled that 3 algos (but it's a shame because mostly x17 is most profitable)

[cryptomoblo]

hi Nemosminers,

I'm running a 6x 1070 rig for 1,5 week now. And my rig keeps crashing once or twice a day, seems to happen when its running the x17 algo.

Powerlevel is set to 85, with 200 mem overclock in MSI afterburner.

 I already lowered the intensity from 21 to 19. Virtual memory minimum is 16000 max 64000. Still not stable. Any thoughts what to do?

EDIT: Actually seems to crash on other algo's as well. Just tested with neoscrypt. Will try running with everything on stock settings.

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.

Having the same problem - sometimes all algos working ok, but most of the time neoscrypt, x17 and nist5 are crashing within one minute, and when i have interval set to 900 for the next 13-14 minutes nothing is mining. At this moment i'm trying older versions of nemosminer, and at version 2.3 disabled that 3 algos (but it's a shame because mostly x17 is most profitable)

When I hooked my Rig up to a monitor again I would notice the BSOD's stating TDR failure. I have removed my videocard drivers and reinstalled version 388.71. No overclocking or adjusted powerlimit.

So far no crash but I have no hopes yet, should run few days without crashes before I can be really happy. Running 8 hours now on all algo's. On my gaming pc with single gtx 1070 nemosminer is running fine for weeks without changing any settings at all. Multi GPU mining seems to be a complete different world.

[BitBustah]

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.

[micha_b]

It would be very helpful if Nemosminer could check the number of accepted shares and in case of no change after one or two minutes switch to the second best algo for the Rest of the interval.

[carlcapone]

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).

[primo1983]

Option to limit mining for example to ahashpool the minimum of it is 0.008 how not to let mine more than 0.008?

[Traz27]

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.