Search content
Sort by
Showing 7 of 7 results by logitech69
Re: [CMD] FarmWatchBot Ewbf, Claymore, Bminer, Dstm, CC, Eth, CastXMR, Phoenix
This program has been a life-saver for me in many, many ways.
Today, I decided to update my Nvidia Drivers to the latest 430.86 and I also updated Claymore miner to v14.7.
Problem is, the FarmWatchBot doesn't load up from startup, I have to manually load it up, defeating the whole purpose.
I added a shortcut to my "shell:startup" folder in Win10, nothing.
I tried doing it through Task Scheduler, but no luck.
After hours of investigation, it literally came down to an option that you have to enable in Windows settings.
Click on the Windows Logo, search for "Startup Apps", Click to open the Startup Apps windows, and make sure the "ETHautorun" is ENABLED with a green icon.
I don't know if this is a new feature in the Windows May 2019 update or what, but it's necessary to do this to make it work.
Hope this helps.
Today, I decided to update my Nvidia Drivers to the latest 430.86 and I also updated Claymore miner to v14.7.
Problem is, the FarmWatchBot doesn't load up from startup, I have to manually load it up, defeating the whole purpose.
I added a shortcut to my "shell:startup" folder in Win10, nothing.
I tried doing it through Task Scheduler, but no luck.
After hours of investigation, it literally came down to an option that you have to enable in Windows settings.
Click on the Windows Logo, search for "Startup Apps", Click to open the Startup Apps windows, and make sure the "ETHautorun" is ENABLED with a green icon.
I don't know if this is a new feature in the Windows May 2019 update or what, but it's necessary to do this to make it work.
Hope this helps.
Re: [ANN]Bminer: a fast Equihash/Ethash/CuckooCycle miner for AMD/NVIDIA GPUs 13.0.0
Hi,
I'm using Bminer v13.0 and as soon as I launch the miner, it keeps throwing this error.
"undefined but requested solver: cuckaroo29"
Is there a quick fix? Thank you
http://i63.tinypic.com/14kxkba.jpg
I'm using Bminer v13.0 and as soon as I launch the miner, it keeps throwing this error.
"undefined but requested solver: cuckaroo29"
Is there a quick fix? Thank you
http://i63.tinypic.com/14kxkba.jpg
Re: [ANN]Bminer: a fast Equihash/Ethash/CuckooCycle miner for AMD/NVIDIA GPUs 12.1.0
Thank you for your hard work and dedication OP. Quick question:
Why does Bminer state 21sol/s for a stock GTX 1070? Seems a bit exaggerated....
I'm running a pretty heavy overclock (80 power limit, +120 core clock, +500 memory) and I max out at 18sol/s... (5%-8% rejected shares)
Win 10, maxed out virtual memory, connected to US sparkpool, using Bminer v12.2.0...
I've tried both Bminer and Gminer... both max out at 18sol/s per GTX 1070 with OC.
Please advise, thank you.
Why does Bminer state 21sol/s for a stock GTX 1070? Seems a bit exaggerated....
I'm running a pretty heavy overclock (80 power limit, +120 core clock, +500 memory) and I max out at 18sol/s... (5%-8% rejected shares)
Win 10, maxed out virtual memory, connected to US sparkpool, using Bminer v12.2.0...
I've tried both Bminer and Gminer... both max out at 18sol/s per GTX 1070 with OC.
Please advise, thank you.
Re: [ANN]Bminer: a fast Equihash/Ethash/CuckooCycle miner for AMD/NVIDIA GPUs 12.1.0
BTW if you are using bminer on windows, on grinmint pool DO NOT format your bat file as follows:
doing this will create a new dashboard for you on grinmint under the email sample@this.com.worker
you can search for this email in the dashboard search box. using a syntax like this will not show under sample@this.com with a worker named "worker"
You can probably omit the worker and password and it will just show under your email as "default" worker. I was trying but grinmint is down right now so I havent tested it. I tried email/worker and that didnt show under my dashboard either. I'm still trying to find the correct syntax for grinmint.
also on grinmint you dont need to include the password when mining and it is highly suggested you do NOT because bminer uses an unencrypted port
Code:
%SCHEME%://sample@this.com.worker@%POOL%
doing this will create a new dashboard for you on grinmint under the email sample@this.com.worker
you can search for this email in the dashboard search box. using a syntax like this will not show under sample@this.com with a worker named "worker"
You can probably omit the worker and password and it will just show under your email as "default" worker. I was trying but grinmint is down right now so I havent tested it. I tried email/worker and that didnt show under my dashboard either. I'm still trying to find the correct syntax for grinmint.
also on grinmint you dont need to include the password when mining and it is highly suggested you do NOT because bminer uses an unencrypted port
so no password is safer? please explain...
Re: GMiner CUDA Equihash 96,5/144,5/150,5(BEAM)/192,7/210,9 Miner v1.15
Confirmed to be working flawlessly mining BEAM 150,5 with GTX 1070 @ 12-13sol/s 
For reference, I was getting 8.5-9sol/s with the official BEAM miner v9.0
Overclock settings with MSI Afterburner for the GTX 1070:
Power Limit: 75
Temp Limit: 72
Core Clock: +75
Memory: +500
Fan: 70%
Proof: https://imgur.com/2XC2C91
Thank you for your work, keep it up!
For reference, I was getting 8.5-9sol/s with the official BEAM miner v9.0
Overclock settings with MSI Afterburner for the GTX 1070:
Power Limit: 75
Temp Limit: 72
Core Clock: +75
Memory: +500
Fan: 70%
Proof: https://imgur.com/2XC2C91
Thank you for your work, keep it up!
75% is too much power
asus 1070ti here power 50% core +240 memory +700
What is your sol/s with those overclock settings mining BEAM? I've noticed that if I push the 1070 past ~600-650 memory clock AND/OR core clock of 140+, it won't be stable and it'll constantly crash....
Re: GMiner CUDA Equihash 96,5/144,5/150,5(BEAM)/192,7/210,9 Miner v1.15
Confirmed to be working flawlessly mining BEAM 150,5 with GTX 1070 @ 12-13sol/s
For reference, I was getting 8.5-9sol/s with the official BEAM miner v9.0
Overclock settings with MSI Afterburner for the GTX 1070:
Power Limit: 75
Temp Limit: 72
Core Clock: +75
Memory: +500
Fan: 70%
Proof: https://imgur.com/2XC2C91
Thank you for your work, keep it up!
For reference, I was getting 8.5-9sol/s with the official BEAM miner v9.0
Overclock settings with MSI Afterburner for the GTX 1070:
Power Limit: 75
Temp Limit: 72
Core Clock: +75
Memory: +500
Fan: 70%
Proof: https://imgur.com/2XC2C91
Thank you for your work, keep it up!
Re: [CMD] Equihash Miner Autorun (Autorestart / Watchdog) for Ewbf & Claymore & Dstm
Hi Acrefawn,
Thanks for your excellent work here.
I am finding that I am experiencing a couple of issues with this using DSTM's miner 0.5.6 with Autorun ver 1.8.1.
Issue 1:
When the server changes difficulty on several GPU's at once, there is sometimes a significant, temporary hashrate drop which autorun incorrectly identifies as a real problem and restarts the miner.
Issue 2:
I regularly receive the "Loaded too many GPUs" report on only one of my rigs.
This is a 7 card rig but for some reason Autorun is detecting 14/7 cards despite the problem not actually existing in the miner.
I suspect that this is related to an erroneous log output from the miner as follows; note that the miner has reported two iterations of each card before outputting the "average" line (the last line of the extract below)
2017-12-07 9:39:51 AM| ========== Sol/s: 2898.4 Sol/W: 3.89 Avg: 2874.0 I/s: 1565.8 Sh: 39.13 1.00 357
2017-12-07 9:39:51 AM|# GPU4 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:53 AM|# GPU5 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:55 AM|# GPU6 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:58 AM| GPU0 63C Sol/s: 291.4 Sol/W: 3.94 Avg: 432.1 I/s: 158.8 Sh: 4.97 1.00 349
2017-12-07 9:39:59 AM| GPU1 67C Sol/s: 279.9 Sol/W: 3.80 Avg: 419.6 I/s: 149.5 Sh: 5.31 1.00 352 ++
2017-12-07 9:40:01 AM| GPU2 54C Sol/s: 295.4 Sol/W: 3.99 Avg: 424.5 I/s: 154.2 Sh: 3.82 1.00 344
2017-12-07 9:40:03 AM| GPU3 66C Sol/s: 284.6 Sol/W: 3.74 Avg: 421.5 I/s: 152.0 Sh: 6.15 1.00 375 +
2017-12-07 9:40:05 AM| GPU4 70C Sol/s: 298.7 Sol/W: 3.83 Avg: 435.5 I/s: 159.8 Sh: 6.31 1.00 416
2017-12-07 9:40:05 AM|> GPU0 62C Sol/s: 229.0 Sol/W: 2.06 Avg: 229.0 I/s: 121.5 Sh: 5.99 1.00 343 ++
2017-12-07 9:40:06 AM|> GPU1 67C Sol/s: 225.1 Sol/W: 2.02 Avg: 225.1 I/s: 120.1 Sh: 2.96 1.00 344 +
2017-12-07 9:40:08 AM|> GPU2 54C Sol/s: 219.8 Sol/W: 2.06 Avg: 219.8 I/s: 119.7 Sh: 5.99 1.00 352 ++
2017-12-07 9:40:09 AM| GPU5 71C Sol/s: 276.1 Sol/W: 3.73 Avg: 437.3 I/s: 148.8 Sh: 7.44 1.00 344 +
2017-12-07 9:40:10 AM|> GPU3 66C Sol/s: 222.7 Sol/W: 1.95 Avg: 222.7 I/s: 119.4 Sh: 5.81 1.00 351 ++
2017-12-07 9:40:11 AM| GPU6 49C Sol/s: 162.0 Sol/W: 3.69 Avg: 248.7 I/s: 84.8 Sh: 3.79 0.96 360 +
2017-12-07 9:40:11 AM| ========== Sol/s: 1888.2 Sol/W: 3.82 Avg: 2819.2 I/s: 1008.0 Sh: 37.79 1.00 362
As a side note;
Inputting the real "average" hashrate into the config.bat file tends to cause autorun to detect too many instances of low hashrate because any reported hashrate below the average appears to be considered an error.
I'd suggest this parameter would be better if named "minimum acceptable hashrate" or similar
or
Add a configurable tolerance to the acceptable range of hashrates. ie, within (say) 10% of the average is -not- considered to be a hashrate error.
Further, (just an idea) rather than the user nominating the average hashrate, perhaps autorun could automatically detect the actual average hashrate from all log files and store it in the config.bat file.
Happy to discuss this with you if the issue isn't clear from my description. Sorry that my input is not in the form of code change suggestions, it's beyond my capability.
That said, using this script has been educational and I'm thankful that you have released it open source.
Thanks again.
Thanks for your excellent work here.
I am finding that I am experiencing a couple of issues with this using DSTM's miner 0.5.6 with Autorun ver 1.8.1.
Issue 1:
When the server changes difficulty on several GPU's at once, there is sometimes a significant, temporary hashrate drop which autorun incorrectly identifies as a real problem and restarts the miner.
Issue 2:
I regularly receive the "Loaded too many GPUs" report on only one of my rigs.
This is a 7 card rig but for some reason Autorun is detecting 14/7 cards despite the problem not actually existing in the miner.
I suspect that this is related to an erroneous log output from the miner as follows; note that the miner has reported two iterations of each card before outputting the "average" line (the last line of the extract below)
2017-12-07 9:39:51 AM| ========== Sol/s: 2898.4 Sol/W: 3.89 Avg: 2874.0 I/s: 1565.8 Sh: 39.13 1.00 357
2017-12-07 9:39:51 AM|# GPU4 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:53 AM|# GPU5 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:55 AM|# GPU6 server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
2017-12-07 9:39:58 AM| GPU0 63C Sol/s: 291.4 Sol/W: 3.94 Avg: 432.1 I/s: 158.8 Sh: 4.97 1.00 349
2017-12-07 9:39:59 AM| GPU1 67C Sol/s: 279.9 Sol/W: 3.80 Avg: 419.6 I/s: 149.5 Sh: 5.31 1.00 352 ++
2017-12-07 9:40:01 AM| GPU2 54C Sol/s: 295.4 Sol/W: 3.99 Avg: 424.5 I/s: 154.2 Sh: 3.82 1.00 344
2017-12-07 9:40:03 AM| GPU3 66C Sol/s: 284.6 Sol/W: 3.74 Avg: 421.5 I/s: 152.0 Sh: 6.15 1.00 375 +
2017-12-07 9:40:05 AM| GPU4 70C Sol/s: 298.7 Sol/W: 3.83 Avg: 435.5 I/s: 159.8 Sh: 6.31 1.00 416
2017-12-07 9:40:05 AM|> GPU0 62C Sol/s: 229.0 Sol/W: 2.06 Avg: 229.0 I/s: 121.5 Sh: 5.99 1.00 343 ++
2017-12-07 9:40:06 AM|> GPU1 67C Sol/s: 225.1 Sol/W: 2.02 Avg: 225.1 I/s: 120.1 Sh: 2.96 1.00 344 +
2017-12-07 9:40:08 AM|> GPU2 54C Sol/s: 219.8 Sol/W: 2.06 Avg: 219.8 I/s: 119.7 Sh: 5.99 1.00 352 ++
2017-12-07 9:40:09 AM| GPU5 71C Sol/s: 276.1 Sol/W: 3.73 Avg: 437.3 I/s: 148.8 Sh: 7.44 1.00 344 +
2017-12-07 9:40:10 AM|> GPU3 66C Sol/s: 222.7 Sol/W: 1.95 Avg: 222.7 I/s: 119.4 Sh: 5.81 1.00 351 ++
2017-12-07 9:40:11 AM| GPU6 49C Sol/s: 162.0 Sol/W: 3.69 Avg: 248.7 I/s: 84.8 Sh: 3.79 0.96 360 +
2017-12-07 9:40:11 AM| ========== Sol/s: 1888.2 Sol/W: 3.82 Avg: 2819.2 I/s: 1008.0 Sh: 37.79 1.00 362
As a side note;
Inputting the real "average" hashrate into the config.bat file tends to cause autorun to detect too many instances of low hashrate because any reported hashrate below the average appears to be considered an error.
I'd suggest this parameter would be better if named "minimum acceptable hashrate" or similar
or
Add a configurable tolerance to the acceptable range of hashrates. ie, within (say) 10% of the average is -not- considered to be a hashrate error.
Further, (just an idea) rather than the user nominating the average hashrate, perhaps autorun could automatically detect the actual average hashrate from all log files and store it in the config.bat file.
Happy to discuss this with you if the issue isn't clear from my description. Sorry that my input is not in the form of code change suggestions, it's beyond my capability.
That said, using this script has been educational and I'm thankful that you have released it open source.
Thanks again.
Hi
Firstly, I would like to thank you for this wonderful script. You are awesome.
I've been testing it for the past few hours and I came across the same problem as posted above.
I am using MiningPoolHub and auto-switching coins within the Equihash algorithm using DSTM on Windows 10 and Nvidia 1070s.
When the difficulty changes or when DSTM is switching from one coin to another, my hashrate temporarily drops by 2000 sol/s for about 15 seconds but the script recognizes it as an error and begins to restart the miner. If I change the "average hashrate" to something very low, it won't make any sense because then there would be no point in monitoring it. Is there anyway I can add a delay or a temporary buffer for those 15 seconds while the difficulty is changing or when it's changing the coin being mined?
I appreciate all of your help and thank you for making this script. Once this gets resolved, I will donate and go for the premium
