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.
Topic: HSRMINER Neoscrypt Fork by Justaminer - High Hashrate, API, all GPUs supported! - page 10. (Read 13352 times)
February 28, 2018, 08:13:32 AM
February 27, 2018, 11:07:29 AM
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?
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.
February 26, 2018, 06:26:46 PM
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
http://img.techpowerup.org/180226/nvidia-20180226-142516.png
February 26, 2018, 04:50:49 PM
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.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?
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
February 26, 2018, 04:46:36 PM
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.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?
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
February 26, 2018, 03:48:49 PM
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.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?
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?
February 26, 2018, 03:26:21 PM
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.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?
I had forgotten to switch back to forcing P0 state.
All good, back to good ol'speeds.
February 26, 2018, 03:19:34 PM
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?
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?
February 26, 2018, 03:15:24 PM
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?
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
February 26, 2018, 10:22:26 AM
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]
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!
February 26, 2018, 09:54:43 AM
You know the best thing about this thread is your AutoIt script, right?
I love the thing!
Thanks!
I love the thing!
Thanks!
Enjoy!
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.
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?
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]
February 26, 2018, 09:47:10 AM
You know the best thing about this thread is your AutoIt script, right?
I love the thing!
Thanks!
I love the thing!
Thanks!
Enjoy!
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.
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?
February 26, 2018, 09:41:36 AM
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.
February 25, 2018, 01:57:46 PM
I know a couple of people that are waiting for the Titan update to try it on their cards.
February 25, 2018, 01:52:56 PM
Have anybody tested latest version with GTX 980 and 980 Ti ?
it works... for a while.https://hostingkartinok.com/show-image.php?id=4b03a731dabe0c26f9c3375670d552bc
February 25, 2018, 10:31:22 AM
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
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
February 25, 2018, 09:23:08 AM
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
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.
February 25, 2018, 09:18:34 AM
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.
February 25, 2018, 09:17:07 AM
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
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
February 25, 2018, 08:52:00 AM
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)
Jump to: