HSRMINER Neoscrypt Fork by Justaminer - New Version!

[dragonmike]

I have another problem now though...

After updating the rig to the fall creator's update - and new nVidia drivers 391.01 I lost 25% hashrate (from 1350 to 1040 kH/s). I have been running the high priority miner, using parameters -i 5 -c 4. I also now seem to get a lot of "Share rejected, invalid job ID" messages. No idea if related or what's going on. Any ideas?

[dragonmike]

I have another problem now though...

After updating the rig to the fall creator's update - and new nVidia drivers 391.01 I lost 25% hashrate (from 1350 to 1040 kH/s). I have been running the high priority miner, using parameters -i 5 -c 4. I also now seem to get a lot of "Share rejected, invalid job ID" messages. No idea if related or what's going on. Any ideas?

HODL your horses, my mistake.
I had forgotten to switch back to forcing P0 state.

All good, back to good ol'speeds.

[MinerMinor]

I have another problem now though...

After updating the rig to the fall creator's update - and new nVidia drivers 391.01 I lost 25% hashrate (from 1350 to 1040 kH/s). I have been running the high priority miner, using parameters -i 5 -c 4. I also now seem to get a lot of "Share rejected, invalid job ID" messages. No idea if related or what's going on. Any ideas?

HODL your horses, my mistake.
I had forgotten to switch back to forcing P0 state.

All good, back to good ol'speeds.

How do you force p0 state? And does this affect 1070 Ti's too?

[giveen1]

I have another problem now though...

After updating the rig to the fall creator's update - and new nVidia drivers 391.01 I lost 25% hashrate (from 1350 to 1040 kH/s). I have been running the high priority miner, using parameters -i 5 -c 4. I also now seem to get a lot of "Share rejected, invalid job ID" messages. No idea if related or what's going on. Any ideas?

HODL your horses, my mistake.
I had forgotten to switch back to forcing P0 state.

All good, back to good ol'speeds.

How do you force p0 state? And does this affect 1070 Ti's too?

Nvidia Profile Inspector and turn P0 to OFF

[dragonmike]

I have another problem now though...

After updating the rig to the fall creator's update - and new nVidia drivers 391.01 I lost 25% hashrate (from 1350 to 1040 kH/s). I have been running the high priority miner, using parameters -i 5 -c 4. I also now seem to get a lot of "Share rejected, invalid job ID" messages. No idea if related or what's going on. Any ideas?

HODL your horses, my mistake.
I had forgotten to switch back to forcing P0 state.

All good, back to good ol'speeds.

How do you force p0 state? And does this affect 1070 Ti's too?

Nvidia Profile Inspector and turn P0 to OFF

...or rather "force P2 state" to OFF.

[MinerMinor]

Interesting. I set it to OFF and yet under the GUI it still shows P2. Any idea?

http://img.techpowerup.org/180226/nvidia-20180226-142516.png

[Just_a_miner]

I have another problem now though...

After updating the rig to the fall creator's update - and new nVidia drivers 391.01 I lost 25% hashrate (from 1350 to 1040 kH/s). I have been running the high priority miner, using parameters -i 5 -c 4. I also now seem to get a lot of "Share rejected, invalid job ID" messages. No idea if related or what's going on. Any ideas?

By the way, when you specify any intensity below or equal 7 - miner will use default intensity anyway, so there is no point to use -i 5. Also if you are running high priority miner, it has -c 4 by default, so you also don't need to use this option.

[Rocstar]

Hey Just_a_miner, wondering if you know what's causing my HSR miner to crash. It happened on the original one and the same thing happens on your forked version. I'm running two mining rigs and one runs sweet, but the other always crashes after a few mintes with this error

'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.

The rig is running 6 Gigabyte gtx 1080 ti Aorus Waterforce video cards. I'm not doing any overclocking and have turned power down to 80%

It makes mining neoscrypt pointless. I'd really appreciate it if you could help.

[mirny]

Interesting. I set it to OFF and yet under the GUI it still shows P2. Any idea?

press apply

[the Great Orchid]

i like this is great is use it no problemo

guess that other guy has no worrys now lol

keep it alive 

[dragonmike]

I have another problem now though...

After updating the rig to the fall creator's update - and new nVidia drivers 391.01 I lost 25% hashrate (from 1350 to 1040 kH/s). I have been running the high priority miner, using parameters -i 5 -c 4. I also now seem to get a lot of "Share rejected, invalid job ID" messages. No idea if related or what's going on. Any ideas?

By the way, when you specify any intensity below or equal 7 - miner will use default intensity anyway, so there is no point to use -i 5. Also if you are running high priority miner, it has -c 4 by default, so you also don't need to use this option.

Thanks for the colour. Have you got a bit more detail on the intensity levels that can be set (and their impact/relation to GPU mem)? Every miner use different intensity parameters...

EDIT: also, I tried your failover script with another miner but then realised you were using parameters only supported by your fork of hsrminer (-r, -R). Too bad, I'd have loved to be able to use your script with DSTM's equihash miner, or any random ccminer out there...

[Just_a_miner]

New version!

See 1st msg of the topic - added support for Titan XP, Titan V, Titan X (Pascal), GTX 950, GTX 960. Fork now contains 1 minute per hour devfee, which is still lower than 70 seconds per hour of original hsrminer.

