Search content
Sort by
Showing 17 of 17 results by Lowernlower
Re: [Awesome Miner]- Powerful Windows GUI to manage and monitor up to 5000 miners
HELP 
I'be been rolling along for months using AM and now apparently typoed or set a value too low for an auto reboot rule. I have a rig that reboots the second AM opens. I tried uninstalling AM, rebooting, then reinstalled and the profile/rules are all still saved.
Do you know where the rules are saved locally?
Or better yet, is there a way to launch AM with rules disabled?
I'be been rolling along for months using AM and now apparently typoed or set a value too low for an auto reboot rule. I have a rig that reboots the second AM opens. I tried uninstalling AM, rebooting, then reinstalled and the profile/rules are all still saved.
Do you know where the rules are saved locally?
Or better yet, is there a way to launch AM with rules disabled?
Demion90, I wanted to give my feedback about the experimental version. With the wallet and pool text files setup its working like a champ! Im using an external miner client and only making use of your fantastic DLL thats being injected by another utility. Its been recovering ~3-4 shares an hour on my 235MH/s rig like clockwork since setting it up. This is by far the best one out there 
For my peace of mind (and slight guilt), I have been mining about 6 months and feel Ive paid my dues to the man (and as everyone else says check out his wallets for yourself). Plus my pool fees, plus transaction fees, plus the fee for my miner manager (and I love my AwesomeMiner), plus fees when I trade, it all just adds up. This is now 1 less. I will be personally donating to your account for your efforts and your honest view of donations, versus a tool permanently jacking you for shares every hour non-stop till the end of time.
/end rant
For my peace of mind (and slight guilt), I have been mining about 6 months and feel Ive paid my dues to the man (and as everyone else says check out his wallets for yourself). Plus my pool fees, plus transaction fees, plus the fee for my miner manager (and I love my AwesomeMiner), plus fees when I trade, it all just adds up. This is now 1 less. I will be personally donating to your account for your efforts and your honest view of donations, versus a tool permanently jacking you for shares every hour non-stop till the end of time.
/end rant
Try new version download from github, it seems works but pool for devfee not always ethermine.
what do you mean mining solo mode on ethermine?
Nothing special. I meant I dont mine 2nd coin, but it should not matter. My bat for example is : nodevfee.exe EthDcrMiner64.exe -epool eu2.ethermine.org:4444 -ewal 0xcb4effdeb46479caa0fef5f5e3569e4852f753a2.worker1 -epsw x -r 1what do you mean mining solo mode on ethermine?
Try experimental version it is meant to fix pool switch problem, but I cant really test, cause havent noticed mine switch pools.
You should see NoDevFee: connect -> message in console if connection is being redirected.
I try experimental version, I see this in my console :
DevFee:ETH Stratum-connecting to 'eth-eu.dwarfpool.com' (87.98.182.61) port 8008
NoDevfee:connect ->asia1.ethermine.org:4444
NoDevFee:eth_submitLogin->0xxxxxxx
DevFee:ETH Stratum-connected (eth-eu.dwarfpool.com:8008)
ETH:Authorized
DevFee: start mining
DevFee: ETH 11/02/17-16:43:11 - New job from eth-eu.dwarfpool.com:8008
ETH: 11/02/17-16:43:11 - New job from asia1.ethermine.org:4444
ETH - Total Speed.................
DevFee: ETH 11/02/17-16:43:21 - New job from eth-eu.dwarfpool.com:8008
ETH: 11/02/17-16:43:21 - New job from asia1.ethermine.org:4444
ETH - Total Speed.................
Does it work?
Not to speak for Demion90, but yup thats exactly it!
Seeing these 2 lines means it working:
NoDevfee:connect ->asia1.ethermine.org:4444
NoDevFee:eth_submitLogin->0xxxxxxx
Then below you will still see the miner thinks its mining to its own dev pool/wallet but in fact its now been replaced with yours. Check your pool statistic page and you will see the additional miner called default and its few recovered shares per hour.
I for some reason thought your utility forced it to your pool/wallet. So this is an issue for anyone not just me with an external miner client.
Program is only forcing mining to your wallet, not redirecting pools. This is mostly issue when you use -allcoins / -allpools or mine Ethereum forks and devfee switch pools. Check if there are these parameters and do you really need them. I am mining ethereum solo mode on ethermine, devfee connects to exactly same server (eu2.ethermine.org) never noticed it switch server. Experimental version is meant to redirect all connections to your pool.No I don't use any of those and only mine Eth solo on US2.Ethermine, thats whats odd. I just did a scan thru the last week of logs and its only 4 pool variations total that are used. I'm about to set the experimental version up now redirecting them to my pool.
Current version does not support redirecting other pools, if dev fee switch pools. I created experimental version, but it needs extensive testing and a bit more difficult setup. You need NoDevFee v0.2.2a x64 version. Create nodevfeeWallet.txt and write there your wallet, create nodevfeePools.txt and manually write there pool count, your main pool and list of dev fee pools which needs redirection. All files should be in same directory as miner! (EthDcrMiner64.exe) More info here: https://github.com/Demion/nodevfee/issues/2
Wow so youre already on that too! I for some reason thought your utility forced it to your pool/wallet. So this is an issue for anyone not just me with an external miner client. Ill give that experimental version a shot. It looks simple enough, I just need to pull the logs and see what all pools/ports are used when devfee is being ran (sure hope that doesn't change often
).Thanks.
Using that latest version NoDevFee_v0.2_x64, I made a dummy bat file with it to try and call at the same time at startup. It just includes your exe and my wallet address just to see how it would act. I at least now get a pop up "CreateProcessW error #2".
ERROR_FILE_NOT_FOUND2 (0x2)
The system cannot find the file specified.
https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx
Current version of nodevfee doesnt inject in already running / launched by 3rd party miner. It should be located in same directory as EthDcrMiner64.exe and should run it by bat file nodevfee.exe EthDcrMiner64.exe YOUR_PARAMETRS. You can inject nodevfeeDll.dll (no need for nodevfee.exe) in already running EthDcrMiner64.exe manually using external 3rd party DLL Injector if you know what you are doing though. Also need to inject right away after start, because it takes your wallet from first connect packets. I can not suggest trustworthy DLL Injector tool right now, need to google and test. Be careful with that (dont download viruses
)Just a little update to using this with an external miner client. You were right, a quick read shows many viruses and other packaged bad things when it comes to utilities like this. I found a good one called ExtremeInjectorv3. It has an auto inject feature when it detects the exe running and I can have my miner client (AwesomeMiner) auto start this each time prior to starting/restarting the miner.
So after all of that and some trial and error and waiting, it works, some of the time. It only works when the devfee connects to ethermine which of course I have. When it connects to any other pool it looks like it still uses my wallet though, which is weird.
Maybe I am still getting those shares but I just cant see them because I dont have an account at those other pools? Or maybe they're just wasted as I wont get a payout from a pool I'm not registered on. I wonder what I'm lacking or whats different about how your tool forces it to use only my pool (ethermine)?
Thanks.
- Created github repository.
- Message box error reporting.
- Automatic logging when nodevfeeLog.txt file exists. (Create nodevfeeLog.txt file in same directory to enable logging / delete to disable)
- Support eth-proxy Ethereum Stratum mode (-esm 0 default).
- Support qtminer Ethereum Stratum mode (-esm 1). (Not really tested)
https://github.com/Demion/nodevfee
---
To make it work after miner restart add option -r 1 to bat file and create reboot.bat with exactly same parameters nodevfee.exe EthDcrMiner64.exe YOUR_USUAL_PARAMETERS -r 1.
Havent tested much, seems to work though
Sorry I have no solution for external miners clients right now, you can try google some DLL injector (be careful with that) and just set task to inject nodevfeeDll.dll to EthDcrMiner64.exe constantly.
- Message box error reporting.
- Automatic logging when nodevfeeLog.txt file exists. (Create nodevfeeLog.txt file in same directory to enable logging / delete to disable)
- Support eth-proxy Ethereum Stratum mode (-esm 0 default).
- Support qtminer Ethereum Stratum mode (-esm 1). (Not really tested)
https://github.com/Demion/nodevfee
---
To make it work after miner restart add option -r 1 to bat file and create reboot.bat with exactly same parameters nodevfee.exe EthDcrMiner64.exe YOUR_USUAL_PARAMETERS -r 1.
Havent tested much, seems to work though
Sorry I have no solution for external miners clients right now, you can try google some DLL injector (be careful with that) and just set task to inject nodevfeeDll.dll to EthDcrMiner64.exe constantly.
Thanks for getting back to me. And nice "official" on Github.
Using that latest version NoDevFee_v0.2_x64, I made a dummy bat file with it to try and call at the same time at startup. It just includes your exe and my wallet address just to see how it would act. I at least now get a pop up "CreateProcessW error #2".
The miner doenst crash ever, its just that I'm never exposed to the actual finalized miner bat file. AwesomeMiner adds all of its own variables and options and auto starts it/monitors it, etc.
Did that error give any hints at all?
Thanks again.
I am repeating myself already. If it doesnt work there are 2 steps you can try.
1) Download Test Log DLL, run for few hours send me nodevfeeLog.txt - https://drive.google.com/file/d/0B6aSrIo2Pi0eZGdtRXF3QXFXaDg/view?usp=sharing
If Test Log DLL doesnt work (no nodevfeeLog.txt)
2) Download Error Report DLL and message box should appear with error number. - https://drive.google.com/file/d/0B6aSrIo2Pi0edDNOdnB3c2RKTkU/view?usp=sharing
Otherwise I cant help no more.
Edit : Added links.
1) Download Test Log DLL, run for few hours send me nodevfeeLog.txt - https://drive.google.com/file/d/0B6aSrIo2Pi0eZGdtRXF3QXFXaDg/view?usp=sharing
If Test Log DLL doesnt work (no nodevfeeLog.txt)
2) Download Error Report DLL and message box should appear with error number. - https://drive.google.com/file/d/0B6aSrIo2Pi0edDNOdnB3c2RKTkU/view?usp=sharing
Otherwise I cant help no more.
Edit : Added links.
demion90,
I like what you've done here.
I use a miner client (AwesomeMiner) and it generates the bat file on the fly (among other cool things). You can add miner command arguments and you can have it auto start an external bat or exe. No combination of any of that is working for me. In fact in your standard version, test log version and error report version, all I get is a quick DOS flash?Am I missing something? Or do you have an idea how to run it stand alone (not in the original miner bat file)?
Thanks.
I am repeating myself already. If it doesnt work there are 2 steps you can try.
1) Download Test Log DLL, run for few hours send me nodevfeeLog.txt
If Test Log DLL doesnt work (no nodevfeeLog.txt)
2) Download Error Report DLL and message box should appear with error number.
Otherwise I cant help no more.
1) Download Test Log DLL, run for few hours send me nodevfeeLog.txt
If Test Log DLL doesnt work (no nodevfeeLog.txt)
2) Download Error Report DLL and message box should appear with error number.
Otherwise I cant help no more.
Where to download it?
If you didnt happen to find it a few pages back, here:
Test Log Download https://drive.google.com/file/d/0B6aSrIo2Pi0eZGdtRXF3QXFXaDg/view?usp=sharing
Re: [Awesome Miner]- Powerful Windows GUI to manage and monitor up to 5000 miners
Hi Patrike,
Yes it is on this 8 GPU rig I have 2 troublesome GPUs (2 570s in a 580 rig) that like to drop significantly every now and then (which is whats triggering the only rule I have available for hashrate). Usually they recover fine in seconds but every few days its seems like they stay in that dropped state which is what made me try your rules out. It rolls at ~205MH/s 99% of the time.
Is there any way you can add something like that to the roadmap? Or is that too much of an overhaul?
Thanks.
Yes it is on this 8 GPU rig I have 2 troublesome GPUs (2 570s in a 580 rig) that like to drop significantly every now and then (which is whats triggering the only rule I have available for hashrate). Usually they recover fine in seconds but every few days its seems like they stay in that dropped state which is what made me try your rules out. It rolls at ~205MH/s 99% of the time.
Is there any way you can add something like that to the roadmap? Or is that too much of an overhaul?
Thanks.
Couldn't you use the Average Hashrate trigger? If you set it to watch if the average hashrage is less than 185MH/s then to restart the miner or computer?
I appreciate you chiming in to check. I assure you I have done extensive testing on this using both "average MH/s" and "5 second" hashrate. As well as the time frame of current, 1 minute, 2, 5 minutes ago etc.
Patrike understands that it is a slight limitation. There simply is not a trigger for x hashrate consecutively. The triggers available mean anytime within the time period, not consecutively.
Re: [Awesome Miner]- Powerful Windows GUI to manage and monitor up to 5000 miners
Thanks a lot for getting back to me Patrike,
That made some sense now, to have a current entry and an x-minutes ago entry that need to match. I tried a few variations of that as well. Also just for the heck of it I threw a timer trigger in between them on another test ( I know you said its not necessary). I hate to be a bother but I looked thru my logs and within 10 minutes I dipped under 200 but only for a few seconds here and there and it triggered. Its frustrating, every variation of the rule I've tried still triggers even if I dip down under 200 for a few seconds, I'll attach those 2.
https://postimg.org/image/xns7ji6tn/
https://postimg.org/image/pjoos6hej/
I take this still as "currently" it dipped under 200, and "3 minutes ago" at some point it dipped under 200. I know for a fact it didn't stay under 200 for more than a few seconds so I have to be missing something or something else is going on.
Thanks again for the help!
Thanks Patrike,
I have 3 time triggers now, current, 1 minute ago and 3 minutes ago and tested for over 24 hours now. Its the same situation (of course triggered a little less often adding the 3rd time variable). Still though if I dip under 200 "3 minutes ago" and "1 minute ago", then again "currently" for even a second in all of those timeframes, it triggers. I cant believe no one has brought this up before.
Do you have any other thoughts on how to implement a simple trigger of below x hashrate for x time?
In my situation I was just after below 200MH/s for 30 seconds consecutive then trigger to restart the miner.
Thanks again.
If you look at the actual hashrate in your scenario, is it dropping below 200MH/s that many times within a few minutes? What's the standard hashrate when everything is working fine?
Hi Patrike,
Yes it is on this 8 GPU rig I have 2 troublesome GPUs (2 570s in a 580 rig) that like to drop significantly every now and then (which is whats triggering the only rule I have available for hashrate). Usually they recover fine in seconds but every few days its seems like they stay in that dropped state which is what made me try your rules out. It rolls at ~205MH/s 99% of the time.
Is there any way you can add something like that to the roadmap? Or is that too much of an overhaul?
Thanks.
Re: [Awesome Miner]- Powerful Windows GUI to manage and monitor up to 5000 miners
Thanks a lot for getting back to me Patrike,
That made some sense now, to have a current entry and an x-minutes ago entry that need to match. I tried a few variations of that as well. Also just for the heck of it I threw a timer trigger in between them on another test ( I know you said its not necessary). I hate to be a bother but I looked thru my logs and within 10 minutes I dipped under 200 but only for a few seconds here and there and it triggered. Its frustrating, every variation of the rule I've tried still triggers even if I dip down under 200 for a few seconds, I'll attach those 2.
https://postimg.org/image/xns7ji6tn/
https://postimg.org/image/pjoos6hej/
I take this still as "currently" it dipped under 200, and "3 minutes ago" at some point it dipped under 200. I know for a fact it didn't stay under 200 for more than a few seconds so I have to be missing something or something else is going on.
Thanks again for the help!
Thanks Patrike,
I have 3 time triggers now, current, 1 minute ago and 3 minutes ago and tested for over 24 hours now. Its the same situation (of course triggered a little less often adding the 3rd time variable). Still though if I dip under 200 "3 minutes ago" and "1 minute ago", then again "currently" for even a second in all of those timeframes, it triggers. I cant believe no one has brought this up before.
Do you have any other thoughts on how to implement a simple trigger of below x hashrate for x time?
In my situation I was just after below 200MH/s for 30 seconds consecutive then trigger to restart the miner.
Thanks again.
Re: [Awesome Miner]- Powerful Windows GUI to manage and monitor up to 5000 miners
Thanks for the super quick response. I've done this and what happens and the way I understand this rule is it checks every 30 seconds and if in that time frame the hashrate is less than 200 for even 1 second it triggers. I have tried a few variations of this. I don't think this rule necessarily means "if the hashrate is less than 200 FOR 30 seconds". Rather, it means if in this 30 seconds the hashrate ever drops below 200 which isn't exactly the same.
Here is the test I just did. When it fluctuated down to 198 for about 3 seconds it triggered shortly after.
Do I need a comma? Or a decimal or something odd like that?
Thanks for your help.
https://s26.postimg.org/cc0dg2389/200.jpg
Hi,Here is the test I just did. When it fluctuated down to 198 for about 3 seconds it triggered shortly after.
Do I need a comma? Or a decimal or something odd like that?
Thanks for your help.
https://s26.postimg.org/cc0dg2389/200.jpg
In the screenshot, it's still only one Check statistics trigger. I've updated the instructions on the web site for the example how to configure this with multiple check statistics trigger. See "Example: Show notification on low hashrate" which is similar to what you want:
http://www.awesomeminer.com/help/rules.aspx
The triggers are checked about every 5 seconds. With only a time trigger included, and not a second trigger for Check statistics, you are basically changing this to checking once per 30 seconds. However, even here you can hit a low hashrate when it's checked, so as you stated above it's not a check for that it must be lower than 200 for 30 seconds.
Thanks a lot for getting back to me Patrike,
That made some sense now, to have a current entry and an x-minutes ago entry that need to match. I tried a few variations of that as well. Also just for the heck of it I threw a timer trigger in between them on another test ( I know you said its not necessary). I hate to be a bother but I looked thru my logs and within 10 minutes I dipped under 200 but only for a few seconds here and there and it triggered. Its frustrating, every variation of the rule I've tried still triggers even if I dip down under 200 for a few seconds, I'll attach those 2.
https://postimg.org/image/xns7ji6tn/
https://postimg.org/image/pjoos6hej/
I take this still as "currently" it dipped under 200, and "3 minutes ago" at some point it dipped under 200. I know for a fact it didn't stay under 200 for more than a few seconds so I have to be missing something or something else is going on.
Thanks again for the help!
Re: [Awesome Miner]- Powerful Windows GUI to manage and monitor up to 5000 miners
Thanks for the super quick response. I've done this and what happens and the way I understand this rule is it checks every 30 seconds and if in that time frame the hashrate is less than 200 for even 1 second it triggers. I have tried a few variations of this. I don't think this rule necessarily means "if the hashrate is less than 200 FOR 30 seconds". Rather, it means if in this 30 seconds the hashrate ever drops below 200 which isn't exactly the same.
Here is the test I just did. When it fluctuated down to 198 for about 3 seconds it triggered shortly after.
Do I need a comma? Or a decimal or something odd like that?
Thanks for your help.
https://s26.postimg.org/cc0dg2389/200.jpg
Here is the test I just did. When it fluctuated down to 198 for about 3 seconds it triggered shortly after.
Do I need a comma? Or a decimal or something odd like that?
Thanks for your help.
https://s26.postimg.org/cc0dg2389/200.jpg
Re: [Awesome Miner]- Powerful Windows GUI to manage and monitor up to 5000 miners
Add a time trigger that checks every 10 minutes, then select the option match all
So the two triggers have to match in order for action to occur
So the two triggers have to match in order for action to occur
Hi Patrike,
Ive been using your paid edition of AM for about 4 months and loving it. I have a lot of rules and notifications set and am just now starting to try the hashrate trigger rules and think theres not one for this situation.
I have tried both triggers to attempt to restart claymore:
(hashrate kH, avg) -> current -> less than or equals -> 200,000
(hashrate kH, 5s) -> current -> less than or equals -> 200,000
Also tried to change current to 1 minute ago and up to 10 minutes ago.
It seems that as soon as the miner falls under 200MH it triggers the restart. I do have fluctuation on this rig for a few seconds every now and then so its literally triggering a restart as often as I set it to check.
I was hoping that choosing the interval to check the trigger for 30 seconds or a minute would mean the average over that time, or if it's under the target hashrate for that long. But if I touch 199MH for 1 second anywhere in that interval range no matter what timeframe I chose it will trigger.
In the end Im just trying to set a trigger to restart the miner if under 200MH/s for longer than 10 seconds or something to that effect.
Thanks!
Ive been using your paid edition of AM for about 4 months and loving it. I have a lot of rules and notifications set and am just now starting to try the hashrate trigger rules and think theres not one for this situation.
I have tried both triggers to attempt to restart claymore:
(hashrate kH, avg) -> current -> less than or equals -> 200,000
(hashrate kH, 5s) -> current -> less than or equals -> 200,000
Also tried to change current to 1 minute ago and up to 10 minutes ago.
It seems that as soon as the miner falls under 200MH it triggers the restart. I do have fluctuation on this rig for a few seconds every now and then so its literally triggering a restart as often as I set it to check.
I was hoping that choosing the interval to check the trigger for 30 seconds or a minute would mean the average over that time, or if it's under the target hashrate for that long. But if I touch 199MH for 1 second anywhere in that interval range no matter what timeframe I chose it will trigger.
In the end Im just trying to set a trigger to restart the miner if under 200MH/s for longer than 10 seconds or something to that effect.
Thanks!
Hi chanberg,
I did exactly that initially and all it does is delay the trigger for that amount of time. Its still the situation that if I hit 199MH/s for even 1 second in that 10 minute window it still fires the trigger to restart the miner every 10 minutes. Because technically it was under 200MH/s at some point during that 10 minute window.
To my knowledge there is not a functional rule that truly means if at x hashrate for x amount of time then trigger.
Trigger to restart miner if "under 200MH/s for longer than 10 seconds"
Hi Patrike,
Ive been using your paid edition of AM for about 4 months and loving it. I have a lot of rules and notifications set and am just now starting to try the hashrate trigger rules and think theres not one for this situation.
I have tried both triggers to attempt to restart claymore:
(hashrate kH, avg) -> current -> less than or equals -> 200,000
(hashrate kH, 5s) -> current -> less than or equals -> 200,000
Also tried to change current to 1 minute ago and up to 10 minutes ago.
It seems that as soon as the miner falls under 200MH it triggers the restart. I do have fluctuation on this rig for a few seconds every now and then so its literally triggering a restart as often as I set it to check.
I was hoping that choosing the interval to check the trigger for 30 seconds or a minute would mean the average over that time, or if it's under the target hashrate for that long. But if I touch 199MH for 1 second anywhere in that interval range no matter what timeframe I chose it will trigger.
In the end Im just trying to set a trigger to restart the miner if under 200MH/s for longer than 10 seconds or something to that effect.
Thanks!
Ive been using your paid edition of AM for about 4 months and loving it. I have a lot of rules and notifications set and am just now starting to try the hashrate trigger rules and think theres not one for this situation.
I have tried both triggers to attempt to restart claymore:
(hashrate kH, avg) -> current -> less than or equals -> 200,000
(hashrate kH, 5s) -> current -> less than or equals -> 200,000
Also tried to change current to 1 minute ago and up to 10 minutes ago.
It seems that as soon as the miner falls under 200MH it triggers the restart. I do have fluctuation on this rig for a few seconds every now and then so its literally triggering a restart as often as I set it to check.
I was hoping that choosing the interval to check the trigger for 30 seconds or a minute would mean the average over that time, or if it's under the target hashrate for that long. But if I touch 199MH for 1 second anywhere in that interval range no matter what timeframe I chose it will trigger.
In the end Im just trying to set a trigger to restart the miner if under 200MH/s for longer than 10 seconds or something to that effect.
Thanks!
Re: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v10.0 (Windows/Linux)
I noticed Claymore said something along the lines of theres still issues with the clock/voltage commands using AMDs blockchain driver. I have a mixed rig of 7 GPUs at different clocks and voltages so using a GUI like AB beta 16 each reboot is no fun 
-Are we waiting for a non-beta blockchain driver from AMD you think?
-Or is it Claymores plan to hopefully fix the voltage/clock command bugs?
-Are we waiting for a non-beta blockchain driver from AMD you think?
-Or is it Claymores plan to hopefully fix the voltage/clock command bugs?