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

How is PhiPhi pool? Is it popular as in crowded?

Announcing Hash Auger 2.3 with new benchmarking controls and pool price options.  The new Benchmark utility allows users to quickly benchmark specific miners and/or algorithms for any number of GPUs. A new pool price option averages recent estimates to help prevent switching work on short term spikes.  

The full list of improvements included in this release:

Hash Auger 2.3

• Added new Benchmark controls via the Benchmark Utility.  Select a list specific miners and and algorithms and benchmark them on all or just some GPUs with a custom duration.
• A new advanced configuration option can be used to have the software automatically benchmark new/upgraded miners.
• Added a new pool pricing option that averages recent price estimates. Users can adjust the time span used to calculate this moving average.
• Added the ability to pass custom parameters to mining executables.  These parameters should be verified first in a command shell as any typos or errors will often prevent the miner from launching.
• Added the ability to disable the revise benchmarks feature for specific algorithms.
• Added the ability to assign group numbers to GPUs for configuration tasks. GPU Manager will preselect all devices with the same group number to simplify making changes to all the devices in that group.
• Added a new Value field to coins on pools that do not auto-exchange so that users can have the software switch to a coin even a mBTC price is not available (coins not available on an exchange).
• Adjusting hash rates based on pool performance is now a user-adjustable config setting.
• Modified the Profitability grid so that all price and hash rate adjustments are reflected in the totals shown in these columns.
• Improvements to the saving and loading of config files to verify that the file contains valid benchmark values.
• Upgraded spmod-raven to version 6.
• Per user request, added PhiPhi pool to the pools that auto-exchange.
• Fixed a localization issue with Cost Per KW/H field.
• Fixed an issue with unconfirmed earnings not being shown for AHashPool.
• Fixed an issue where the earnings chart colors might not be consistent.
• Fixed an issue where coins without recent blocks were not always filtered out from some pools.

The first beta for Hash Auger 2.3 has been posted in the Discord channel. It includes new miner settings, the ability to set custom switch values for coins that are not currently on an exchange and more.

Any HA users mining the new Hex algorithm may want to upgrade to the latest release of Z-Enemy (1.15a).  Users who wish to do so can either download that version directly from Z-Enemy's distribution site  and overwrite the files in the Z-Enemy 1.15_2 miner directory or by grabbing the latest Hash Auger config files from the Discord channel and overwriting HA's static data files.  Z-Enemy 1.15a allows users to specify a higher intensity for the hex algorithm which can improve hash rates. It also corrects the issue with the pool-assigned difficulty so that users no longer have to specify a custom difficulty multiplier, so if you are currently using a custom diff % in HA please remove it after upgrading to Z-Enemy 1.15a.

Hash Auger 2.2.2.2 has been released to update Z-Enemy 1.15 to version 2.  It also fixes a parameter issue that prevented users from setting a custom diff multiplier for Z-Enemy. Setting a custom difficulty can substantially improve earnings with Hex.  The Z-Enemy devs recommend using a Diff Factor of 2 when mining the new hex algorithm. Since Hash Auger uses a percentage-based difficulty multiplier, enter 50 in the Diff % column for the Hex algorithm to achieve the same effect of halving the difficulty assigned by the pool.

To better link to change logs for specific versions, the list of changes for each release will now be appended to the original message.

Hash Auger 2.2.2.1

• Upgrades CryptoDredge to 8.3 (fixes Phi2 issue and tribus improvements).
• Upgrades Dumax to 9.4 (fixes Phi2 compatibility).
• Upgrades Z-Enemy to 1.15 (adds support for Hex and speed improvements for most other algorithms).
• Removes old coin specific Equihash144 algorithms on Zergpool now that the auto-switch port is running.
• Adds a new utility to enable P0 State on certain Nvidia GPUs and a GPU specific option to force p0 state when setting overclocks.
• Improvements to the handling of corrupted config files.
• Misc bug fixed and usability enhancements.

Users who would like to enable P-State 0 on their cards should use the new option in the Utilities tab on the Setup screen. After confirming that they want to enable that performance mode on their GPUs, they should see a second message that the Profile was loaded.  Unless the device drivers are modified or upgraded, it should not be necessary to re-enable P-State 0 on a rig, even after a reboot.  Before enabling, P-State 0, users are encouraged to do some research as to how it will affect their GPUs.  While it may improve mining performance for some algorithms, it will increase energy usage and heat and may also affect stability. 

