giveen1
Newbie
Offline
Activity: 70
Merit: 0
|
|
January 25, 2018, 04:16:12 PM |
|
Just curious why y'all would want to add this miner to nicehash legacy versus just using the miner and pointing it to a nicehash pool?
Or are you simply building out nicehash legacy with your preferred miners and still letting it manage profit switching?
You might be able to help me there: I simply do not know how to mine differently. Yes: Nicehash is great for profit switching, but it the rates of hsrminer are real then it's better than anything else out there. So how do I point "to a nicehash pool" in such a way that nicepool recognises me? Make sure you research nicehash to see if that's the right service for you. Depending on your goals, it may or may not be the best service. Here's a list of pools: https://www.nicehash.com/help/which-stratum-servers-are-availableTheir FAQ is pretty good. Essentially, you just point your miner to the appropriate nicehash pool and use the nicehash generated address from your account as your username. Perfect! Thank you It worked. For those looking to do the same thing: hsrminer_neoscrypt.exe -o stratum+tcp://neoscrypt.eu.nicehash.com:3341 -u (nicehash wallet address) Question: Any way to define a worker name? I did not see that in hsrminer's help file. Yes add a period after your wallet WALLET_ADDRESS_HERE.workername
|
|
|
|
xberg
Jr. Member
Offline
Activity: 159
Merit: 5
|
|
January 25, 2018, 04:22:17 PM |
|
Yes add a period after your wallet
WALLET_ADDRESS_HERE.workername
Thanks!!
|
|
|
|
kostas554
Newbie
Offline
Activity: 60
Merit: 0
|
|
January 25, 2018, 04:42:55 PM |
|
Looks interesting, will give it a try. What other algos are you targeting for addition?
|
|
|
|
Monberg75
Copper Member
Newbie
Offline
Activity: 109
Merit: 0
|
|
January 25, 2018, 05:08:54 PM |
|
Hi, got a little problem here.. My HSR miner is stopping once a while with this message. -- Cuda error in func 'neoscrypt_cpu_hash_1060' at line 1420 : unspecified launch failure. Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : unspecified launch failure. -- http://img.techpowerup.org/180125/p1kalmig2k256.jpgAny clue on what i should do? Best regards: Monberg75
|
|
|
|
NetopyrMan
Member
Offline
Activity: 144
Merit: 10
|
|
January 25, 2018, 07:35:20 PM |
|
Hi, got a little problem here.. My HSR miner is stopping once a while with this message. -- Cuda error in func 'neoscrypt_cpu_hash_1060' at line 1420 : unspecified launch failure. Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : unspecified launch failure. -- http://img.techpowerup.org/180125/p1kalmig2k256.jpgAny clue on what i should do? Best regards: Monberg75 :loop hsrminer command goto loop
|
|
|
|
Monberg75
Copper Member
Newbie
Offline
Activity: 109
Merit: 0
|
|
January 25, 2018, 07:52:14 PM |
|
How does that solve the problem?
|
|
|
|
MagicSmoker
|
|
January 25, 2018, 09:21:38 PM |
|
How does that solve the problem?
It automatically restarts the miner. Your problem is likely from overclocking too much. This miner is very finicky about that. Try backing off core clock or increasing core voltage *if* it has been lowered.
|
|
|
|
maggari
Newbie
Offline
Activity: 18
Merit: 0
|
|
January 26, 2018, 12:49:49 AM |
|
Miner working fine, though according to pool data (actual hashrate), seems to be even lower than KlausT or similar minus donations. No matter what those pretty numbers tell in miners. Well, about 36hours and I have screenshots to give. Might also be my R9 Fury rig having it's periods and ruining the results, it's mining into same wallet, should restrict it into separate one.
|
|
|
|
Elder III
|
|
January 26, 2018, 01:27:15 AM |
|
If anyone has problems with 100% rejected shares on a GTX 1060, try running the test version of the miner that is on the first page of this thread. We had 2 rigs that would not work (100% rejected shares) until we tried out the test version. Those 2 rigs have been working fine for going on 2 full days now using the test miner.
|
|
|
|
Monberg75
Copper Member
Newbie
Offline
Activity: 109
Merit: 0
|
|
January 26, 2018, 06:16:13 AM |
|
How does that solve the problem?
It automatically restarts the miner. Your problem is likely from overclocking too much. This miner is very finicky about that. Try backing off core clock or increasing core voltage *if* it has been lowered. I'm not running any overclock. Standard all the way. Already got a script to restart the program, but in the end it all locks up. I'll try to run an instance for every card to se if I can solve the problem. Maybe it's because I'm using 3 different cards in same miner. Then I'll try to separate every type to a specific miner.
|
|
|
|
stevascha
Member
Offline
Activity: 312
Merit: 10
|
|
January 26, 2018, 07:14:41 AM |
|
Hi, got a little problem here.. My HSR miner is stopping once a while with this message. -- Cuda error in func 'neoscrypt_cpu_hash_1060' at line 1420 : unspecified launch failure. Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : unspecified launch failure. -- http://img.techpowerup.org/180125/p1kalmig2k256.jpgAny clue on what i should do? Best regards: Monberg75 yeah me too, but when use another ccmin (ex klaust) it don't show ur message
|
|
|
|
Monberg75
Copper Member
Newbie
Offline
Activity: 109
Merit: 0
|
|
January 26, 2018, 07:19:54 AM |
|
Hi, got a little problem here.. My HSR miner is stopping once a while with this message. -- Cuda error in func 'neoscrypt_cpu_hash_1060' at line 1420 : unspecified launch failure. Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : unspecified launch failure. -- http://img.techpowerup.org/180125/p1kalmig2k256.jpgAny clue on what i should do? Best regards: Monberg75 yeah me too, but when use another ccmin (ex klaust) it don't show ur message I think I'll be switching to Nemos instead.. I have to try something else, at least til i solve this problem with HSR.
|
|
|
|
sugi88999
Newbie
Offline
Activity: 68
Merit: 0
|
|
January 26, 2018, 07:57:01 AM |
|
my HSR miner stop after a few hour, and it happened several time. i use it on windows 10. how to solve the problem tq
|
|
|
|
al1n
Member
Offline
Activity: 154
Merit: 29
|
|
January 26, 2018, 08:11:11 AM |
|
my HSR miner stop after a few hour, and it happened several time. i use it on windows 10. how to solve the problem tq
I have the same issue on win 10 too I solved it by automatically closing and restarting the process every hour
|
|
|
|
Dropsh0t
Newbie
Offline
Activity: 9
Merit: 0
|
|
January 26, 2018, 12:20:34 PM |
|
When Linux?
Hy кoгдa, нaкoнeц, coбepeтe пoд линyкc?
source on githab, find the one who does under Linux, will you be a miner иcxoдники нa гитxaбe, нaйди тoгo ктo дeлaeт пoд линyкc, бyдeт тeбe мaйнep There's no sources. Release only. It's closed code miner with fee.
|
|
|
|
jugger1028
Jr. Member
Offline
Activity: 213
Merit: 3
|
|
January 26, 2018, 01:20:11 PM |
|
For you people that keep crashing, lower your overclock settings, HSRMiner is not as stable as CCMiner when it comes to overclocking so lower it. The cuda errors are overclock errors. Also, make sure you have AT LEAST the same amount of virtual memory set up as you have memory on the card.. 5 1080ti cards = 11*5 = 55gb of virtual memory minimum. You shouldn't need to set it to restart every hour, this is stable IF you don't push the limits.
|
Check out Trezarcoin @ Trezarcoin.com, book +VIP hotel stays with -20% discounts from Expedia by using $TZC to Pay, TrezarTravels.com to learn more!
|
|
|
Monberg75
Copper Member
Newbie
Offline
Activity: 109
Merit: 0
|
|
January 26, 2018, 01:21:50 PM |
|
For you people that keep crashing, lower your overclock settings, HSRMiner is not as stable as CCMiner when it comes to overclocking so lower it. The cuda errors are overclock errors. Also, make sure you have AT LEAST the same amount of virtual memory set up as you have memory on the card.. 5 1080ti cards = 11*5 = 55gb of virtual memory minimum. You shouldn't need to set it to restart every hour, this is stable IF you don't push the limits.
How do i set the virtual memory. I don't have any overclock, just standard settings, so the virtual memory might be my problem.
|
|
|
|
MagicSmoker
|
|
January 26, 2018, 01:28:15 PM |
|
For you people that keep crashing, lower your overclock settings, HSRMiner is not as stable as CCMiner when it comes to overclocking so lower it. The cuda errors are overclock errors. Also, make sure you have AT LEAST the same amount of virtual memory set up as you have memory on the card.. 5 1080ti cards = 11*5 = 55gb of virtual memory minimum. You shouldn't need to set it to restart every hour, this is stable IF you don't push the limits.
How do i set the virtual memory. I don't have any overclock, just standard settings, so the virtual memory might be my problem. Then you may have to *underclock* your card for it to work with hsrminer; I did with one GTX 1080 I have that comes with a factory overclock (more specifically, I had to lower the core clock by setting -125 in MSI AB). Virtual memory is almost certainly not the issue unless you have the minimum amount of system RAM (e.g. - 4GB for Windows 10) and multiple GPUs.
|
|
|
|
jugger1028
Jr. Member
Offline
Activity: 213
Merit: 3
|
|
January 26, 2018, 01:39:50 PM |
|
lol, virtually memory is most definitely a very big factor. Mining rigs usually have 4-8gb of ram and if you have even 1 or 2 cards with low virtual memory you will most definitely get crashes and errors. I run 8 1080ti's, I need 88gb of virtual memory minimum. My system hasn't crashed in weeks and my oc settings are 90%tdp, +100 +600 (some cores run +150 on my hybrids). No crashes.
Go to system, advanced settings (on left side) then advanced tab, then set it there.. Or just google changing virtual memory to get a more thorough guide.
|
Check out Trezarcoin @ Trezarcoin.com, book +VIP hotel stays with -20% discounts from Expedia by using $TZC to Pay, TrezarTravels.com to learn more!
|
|
|
MagicSmoker
|
|
January 26, 2018, 02:47:05 PM |
|
lol, virtually memory is most definitely a very big factor....
Yeah, well, I did say that virtual memory isn't likely an issue unless minimum system memory and/or several GPUs are present. Regardless, I've only seen the Cuda error from hsrminer when I try to manually run too high an intensity; I either have way more system memory than is necessary for both Windows and the GPU, or else a fixed pagefile with a minimum size of the sum of all the GPU VRAM, so running out of memory, virtual or physical, isn't an issue. Now could those Cuda errors be caused by insufficient physical + virtual memory? I dunno, I'm not a programmer, but it certainly seems possible; it's just that I have seen similar errors and insufficient memory wasn't the cause.
|
|
|
|
|