Hash Auger has a number of features to help manage hardware and reduce downtime. By running each GPU in its own miner process, Hash Auger minimizes the impact of any miner crashes or hardware failures. If one mining process fails, all the others continue mining unaffected. If a miner process crashes or becomes unresponsive, the software will restart it quickly. Per algorithm and GPU overclocking profiles can also help improve stability by allowing the user to adjust settings based on how each algorithm affects the hardware.

Multiple layers of monitoring detect and respond to different types of errors. Not only does the software monitor mining processes to ensure they are running, but also their output to verify that they are actually mining. GPU utilization is also monitored to detect situations where the mining process may be active, but not effectively using the hardware. Hash Auger also monitors pool connectivity and will stop mining on a pool if its servers are temporarily unavailable.

Despite these features, cryptomining is a hardware intensive process and occasional, more severe errors can occur. Hash Auger includes a number of features that help the software respond to these failures so that your mining rigs stay productive. Most of these settings can be found within the Advanced Config tab, but the behavior of some of them can also be adjusted per GPU using the individual Device panels.

Config Settings

Failsafe Benchmarks

Hash Auger automatically creates backup copies of your configuration and device files. However, there is the remote possibility that benchmark data will be erased or corrupted during a system crash. The Failsafe Benchmark feature can be used to have Hash Auger automatically re-benchmark a rig if all the previous benchmark data is unrecoverable. Mining will start automatically once the benchmarking process has completed.

Monitor GPUs

When enabled, Hash Auger will query current operating information such as power consumption, temperature and utilization from each GPU at a regular interval. The power consumption information can be used to switch algorithms based on profitability rather than simply revenue like most other algorithm-switching software does. Utilization is monitored during mining to ensure that GPUs are actually mining even if the mining process has not crashed and is still responsive. Finally, temperature monitoring can be used to adjust the fan speed of each GPU.

The Temperature tab on each GPU can be used to set fan speed percentages based on the GPU's current temperature. Hash Auger will use the Fan Speed % on a GPU's Hardware tab as the default fan speed when overclock settings are enabled. The additional fan speed settings on the Temperature tab are used only when the GPU's current temperature exceeds the limits that the user has defined. Temperature limits should be defined so that the first limit is lower than the second limit. Therefore, the order in which the software sets fan speeds is: default, temperature 1 and then temperature 2. Finally, Hash Auger can also automatically suspend mining on a GPU if the current temperature exceeds a certain limit - helping protect your hardware investment.

Monitor Internet Connection

This config option helps prevent false alarms due to disruptions in internet connectivity. Hash Auger will attempt to connect to two different public servers to verify that a mining rig is connected. If neither connection can be made, the software will suspend mining until connectivity is restored.

Monitor Hash Auger for App Crashes

Enabling this feature will cause the software to load a watchdog process that monitors the main Hash Auger process. If Hash Auger crashes or becomes unresponsive, the watchdog process will restart Hash Auger so that it can resume mining again.

Reboot on Monitoring Errors

This option instructs Hash Auger to automatically reboot a rig if several types of GPU failures are detected. For example, sometimes a GPU will become invisible to the device driver after a catastrophic software failure and only a restart of the system will allow it to be used for mining again. Hash Auger communicates with the device driver directly to identify these situations. If this option is enabled, the software will reboot the rig to restore the GPU to a productive state. Otherwise, the software will continue to mine on all available GPUs.
Similarly, Hash Auger can also be configured to automatically reboot a mining rig if too many errors are recorded for the same GPU. The device errors limit set on the Hardware tab of each GPU determines how many errors are permitted before the software stops attempting to mine with that GPU or restarts the system.

Since restarting the system is only useful if it is configured to automatically resume mining, the option is disabled if the Start Mining on Launch option is not enabled. Also, users should verify that they have the startup task for Hash Auger is working correctly before using this config setting.


Hash Auger can save logs of both its activity and the output of mining programs for troubleshooting purposes. All logs are saved in a subdirectory of the Hash Auger AppData directory called Logs. Miner console output is saved as one log file per GPU per day. The Debug Logging Mode can be used to write log data more frequently to disk for most mining programs.

Miner and Device Errors

To minimize downtime due to software or hardware issues, Hash Auger limits the number of errors that are allowed for each mining program and GPU. If too many errors occur within a short amount of time, the software will automatically stop using a mining program with a specific GPU. Hash Auger will attempt to use a different mining program for the same algorithm or switch algorithms if an alternative mining program is not available. Similarly, Hash Auger will stop using user-defined overclock settings if a mining program keeps crashing with those settings to keep the GPU productive. The number of errors that are allowed before the software stops using a mining program with a GPU is defined in the Miner Errors field of the GPU's Hardware tab.

On rare occasions that a GPU fails to mine even though other forms of monitoring (utilization and device driver detection) indicate it is still available, Hash Auger can reboot a rig or stop using that GPU if the number of errors exceeds the limit set in the Device Errors field. Since multiple errors can occur with a GPU using different miners, the permitted device errors should always be greater than the allowed miner errors.