A beta version of Hash Auger 2.2.2 is available in the Discord channel to add support for the latest version of CryptoDredge (8.2).  Earlier versions of CryptoDredge are not compatible with recent changes to Luxcoin and cannot be used to mine Phi2. Similarly, T-Rex miner is no longer compatible with Phi2 until its developers update it.  However, the versions of Z-Enemy and Tpruvot included in Hash AUger 2.2.1 are compatible with the recent Lux changes.

Based on user feedback, it appears that the Nvidia-SMI daemon that HA uses for GPU monitoring can cause stability issues when other GPU monitoring utilities such as AfterBurner or NvidiaInspector are also running in the background.  It is recommended that anyone wanting to use one of those programs not enable GPU Monitoring in HA until Nvidia fixes these issues with a future driver release. 

Thanks to all the beta testers on the Discord channel who provided feedback on the electricity usage monitoring features in HA 2.2.  When GPU Monitoring is enabled, HA will automatically capture energy usage information during mining and benchmarking. While Hash Auger automatically captures energy users during regular mining, existing users wanting to use the new profit-based switching method should re-benchmark their GPUs to capture the required energy data more quickly. If a Kilowatt/Hour cost is entered into the application config, Hash Auger can now switch algorithms based on their estimated profits instead of revenues.  The type of switching used for a device is set in each GPU's profitability settings.  Users can choose to enable profit based switching for all their GPUs or just the least efficient or any combination. In profit-switching mode, Hash Auger will use the most efficient miner for an algorithm on each GPU instead of the fastest, further reducing energy costs. Finally, users can also choose to enable profit-based switching for a certain time of each day to reduce energy costs during more expensive peak-energy hours and then have Hash Auger automatically switch back to revenue-based switching during the off-peak hours.

Anyone wanting to try beta and preview releases of Hash Auger is encouraged to join the conversation on the Discord channel at https://discord.gg/HUr8z8t.  For example, right now on the Discord channel users can download the latest config files to add support for T-Rex 5.7 and the Renesis algorithm. 

Per user request via the Discord channel, Hash Auger 2.1.2 also added some command line parameters: -automine, -noautomine and -noprockill.  The two automine parameters override the config settings and the -noprockill parameter tells the software not to close down any miners that may already be running on their own. The -noprockill parameter is intended for users who are tuning OC settings outside of HA and want to record the results in HA while those miners are still running in the background. Normally, HA closes any running miner processes to prevent more than one process from mining on a GPU.

Users wanting to see earnings for their internal Nicehash wallet along with their other Bitcoin earnings can now do so using a new wallet feature.  Select one wallet as the "master" wallet for a coin and earnings from one or more other wallets of that same coin can now be grouped into the same earnings tab as the coin's master wallet. While Nicehash wallets are the most common use of this feature, it will work for any coin. Existing users will need to restart HA after setting up their master and grouped wallets for the Earnings tab to be updated.

HA 2.1.2 also adds the ability to disable the software's GPU monitoring. Users may wish to do so if they prefer to use a different application to monitor their cards and rigs as the Nvidia-SMI program that HA uses to query the GPUs can cause stability issues with some monitoring applications on some systems.

Thank you to everyone on the Discord channel who helped beta test version 2.1 and provided a great amount of feedback and suggestions for this latest release.  The new temperature management features, GPU utilization monitoring and enhanced handling of miner errors are all exciting additions to software. While removing CPU mining capabilities was not a decision I took lightly, it was one I made to keep Hash Auger focused on providing a great user experience for its core user base.  HA users wanting to CPU mine can still use version 2.0.3 of the software with the CPU and start a separate instance of 2.1 or later for GPU mining.

The HashAuger software itself does not control payouts because it is not a mining pool or service like NiceHash. It provides your wallet address to the pools you choose to use and those pools control the payouts.  Each pool has its own minimum payment amount which is listed on each pool’s website. For example, Blazepool will automatically send a payout at a certain time of the day once your wallet balance on the pool is .003 or higher. Other pools have lower payment limits and may send payments several days per week.

How to find out how payment occurs from Hash Auger to my BTC address.
What output limit.
The site has nowhere found such information.

Sorry to hear that you are having those issues.  Unfortunately, I do not have access to 1050 GPUs, so I have not been able to test that all the miners that are enabled by default work with that type of GPU.  However, I know of some users who have used HA with those cards and have not had the same amount of issues that you are reporting. If you notice that a specific miner does not work on your GPUs, you can disable it using the drop-down list on the Benchmark's tab.

HA uses each GPU's current settings if you do not set any overclock settings in the software. If you are using NvidiaInspector to set those settings for each card, HA will leave those settings alone and not try to change them since you do not have any OC settings in HA.  Like you mentioned, those settings may not be the best for every algorithm.  My suggestion would be to enable the Write HA Log File to Disk and Write Miner Output to Disk settings so you can see what miners and algorithms were being used before a crash.  Then you can change the OC settings for those algorithms to prevent crashes and miner errors.

You may also want to try using a lower OC mem and core setting as the default and then set higher values for those algorithms you know are stable to reduce the amount of time that you spend troubleshooting. HA will use the OC settings set on each GPU's Hardware tab as the default for each algorithm that does not have its own settings.  If you set custom settings for an algorithm, HA will use those settings instead when HA starts mining with algorithm.

For example, if enter your +100 core, +250 mem and 75% power limit on the GPU's hardware tab, HA will use those settings for every algorithm except for the ones that have their own settings.  If you enter +50 core, +0 mem and 80% power limit for x16r, it will use those settings anytime it mines x16r.  With those settings, if the software starts mining Lyra2v2, the core OC would be +100, then when it switches to x16r, the core OC would be +50 and then when it switches to Equihash the core would be +100 again. 

Hi.
Trying your software, mostly because you added trex fast in my smallest rig of 6 1050ti 4gb

I am not OC the GPUs

I didn't select any specific intensity or setting for he various miner.

Rig either crash and everything restart or miners got errors.

I was unable to understand what the basic setting are for the miners when nothing is selected.

The only stable but not so much configuration happen if I use nvdia inspector to oc +100 +250mem the card PL 75 %.

But still, once a day it reset the rig.

Suggestion ? I have to setup each individual miner with the intensity and the OC I suppose its working ?
Hashhauger will automaticly change setting when algos are changed ?

The HTTP Server stop error is a message that the T-rex miner shows each time it is closing, when switching work for example.  Since Hash Auger does not use the http server for T-Rex, that warning can be ignored.  That warning does not affect your mining or the stability of the software.

On my rigs the full message text is:  
"20180724 14:16:58 WARN: HTTP Server stop error: close: Either the application has not called WSAStartup, or WSAStartup failed 20180724 14:16:58 WARN: HTTP Server stop error: close: Either the application has not called WSAStartup, or WSAStartup failed."

He paбoтaeт пpилoжeниe.
Hecкoлькo минyт paбoтaeт, пoтoм выдaeт oшибкy...
20180724 14:16:12 tribus block 1051822, diff 2550.315
20180724 14:16:49 tribus block 371406, diff 115.665
20180724 14:16:50 [ OK ] 35/35 - 120.75 MH/s
20180724 14:16:50 GPU #2: 121.29 MH/s
20180724 14:16:57 tribus block 1051823, diff 1289.485
20180724 14:16:58 WARN: HTTP Server stop error: close: ��� ���������� �� ������� WSAStartup, ��� ��������� ������ � WSAStartup20180724 14:16:58 WARN: HTTP Server stop error: close: ��� ���������� �� ������� WSAStartup, ��� ��������� ������ � WSAStartup

Okay. According to the Blockmaster website for option 2:  "Required: Use -p c=,mc= To set your payout coin, as well as your mining coin. Failure to set payout coin may result in your payments being sent through the wrong coin. "

For either Blockmasters or Zergpool, you can go to the Pricing tab of either Pool's settings and check the Use MC Parameter option and then save the pool settings. This wlll cause HA to mine specific coins for that pool using the mc= parameter.  Then, you can use the GPU Coin drop-down list to mine just Ravecoin on either Blockmasters or Zergpool and still receive BTC payouts. Currently, those are the only two pools that support that option.