Quote from: Mr.Spider703 on January 31, 2018, 12:34:13 AM

Quote from: niehues313 on January 31, 2018, 12:28:19 AM

Hello.

Any ideia what this error can be:

Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1460 : the launch timed out and was terminated.
Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1464 : the launch timed out and was terminated.
Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1464 : the launch timed out and was terminated.
Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1464 : the launch timed out and was terminated.
Cuda error in func 'neoscrypt_cpu_hash_1070' at line 1460 : the launch timed out and was terminated.

Closed program.

Thanks !

overclock what is it worth? PL?

Quote from: EVERYUSERNAMEISTAKEN on January 31, 2018, 12:14:12 AM

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

~11hr (~6.75h to ~16.25h on the graph) test for hsrminer on Nemosminer.

Ignore the rollercoaster at the 5h mark, I was playing around with settings. The drop at 17h is a result of a 30min internet outage, this screws up the following moving average.

As you might be able to see, the relevant moving average is about 2820-2880kh. I'd say it's closer to a 2850-2860kh average if you hover above the data points. This is server-side on AHP24h (pure Neoscrypt). Client-side, I'm averaging 2930-2950kh.

So where'd the extra 100kh go? Take into account a 1% fee and that leaves us at 2900-2920kh. From here we're still missing a bit. I'm going to assume AHP takes the 1% from your actual profits, and doesn't just cut your hash rate accordingly. The only logical explanation is my 99% efficiency, which would take us to 2871-2890kh. Still missing 10-20kh, but in the grand scheme of things, that's pretty negligible. I've seen a lot of people claim hsrminer doesn't deliver the promised client-side numbers, but my experience differs. I'm not trying to discredit any claims, but I would encourage everyone to try it and see whether it works for them.

Stats in the Powershell window are fairly accurate, may be the 1070Ti should be closer to ~142w.

Specifics:

1070Ti @ 85% TDP, 80c target, +200 core, +400 memory (may be I should clock this down too), ~58c @ 65% fan
1080Ti @ 85% TDP, 80c target, +190 core, +100 memory (+300 mem didn't really help for me in Neo), ~52c @ 85% fan

Ambient temp is ~21-22c.

All in all, I'm much more concerned about my Blake2s hashrates being quite different from what I'm getting client-side.

in blake2s 12 Gh/s on 3*1060 (PL 75, mem 550, core 150) & 1*1080 (PL 75, mem 0, core 0) 10 min working and closed

I was doing 100% PL, 0 overclock, 90% fan speed.
Now i'm trying 90% PL, 0 overclock, 90% fan speed.

It ran for about an hour before the reported crash.