Quote from: Rocstar on February 28, 2018, 12:13:32 PM

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.

Quote from: dragonmike on February 28, 2018, 04:39:54 PM

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

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"