So many complaints by, what feels like, a bunch of 12 year olds that i wanted to chime in and let you know that your program has been working flawlessly for me and my 1080 ti's. Was on 2.2.2 and now on 2.3c... no issues with either for over a month.
Thank you and Happy New Year!
Topic: [NemosMiner] multi algo profit switching NVIDIA/CPU miner - page 118. (Read 289447 times)
hi guys.
New miner here. Just finished building my rig over the weekend, and get everything setup using this miner. I have been enjoying it so far. Lots of valuable information in this thread as well - thanks to everyone who has contributed!
Had 2 quick questions though (more related to my setup). I'm running two 1070ti cards: 0 GPU, +650 MEM
1) I'm seeing a hash rate of out 12.5 Mh/s per card, mining X-17. Does that sound about right? Playing with GPU/MEM clock settings seems to have no impact on this number.
2) Is it normal to see the hashrate bouncing around like this (ahashpool wallet page)?
http://img.photobucket.com/albums/v168/yashart7/hashrate.png
New miner here. Just finished building my rig over the weekend, and get everything setup using this miner. I have been enjoying it so far. Lots of valuable information in this thread as well - thanks to everyone who has contributed!
Had 2 quick questions though (more related to my setup). I'm running two 1070ti cards: 0 GPU, +650 MEM
1) I'm seeing a hash rate of out 12.5 Mh/s per card, mining X-17. Does that sound about right? Playing with GPU/MEM clock settings seems to have no impact on this number.
2) Is it normal to see the hashrate bouncing around like this (ahashpool wallet page)?
http://img.photobucket.com/albums/v168/yashart7/hashrate.png
Nemos! Love the miner man, works awesome. Thanks for all the hard work you put into this!
Question for you veterans out there... My miner crashes every once in a while, which is very irritating :-) I have set a 4 hour reboot script to bounce the machine every 4 hours to fix it...
I was wondering -- does anyone have watchdog going on this miner so you can see a report out of the temperatures of the GPUs or any other statistics?
Logging doesn't tell me why it crashed and I don't feel comfortable with not knowing how my GPUs are doing.
Has anyone solved this one?
Question for you veterans out there... My miner crashes every once in a while, which is very irritating :-) I have set a 4 hour reboot script to bounce the machine every 4 hours to fix it...
I was wondering -- does anyone have watchdog going on this miner so you can see a report out of the temperatures of the GPUs or any other statistics?
Logging doesn't tell me why it crashed and I don't feel comfortable with not knowing how my GPUs are doing.
Has anyone solved this one?
What is your GPU and MEM overclock? What model cards? I've seen +115 CPU cause issues on some rigs so I back those down to +100 or +85 and it fixes. Or +600 mem back down to +500
You can edit 2 registry entries (see earlier post on this thread page 111) to auto close the crash. Also intensity can be adjusted as well
modify Ccmineralexis78.ps1
"sib" = " -i 19 -d $SelGPUCC" #Sib
"x17" = " -i 19 -d $SelGPUCC" #X17
"c11" = " -i 19 -d $SelGPUCC" #C11
modify CcminerKlaust.ps1
"neoscrypt" = " -i 15 -d $SelGPUCC" #NeoScrypt
Heya Millsys -
GPU and Mem overclock are pretty standard/stable with other miner .exe's, but I'll back them off a little bit. Thanks for the suggestion.
The other problem i have is that I get the error "Error contacting pool, retrying.." error sometimes for no reason. Only a reboot fixes it...
a ccminer crash + this error is what keeps taking me offline
If I auto close the crash, will that restart the miner?
Auto Close will help NemosMiner see there is no running ccminer and launch it again automatically
GPU/MEM depends on intensity setting, since you don't want to give us your values I can't help you much.
Error Contacting Pool is Internet issue, try DNS 9.9.9.9, update network drivers, you shouldn't be losing internet access.... Don't blame that on ccminer/nemos
heya, thanks for the help. Wasn't trying to be stingy with the GPU/mem stuff, my GPU settings are essentially what you recommended -- around +100 / +550, hashing at 42mhs for 6x1060s, but different for each card.
Appreciate the info on the error contacting pool issue -- i've set a reboot script so hopefully that helps.
Back down memory to +500, adjust to intensity, update network card drivers (realtek, intel whatever it is).
modify Ccmineralexis78.ps1
"sib" = " -i 19 -d $SelGPUCC" #Sib
"x17" = " -i 19 -d $SelGPUCC" #X17
"c11" = " -i 19 -d $SelGPUCC" #C11
modify CcminerKlaust.ps1
"neoscrypt" = " -i 15 -d $SelGPUCC" #NeoScrypt
blake2s and skein make my card run in the 76-77 degree range. I'm fighting a temperature battle right now with bad airflow and would like to change the intensities of these two algorithms so they can still run, but at a lower intensity. What intensity would you guys recommend for an 1080 FTW for blake2s and skein?
i=20 for my 1080 rig's.21 — too ruthless for my 1080 cards. the power curve is too "dancing"
Nemos! Love the miner man, works awesome. Thanks for all the hard work you put into this!
Question for you veterans out there... My miner crashes every once in a while, which is very irritating :-) I have set a 4 hour reboot script to bounce the machine every 4 hours to fix it...
I was wondering -- does anyone have watchdog going on this miner so you can see a report out of the temperatures of the GPUs or any other statistics?
Logging doesn't tell me why it crashed and I don't feel comfortable with not knowing how my GPUs are doing.
Has anyone solved this one?
Question for you veterans out there... My miner crashes every once in a while, which is very irritating :-) I have set a 4 hour reboot script to bounce the machine every 4 hours to fix it...
I was wondering -- does anyone have watchdog going on this miner so you can see a report out of the temperatures of the GPUs or any other statistics?
Logging doesn't tell me why it crashed and I don't feel comfortable with not knowing how my GPUs are doing.
Has anyone solved this one?
What is your GPU and MEM overclock? What model cards? I've seen +115 CPU cause issues on some rigs so I back those down to +100 or +85 and it fixes. Or +600 mem back down to +500
You can edit 2 registry entries (see earlier post on this thread page 111) to auto close the crash. Also intensity can be adjusted as well
modify Ccmineralexis78.ps1
"sib" = " -i 19 -d $SelGPUCC" #Sib
"x17" = " -i 19 -d $SelGPUCC" #X17
"c11" = " -i 19 -d $SelGPUCC" #C11
modify CcminerKlaust.ps1
"neoscrypt" = " -i 15 -d $SelGPUCC" #NeoScrypt
Heya Millsys -
GPU and Mem overclock are pretty standard/stable with other miner .exe's, but I'll back them off a little bit. Thanks for the suggestion.
The other problem i have is that I get the error "Error contacting pool, retrying.." error sometimes for no reason. Only a reboot fixes it...
a ccminer crash + this error is what keeps taking me offline
If I auto close the crash, will that restart the miner?
Auto Close will help NemosMiner see there is no running ccminer and launch it again automatically
GPU/MEM depends on intensity setting, since you don't want to give us your values I can't help you much.
Error Contacting Pool is Internet issue, try DNS 9.9.9.9, update network drivers, you shouldn't be losing internet access.... Don't blame that on ccminer/nemos
heya, thanks for the help. Wasn't trying to be stingy with the GPU/mem stuff, my GPU settings are essentially what you recommended -- around +100 / +550, hashing at 42mhs for 6x1060s, but different for each card.
Appreciate the info on the error contacting pool issue -- i've set a reboot script so hopefully that helps.
Hi,
is there a way to rerun a benchmark for a particular algorithm without having to rerun through them all?
I noticed for x17 it takes a long time for it to come up to full speed ( over 5 minutes ) so the default 120 seconds is not enough and the benchmark result is not accurate.
The same for NIST. My single GPU 1080 scores 58.18 MH/s and my 8 x 1070 only scored 97.43 MH/s ( the benchmarking time was too short so it did not have time to ram p to full speed )
The last option is just change the number to 1800 but then it will run each benchmark for 1/2 an hour.....
regards
How do you extend the benchmark time? is there a way to rerun a benchmark for a particular algorithm without having to rerun through them all?
I noticed for x17 it takes a long time for it to come up to full speed ( over 5 minutes ) so the default 120 seconds is not enough and the benchmark result is not accurate.
The same for NIST. My single GPU 1080 scores 58.18 MH/s and my 8 x 1070 only scored 97.43 MH/s ( the benchmarking time was too short so it did not have time to ram p to full speed )
The last option is just change the number to 1800 but then it will run each benchmark for 1/2 an hour.....
regards
any profit calculator?
want to compare before.
lets say i have 6 1060 6gbs, how much would i earn per day?
want to compare before.
lets say i have 6 1060 6gbs, how much would i earn per day?
If you know your hashrates you can use my tool:
http://pools.you-stupid-woman.com
Which pool do you recommend?
I use zpool but I think that is very variable, I tried zpool24 but often my pc don't connect to pool.
I have only one 1070.
Thanks.
I use zpool but I think that is very variable, I tried zpool24 but often my pc don't connect to pool.
I have only one 1070.
Thanks.
any profit calculator?
want to compare before.
lets say i have 6 1060 6gbs, how much would i earn per day?
want to compare before.
lets say i have 6 1060 6gbs, how much would i earn per day?
blake2s and skein make my card run in the 76-77 degree range. I'm fighting a temperature battle right now with bad airflow and would like to change the intensities of these two algorithms so they can still run, but at a lower intensity. What intensity would you guys recommend for an 1080 FTW for blake2s and skein?
use a program like this: http://download.gigabyte.asia/FileList/Utility/vga_xtreme_engine_setup_1.25.exe
keep lowering your power-limit (tdp) until you reach desired temps....
Best Regards
Nemo
Nemos! Love the miner man, works awesome. Thanks for all the hard work you put into this!
Question for you veterans out there... My miner crashes every once in a while, which is very irritating :-) I have set a 4 hour reboot script to bounce the machine every 4 hours to fix it...
I was wondering -- does anyone have watchdog going on this miner so you can see a report out of the temperatures of the GPUs or any other statistics?
Logging doesn't tell me why it crashed and I don't feel comfortable with not knowing how my GPUs are doing.
Has anyone solved this one?
Question for you veterans out there... My miner crashes every once in a while, which is very irritating :-) I have set a 4 hour reboot script to bounce the machine every 4 hours to fix it...
I was wondering -- does anyone have watchdog going on this miner so you can see a report out of the temperatures of the GPUs or any other statistics?
Logging doesn't tell me why it crashed and I don't feel comfortable with not knowing how my GPUs are doing.
Has anyone solved this one?
What is your GPU and MEM overclock? What model cards? I've seen +115 CPU cause issues on some rigs so I back those down to +100 or +85 and it fixes. Or +600 mem back down to +500
You can edit 2 registry entries (see earlier post on this thread page 111) to auto close the crash. Also intensity can be adjusted as well
modify Ccmineralexis78.ps1
"sib" = " -i 19 -d $SelGPUCC" #Sib
"x17" = " -i 19 -d $SelGPUCC" #X17
"c11" = " -i 19 -d $SelGPUCC" #C11
modify CcminerKlaust.ps1
"neoscrypt" = " -i 15 -d $SelGPUCC" #NeoScrypt
Heya Millsys -
GPU and Mem overclock are pretty standard/stable with other miner .exe's, but I'll back them off a little bit. Thanks for the suggestion.
The other problem i have is that I get the error "Error contacting pool, retrying.." error sometimes for no reason. Only a reboot fixes it...
a ccminer crash + this error is what keeps taking me offline
If I auto close the crash, will that restart the miner?
Auto Close will help NemosMiner see there is no running ccminer and launch it again automatically
GPU/MEM depends on intensity setting, since you don't want to give us your values I can't help you much.
Error Contacting Pool is Internet issue, try DNS 9.9.9.9, update network drivers, you shouldn't be losing internet access.... Don't blame that on ccminer/nemos
last question for you guys for a bit- -
i'd like to query the ccminer API, but telnetting to port 4068 doesn't work -- for the ccminers that use --api-remote, is there a way to query the system to get status?
i'd like to query the ccminer API, but telnetting to port 4068 doesn't work -- for the ccminers that use --api-remote, is there a way to query the system to get status?
Nemos! Love the miner man, works awesome. Thanks for all the hard work you put into this!
Question for you veterans out there... My miner crashes every once in a while, which is very irritating :-) I have set a 4 hour reboot script to bounce the machine every 4 hours to fix it...
I was wondering -- does anyone have watchdog going on this miner so you can see a report out of the temperatures of the GPUs or any other statistics?
Logging doesn't tell me why it crashed and I don't feel comfortable with not knowing how my GPUs are doing.
Has anyone solved this one?
Question for you veterans out there... My miner crashes every once in a while, which is very irritating :-) I have set a 4 hour reboot script to bounce the machine every 4 hours to fix it...
I was wondering -- does anyone have watchdog going on this miner so you can see a report out of the temperatures of the GPUs or any other statistics?
Logging doesn't tell me why it crashed and I don't feel comfortable with not knowing how my GPUs are doing.
Has anyone solved this one?
What is your GPU and MEM overclock? What model cards? I've seen +115 CPU cause issues on some rigs so I back those down to +100 or +85 and it fixes. Or +600 mem back down to +500
You can edit 2 registry entries (see earlier post on this thread page 111) to auto close the crash. Also intensity can be adjusted as well
modify Ccmineralexis78.ps1
"sib" = " -i 19 -d $SelGPUCC" #Sib
"x17" = " -i 19 -d $SelGPUCC" #X17
"c11" = " -i 19 -d $SelGPUCC" #C11
modify CcminerKlaust.ps1
"neoscrypt" = " -i 15 -d $SelGPUCC" #NeoScrypt
Heya Millsys -
GPU and Mem overclock are pretty standard/stable with other miner .exe's, but I'll back them off a little bit. Thanks for the suggestion.
The other problem i have is that I get the error "Error contacting pool, retrying.." error sometimes for no reason. Only a reboot fixes it...
a ccminer crash + this error is what keeps taking me offline
If I auto close the crash, will that restart the miner?
why can't i run it in Admin Mode?
Thanks for all that coding!
awesome tool.
Thanks for all that coding!
awesome tool.
Nemos! Love the miner man, works awesome. Thanks for all the hard work you put into this!
Question for you veterans out there... My miner crashes every once in a while, which is very irritating :-) I have set a 4 hour reboot script to bounce the machine every 4 hours to fix it...
I was wondering -- does anyone have watchdog going on this miner so you can see a report out of the temperatures of the GPUs or any other statistics?
Logging doesn't tell me why it crashed and I don't feel comfortable with not knowing how my GPUs are doing.
Has anyone solved this one?
Question for you veterans out there... My miner crashes every once in a while, which is very irritating :-) I have set a 4 hour reboot script to bounce the machine every 4 hours to fix it...
I was wondering -- does anyone have watchdog going on this miner so you can see a report out of the temperatures of the GPUs or any other statistics?
Logging doesn't tell me why it crashed and I don't feel comfortable with not knowing how my GPUs are doing.
Has anyone solved this one?
What is your GPU and MEM overclock? What model cards? I've seen +115 CPU cause issues on some rigs so I back those down to +100 or +85 and it fixes. Or +600 mem back down to +500
You can edit 2 registry entries (see earlier post on this thread page 111) to auto close the crash. Also intensity can be adjusted as well
modify Ccmineralexis78.ps1
"sib" = " -i 19 -d $SelGPUCC" #Sib
"x17" = " -i 19 -d $SelGPUCC" #X17
"c11" = " -i 19 -d $SelGPUCC" #C11
modify CcminerKlaust.ps1
"neoscrypt" = " -i 15 -d $SelGPUCC" #NeoScrypt
Nemos! Love the miner man, works awesome. Thanks for all the hard work you put into this!
Question for you veterans out there... My miner crashes every once in a while, which is very irritating :-) I have set a 4 hour reboot script to bounce the machine every 4 hours to fix it...
I was wondering -- does anyone have watchdog going on this miner so you can see a report out of the temperatures of the GPUs or any other statistics?
Logging doesn't tell me why it crashed and I don't feel comfortable with not knowing how my GPUs are doing.
Has anyone solved this one?
Question for you veterans out there... My miner crashes every once in a while, which is very irritating :-) I have set a 4 hour reboot script to bounce the machine every 4 hours to fix it...
I was wondering -- does anyone have watchdog going on this miner so you can see a report out of the temperatures of the GPUs or any other statistics?
Logging doesn't tell me why it crashed and I don't feel comfortable with not knowing how my GPUs are doing.
Has anyone solved this one?
Hi,
is there a way to rerun a benchmark for a particular algorithm without having to rerun through them all?
I noticed for x17 it takes a long time for it to come up to full speed ( over 5 minutes ) so the default 120 seconds is not enough and the benchmark result is not accurate.
The same for NIST. My single GPU 1080 scores 58.18 MH/s and my 8 x 1070 only scored 97.43 MH/s ( the benchmarking time was too short so it did not have time to ram p to full speed )
The last option is just change the number to 1800 but then it will run each benchmark for 1/2 an hour.....
regards
is there a way to rerun a benchmark for a particular algorithm without having to rerun through them all?
I noticed for x17 it takes a long time for it to come up to full speed ( over 5 minutes ) so the default 120 seconds is not enough and the benchmark result is not accurate.
The same for NIST. My single GPU 1080 scores 58.18 MH/s and my 8 x 1070 only scored 97.43 MH/s ( the benchmarking time was too short so it did not have time to ram p to full speed )
The last option is just change the number to 1800 but then it will run each benchmark for 1/2 an hour.....
regards
Yes, quit Nemos, open the Stats folder and delete the relevant xxx_HashRate.txt file
e.g. to rebenchmark X17 delete the file called ccminerAlexis78_X17_HashRate.txt
Then you can extend the duration and it will only apply to the newly created benchmark
I restarted benchmarking all algorithms. When it got to the x11 benchmark and it initially showed 49 MH/s, then 30 minutes later it got up to 84.97 MH/s.
Then the benchmark ended, so I guess now I have to extend the benchmark for this algorithm to 1 hour since it never had the chance to get to the top speed.
That's kind of ridiculous.
Now Nemos miner shows the speed on top of the screen as 83.97 MH/s, but this is NOT the top speed since I am sure it would have kept going up even after 1/2 an hour.
Anyone else pay attention to this X-17 algorithm while benchmarking?
Hi,
is there a way to rerun a benchmark for a particular algorithm without having to rerun through them all?
I noticed for x17 it takes a long time for it to come up to full speed ( over 5 minutes ) so the default 120 seconds is not enough and the benchmark result is not accurate.
The same for NIST. My single GPU 1080 scores 58.18 MH/s and my 8 x 1070 only scored 97.43 MH/s ( the benchmarking time was too short so it did not have time to ram p to full speed )
The last option is just change the number to 1800 but then it will run each benchmark for 1/2 an hour.....
regards
is there a way to rerun a benchmark for a particular algorithm without having to rerun through them all?
I noticed for x17 it takes a long time for it to come up to full speed ( over 5 minutes ) so the default 120 seconds is not enough and the benchmark result is not accurate.
The same for NIST. My single GPU 1080 scores 58.18 MH/s and my 8 x 1070 only scored 97.43 MH/s ( the benchmarking time was too short so it did not have time to ram p to full speed )
The last option is just change the number to 1800 but then it will run each benchmark for 1/2 an hour.....
regards
Yes, quit Nemos, open the Stats folder and delete the relevant xxx_HashRate.txt file
e.g. to rebenchmark X17 delete the file called ccminerAlexis78_X17_HashRate .txt
Then you can extend the duration and it will only apply to the newly created benchmark
Hi,
is there a way to rerun a benchmark for a particular algorithm without having to rerun through them all?
I noticed for x17 it takes a long time for it to come up to full speed ( over 5 minutes ) so the default 120 seconds is not enough and the benchmark result is not accurate.
The same for NIST. My single GPU 1080 scores 58.18 MH/s and my 8 x 1070 only scored 97.43 MH/s ( the benchmarking time was too short so it did not have time to ram p to full speed )
The last option is just change the number to 1800 but then it will run each benchmark for 1/2 an hour.....
regards
is there a way to rerun a benchmark for a particular algorithm without having to rerun through them all?
I noticed for x17 it takes a long time for it to come up to full speed ( over 5 minutes ) so the default 120 seconds is not enough and the benchmark result is not accurate.
The same for NIST. My single GPU 1080 scores 58.18 MH/s and my 8 x 1070 only scored 97.43 MH/s ( the benchmarking time was too short so it did not have time to ram p to full speed )
The last option is just change the number to 1800 but then it will run each benchmark for 1/2 an hour.....
regards
Hye,
I've a problem since 2 days that I can't resolve, when I start the miner, it's locked on benchmarking and A little window open and close a few seconds later like this : https://www.noelshack.com/2018-01-2-1514888849-ininii.png
I try to put EU in the start file but after that the miner doesn't work at all, so I retry with US, different workers, different algos, etc...
What can I do now?
Thank's!
I've a problem since 2 days that I can't resolve, when I start the miner, it's locked on benchmarking and A little window open and close a few seconds later like this : https://www.noelshack.com/2018-01-2-1514888849-ininii.png
I try to put EU in the start file but after that the miner doesn't work at all, so I retry with US, different workers, different algos, etc...
What can I do now?
Thank's!
I had many problems then I increased my paging file size from 16000 to 50000 and everything is working, even neoscrypt miner which would crash before.
Thank's to help me, I try to increase it to 50000MB and then 75000MB but nothing change, still on benchmarking, and I see on afterburner that my gpu does'nt do anything
Jump to: