Pages:
Author

Topic: Hash Auger 2.9.7.5 Mining Manager and Switcher for NVIDIA GPUs - page 28. (Read 8798 times)

newbie
Activity: 481
Merit: 0
Added the exclusions to defender. It still ran into the same issue. Even uninstalled it and reinstalled it again

Unfortunately, I still can't duplicate the issue here.  I'm setting up a fresh Windows 10 install to see if I reproduce your issue, but that will take a couple of hours. If you start Hash Auger, let it download the miners and then exit the application, can you check the contents of both the Xmrig-Nivida and Tpruvot directories within the Miners directory? Do both of those directories exist? Do they have executable files within them?
jr. member
Activity: 756
Merit: 2
thaks for   https://pool.miningmachine.io/   ,  yiimp full... THX
newbie
Activity: 82
Merit: 0
Added the exclusions to defender. It still ran into the same issue. Even uninstalled it and reinstalled it again
newbie
Activity: 481
Merit: 0
Yes,  I have. Still the same issue. Previous version was fine.

The only thing that changed with the miners is that I updated Tpruvot and added XmRig. The process for downloading/extracting miners hasn't been changed. Before releasing each new version, I manually install the software on all my rigs using the same executable that is uploaded to my website. On each machine, I try both an "upgrade" from an existing install and a new install.  Both cases worked fine when there is a Windows Defender exclusion for the Miners folder and the user has cleared any pending actions in Windows Defender. Unfortunately Windows Defender flags some of the miners as trojans and won't allow them to be extracted until the user manually selects "Allow on this machine" for each one. 

You're the first user to report any issues with installing this release. Take a look in the Miners subdirectory after the software has tried downloading them (there should be 11 folders named after each miner if you are CPU mining or 8 folders for the GPU). If all the folders are there, look inside each one to see if there are any executable files. Sometimes Windows Defender will block executable files from being extracted from archives while letting the rest of the files copy over.  Hash Auger checks for the presence of the required executable in each miner folder to see if the download/install was successful. If not, it shows the warning that you've been seeing.

Unfortunately, all these false alarms about mining software is a real pain for everyone involved; you cannot even download Claymore or Phoenix Miner in Edge anymore.
newbie
Activity: 82
Merit: 0
Yes,  I have. Still the same issue. Previous version was fine.
newbie
Activity: 481
Merit: 0
I tried to benchmark but the app told me that not all miners were d/l and if empty restart the app. I did that still the same message. Even reinstalled the app and same thing. Anyone else having issue with this app saying miner missing and then not start?

Have you made the miners folder an exclusion for Windows Defender? With each new anti-virus update, Microsoft is flagging more and more miners as threats.
newbie
Activity: 82
Merit: 0
I tried to benchmark but the app told me that not all miners were d/l and if empty restart the app. I did that still the same message. Even reinstalled the app and same thing. Anyone else having issue with this app saying miner missing and then not start?
newbie
Activity: 481
Merit: 0
I've included instructions on how to bypass the UAC dialog if you would like to setup Hash Auger to automatically start mining after system reboots: https://hashauger.com/faq.html
newbie
Activity: 82
Merit: 0
Thank you for the reply. Good know about cpu update.
newbie
Activity: 481
Merit: 0
The moment the miner starts the app just fully freezes and crashes with C11 on 1.5. I'll have to try 1.6 when I get home tonight, I am hopeful that will be better.

In another note for some reason with cpu mining auto switching picks the an option that isn't optimal(one that's closer 0 zero than $1). I've had to stop mining because of it. Manual isn't good either because after 1-2 hours it stops mining the more profitable coin.

I've been mining C11 on my development machine for nearly two hours on Zergpool and no problems so far. I also checked my other mining rigs and they have run C11 off and on the past day without any problems. Usually a full system freeze is caused when the mining software - in this case Klaust - corrupts the device driver. Version 1.5 already has the most recent version of the Klaust miner, which version of the Nvidia drivers are you using? All my machines are on 391.24 Also, if you have an overclock, you may need to dial it back for that algorithm or try a slightly lower intensity.  You may also want to try running C11 on one card at a time to see if the problem is with a specific GPU. If it is, you can just disable C11 for that particular card if you don't want to try setting a custom overclock or intensity setting for that card.

The CPU benchmarking issues that were fixed in 1.6 should allow the profit-switcher to work better with the CPU. There was an issue where the hash rate was being returned in the wrong format by the CPU mining software for certain algorithms; this made the software calculate the wrong estimated earnings for those coins.

The downside to manually selecting a coin is that you'll keep mining it regardless of its current price because the software makes no attempt to change it. That feature is mainly intended for people that want to mine a specific coin as part of a long-term investing strategy and are not concerned with its current value.
newbie
Activity: 82
Merit: 0
The moment the miner starts the app just fully freezes and crashes with C11 on 1.5. I'll have to try 1.6 when I get home tonight, I am hopeful that will be better.

In another note for some reason with cpu mining auto switching picks the an option that isn't optimal(one that's closer 0 zero than $1). I've had to stop mining because of it. Manual isn't good either because after 1-2 hours it stops mining the more profitable coin.
newbie
Activity: 481
Merit: 0
I just noticed on 1.5 that C11 on Zergpool crashes and that qubit(even after benching) still off. This on gpu for both. Will have to try 1.6 later.

Your issue with qubit should be fixed in 1.6. That was the first update that I released after you posted about the issue. As I mentioned previously, it was a display issue that only occurred when you manually selected the coin and not something that affected the algorithm switcher.

