HSRMINER Neoscrypt Fork by Justaminer - New Version!

[MinerMinor]

Windows 10 1709 (build 16299.248)
3x nVidia 1070 Ti @ 100% PL, +200 core, +700 memory
Biostar 250-BTC
4gb ram
80gb page file

With 388 this worked just fine with no errors.

Jumping to 390 this causes errors. Even at 70% PL same thing. I had to drop it down to 50% and only then it would not cause that error. So I downgraded back to 388 drivers and run at 100% PL right now until we can debug it?

[1715660799]

1715660799

[1715660799]

1715660799

[1715660799]

1715660799

[Bluecheese]

Are you going to let us make changes to the intensity?  I see some of my cards tops out at 16.5.

-i 7 = 16.5 Intensity

OR are you using this as what say, "-i 7 = use as much of the VRAM as possible"

All in all, I like what you and your team has done.  Thanks to you all my GPUs are full and digging away.  Can't wait to see what else you can do.

HSR is also supported by this software?

[Zackdaystar]

Still crashing for me.

Code:

hsrminer_neoscrypt_fork.exe -a neoscrypt -o stratum+tcp://hub.miningpoolhub.com:17012 -u Zackdaystar.miner1 -p x

              888888ba           oo       dP oo
              88    `8b                   88
              88     88 dP   .dP dP .d888b88 dP .d8888b.
              88     88 88   d8' 88 88'  `88 88 88'  `88     888888b                   8P   dP
              88     88 88 .88'  88 88.  .88 88 88.  .88     88      .d8888b. 88d888b. 88  d8
              dP     dP 8888P'   dP `88888P8 dP `88888P8     888888  88'  `88 88'  `88 88d88
                                                             88      88.  .88 88       88  d8
                                                             dP      `88888P' dP       8P   dP
  dP                                    oo
  88
  88d888b. .d8888b. 88d888b. 88d8b.d8b. dP 88d888b. .d8888b. 88d888b.
  88'  `88 Y8ooooo. 88'  `88 88'`88'`88 88 88'  `88 88ooood8 88'  `88
  88    88       88 88       88  88  88 88 88    88 88.  ... 88
  dP    dP `88888P' dP       dP  dP  dP dP dP    dP `88888P' dP

                                                             https://github.com/justaminer/hsrm-fork
****************************************************************************************************
 NVIDIA hsrminer 1.0.1+ for Neoscrypt forked of palgin by Justaminer.    Fork's version: 25.02.2018
****************************************************************************************************
 Fork contains 0% devfee, working API and -r option, enjoy! ( run with -h to see all new options! )
****************************************************************************************************

 INFO : [10:31:23] : POOL: stratum+tcp://hub.miningpoolhub.com:17012
 INFO : [10:31:23] : Checking for NVML...
 INFO : [10:31:23] : NVML monitoring enabled, continue...
 INFO : [10:31:23] : 1 GPU found/specified, initializing miner...
 INFO : [10:31:24] : Share difficulty reset -- 32 (0.00049)

and this in the event logs

Code:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2018-02-25T10:22:28.322310500Z" /> 
  <EventRecordID>59361</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>black-gold</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>hsrminer_neoscrypt.exe</Data> 
  <Data>1.0.1.0</Data> 
  <Data>5a47af32</Data> 
  <Data>hsrminer_neoscrypt.exe</Data> 
  <Data>1.0.1.0</Data> 
  <Data>5a47af32</Data> 
  <Data>c0000005</Data> 
  <Data>000000000012e349</Data> 
  <Data>2248</Data> 
  <Data>01d3ae228741f3ac</Data> 
  <Data>C:\MultiPoolMinerV2\Bin\NeoScrypt-Palgin\hsrminer_neoscrypt.exe</Data> 
  <Data>C:\MultiPoolMinerV2\Bin\NeoScrypt-Palgin\hsrminer_neoscrypt.exe</Data> 
  <Data>88576d72-a9a0-40c7-9172-385945a73237</Data> 
  <Data /> 
  <Data /> 
  </EventData>
  </Event>

