I'm running all my rigs as Managed Profit Miners. Most of my rigs contain identical GPUs, but I do have a few that are mixed, and I'm having a hard time getting different clock profiles to work consistently with them
I have my Profit Profiles and Groups already setup, and they are as follows:
Profit Profiles
GTX 1050Ti
GTX 1060 3GB
GTX 1070
GTX 1070Ti
GTX 1080
GTX 1080Ti
Profit Profile Groups (these are my mixed rigs other than one that is a mix of air and water 1080Tis discussed below)
1x 1050Ti 1x 1070Ti
2x 1070 x1 1080Ti
1x 1070 1x 1080
For Profit Profiles, I figured it would not be necessary to distinguish between Air and Water Cooled GPUs. Agreed?
For GPU Clocking Profiles on the other hand, I have created different profiles for Air vs. Water cooled GPUs since they require different settings. So I have the following:
GTX 1050Ti ETH
GTX 1050Ti Standard
GTX 1060 3GB ETH
GTX 1060 3GB Standard
GTX 1070 ETH
GTX 1070 Standard
GTX 1070 Hybrid ETH
GTX 1070 Hybrid Standard
GTX 1070Ti ETH
GTX 1070Ti Standard
GXT 1080 Hybrid ETH
GTX 1080 Hybrid Standard
GTX 1080Ti ETH
GTX 1080Ti Standard
GTX 1080Ti Hybrid ETH
GTX 1080Ti Hybrid Standard
So I have this one rig with a mix of 1080Ti's that are air cooled and one that is a hybrid. The GPUs are as follows according to AM:
GPU0 EVGA 1080Ti SC2
GPU1 EVGA 1080Ti SC2
GPU2 EVGA 1080Ti SC2
GPU3 EVGA 1080Ti FTW3 Hybrid
GPU4 EVGA 1080Ti SC2
GPU5 EVGA 1080Ti SC2
GPU6 EVGA 1080Ti SC2
I created a Clocking profile group with 6x 1080Ti Standard profiles and 1x 1080Ti Hybrid Standard. I arranged the GPUs in the profile to match what is shown in the table above by simply entering 0 - 6 for each GPU. But apparently I'm doing something wrong since all 7 GPUs share the same clock and power settings and after a short while the miner software is restarted by AM since the FTW3 hybrid keeps falling over because the clocks are too high given the much factory OC of the FTW3 card compared to the SC2's.
When I look at this mining rig in the GPU tab, I can clearly see that the clock on the FTW3 is about 80 MHz higher than the other 6 and it also uses about 40 more Watts. When I click GPU settings/settings via Awesome Miner and MSI Afterburner... I can confirm that all 7 GPUs share the exact same power and clock settings, which is why the FTW3 runs higher than the rest. When I click the Profile drop down, the Clocking Profile Group I created is not in the list to choose from. So how do I associate a Clocking profile group to a particular miner?
Do I have to create a Profit Profile specifically to this mining rig instead of using the regular
GXT 1080Ti Profit Profile that I use for all my 1080Ti Air cooled only rigs?
That appears to be the only way I can then select this "custom" 1080Ti Profit Profile, from within which I can then select the Clocking Profile Group I created for individual algos.
EDIT: So I went ahead and created a Profit Profile called
GTX 1080Ti Mix and within it, I selected my Clocking profile group with 6x 1080Ti and 1x 1080Ti hybrid. I then went to this miner and changed the miner properties to point to the new Profit profile I created. I restarted the miner, but it is still showing all 7 GPUs at 80% and +120 Core.
EDIT2: I changed to match on GPU Name instead of ID. Still didn't work. Here are some pic of my config:
https://ibb.co/jo0hYAhttps://ibb.co/mLh1RVhttps://ibb.co/iUQufqhttps://ibb.co/nJyrRVhttps://ibb.co/igBNYANote that in the last screenshot above, where I'm showing the "Settings via Awesome Miner and MSI Afterburner", all that is showing GPU 0:, GPU 1:, etc. The actual name you can see in the window behind, do not carry through to the Afterburner window. Could that be the issue? If so, how do I get the GPU names I assigned to show up there?
Thanks!
If you use the GPU name Awesome Miner must be able to get the names from MSI Afterburner, but in your case you only get "GPU 0" and so on without the name.
Can you please try to apply the updated fix for MSI Afterburner Remote Server, listed at the bottom of this page?
I know a few other users that were able to resolve the GPU name problem by applying the updated DLL-file.