I've been running C11 on Zergpool with a both a 1070 ti (overclocked at +225 GPU, +400 Memory) and a 1080 running at stock speeds for at least 15 minutes now and haven't experienced a single crash.  If you look at the Miners tab, do you see any error messages from the Klaust miner itself?  Hash Auger will restart miners based on both hard crashes and if the miner has stopped communicating with the pool after a few minutes. According to their Twitter account, Zergpool recently upgraded their servers, which may be the cause of some of your issues. If you send me a copy of the miner output, I can investigate the issue further.
newbie
Activity: 481
Merit: 0
HA - are there plans to add in the ability for the user to select more than one version of cc-miner? For example, there are a few different x16r ones out there (e.g. enemyminer 1.03) that work. Some also algorithms see improvemnts with KlausT or Alexis, for example.   Having just 3 miner choices (tpruvot, dstm, and ethhash or whatever) seems a bit limiting.  Would it create more problems than it solves to allow for different miner software?

I went with Klaust's variant of CCMiner as it is still being actively maintained and it is a bit faster with some algorithms such as Skein and Neoscrypt. Also, I decided upon Nevermore miner instead of EnemyMiner because there is no longer an official repository for EnermyMiner. That  makes me wonder about that software's future and the integrity of some of the copies of EnemyMiner floating around.  The developer of Nevermore is pretty active when it comes to improving his product and that miner is a bit faster at mining RavenCoin than CCMiner 2.2.5.   I also added an Xevan miner even though it has not been updated in a while since some coins that use that algorithm are still profitable and the miner seems pretty stable despite its age. I'm hoping that the upcoming Monero fork will help make Cryptonight mining profitable again, which is why I added XMRig.

Stability issues are still my primary concern when it comes to evaluating which miners to add. For instance, I looked into HSRMiner for Neoscrypt, but a lot of users say that after a few hours it is no faster than Klaust and there are quite a few stability complaints. Similarly, I have held off on including the latest release of Ethminer because its release candidates have broken a lot of basic things at one time or another according to the Github issues list.  Of course, I'll continue to watch the development of all these miners and update Hash Auger accordingly.

There is still a bit of tweaking potential in the current versions of these miners to improve both their performance and stability. Obviously over-clocking is part of that, but the CCminer-variants also support adjustable intensity levels for each algorithm. The miner developer assigns a default intensity to each one based on their own testing.  Yet the default intensity level is not hardware-dependent; too high of an intensity level can cause stability issues and too low of a level can reduce performance. Version 1.6 of Hash Auger allows users to define custom intensity levels to help address both issues, but I am looking at ways to automate to process of selecting the best intensity level per device for a future release.
newbie
Activity: 82
Merit: 0
I just noticed on 1.5 that C11 on Zergpool crashes and that qubit(even after benching) still off. This on gpu for both. Will have to try 1.6 later.
newbie
Activity: 481
Merit: 0
Okay so numbers went down for me. Right now on ahashpool mining qubit it shows $2.30 when previously was $20+. I think that is correct, but not 100% sure. Don't have time right now to bench, but will do when I get back later tonight.

FYI, I released version 1.6 that fixes this issue. I also fixed a couple of issues related to CPU benchmarking.

Knowing your interest in new coins, I also wanted to mention that this version includes the latest release of Tpruvot miner - which adds support for the x12 algorithm used by a new coin called Galaxy Cash.  From what I've seen, only BSoD currently supports Galaxy Cash and you need to have a Galaxy Cash wallet in order to mine it there.
newbie
Activity: 481
Merit: 0
Okay so numbers went down for me. Right now on ahashpool mining qubit it shows $2.30 when previously was $20+. I think that is correct, but not 100% sure. Don't have time right now to bench, but will do when I get back later tonight.


Now that I know the algorithm, I was able to test it. I noticed a brief display issue with the mining stats - on my 1070ti, it showed $28 for the first 30 seconds or so, but then the estimated earnings quickly settled down to the real value of 3 cents. The Profitability grid shows the correct estimate for the coin and the algorithm switcher rightly ignores Qubit, so this is just a temporary display issue based on how the pool prices this coin.  You shouldn't need to re-benchmark your devices as your hash rates are inline with what my 1070ti is doing.  

Upon further inspection, it is a display issue that only happens when you are manually selecting coins instead of using the auto-switch feature. FYI, this glitch will also happen when you specifically select a few additional coins on AHashPool and some other pools that don't provide their prices in uniform formats. It's already fixed and that fix will be included the next release. Thanks for bringing it to my attention.
newbie
Activity: 82
Merit: 0
Okay so numbers went down for me. Right now on ahashpool mining qubit it shows $2.30 when previously was $20+. I think that is correct, but not 100% sure. Don't have time right now to bench, but will do when I get back later tonight.
newbie
Activity: 481
Merit: 0
Couple of different coins on Ahashpool are showing a profit of a little over $20 on my 1060 & $36(23mh) on my 1070 ti. I wish it was true, but I sadly doubt it.

I double-checked the pool on my rigs and the estimates appear normal. I also reviewed the pool's conversion information with what the software uses and it doesn't look like it has changed.  Take a look at the benchmarks for the algorithms that those coins use and see how they compare to your other devices. If they seem excessively high, you should manually enter lower numbers or benchmark those two cards again.
newbie
Activity: 82
Merit: 0
Couple of different coins on Ahashpool are showing a profit of a little over $20 on my 1060 & $36(23mh) on my 1070 ti. I wish it was true, but I sadly doubt it.
newbie
Activity: 82
Merit: 0
I have a semi-closed rig(back and front is closed, while sides have the doors open and top is off). I should have been a hair more clear, it seems like gpu are at a lower temp, cpu was never an issue as it was upgraded over the stock AMD fan to zalman model. The new XMRStack would be neat to have, and can't wait for the new cryptonight as it should help increase profits from CPU mining again.
Pages:
Jump to: