Hash Auger requires elevated privileges in order to adjust GPU hardware settings; unfortunately, the UAC permission box can prevent the app from automatically mining after a reboot such as a power failure or system update. The following steps will walk you through how to create a Windows task that will automatically start Hash Auger on startup without requiring use of the UAC message box.
Unfortunately most of the third-party mining software used by Hash Auger and similar programs has also been misused by various malware that mine cryptocurrencies without the user's permission. Consequently, many anti-virus software programs associate the mining software's files with this malware even though they are separate programs written by different authors for different purposes.
Since Hash Auger requires the miner's files to be installed and available in order to mine cryptocurrencies on your behalf, you may need to configure your anti-virus software to exclude monitoring the HashAuger\Miners subfolder in order to use this software. Before doing so, you are encouraged to research this issue on your own and determine whether the mining software poses an actual threat to your system.
For Windows Defender, the process of creating an exclusion is as follows:
Most, but not all, of the third-party mining software allows Hash Auger to "read" its text-based output to determine the miner's current hash rate and results. Unfortunately, a few miners have been programmed in such a way that their text-output cannot be processed in real-time. For those few miners, the active miner panels will say Mining Stats Unavilable instead of showing the current hash rate and estimated earnings even though the miner is connected to a pool and doing work. This only affects how Hash Auger displays data and does not affect your earnings or mining output.
Some GPU monitoring utilities such as Afterburner and Nvidia Inspector do not refresh the selected card's current settings (power limit, core clock, memory clock, temp limit, etc) if changes were made to the GPU by a different application such as Hash Auger. Selecting a different card and then going back to the originally selected card should refresh the display. Also, if you start Afterburner after Hash Auger has applied overclock settings, Afterburner may apply its own startup settings to the card. For example, some recent versions of Afterburner will automatically load the most recent profile settings automatically on startup. Because of this, it is recommended that you start Afterburner before starting to mine with Hash Auger. Once Afterburner is running, it should only apply device settings if the user loads a different profile.
The Price Spike Limit tells Hash Auger to ignore coins with unrealistic earnings estimates. It helps miners avoid wasting their hash rate on orphan coins or coins that have prices based on bad data. Since different devices often have different earnings potentials, this feature is set on each device's Profitability tab.
In cases where a pool is on the wrong side of a coin fork and is mining a string of orphan coins, the pool's estimated earnings for that coin can be signficantly inflated beyond realistic amounts due to the fact that the pool's hash rate and difficulty changes drastically from the rest of the network. Unfortunately, in these situations it can take an hour or more for enough data to be generated by the pool to determine whether or not these prices are accurate. Often, it can take much longer for the pool to temporarily suspend mining of that coin. Miners typically do not receive any payouts for orphan coins because these coins are not accepted by exchanges and thus, have no value. Therefore, any time spent mining these coins is usually wasted, but since the prices rise in a sustained manner, the estimated earnings look legitimate and cause many miners to switch their mining work to these coins.
Additionally, there can be times when a pool introduces a new coin or changes the underlying data their prices are based on that can cause algorithm-switching software to miscalculate the estimated earnings. Other times, the price of a coin will temporarily spike due to sudden changes on the pool or to the coin's value.
Setting a realistic Price Spike Limit can help reduce wasted mining output due to all three of those situations. While the exact amount depends on each miner's risk/reward preferences, a Price Spike Limit of 1.5 - 2 times a device's average earnings should prevent the majority of spikes while still allowing the software to take advantage of short, but legtimate increases in a coin's value. Price Spike Limits closer to a device's daily earnings may prevent more spikes, but might also limit earnings if real prices experience a sustained rise.
Prior to version 1.8.9 of Hash Auger, there was a known incompatibility with remote viewing software on monitorless systems due to the programming framework used to develop the software. In short, the remote viewing software prevented the Hash Auger window from completely rendering. Version 1.8.9 of the software includes some changes that fix this issue on most systems. If this problem still occurs, the following registry change that disables hardware acceleration of certain types of applications can be used: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics\DisableHWAcceleration with a DWORD value of 1. Please note that this registry setting will affect all WPF applications on your system, not just Hash Auger.
Zergpool recently introduced a Mine Coin (MC) parameter that allows users to mine specific coins instead of using the pool's coin switching feature. Without the Mine Coin parameter, the pool directs a miner's hash rate to a variety of coins that use that algoritm. On the other hand, when using the MC parameter the miner's hash rate will always be directed towards a specific coin. Since each coin is priced separately than the one currently mined by the pool's auto-switch feature, it may be more profitable for users to mine specific coins on Zergpool. Hash Auger 1.8 now includes functionality to compare prices for both auto-switch and individual coins on Zergpool.
To mine specific coins on Zergpool, simply checkmark the Use Mine Coin Parameter? option on the pool's Pricing tab. The Include Auto Switch Ports? option on the same tab determines whether auto-switch coins will also be used. In this way, users can configure Zergpool to use auto-switch coins (only Include Auto Switch Ports? checked), specific coins (only Use Mine Coin Parameter checked) or both (both options checked). If the Use Mine Coin Parameter is de-selected, the Include Auto Switch Ports option is automatically selected so that at least some coin prices will always be calculated for the pool. Use the pool's Enabled? setting to disable the pool if you don't want to mine on it.
If an auto-switch coin has the best price estimate for a device, Hash Auger will mine on that algorithm's port using the pool's Current Wallet as the payout wallet. This corresponds to Option 1 on Zergpool homepage. Alternatively, if a specific coin has the best price estimate instead, Hash Auger will automatically use the MC parameter to mine only that coin. In this case, the payout wallet depends on the coin that will be mined along with which wallets have been assigned to Zergpool.
When mining specific coins on Zergpool, the software will check to see if a wallet for that coin has been assigned to the pool. It doesn't have to be the Current Wallet, just any wallet assigned to the pool in the pool's Wallets tab. If a wallet for that coin is currently assigned to Zergpool, the software will use that wallet and not the Current Wallet as the payout address. This is referred to as Option 2 on the Zergpool website. However, if a wallet for that coin has not been assigned to the pool, the software will use the pool's Current Wallet instead - which corresponds to Zergpool's Option 3.
To illustrate the difference between Option 2 and Option 3, consider the following example: a user configures Zergpool in Hash Auger to use a Bitcoin wallet as its Current Wallet while also assigning a Lux wallet to the pool. When the Use MC Parameter? is enabled, the software will use the Lux wallet when mining the Lux coin directly on Zergpool (option 2). Otherwise, Hash Auger will use the Bitcoin wallet when mining the Phi auto-switch coin, Folm or any other specific coin on Zergpool (Option 3).
One final consideration is that some coins on Zergpool are not auto-traded, which prevents them from being exchanged into a different coin (Options 1 and 3). Consequently, Hash Auger will automatically exclude any coins that cannot be exchanged unless a wallet for that coin has been assigned to Zergpool. For example, at the time of this writtng, ElliotCoin cannot be exchanged into another coin; Hash Auger filters out ElliotCoin from the Zergpool's coin list even if the Use MC Parameter? option is enabled unless an Elliotcoin wallet has been assigned to Zergpool.
The Use Mine Coin Parameter? and Include Auto Switch Ports? settings are used by both Hash Auger's algorithm-switching functionality as well as the coin drop-down lists. For example, if the Use Mine Coin Parameter setting is disabled, only Zergpool's auto-switch coins will be used by the algorithm-switcher and visible in the drop-down lists. Conversely, only individual coins will be listed for Zergpool if the Include Auto Switch Ports setting is off.
Some mining software such as Tpruvot, Klaust and Nevermore calculate two different hash rate averages. One average reflects the total hash rate while the other is based on only on the average hash rate of actual results. Considering that the total hash rate includes work that were done at a lower difficulty than what the pool is currently using, it is often significantly higher than the average based on accepted results. Hash Auger uses the result hash rate for more accurate price estimates even if the hash rates may be lower than the total hash rate.
These features can provide GPUs with faster access to the CPU to validate results and get new work - which may improve hash rate consistency for high-throughput cards. However, this performance gain comes at the cost of higher CPU utilization for each card that uses either of these settings. Furthermore, overall system responsiveness may slow if too many processes use an elevated priority on a CPU that does not have many processor cores. Therefore, use of this feature should be limited to the fastest cards in a system and should not be used when also mining with the CPU. On systems with more GPUs than processor cores, it is usually more efficient to limit use of this feature to a few cards so that the CPU is not fully utilized. For example, on an eight core processor, consider enabling this feature on no more than six cards. Not every miner supports this feature, only some versions of CCMiner.
Older mining software written for Cuda 8.0 and lower may have stability issues on fast GPUs such as Nvidia 1080tis. If you encounter system freezes or restarts while using these miners, try reducing the default intensity level of the algorithm causing problems or reduce any overclocks that you may be using with these algorithms. Alternatively, you can disable these miners and use a newer alternative.
By default, Hash Auger uses the current price estimates that each pool provides when it calculates earnings. However, some pool estimates are slower to respond to market volatility than those provided by other pools. When a pool's price estimates do not seem accurate, you may want to enable the Use Actual Prices Instead of Estimates option on the pool's Pricing tab. This setting uses the pool's recent earnings for each coin/algorithm instead of current estimates.
Most miner errors occur due to too aggressive overclocks for certain algorithms and graphics cards. Due to variations in manufacturing tolerances ("the silicon lottery") and other factors, the same overclock settings may not be stable on two cards of the same type and brand. Similarly, different algorithms require different computing resources, so their optimal overclock is often different on the same GPU. Hash Auger makes it easy to set custom overclocks per GPU and algorithm. If you encounter stability issues with some algorithms on one or more cards when using overclocks, it is recommended that you remove the current overclock settings for those algorithms on the affected cards. If that prevents the errors from occurring, then you can gradually increase the overclocks until you find the highest values that do not affect stability.
Additionally some of the mining software used by Hash Auger and similar applications were originally written for older versions of Nvidia device drivers and the Cuda SDK. As Nvidia has modified both the device drivers and SDK, those older mining programs may no longer be compatible with the latest versions. If you encounter repeated issues with older miners such as Alexis, CCMiner-Phi, Palginmod and Xevan, it is recommended that you disable them as they are no longer being maintained by their authors.
Most pools provide two different prices for their algorithms and coins. One is an estimate based on the current mining activity and the market value of the expected rewards. The second is an average of the pool's earnings for an algorithm during the past 24 hours. By default, Hash Auger uses the current estimate for each pool as this price better reflects market volatility and changes in mining patterns. However, the current estimates provided by a pool may sometimes be inaccurate due to various factors. Thus, some users prefer to use the more conservative actual prices instead.
Recently, Hash Auger introduced the ability to use mixed pricing for most pools. This option bases a pool's prices on a user adjustable mix of both estimated and actual prices. Doing so can help smooth out fluctuations common in most current estimates. With mixed pricing, users specify the percentage of the current estimates that be used in the calculation - the remainder of the amount will be based on the actual prices. For example, a mixed price that is based on 80% estimates will also include 20% of the actual prices. Users who prefer more conservative pricing will want to use a lower Estimate % while users looking to take advantage of frequent, but brief pricing opportunities will prefer the Estimate % to be closer to 100.
When using mixed pricing, the pricing for each algorithm or coin on a pool can be based on its own Est % to override the pool default. This is due to the fact that the accuracy of estimates tends to vary for different algorithms - even on the same pool. Some algorithms may have false price spikes and should be more heavily based on actual prices. Conversely, it may more beneficial to base the prices for other algorithms entirely on the current estimates.
Port volumes are based on the total hash rate mining on an algorithm port. Hash Auger calculates the proportion of the user's total hash rate to the port's current hash rate and can exclude ports when the current mining volume is too low or high. Too low of a volume can delay earnings as there is insufficent total hash power to quickly find new blocks. Conversely, too high of a total hash rate can also negatively affect earnings as it will increase the difficulty of finding new blocks while also lowering the user's share of new rewards.
When the auto volume settings are used, Hash Auger excludes any ports that have extremely low or high mining volumes based on conservative thresholds. Users can customize the threshold settings that are used in a few different ways. First, a custom threshold can be set for an entire pool. Custom thresholds can also be defined for individual algorithms; a threshold defined for an algorithm will override the pool's threshold whether the pool uses the Auto setting or a custom setting. Finally, users can disable the individual low/high volume filters altogether for specific algorithms using the respective checkboxes.
For the Low Volume setting, Hash Auger excludes a port if the user's share of the total hash rate is greater than the threshold. Conversely, the software will exclude a port if the user's share of the total hash rate is less than the High Volume threshold. For example, a user may set a Low Volume threshold of 25% to exclude ports where the user's share represents more than a quarter of the total hash rate. Similarly, a High Volume Threshold of .001% would exclude any ports where the user's share is less than a thousandth of a percent of the total hash rate. When defining custom thresholds, users should consider the total hash rate for a port as shown on the pool's website as well as the user's total benchmarked hash rate for each algorithm. It should be noted that total hash rates for a given algorithm port often change with prices and mining demand.
©2018 Congeries Software All Rights Reserved.