[quato]

Testing last version from 25.02.2018

INFO : [14:23:16] : GPU#0 - ASUS GTX 1070, speed is 829.04kH/s
INFO : [14:23:16] : GPU#4 - Gigabyte GTX 980, speed is 696.24kH/s
INFO : [14:23:16] : GPU#7 - Gigabyte GTX 1070, speed is 1108.09kH/s
INFO : [14:23:16] : GPU#8 - Zotac GTX 980 Ti, speed is 820.14kH/s
INFO : [14:23:16] : GPU#9 - Gigabyte GTX 1070, speed is 1110.91kH/s

INFO : [14:38:15] : Share Accepted, overall speed is 4541.39kH/s, efficiency 100.00%

70-80 PL, +100 Core, +400 Memory

Windows 10 v1703
Video Driver: 390.65
GPUS:
Asus GTX 1070 - Expedition
2x Gigabyte GTX 1070 - Gaming 1
Gigabyte GTX 980 - Windforce 3x
Zotac GTX 980Ti - AMP! Edition

Tested with default intensity and increased priority version. I can benchmark full rig from 11 cards - 4x1050Ti, 2x1060-6Gb, 3x1070, 1x980, 1x980Ti, if anybody want it.

[Just_a_miner]

Windows 10 1709 (build 16299.248)
3x nVidia 1070 Ti @ 100% PL, +200 core, +700 memory
Biostar 250-BTC
4gb ram
80gb page file

With 388 this worked just fine with no errors.

Jumping to 390 this causes errors. Even at 70% PL same thing. I had to drop it down to 50% and only then it would not cause that error. So I downgraded back to 388 drivers and run at 100% PL right now until we can debug it?

I don't know if I will be able to debug such problem. Don't you think that +200 core + 700 mem is too much for your gpu? Have you tried to reduce overclocking with 390.77 drivers?

[Just_a_miner]

Are you going to let us make changes to the intensity?  I see some of my cards tops out at 16.5.

-i 7 = 16.5 Intensity

OR are you using this as what say, "-i 7 = use as much of the VRAM as possible"

All in all, I like what you and your team has done.  Thanks to you all my GPUs are full and digging away.  Can't wait to see what else you can do.

HSR is also supported by this software?

Current version doesn't allow to change intensity with --benchmark, i.e. even if you specify -i N, it will be reset to defaults anyway before benchmark - it's default behavior of hsrminer. I will change that with the next release, so you will be able to actually change it and see effect with --benchmark.

Default intensity for 9xx GPU right now is 16.1, I've tried to change it, doesn't have much effect, but you can try anyway. For 970 you have to watch out not to cross 3.5 gb memory limit, or GPU will hash very very slow, use tools like GPU-Z to see video memory usage.

There is no team, I'm doing all the work myself. This is neoscrypt only software.

[Just_a_miner]

Still crashing for me.

Do you have Titan XP? It will be supported with the next release.

[Just_a_miner]

Testing last version from 25.02.2018

INFO : [14:23:16] : GPU#0 - ASUS GTX 1070, speed is 829.04kH/s
INFO : [14:23:16] : GPU#4 - Gigabyte GTX 980, speed is 696.24kH/s
INFO : [14:23:16] : GPU#7 - Gigabyte GTX 1070, speed is 1108.09kH/s
INFO : [14:23:16] : GPU#8 - Zotac GTX 980 Ti, speed is 820.14kH/s
INFO : [14:23:16] : GPU#9 - Gigabyte GTX 1070, speed is 1110.91kH/s

INFO : [14:38:15] : Share Accepted, overall speed is 4541.39kH/s, efficiency 100.00%

70-80 PL, +100 Core, +400 Memory

Windows 10 v1703
Video Driver: 390.65
GPUS:
Asus GTX 1070 - Expedition
2x Gigabyte GTX 1070 - Gaming 1
Gigabyte GTX 980 - Windforce 3x
Zotac GTX 980Ti - AMP! Edition

Tested with default intensity and increased priority version. I can benchmark full rig from 11 cards - 4x1050Ti, 2x1060-6Gb, 3x1070, 1x980, 1x980Ti, if anybody want it.

Thanks for the info, what's the problem with GPU#0 - ASUS GTX 1070, speed is 829.04kH/s ? Is it downclocked or you've been using it during benchmark?

[quato]

Thanks for the info, what's the problem with GPU#0 - ASUS GTX 1070, speed is 829.04kH/s ? Is it downclocked or you've been using it during benchmark?

It was Power Limited to 65% (and power consumption around 90W), and core clock was at 1200-1400 MHz, now I set PL to 85%, and Core +150.
Now core shows 1620 Mhz, hasrate is 1146kH/s an power consumption is 110-115W for this card.

Have an another RIG with 4x1070 Asus Strix with PL 90 and core/mem +100/+400 the result is overall around 4950 kH/s, and for each card hashrate is around 1230-1280 kH/s (with power draw at 128-133W for each)

[cirlama]

Hi and thanks to the devs (old & new),
my GTX 1070 tops at 1200 kh/s core +120, mem +500 and pw 100%, latest version & latest nvidia drivers, both normal and priority version, no way to come close to 1322/1365 as shown in benchmarks page 1, unless I have to downgrade the nvidia driver?

for info, my 1080ti gives 1950 kh/s core +120, mem +500 and pw 100%, while latest excavator gives 2050 kh/s

[Just_a_miner]

Thanks for the info, what's the problem with GPU#0 - ASUS GTX 1070, speed is 829.04kH/s ? Is it downclocked or you've been using it during benchmark?

It was Power Limited to 65% (and power consumption around 90W), and core clock was at 1200-1400 MHz, now I set PL to 85%, and Core +150.
Now core shows 1620 Mhz, hasrate is 1146kH/s an power consumption is 110-115W for this card.

Have an another RIG with 4x1070 Asus Strix with PL 90 and core/mem +100/+400 the result is overall around 4950 kH/s, and for each card hashrate is around 1230-1280 kH/s (with power draw at 128-133W for each)

I see. You did right when increased PL, for neoscrypt algo you should not decrease PL too much, it's not ethash, and require more compute power.
My MSI GTX 1070 Gaming X with PL 90%, +100 core and + 400 mem hash at ~ 1350+ kh/s with power draw at 180-190W. I can OC it to higher values with PL 100%+ and get 1400+ hashrate, but it would eat 220W+, so no point.

[Just_a_miner]

Hi and thanks to the devs (old & new),
my GTX 1070 tops at 1200 kh/s core +120, mem +500 and pw 100%, latest version & latest nvidia drivers, both normal and priority version, no way to come close to 1322/1365 as shown in benchmarks page 1, unless I have to downgrade the nvidia driver?

for info, my 1080ti gives 1950 kh/s core +120, mem +500 and pw 100%, while latest excavator gives 2050 kh/s

You can use excavator for 1080ti card and my miner for others. In future I will try to improve performance of 1080ti.

About benchmark results - benchmark was done with MSI GTX 1070 Gaming X, at specified OC settings it had 2025 mhz core and 4200 mhz mem - it's high values and not every 1070 gpu can reach it, that's why results are high.

[cirlama]

Hi and thanks to the devs (old & new),
my GTX 1070 tops at 1200 kh/s core +120, mem +500 and pw 100%, latest version & latest nvidia drivers, both normal and priority version, no way to come close to 1322/1365 as shown in benchmarks page 1, unless I have to downgrade the nvidia driver?

for info, my 1080ti gives 1950 kh/s core +120, mem +500 and pw 100%, while latest excavator gives 2050 kh/s

You can use excavator for 1080ti card and my miner for others. In future I will try to improve performance of 1080ti.

About benchmark results - benchmark was done with MSI GTX 1070 Gaming X, at specified OC settings it had 2025 mhz core and 4200 mhz mem - it's high values and not every 1070 gpu can reach it, that's why results are high.

thanks for the answer, it's true that 2025 core is high, my 1070 is fluctuating around 1900 (with mem at 4300), can go higher but I am not sure it's worth it

[andrewpuzoff]

Have anybody tested latest version with GTX 980 and 980 Ti ?

it works... for a while.

https://hostingkartinok.com/show-image.php?id=4b03a731dabe0c26f9c3375670d552bc

[jugger1028]

I know a couple of people that are waiting for the Titan update to try it on their cards.

[Just_a_miner]

Have anybody tested latest version with GTX 980 and 980 Ti ?

it works... for a while.

720 kh/s for good old MSI GTX 970? Not bad

I know a couple of people that are waiting for the Titan update to try it on their cards.

I'm working on it, new version will be released in two days or so.

[Just_a_miner]

You know the best thing about this thread is your AutoIt script, right?


I love the thing!

Thanks!

Enjoy! 

Got a question though... Your script does not attempt to reconnect to the main pool automatically so it will keep mining on the "failover" until it crashes.
Is there a way you could implement an automatic reconnection attempt to pool 1, say, every 15min? I'm useless at coding otherwise I'd gladly try to do it myself...

Take a look, I've implemented what you have been asking for - miners_autorun_fp.zip

Pool 0 is always main pool, all other pools are failover pools. You can change failover timelimit, default is 15 minutes.

Brilliant! Thanks!
I'll give it a whirl asap and let you and others know in here if it works as intended!

Mike, I'm starting to worry, are you ok man? 

[dragonmike]

You know the best thing about this thread is your AutoIt script, right?


I love the thing!

Thanks!

Enjoy! 

Got a question though... Your script does not attempt to reconnect to the main pool automatically so it will keep mining on the "failover" until it crashes.
Is there a way you could implement an automatic reconnection attempt to pool 1, say, every 15min? I'm useless at coding otherwise I'd gladly try to do it myself...

Take a look, I've implemented what you have been asking for - miners_autorun_fp.zip

Pool 0 is always main pool, all other pools are failover pools. You can change failover timelimit, default is 15 minutes.

Brilliant! Thanks!
I'll give it a whirl asap and let you and others know in here if it works as intended!

Mike, I'm starting to worry, are you ok man? 

Ha!
Doing absolutely fine. Had to take the rig offline for 36 hours for external reasons, but it's been hashing fine since yesterday midday. I saw it switch to secondary pool twice, and went automatically back on to the main pool a few minutes later (I left the 15min default "switch-back" delay as you set it).

Bottomline: it works like a charm! Many thanks!
[insert dragonmike seal of approval here]

[Just_a_miner]

Ha!
Doing absolutely fine. Had to take the rig offline for 36 hours for external reasons, but it's been hashing fine since yesterday midday. I saw it switch to secondary pool twice, and went automatically back on to the main pool a few minutes later (I left the 15min default "switch-back" delay as you set it).

Bottomline: it works like a charm! Many thanks!
[insert dragonmike seal of approval here]

Very good! You are welcome! 

[MinerMinor]

Windows 10 1709 (build 16299.248)
3x nVidia 1070 Ti @ 100% PL, +200 core, +700 memory
Biostar 250-BTC
4gb ram
80gb page file

With 388 this worked just fine with no errors.

Jumping to 390 this causes errors. Even at 70% PL same thing. I had to drop it down to 50% and only then it would not cause that error. So I downgraded back to 388 drivers and run at 100% PL right now until we can debug it?

I don't know if I will be able to debug such problem. Don't you think that +200 core + 700 mem is too much for your gpu? Have you tried to reduce overclocking with 390.77 drivers?

I dropped it down to +400 memory (like you have yours I believe?) and it's working okay without any hashrate penalty. I am still on the 388 drivers though. +700 worked okay for all other algoths/miners before. Will eventually upgrade drivers again I suppose. Until then thanks and keep up the great work!

4,190 hashrate for 3x 1070 Ti at 100% PL, +200 core, +400 memory