[Just_a_miner]

Hey Just_a_miner, wondering if you know what's causing my HSR miner to crash. It happened on the original one and the same thing happens on your forked version. I'm running two mining rigs and one runs sweet, but the other always crashes after a few mintes with this error

'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.

The rig is running 6 Gigabyte gtx 1080 ti Aorus Waterforce video cards. I'm not doing any overclocking and have turned power down to 80%

It makes mining neoscrypt pointless. I'd really appreciate it if you could help.

Hi, hard to say what's the problem for now, I will take a look.

Thanks for the colour. Have you got a bit more detail on the intensity levels that can be set (and their impact/relation to GPU mem)? Every miner use different intensity parameters...

EDIT: also, I tried your failover script with another miner but then realised you were using parameters only supported by your fork of hsrminer (-r, -R). Too bad, I'd have loved to be able to use your script with DSTM's equihash miner, or any random ccminer out there...

What gpu type are you trying to tweak?

As for script, you can specify any parameter you want instead of -r, just edit the .au3, for dstm it would be like:

Code:

$cmdlineArray[0]="--server SERVER --port PORT --user ADDRESS.WORKER --time --noreconnect"

[dragonmike]

Thanks for the colour. Have you got a bit more detail on the intensity levels that can be set (and their impact/relation to GPU mem)? Every miner use different intensity parameters...

EDIT: also, I tried your failover script with another miner but then realised you were using parameters only supported by your fork of hsrminer (-r, -R). Too bad, I'd have loved to be able to use your script with DSTM's equihash miner, or any random ccminer out there...

What gpu type are you trying to tweak?

As for script, you can specify any parameter you want instead of -r, just edit the .au3, for dstm it would be like:

Code:

$cmdlineArray[0]="--server SERVER --port PORT --user ADDRESS.WORKER --time --noreconnect"

I'm trying to extract the most out of a handful of GTX 1080's!

Hmm, ok, thx for that, I'll give it a go. What is the difference between -r and -R by the way (as you got both in your line)?

[giveen1]

 
~  Added 1 minute per hour devfee.


Enjoy!

I really dont mind paying dev fee's. I'm just amused that this was one of the things you raged about with the original one from plagin.

I do understand that you are actually improving it with your fork. 1.6% dev isn't bad.

[Just_a_miner]

Thanks for the colour. Have you got a bit more detail on the intensity levels that can be set (and their impact/relation to GPU mem)? Every miner use different intensity parameters...

EDIT: also, I tried your failover script with another miner but then realised you were using parameters only supported by your fork of hsrminer (-r, -R). Too bad, I'd have loved to be able to use your script with DSTM's equihash miner, or any random ccminer out there...

What gpu type are you trying to tweak?

As for script, you can specify any parameter you want instead of -r, just edit the .au3, for dstm it would be like:

Code:

$cmdlineArray[0]="--server SERVER --port PORT --user ADDRESS.WORKER --time --noreconnect"

I'm trying to extract the most out of a handful of GTX 1080's!

Hmm, ok, thx for that, I'll give it a go. What is the difference between -r and -R by the way (as you got both in your line)?

-r N is a number of reconnection attempts in case of connection failure. -R N is pause in seconds before trying another connection attempt. Default value is 10 seconds, that is high value, so you can tweak it with -R

[Just_a_miner]

 
~  Added 1 minute per hour devfee.


Enjoy!

I really dont mind paying dev fee's. I'm just amused that this was one of the things you raged about with the original one from plagin.

I do understand that you are actually improving it with your fork. 1.6% dev isn't bad.

This is not correct, first post was like that:

Are you mad at Hsrminer_Neoscrypt because it tries to connect to dead pools for several hours, making your farms waste time and profits?
So am i, because i'm just another miner like you, and i want my rigs to work 24/7!

And here is my solution:

This is fork of Hsrminer for Neoscrypt miner.
....

Main problem that was bothering me was not devfee, but exactly lack of -r option, because of that miner was unreliable. Once I woke up in the morning and checked farm's status - all rigs with hsrminer were chilling, doing nothing because pool was dead for like 4 or 6 hours. That's what make me mad and motivated to solve this problem.

[Just_a_miner]

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

Titan XP, Titan V, Titan X (Pascal) is now supported (later two would probably require some additional tweaking as it was done for 970+ GPUs).

[Just_a_miner]

One more major issue. It won't run at all with Titan XP cards. My 1080ti rig works fine, but TitanXP just ends the program. The original HSRminer had a similar issue. No idea why, TitanXP=fully enabled 1080TI (with 12gb vs 11 and no crippled SM).

Try new version, Titan XP should work now.

[Just_a_miner]

Hey Just_a_miner, wondering if you know what's causing my HSR miner to crash. It happened on the original one and the same thing happens on your forked version. I'm running two mining rigs and one runs sweet, but the other always crashes after a few mintes with this error

'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.

The rig is running 6 Gigabyte gtx 1080 ti Aorus Waterforce video cards. I'm not doing any overclocking and have turned power down to 80%

It makes mining neoscrypt pointless. I'd really appreciate it if you could help.

I need some more info, you can PM me screenshot of error. Or at least describe how it happens - are there any accepted shares before error?