Topic: [NemosMiner] multi algo profit switching NVIDIA/CPU miner - page 41. (Read 289447 times)
plus pools are a real headache.... Just tested zergpoolplus and same issues with profits not updating. I've switched back to the regular non 24hr version, and so far no issues updating.
2.5.1 switching like on crack on zpoolplus.bat like 3-4 times per hour, cant figure out is that affecting earnings. tried with 5% and 240 interval but doesn't seem to help. any ideas?
Code:
"date","algo","wallet","username","Stratum"
"1.3.2018. 12:15:16 ","Skein","addres","nemo","stratum+tcp://skein.mine.zpool.ca:4933"
"1.3.2018. 12:25:26 ","Bitcore","addres","nemo","stratum+tcp://bitcore.mine.zpool.ca:3556"
"1.3.2018. 12:35:36 ","Skunk","addres","nemo","stratum+tcp://skunk.mine.zpool.ca:8433"
"1.3.2018. 12:45:46 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"1.3.2018. 12:55:56 ","Poly","addres","nemo","stratum+tcp://polytimos.mine.zpool.ca:8463"
"1.3.2018. 1:06:09 ","Groestl","1QGADhdMRpp9Pk5u5zG1TrHKRrdK5R81TE","nemo","stratum+tcp://groestl.mine.zpool.ca:5333"
"1.3.2018. 1:16:20 ","Nist5","addres","nemo","stratum+tcp://nist5.mine.zpool.ca:3833"
"1.3.2018. 1:26:32 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233"
"1.3.2018. 1:36:43 ","Lyra2RE2","addres","nemo","stratum+tcp://lyra2v2.mine.zpool.ca:4533"
"1.3.2018. 1:46:52 ","Equihash","addres","nemo",""
"1.3.2018. 1:57:03 ","Lbry","addres","nemo","stratum+tcp://lbry.mine.zpool.ca:3334"
"1.3.2018. 2:07:42 ","C11","addres","nemo","stratum+tcp://c11.mine.zpool.ca:3573"
"1.3.2018. 2:29:59 ","Blake2s","addres","nemo","stratum+tcp://blake2s.mine.zpool.ca:5766"
"1.3.2018. 2:40:08 ","Lyra2z","addres","nemo","stratum+tcp://lyra2z.mine.zpool.ca:4553"
"1.3.2018. 2:50:19 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"1.3.2018. 3:00:30 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"1.3.2018. 3:10:41 ","Sib","addres","nemo","stratum+tcp://sib.mine.zpool.ca:5033"
"1.3.2018. 3:20:53 ","X11evo","addres","nemo","stratum+tcp://x11evo.mine.zpool.ca:3553"
"1.3.2018. 3:31:03 ","MyriadGroestl","addres","nemo","stratum+tcp://myr-gr.mine.zpool.ca:5433"
"1.3.2018. 3:41:15 ","Tribus","addres","nemo","stratum+tcp://tribus.mine.zpool.ca:8533"
"1.3.2018. 3:51:26 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433"
"1.3.2018. 4:01:37 ","Blakecoin","addres","nemo","stratum+tcp://blakecoin.mine.zpool.ca:5743"
"1.3.2018. 4:11:47 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"1.3.2018. 5:19:37 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"1.3.2018. 5:51:04 ","Lyra2RE2","addres","nemo","stratum+tcp://lyra2v2.mine.zpool.ca:4533"
"1.3.2018. 6:16:28 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"1.3.2018. 7:00:05 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"1.3.2018. 7:31:59 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"1.3.2018. 9:04:02 ","Tribus","addres","nemo","stratum+tcp://tribus.mine.zpool.ca:8533"
"1.3.2018. 9:11:15 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"1.3.2018. 11:01:30 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"1.3.2018. 11:26:54 ","Skein","addres","nemo","stratum+tcp://skein.mine.zpool.ca:4933"
"1.3.2018. 11:40:11 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433"
"2.3.2018. 12:17:42 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"2.3.2018. 1:19:30 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"2.3.2018. 1:50:58 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"2.3.2018. 3:04:52 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433"
"2.3.2018. 3:18:09 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"2.3.2018. 4:38:07 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"2.3.2018. 6:28:25 ","Tribus","addres","nemo","stratum+tcp://tribus.mine.zpool.ca:8533"
"2.3.2018. 6:59:53 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"2.3.2018. 8:01:40 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"2.3.2018. 9:33:47 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"2.3.2018. 10:53:48 ","Tribus","addres","nemo","stratum+tcp://tribus.mine.zpool.ca:8533"
"2.3.2018. 11:19:12 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"2.3.2018. 1:15:36 ","Xevan","134bw4oTorEJUUVFhokDQDfNqTs7rBMNYy","MrPlus","stratum+tcp://xevan.mine.zpool.ca:3739"
"2.3.2018. 1:16:45 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"2.3.2018. 1:48:14 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"2.3.2018. 3:02:10 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"2.3.2018. 4:10:04 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"2.3.2018. 4:47:38 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"2.3.2018. 5:25:10 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"2.3.2018. 7:27:36 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"2.3.2018. 8:35:30 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"2.3.2018. 9:06:59 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"2.3.2018. 9:38:29 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233"
"2.3.2018. 10:03:54 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"2.3.2018. 10:47:32 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233"
"2.3.2018. 11:25:31 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"2.3.2018. 11:57:01 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"3.3.2018. 1:10:59 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"3.3.2018. 1:55:08 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"3.3.2018. 2:20:34 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433"
"3.3.2018. 2:46:00 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233"
"3.3.2018. 3:29:37 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"3.3.2018. 4:25:22 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233"
"3.3.2018. 5:21:08 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"3.3.2018. 6:47:13 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"3.3.2018. 7:49:02 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"3.3.2018. 8:32:52 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"3.3.2018. 10:17:09 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"3.3.2018. 11:37:12 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"3.3.2018. 12:39:05 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233"
"3.3.2018. 1:16:42 ","Xevan","1MsrCoAt8qM53HUMsUxvy9gMj3QVbHLazH","aaronsace","stratum+tcp://xevan.mine.zpool.ca:3739"
"3.3.2018. 1:17:50 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"3.3.2018. 3:40:25 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"3.3.2018. 4:48:17 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"3.3.2018. 6:08:22 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"3.3.2018. 6:58:03 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233"
"3.3.2018. 7:47:44 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"3.3.2018. 8:19:15 ","Equihash","addres","nemo",""
"3.3.2018. 9:15:02 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"3.3.2018. 10:04:43 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233"
"3.3.2018. 10:42:18 ","Lyra2z","addres","nemo","stratum+tcp://lyra2z.mine.zpool.ca:4553"
"3.3.2018. 11:13:48 ","Equihash","addres","nemo",""
"3.3.2018. 11:45:20 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"4.3.2018. 12:35:06 ","Equihash","addres","nemo",""
"4.3.2018. 2:07:24 ","Lyra2z","addres","nemo","stratum+tcp://lyra2z.mine.zpool.ca:4553"
"4.3.2018. 2:32:52 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433"
"4.3.2018. 4:35:27 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"4.3.2018. 5:31:14 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"4.3.2018. 7:28:56 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"4.3.2018. 8:42:55 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233"
"4.3.2018. 9:14:25 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"4.3.2018. 10:04:10 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233"
"4.3.2018. 10:47:55 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"4.3.2018. 12:32:18 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233"
"4.3.2018. 1:15:57 ","Phi","134bw4oTorEJUUVFhokDQDfNqTs7rBMNYy","MrPlus","stratum+tcp://phi.mine.zpool.ca:8333"
"4.3.2018. 1:23:12 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"4.3.2018. 3:31:52 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"4.3.2018. 4:15:31 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233"
"4.3.2018. 5:05:16 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"4.3.2018. 5:30:42 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"4.3.2018. 6:26:31 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"4.3.2018. 7:16:14 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"4.3.2018. 8:18:09 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233"
"4.3.2018. 8:55:46 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"4.3.2018. 9:33:24 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"4.3.2018. 9:58:49 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433"
"4.3.2018. 10:18:24 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"4.3.2018. 10:55:59 ","C11","addres","nemo","stratum+tcp://c11.mine.zpool.ca:3573"
"4.3.2018. 11:15:21 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433"
"4.3.2018. 11:28:39 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"5.3.2018. 12:30:30 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"5.3.2018. 1:32:20 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433"
"5.3.2018. 2:22:01 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"5.3.2018. 3:23:51 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433"
"5.3.2018. 3:43:14 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"5.3.2018. 4:32:56 ","Lyra2z","addres","nemo","stratum+tcp://lyra2z.mine.zpool.ca:4553"
"5.3.2018. 4:52:19 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"5.3.2018. 6:00:14 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433"
"5.3.2018. 6:44:38 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"5.3.2018. 7:22:12 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"5.3.2018. 9:37:13 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"5.3.2018. 9:50:30 ","Bitcore","addres","nemo","stratum+tcp://bitcore.mine.zpool.ca:3556"
"5.3.2018. 10:22:02 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"5.3.2018. 11:42:34 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"5.3.2018. 12:20:48 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"5.3.2018. 1:22:41 ","X17","1QGADhdMRpp9Pk5u5zG1TrHKRrdK5R81TE","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"5.3.2018. 1:23:52 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"5.3.2018. 3:32:30 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"5.3.2018. 5:10:46 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"5.3.2018. 5:36:12 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"5.3.2018. 6:56:18 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"5.3.2018. 7:12:25 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739"
"5.3.2018. 7:13:03 ","Tribus","addres","nemo","stratum+tcp://tribus.mine.zpool.ca:8533"
"5.3.2018. 7:17:40 ","Tribus","addres","nemo","stratum+tcp://tribus.mine.zpool.ca:8533"
"5.3.2018. 7:18:49 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
"5.3.2018. 8:00:16 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"5.3.2018. 8:17:32 ","X17","1MsrCoAt8qM53HUMsUxvy9gMj3QVbHLazH","aaronsace","stratum+tcp://x17.mine.zpool.ca:3737"
"5.3.2018. 8:18:41 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737"
"5.3.2018. 9:16:15 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
I downloaded latest Nemosminer, and run STARTZERGPOOLPLUS.BAT
Benchmark tests RUN and if test lyra2z, mining pool error message.
https://ibb.co/ijBqf7
Benchmark tests RUN and if test lyra2z, mining pool error message.
https://ibb.co/ijBqf7
It's the same like i have in 1 out of 3 pc. the miner starts and quits.
No error, nothing. the other 2 are working fine. it's probably a combination
of installed software that causes this to happen.
No error, nothing. the other 2 are working fine. it's probably a combination
of installed software that causes this to happen.
Check PM please, let's solve the issue.
2. My HSRminer always fails to mine. Any ideas how to get it to work?
Hello, I can help you but I need more info. You can PM me screenshot with error or describe the issue.
It's the same like i have in 1 out of 3 pc. the miner starts and quits.
No error, nothing. the other 2 are working fine. it's probably a combination
of installed software that causes this to happen.
"27.02.2018 EU stratum server added for better connectivity in Europe region europe.mine.zergpool.com"
Please update nemosminer-files !
Please update nemosminer-files !
2. My HSRminer always fails to mine. Any ideas how to get it to work?
Hello, I can help you but I need more info. You can PM me screenshot with error or describe the issue.
2 questions.
1. I had to restart the miner and now I am no longer seeing the benchmarks with the possible revenue/day listing. How do I get it back without resetting the benchmark?
2. My HSRminer always fails to mine. Any ideas how to get it to work?
1. I had to restart the miner and now I am no longer seeing the benchmarks with the possible revenue/day listing. How do I get it back without resetting the benchmark?
2. My HSRminer always fails to mine. Any ideas how to get it to work?
2
Quote from: georat72 on March 03, 2018, 08:22:20 AM
Hi Guys,
How can i change neoscrypt algo miner?
I want to change hsr miner with ccminer KlausT .
Best regards
-----------------------------------
I`m ready - changed it.
Go in the miner folder you want to change and add # to turn it off and remove the # in the miner you want to run, then restart the software and it will benchmark that new software change.
1
add -UIStyle Full in start.bat
Enjoy
Which differences between NemosMiner and MultiPoolMiner?
Hi guys,
Recently I see in WTM X11 popping up at the top coins more ofter. Is it possible to add this algorithm to Nemosminer linking with MPH?
Recently I see in WTM X11 popping up at the top coins more ofter. Is it possible to add this algorithm to Nemosminer linking with MPH?
just google: "x11 asic"
2 questions.
1. I had to restart the miner and now I am no longer seeing the benchmarks with the possible revenue/day listing. How do I get it back without resetting the benchmark?
2. My HSRminer always fails to mine. Any ideas how to get it to work?
1. I had to restart the miner and now I am no longer seeing the benchmarks with the possible revenue/day listing. How do I get it back without resetting the benchmark?
2. My HSRminer always fails to mine. Any ideas how to get it to work?
I installed 2.4.2 on 2 rigs and one of them is rebooting repeatedly now every few hours, and the other is fine. Very odd behavior.. Had to revert back to 2.3.. Anyone else have this issue?
No errors in the event viewer, nothing in whocrashed (no minidumps or bluescreens), and log files are not helpful.
The rig was super stable with 2.3.1...
No errors in the event viewer, nothing in whocrashed (no minidumps or bluescreens), and log files are not helpful.
The rig was super stable with 2.3.1...
sounds like you need to pull back OC settings for your cards, i dont push my rigs to the very max on OC settings, i found profit switching them at 98-99% of their possible hashrate, i can get weeks and weeks of uptime without a single hiccup, but when i tried to push rigs to the max on OC settings, they would run with random hangups and restarts, loosing way more than the 1-2% i would loose in profits by just turning them down.
My policy now when i setup a new rig now is i set it up with known reliable settings, if it ever locks up and hangs up on me i just subtract -5 from the core OC, run it.. if it ever hangs up i take another -5, i have rigs of 6x1080ti's running only +120 core, but you know what those rigs have been 100% up mining for 4+ months now without a single hiccup.
Hi guys,
Recently I see in WTM X11 popping up at the top coins more ofter. Is it possible to add this algorithm to Nemosminer linking with MPH?
Recently I see in WTM X11 popping up at the top coins more ofter. Is it possible to add this algorithm to Nemosminer linking with MPH?
I installed 2.4.2 on 2 rigs and one of them is rebooting repeatedly now every few hours, and the other is fine. Very odd behavior.. Had to revert back to 2.3.. Anyone else have this issue?
No errors in the event viewer, nothing in whocrashed (no minidumps or bluescreens), and log files are not helpful.
The rig was super stable with 2.3.1...
No errors in the event viewer, nothing in whocrashed (no minidumps or bluescreens), and log files are not helpful.
The rig was super stable with 2.3.1...
Probably pushing your power limits when hashing a particular algo. Try backing off power limit 10% in MSI AfterBurner. Also time to upgrade to 2.5
I decided to test out Nicehash vs Ahashpool again with my rig
both cards 1080ti's watercooled on same settings
GPU 1 Nicehash, 24hr profit 0.00024200 btc on single 1080ti using nicehash miner
GPU 2 Ahashpoolplus 24hr profit 0.00033000 btc on single 1080ti using nemo miner
both cards 1080ti's watercooled on same settings
GPU 1 Nicehash, 24hr profit 0.00024200 btc on single 1080ti using nicehash miner
GPU 2 Ahashpoolplus 24hr profit 0.00033000 btc on single 1080ti using nemo miner
Which would make sense with some of the testing that has been done between 1060s to 1080s.
A 1060's ethereum hash rate compared to x17 or other core dependent algorithms is relatively higher than a 1080ti's ethereum to x17 ratio.
1060: 24 mh/s ethereum / 7.7 mh/s X17 = 3.1
1080ti: 36.5 mh/s ethereum / 20 mh/s X17 = 1.875
It makes sense that multi-algo pools that have core dependent algorithms could easily be more profitable at any given time compared to NH.
Nice work everyone for doing tests!
I installed 2.4.2 on 2 rigs and one of them is rebooting repeatedly now every few hours, and the other is fine. Very odd behavior.. Had to revert back to 2.3.. Anyone else have this issue?
No errors in the event viewer, nothing in whocrashed (no minidumps or bluescreens), and log files are not helpful.
The rig was super stable with 2.3.1...
No errors in the event viewer, nothing in whocrashed (no minidumps or bluescreens), and log files are not helpful.
The rig was super stable with 2.3.1...
I decided to test out Nicehash vs Ahashpool again with my rig
both cards 1080ti's watercooled on same settings
GPU 1 Nicehash, 24hr profit 0.00024200 btc on single 1080ti using nicehash miner
GPU 2 Ahashpoolplus 24hr profit 0.00033000 btc on single 1080ti using nemo miner
both cards 1080ti's watercooled on same settings
GPU 1 Nicehash, 24hr profit 0.00024200 btc on single 1080ti using nicehash miner
GPU 2 Ahashpoolplus 24hr profit 0.00033000 btc on single 1080ti using nemo miner
what algorithm for the test?
Hello nemos users. I have a problem like this. I have a 7 gpu rig.
Ccmineralexis and x17 does not start all gpus and sometimes only one or two gpus run for a while. In the end it updates the hashrate as 34mh instead of 120mh. By calculating 34mh it does not switch x17 again. I solved this by making x17 hashrate file read only.
Does anyone has a solution for this?
Ccmineralexis and x17 does not start all gpus and sometimes only one or two gpus run for a while. In the end it updates the hashrate as 34mh instead of 120mh. By calculating 34mh it does not switch x17 again. I solved this by making x17 hashrate file read only.
Does anyone has a solution for this?
I decided to test out Nicehash vs Ahashpool again with my rig
both cards 1080ti's watercooled on same settings
GPU 1 Nicehash, 24hr profit 0.00024200 btc on single 1080ti using nicehash miner
GPU 2 Ahashpoolplus 24hr profit 0.00033000 btc on single 1080ti using nemo miner
both cards 1080ti's watercooled on same settings
GPU 1 Nicehash, 24hr profit 0.00024200 btc on single 1080ti using nicehash miner
GPU 2 Ahashpoolplus 24hr profit 0.00033000 btc on single 1080ti using nemo miner
Jump to: