HSRMINER Neoscrypt Fork by Justaminer - New Version!

[katak]

Hello,

I can't make it work for Mining Rig Rental on a GTX1080, did anyone succeed ?

Thx

[Just_a_miner]

The Bitlab GUI miner now supports HSRMiner Neoscrypt.
Bitlab takes all configuration hassle away from the user and allows to start mining within seconds without ever having to edit a file.

Interesting, will take a look.

Hello,
I can't make it work for Mining Rig Rental on a GTX1080, did anyone succeed ?

Thx

Hi, what exactly doesn't work, can you provide more info?

[jdubya]

If you want to specify some of your cards, example; cards 10 and 11......-d doesn't recognize a number over 9......how do I set cards 10, 11 and 12?

[malthrax]

What are you guys mining on Neoscrypt that's even worthwhile these days?

[giveen1]

The Bitlab GUI miner now supports HSRMiner Neoscrypt.
Bitlab takes all configuration hassle away from the user and allows to start mining within seconds without ever having to edit a file.

Interesting, will take a look.

Hello,
I can't make it work for Mining Rig Rental on a GTX1080, did anyone succeed ?

Thx

Hi, what exactly doesn't work, can you provide more info?

miner client.reconnect support

https://www.miningrigrentals.com/helpcenter/Rig-Setup

Its a known issue with ccminer.

[Just_a_miner]

If you want to specify some of your cards, example; cards 10 and 11......-d doesn't recognize a number over 9......how do I set cards 10, 11 and 12?

I haven't seen any artificial limits in -d option parser, so it may be error in cuda function, that query specified video card. What kind of error does program show?

What are you guys mining on Neoscrypt that's even worthwhile these days?

I let zpool/nicehash decide what is good on neoscrypt for now as I'm very busy lately to catch coins manually Btw, nicehash profitability calculator has default equihash speed setting for 1070 card about 515 sol/s, and 1.07 mh/s for neoscrypt. With those setting it shows equihash is more profitable. But in reality even with dstm miner I get maximum 495 sol/s for equihash, but 1305 mh/s with my fork for neoscrypt - if I use these setting in nicehash calculator - it shows neoscrypt is more profitable.

[MaynardVII]

I have been using this miner over the weekend, and it's been doing much better as far as hashing and using less resources. I am using windows 10 with 12 CPU's.

My only issue is that the miner stops working. It doesn't crash, nor does the cpu lock up- the miner just blinks, and nothing happens  (but it is still running). I tried making a crash restart, but since its technically not crashing- I can't auto restart the miner.

Is there a way to have the program self-test itself and if it isn't hashing, or maybe if the GPU voltages are low- It will automatically end, or even just stop what it was doing, and start over? If it at least crashes, I can run a scrypt to restart it. but if the screen is just blinking there's really nothing I can do.

Other than that though, you did a good job, man. It seems to be much more stable than the original.

[jagauthier]

Can you set intensity from each individual card?  Will the benchmark tell me what the intensity setting should be for each card?  Can someone post a benchmark batch file example?

Thank You.

you can, you correspond -i with -d

Benchmarking just records your hash speed. The miners themselves are not adept enough to determine the intensity. You'll need to play with it a little.
No specific batch file for benching is needed, just run it and watch.

<conspiracy>
However, I feel that HSRminer's hash speed it artificially inflated, so that everyone will jump to it, and the dev's will get that 1% fee. (original, of course)
</conspiracy>

[Just_a_miner]

I have been using this miner over the weekend, and it's been doing much better as far as hashing and using less resources. I am using windows 10 with 12 CPU's.

My only issue is that the miner stops working. It doesn't crash, nor does the cpu lock up- the miner just blinks, and nothing happens  (but it is still running). I tried making a crash restart, but since its technically not crashing- I can't auto restart the miner.

Is there a way to have the program self-test itself and if it isn't hashing, or maybe if the GPU voltages are low- It will automatically end, or even just stop what it was doing, and start over? If it at least crashes, I can run a scrypt to restart it. but if the screen is just blinking there's really nothing I can do.

Other than that though, you did a good job, man. It seems to be much more stable than the original.

Thanks man. As for screen blinks - it means some of gpus reseted and dropped clocks to 2d values, either due to hardware error or to much overclocking, am I right? If that so, I think restart of the miner won't help and you will need restart rig?  Anyway - it will be very hard for me to make what you are asking right now, as temporary solution I can offer you next thing - new version will be released in a few days, it will correctly report gpu's core frequency via api, so it will be possible to monitor if some of gpus would drop core clock to low values and restart miner. Need to check AwesomeMiner, if it's capable of that.

[MaynardVII]

I have been using this miner over the weekend, and it's been doing much better as far as hashing and using less resources. I am using windows 10 with 12 CPU's.

My only issue is that the miner stops working. It doesn't crash, nor does the cpu lock up- the miner just blinks, and nothing happens  (but it is still running). I tried making a crash restart, but since its technically not crashing- I can't auto restart the miner.

Is there a way to have the program self-test itself and if it isn't hashing, or maybe if the GPU voltages are low- It will automatically end, or even just stop what it was doing, and start over? If it at least crashes, I can run a scrypt to restart it. but if the screen is just blinking there's really nothing I can do.

Other than that though, you did a good job, man. It seems to be much more stable than the original.

Thanks man. As for screen blinks - it means some of gpus reseted and dropped clocks to 2d values, either due to hardware error or to much overclocking, am I right? If that so, I think restart of the miner won't help and you will need restart rig?  Anyway - it will be very hard for me to make what you are asking right now, as temporary solution I can offer you next thing - new version will be released in a few days, it will correctly report gpu's core frequency via api, so it will be possible to monitor if some of gpus would drop core clock to low values and restart miner. Need to check AwesomeMiner, if it's capable of that.

I ended up just making some regedits to autoend the task last night if it hangs, and scheduled a .cmd task to restart the miner every hour in case that fails. It seems to be stable so far, at least if its crashing- I can't see it yet. I haven't sat in front of it to check the logs.

That update sounds good, thanks.

[ElMinator]

What W10 build / NVIDIA drivers combo are you using to run this miner?. I keep getting error 43 on some cards

[MaynardVII]

What W10 build / NVIDIA drivers combo are you using to run this miner?. I keep getting error 43 on some cards

I'm using latest drivers and no issues (390.77 package). I noticed actually the latest drivers boost 1070's, but drag 1050 ti's. This seemed to fix that drag with the 1050 ti. I'm getting about what I should get when running with normal settings (I normally OC though).

[ElMinator]

How many GPU u got?

[car1999]

will try this miner, which pool do u use?

[cyberdeath]

There is a bug same as in hsr miner.
It does not support multi gpu mining, when gpu's more than 15
Example: i've choosen to mine with device number 10 but miner understood 10 as device number 0
And when i try to use only device with number 12 i get the following error
INFO : [08:30:55] : Wrong CUDA device GPU#'12' specified in -d option
When try 11 device error is  Wrong CUDA device GPU#'11' specified in -d option
https://s9.postimg.org/izcx757sf/10-0b.png



Here are my devices
GPU #0: SM 6.1 P104-100
GPU #1: SM 6.1 Gigabyte GTX 1080 Ti
GPU #2: SM 6.1 Gigabyte GTX 1080 Ti
GPU #3: SM 6.1 MSI GTX 1080
GPU #4: SM 6.1 Gigabyte GTX 1080 Ti
GPU #5: SM 6.1 MSI GTX 1080
GPU #6: SM 6.1 MSI GTX 1080
GPU #7: SM 6.1 P104-100
GPU #8: SM 6.1 Gigabyte GTX 1080 Ti
GPU #9: SM 6.1 MSI GTX 1080
GPU #10: SM 6.1 MSI GTX 1080
GPU #11: SM 6.1 P104-100
GPU #12: SM 6.1 P104-100
GPU #13: SM 6.1 P104-100
GPU #14: SM 6.1 Gigabyte GTX 1080 Ti
GPU #15: SM 6.1 P104-100

[ElMinator]

There is a bug same as in hsr miner.
It does not support multi gpu mining, when gpu's more than 15
Example: i've choosen to mine with device number 10 but miner understood 10 as device number 0
And when i try to use only device with number 12 i get the following error
INFO : [08:30:55] : Wrong CUDA device GPU#'12' specified in -d option
When try 11 device error is  Wrong CUDA device GPU#'11' specified in -d option
https://s9.postimg.org/izcx757sf/10-0b.png



Here are my devices
GPU #0: SM 6.1 P104-100
GPU #1: SM 6.1 Gigabyte GTX 1080 Ti
GPU #2: SM 6.1 Gigabyte GTX 1080 Ti
GPU #3: SM 6.1 MSI GTX 1080
GPU #4: SM 6.1 Gigabyte GTX 1080 Ti
GPU #5: SM 6.1 MSI GTX 1080
GPU #6: SM 6.1 MSI GTX 1080
GPU #7: SM 6.1 P104-100
GPU #8: SM 6.1 Gigabyte GTX 1080 Ti
GPU #9: SM 6.1 MSI GTX 1080
GPU #10: SM 6.1 MSI GTX 1080
GPU #11: SM 6.1 P104-100
GPU #12: SM 6.1 P104-100
GPU #13: SM 6.1 P104-100
GPU #14: SM 6.1 Gigabyte GTX 1080 Ti
GPU #15: SM 6.1 P104-100

What W10 build and NVIDIA driver are you using?

[cyberdeath]

OS Name:                   Microsoft Windows Server 2016 Standard
OS Version:                10.0.14393 N/A Build 14393

video 390.77

ccminer 2.2.4 works fine in the same config (16gpu's), ccminer does not work correctly with 17+ cards

[ElMinator]

OS Name:                   Microsoft Windows Server 2016 Standard
OS Version:                10.0.14393 N/A Build 14393

video 390.77

ccminer 2.2.4 works fine in the same config (16gpu's), ccminer does not work correctly with 17+ cards

Why server version?

[cyberdeath]

any difference? more stable

[ElMinator]

any difference? more stable

Have you tried upgrading to the latest version?