[Awesome Miner] - Powerful Windows GUI to manage and monitor up to 200000 miners

[patrike]

https://www.dropbox.com/s/rpnbqhv17lcytdu/Captura%20de%20pantalla%202019-05-08%20a%20las%2020.39.05.png?dl=0

Hello PAtrike I leave you a capture with URL format to not occupy space in the post.

It is a small problem with the native OC, I already realized a while ago but now they are asking me a lot in the telegram group and I decided to notify them.

As you will see in the capture in a rig of 6 RTX 2080, all buy at the same time in the same batch, same model, same bios. I mean 6 exactly the same cards.

How can it be that applying a native OC profile, some have the highest core, and others the lowest core ?, and even the voltages change but that does not worry me much, the voltage does not touch it.

But if it is very rare, that if I apply an OC, some cards remain in 1600 and others exceed 1750 of the clock, when all supposedly the same OC is applied to it. As a result it happens that many times the miner fails and restarts, it is not serious but annoying and the only way is to lower the OC of the whole rig, at the cost of losing power to have stability.

I did the test with Aftherburner and being all the same, they were all at the same core speed. That does not happen with the native OC, which seems to apply some cards if not others, and I do not understand.

The great advantage of the native OC is its ease, but I already made it clear that the work with fans does not work, and you will see the amount of complaints that you will have in summer, I only use Aftherburner for the control of fans.

Check the programming of the native Oc. Because I can understand that if I have a rig with several brands, that's what happens. But having the same model bought at the same time in the same batch, with the same bios, in the same machine. Because some rise more the core and others do not?

What I do not want is to use the MSI server again for the OC.

Given that everything else is the same in terms of mining algorithm and software, it would be interesting to see if there are any differences in the GPU clocking settings when Awesome Miner reads them from the nVidia driver.

Can you open the GPU clocking dialog in Awesome Miner and click the View GPU Details button to generate a full report of the GPU settings. Please do this once after you set the clocking with MSI Afterburner and once after you set the clocking with Native Overclocking. Any differences in these two reports?

[1714988143]

1714988143

[1714988143]

1714988143

[1714988143]

1714988143

[1714988143]

1714988143

[1714988143]

1714988143

[patrike]

I re-installed and started over, when I run diagnostics I see that automatic downloads are being located in root/.config/AwesomeMinerService
Is that correct?

Thanks for your questions. That's the top level folder where mining software should be downloaded.

To take Nanominer as an example, it should end up in a folder similar to:
/root/.config/AwesomeMinerService/nanominer-linux-1.2.4.tar_1/nanominer-linux-1.2.4/
Can you please verify if the nanominer executable can be found here?

Yes I can confirm that the files are in the correct location as well as any that I upload are in the local share as well. They just fail to execute, I imagine it is something I am doing wrong, I would love to use AM on linux, I have an enterprise license and have been on Windows for awhile but would like to test a conversion of my farms to linux, thanks for thehelp and great product as always

Thanks for the update. Can you please send me the Remote Agent log file and I will investigate.
Log folder is: ~/.local/share/AwesomeMinerService/

The folder is not there " Log folder is: ~/.local/share/AwesomeMinerService/ " , I apologize for stating that the uploaded miners were there I was confused and forgot I had re-installed the service. what should I do see as how the folder is not where it should be?
I installed per the instructions ( https://support.awesomeminer.com/support/solutions/articles/35000086210-remote-agent-for-linux ) using sudo for installing the service and also changing ( /home/user/awesomeminer-remoteagent/AwesomeMiner.RemoteAgent.Linux ) to reflect the pc's username.
I feel like I'm just missing something silly here.

UPDATE: just re-read prerequisites and noted that I did not have "screen" installed, bash already was , going to retry again from scratch

OK I got things working now. I have 2 questions:
I do not see a preview in the "console" tab. Will this be the case for any miner I am using, I really do enjoy that feature , just not sure if it work in linux, also there is no mining screen on the pc itself. Is there a way to "see" the mining process either way?

Also, not that I use configs to launch my miners very often, but I did find that when I edited the config.ini for nanominer, when I would launch it , AM would change it back to only mport and watchdog settings. I would like to know how to keep the config if possible for future knowledge.

Thank You

Thanks for the update and great that it's working.

Console tab is currently not giving a preview on Linux systems, but this is of course planned to be supported. Right now it's not possible to see the mining process unless you use the screen-command on the Linux computer.

The nanominer config file should also contain the pools. The file is currently being generated by Awesome Miner when you start the mining process. Making the file read-only to Awesome Miner is probably the only way to prevent it.

[patrike]

Version 6.3.7 (Development preview of 6.4)
 ASIC mining
  - External Miners representing Antminers can be configured to perform the reboot operation over the web interface instead of SSH
 GPU mining
  - Added additional algorithms based on Argon2d
  - Diagnostics improved by allowing configuration of how long the diagnostics should be running before Awesome Miner terminates the mining process. The setting is available via the Advanced button in the Diagnostics dialog.
 Features
  - The setting to override the algorithm for a coin provided by a coin statistics provider allows specification of specific coin algorithm to map from, in case the coin is based on multiple algorithms
 User interface
   - Indicate failed dynamic source updates with red color for the coins in the Coins tab
   - Control+C keyboard shortcut can be used to copy the current information of all selected miners in the Miners tab to the clipboard.
 Mining software
  - Claymore Ethereum Miner 14.0 beta
  - SrbMiner 1.8.8
  - Gminer 1.42
  - WildRig Miner 0.16
 Corrections
  - Correction to CryptoDredge parameter for the Argon2d-dyn algorithm
  - Correction to prevent Phoenix Miner failover to algorithms not considered the most profitable by the Managed Profit Switcher

To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates.

Direct download links if needed:
https://www.awesomeminer.com/download/setupdev/AwesomeMiner.msi
https://www.awesomeminer.com/download/setupdev/AwesomeMinerRemoteService.msi

[trucobit]

But, that core settings also depends on the algo you use. Most algos running in a variable clock range, only a handful algos running with a nearly stable core.

Check that first. Also set your Afterburner to 100ms polling (standard is 1000ms) and check the clock range now.

Thank you for your response but it is not a reason, it happens in all the gospels, it is happening to more people in my telegram, and it is always the same cards that go higher. It's a strange thing, it does not matter x16r, that phi2, that hex, does not matter, it happens in all algos.

It is not something that is now very important, it is not a catastrophic failure, nor is it something urgent. But I inform you in case there is some kind of undiscovered problem in the native OC, which I continue to use despite this mini problem.

TEngo colleagues in TElegram who have many rigs equal totalemente, and for a while have a problem that sometimes some miners are restarted, only the miner not the rig. And the common problem in all is the same, different speeds of cores. When my colleagues used MSI SERVER with Atherburner, that did not happen to them.

I only let you know, I still use it, but it's a strange thing.

[trucobit]

https://www.dropbox.com/s/rpnbqhv17lcytdu/Captura%20de%20pantalla%202019-05-08%20a%20las%2020.39.05.png?dl=0

Hello PAtrike I leave you a capture with URL format to not occupy space in the post.

It is a small problem with the native OC, I already realized a while ago but now they are asking me a lot in the telegram group and I decided to notify them.

As you will see in the capture in a rig of 6 RTX 2080, all buy at the same time in the same batch, same model, same bios. I mean 6 exactly the same cards.

How can it be that applying a native OC profile, some have the highest core, and others the lowest core ?, and even the voltages change but that does not worry me much, the voltage does not touch it.

But if it is very rare, that if I apply an OC, some cards remain in 1600 and others exceed 1750 of the clock, when all supposedly the same OC is applied to it. As a result it happens that many times the miner fails and restarts, it is not serious but annoying and the only way is to lower the OC of the whole rig, at the cost of losing power to have stability.

I did the test with Aftherburner and being all the same, they were all at the same core speed. That does not happen with the native OC, which seems to apply some cards if not others, and I do not understand.

The great advantage of the native OC is its ease, but I already made it clear that the work with fans does not work, and you will see the amount of complaints that you will have in summer, I only use Aftherburner for the control of fans.

Check the programming of the native Oc. Because I can understand that if I have a rig with several brands, that's what happens. But having the same model bought at the same time in the same batch, with the same bios, in the same machine. Because some rise more the core and others do not?

What I do not want is to use the MSI server again for the OC.

Given that everything else is the same in terms of mining algorithm and software, it would be interesting to see if there are any differences in the GPU clocking settings when Awesome Miner reads them from the nVidia driver.

Can you open the GPU clocking dialog in Awesome Miner and click the View GPU Details button to generate a full report of the GPU settings. Please do this once after you set the clocking with MSI Afterburner and once after you set the clocking with Native Overclocking. Any differences in these two reports?

I do the tests you want, but I can not understand it with the automatic translation. If you give me a capture of that option, I'll understand. But I do not get to understand it well, sorry

[terryborg]

hi patrike,

Please help to add the jp server selection (*.jp.mine.zpool.ca) for zpool on the next release.

thanks

[patrike]

https://www.dropbox.com/s/rpnbqhv17lcytdu/Captura%20de%20pantalla%202019-05-08%20a%20las%2020.39.05.png?dl=0

Hello PAtrike I leave you a capture with URL format to not occupy space in the post.

It is a small problem with the native OC, I already realized a while ago but now they are asking me a lot in the telegram group and I decided to notify them.

As you will see in the capture in a rig of 6 RTX 2080, all buy at the same time in the same batch, same model, same bios. I mean 6 exactly the same cards.

How can it be that applying a native OC profile, some have the highest core, and others the lowest core ?, and even the voltages change but that does not worry me much, the voltage does not touch it.

But if it is very rare, that if I apply an OC, some cards remain in 1600 and others exceed 1750 of the clock, when all supposedly the same OC is applied to it. As a result it happens that many times the miner fails and restarts, it is not serious but annoying and the only way is to lower the OC of the whole rig, at the cost of losing power to have stability.

I did the test with Aftherburner and being all the same, they were all at the same core speed. That does not happen with the native OC, which seems to apply some cards if not others, and I do not understand.

The great advantage of the native OC is its ease, but I already made it clear that the work with fans does not work, and you will see the amount of complaints that you will have in summer, I only use Aftherburner for the control of fans.

Check the programming of the native Oc. Because I can understand that if I have a rig with several brands, that's what happens. But having the same model bought at the same time in the same batch, with the same bios, in the same machine. Because some rise more the core and others do not?

What I do not want is to use the MSI server again for the OC.

Given that everything else is the same in terms of mining algorithm and software, it would be interesting to see if there are any differences in the GPU clocking settings when Awesome Miner reads them from the nVidia driver.

Can you open the GPU clocking dialog in Awesome Miner and click the View GPU Details button to generate a full report of the GPU settings. Please do this once after you set the clocking with MSI Afterburner and once after you set the clocking with Native Overclocking. Any differences in these two reports?

I do the tests you want, but I can not understand it with the automatic translation. If you give me a capture of that option, I'll understand. But I do not get to understand it well, sorry

I will first do a few more tests myself. I will get back to you if I need more information. Thanks for your questions about this.

[patrike]

hi patrike,

Please help to add the jp server selection (*.jp.mine.zpool.ca) for zpool on the next release.

thanks

Thanks for the suggestion - I will add it in the next release.

[Tigggger]

You can enable an exchange volume filter to make it less likely to run into these issues with a low volume exchange. Please go to the Options dialog, Statistics Provider section, where you can set the Minimum Exchange Volume to 0.01 BTC for example. When you apply this change the prices you see should be more realistic.

Thanks, I knew there would be an option somewhere, all sorted now 

[patrike]

https://www.dropbox.com/s/rpnbqhv17lcytdu/Captura%20de%20pantalla%202019-05-08%20a%20las%2020.39.05.png?dl=0

Hello PAtrike I leave you a capture with URL format to not occupy space in the post.

It is a small problem with the native OC, I already realized a while ago but now they are asking me a lot in the telegram group and I decided to notify them.

As you will see in the capture in a rig of 6 RTX 2080, all buy at the same time in the same batch, same model, same bios. I mean 6 exactly the same cards.

How can it be that applying a native OC profile, some have the highest core, and others the lowest core ?, and even the voltages change but that does not worry me much, the voltage does not touch it.

But if it is very rare, that if I apply an OC, some cards remain in 1600 and others exceed 1750 of the clock, when all supposedly the same OC is applied to it. As a result it happens that many times the miner fails and restarts, it is not serious but annoying and the only way is to lower the OC of the whole rig, at the cost of losing power to have stability.

I did the test with Aftherburner and being all the same, they were all at the same core speed. That does not happen with the native OC, which seems to apply some cards if not others, and I do not understand.

The great advantage of the native OC is its ease, but I already made it clear that the work with fans does not work, and you will see the amount of complaints that you will have in summer, I only use Aftherburner for the control of fans.

Check the programming of the native Oc. Because I can understand that if I have a rig with several brands, that's what happens. But having the same model bought at the same time in the same batch, with the same bios, in the same machine. Because some rise more the core and others do not?

What I do not want is to use the MSI server again for the OC.

Given that everything else is the same in terms of mining algorithm and software, it would be interesting to see if there are any differences in the GPU clocking settings when Awesome Miner reads them from the nVidia driver.

Can you open the GPU clocking dialog in Awesome Miner and click the View GPU Details button to generate a full report of the GPU settings. Please do this once after you set the clocking with MSI Afterburner and once after you set the clocking with Native Overclocking. Any differences in these two reports?

I do the tests you want, but I can not understand it with the automatic translation. If you give me a capture of that option, I'll understand. But I do not get to understand it well, sorry

I will first do a few more tests myself. I will get back to you if I need more information. Thanks for your questions about this.

I think I need some guidance from you or someone else with MSI Afterburner skills here related to how to lock the Core clock based on the behavior described above.

What Awesome Miner and most nVidia clocking tools do is to set the Core Clock Boost, which is a way to increase or decrease the Core Clock frequency relative a base line. It's an offset like -50MHz or +75MHz. The nVidia GPU boost feature will then use this as input when setting the Core Clock speed, and this speed can change any second based on many factors.

I've tested with nVidia P104 and nVidia 2080. No matter how I set the Core Clock setting in MSI Afterburner, it still behaves like when I'm clocking via Awesome Miner with a Core Clock speed that isn't constant during mining. If I use algorithms like Neoscrypt, I see Core clock variations all the time. If I use memory heavy algorithms like Ethereum or Phi2, the Core clock is however much more stable. Same behavior no matter if I change the Core Clock via Awesome Miner or via MSI Afterburner.

Did I miss something in MSI Afterburner to get another behavior? Are there any other clocking tools like nVidiaInspector that also would behave like MSI Afterburner or is MSI Afterburner the exception here?

[joseph32]

Thats what I also said before. There are just a few coins with a nearly stable core clock. But all other coins have a core clock range, no matter what clock you set.

Some Equihash variants are nearly stable, used them ago to find the highest possible overclocks. But now, even 150.5 has a small range.

Edit: @trucobit, which stable clock coin(s) do you mean?

[Cryptarded]

I re-installed and started over, when I run diagnostics I see that automatic downloads are being located in root/.config/AwesomeMinerService
Is that correct?

Thanks for your questions. That's the top level folder where mining software should be downloaded.

To take Nanominer as an example, it should end up in a folder similar to:
/root/.config/AwesomeMinerService/nanominer-linux-1.2.4.tar_1/nanominer-linux-1.2.4/
Can you please verify if the nanominer executable can be found here?

Yes I can confirm that the files are in the correct location as well as any that I upload are in the local share as well. They just fail to execute, I imagine it is something I am doing wrong, I would love to use AM on linux, I have an enterprise license and have been on Windows for awhile but would like to test a conversion of my farms to linux, thanks for thehelp and great product as always

Thanks for the update. Can you please send me the Remote Agent log file and I will investigate.
Log folder is: ~/.local/share/AwesomeMinerService/

The folder is not there " Log folder is: ~/.local/share/AwesomeMinerService/ " , I apologize for stating that the uploaded miners were there I was confused and forgot I had re-installed the service. what should I do see as how the folder is not where it should be?
I installed per the instructions ( https://support.awesomeminer.com/support/solutions/articles/35000086210-remote-agent-for-linux ) using sudo for installing the service and also changing ( /home/user/awesomeminer-remoteagent/AwesomeMiner.RemoteAgent.Linux ) to reflect the pc's username.
I feel like I'm just missing something silly here.

UPDATE: just re-read prerequisites and noted that I did not have "screen" installed, bash already was , going to retry again from scratch

OK I got things working now. I have 2 questions:
I do not see a preview in the "console" tab. Will this be the case for any miner I am using, I really do enjoy that feature , just not sure if it work in linux, also there is no mining screen on the pc itself. Is there a way to "see" the mining process either way?

Also, not that I use configs to launch my miners very often, but I did find that when I edited the config.ini for nanominer, when I would launch it , AM would change it back to only mport and watchdog settings. I would like to know how to keep the config if possible for future knowledge.

Thank You

Thanks for the update and great that it's working.

Console tab is currently not giving a preview on Linux systems, but this is of course planned to be supported. Right now it's not possible to see the mining process unless you use the screen-command on the Linux computer.

The nanominer config file should also contain the pools. The file is currently being generated by Awesome Miner when you start the mining process. Making the file read-only to Awesome Miner is probably the only way to prevent it.

Thanks for the info. I see the "screen" session listed when I screen -ls , but I am not able bring it up. I am new to using these commands.
Could you suggest how I could do this, to make it appear, thanks again.

UPDATE: I figured it out, had to run it as root , once I found the process in htop, I used sudo -i and then I could screen -r ...... thanks

[moppidoo]

Supposedly this is normal behavior with GPUBoost, not sure what settings you are running under afterburner to see clocks all the same @trucobit? The fan curves, OC settings, algorithms and miner programs you're running.

If you Google, many ppl will tell you that these acute thermal throttling happen at roughly 50 something degrees Celsius or higher from their experience. Factors at every moment that causes fluctuation from highest probably goes like this:

Temperature > load | voltage

To mitigate, easiest is to first run efficient cooling (or turn the fan up high, which generally kills the fan quicker especially with the low quality fans gigabyte uses)

Quality PSU, Risers, power cables that used with the risers

Remove power saving features in Windows.

Choose "prefer maximum performance" in global profile under nvidia control panel's 3D setting section. Sometimes you might have to use nvidia profile inspector to find and change hidden settings.

Use EVGA's KBoost to keep the cards running at max boost clock indefinitely (need some hack for non evga cards) at your own risk, normally not recommended.


Running random hash algos will always cause fluctuations, and mining software complicate it further since they assign loads differently on top of the shuffling algo orders.

[Chevy_Roadster]

Hi Patrike

There is a new Cuckoocycle pool at Nicehash, please can you add it in the built-in Online service in the next AM release.

No miner built-in in AM is compatible with Nicehash so far...

Thanks in advance

[jhartbarger]

Any chance we can get working API Support for Obelisk SC1 Slim's ?


this is what it looks like.
https://imgur.com/qUG7lwD

[trucobit]

https://www.dropbox.com/s/rpnbqhv17lcytdu/Captura%20de%20pantalla%202019-05-08%20a%20las%2020.39.05.png?dl=0

Hello PAtrike I leave you a capture with URL format to not occupy space in the post.

It is a small problem with the native OC, I already realized a while ago but now they are asking me a lot in the telegram group and I decided to notify them.

As you will see in the capture in a rig of 6 RTX 2080, all buy at the same time in the same batch, same model, same bios. I mean 6 exactly the same cards.

How can it be that applying a native OC profile, some have the highest core, and others the lowest core ?, and even the voltages change but that does not worry me much, the voltage does not touch it.

But if it is very rare, that if I apply an OC, some cards remain in 1600 and others exceed 1750 of the clock, when all supposedly the same OC is applied to it. As a result it happens that many times the miner fails and restarts, it is not serious but annoying and the only way is to lower the OC of the whole rig, at the cost of losing power to have stability.

I did the test with Aftherburner and being all the same, they were all at the same core speed. That does not happen with the native OC, which seems to apply some cards if not others, and I do not understand.

The great advantage of the native OC is its ease, but I already made it clear that the work with fans does not work, and you will see the amount of complaints that you will have in summer, I only use Aftherburner for the control of fans.

Check the programming of the native Oc. Because I can understand that if I have a rig with several brands, that's what happens. But having the same model bought at the same time in the same batch, with the same bios, in the same machine. Because some rise more the core and others do not?

What I do not want is to use the MSI server again for the OC.

Given that everything else is the same in terms of mining algorithm and software, it would be interesting to see if there are any differences in the GPU clocking settings when Awesome Miner reads them from the nVidia driver.

Can you open the GPU clocking dialog in Awesome Miner and click the View GPU Details button to generate a full report of the GPU settings. Please do this once after you set the clocking with MSI Afterburner and once after you set the clocking with Native Overclocking. Any differences in these two reports?

I do the tests you want, but I can not understand it with the automatic translation. If you give me a capture of that option, I'll understand. But I do not get to understand it well, sorry

I will first do a few more tests myself. I will get back to you if I need more information. Thanks for your questions about this.

I think I need some guidance from you or someone else with MSI Afterburner skills here related to how to lock the Core clock based on the behavior described above.

What Awesome Miner and most nVidia clocking tools do is to set the Core Clock Boost, which is a way to increase or decrease the Core Clock frequency relative a base line. It's an offset like -50MHz or +75MHz. The nVidia GPU boost feature will then use this as input when setting the Core Clock speed, and this speed can change any second based on many factors.

I've tested with nVidia P104 and nVidia 2080. No matter how I set the Core Clock setting in MSI Afterburner, it still behaves like when I'm clocking via Awesome Miner with a Core Clock speed that isn't constant during mining. If I use algorithms like Neoscrypt, I see Core clock variations all the time. If I use memory heavy algorithms like Ethereum or Phi2, the Core clock is however much more stable. Same behavior no matter if I change the Core Clock via Awesome Miner or via MSI Afterburner.

Did I miss something in MSI Afterburner to get another behavior? Are there any other clocking tools like nVidiaInspector that also would behave like MSI Afterburner or is MSI Afterburner the exception here?

I know that the core can vary a bit, that is normal, it is not exact all the time.

That's not the problem. The problem that using 6 equal cards, some always have the higher core than others. They all oscillate a bit inside your watch. But it is not the same to oscillate between 1600-1650 all the time, and that other similar cards are oscillating between 1720 and 1770. Always the same cards.

I mean, I know that the core can oscillate a bit, I see it in the cards, but some are placed in a higher core and oscillate there, and others are in a lower core oscillating there. When the OC is the same for all and they are exactly the same card purchased in the same lot.

If you look again at my capture that you leave, you will see that for example the memory frequency is exact on all the cards. But you will see cards in 1600 core and oscillate there, and others that do not fall below 1720 oscillating there.

I would understand that, if they were cards of different brands, because I myself have rigs with multi brand cards, and there I can not comment. I comment the case when all the cards are the same, and accepting their oscillation of Core, some for whatever reason, they are placed higher and others below, a difference of +100 in core I do not see it right. In Aftherburner I saw the oscillation too, but they were all in a range of core closest to each other.

In any case, I only report what happens to me and to other people in my telegram group. If it can be fixed well, if not, then we will continue like this, I will not remove the native OC because I like it a lot, except for the control of FAN, which is why I use Aftherburner.

If this can be improved then better. If this is so and you can not do anything, then I'm satisfied. I love native OC, I only intend to help with my observations and I can not always guess what I say.

Also thinking a bit, I do not know to what extent the chipset of the motherboard can influence in this sense, in its internal handling of the PCI.

Anyway, if you Patrike, after investigating it, believe that everything is fine, because it is already there, I accept it, it will be like that.

[patrike]

Hi Patrike

There is a new Cuckoocycle pool at Nicehash, please can you add it in the built-in Online service in the next AM release.

No miner built-in in AM is compatible with Nicehash so far...

Thanks in advance

Thanks for the suggestion. It looks like the latest NBMiner version claims it will support Nicehash CuckooCycle. I'm planning to have a new development release for this soon.

[patrike]

Any chance we can get working API Support for Obelisk SC1 Slim's ?


this is what it looks like.
https://imgur.com/qUG7lwD

The second generation of Obelisk SC1 miners doesn't provide any complete standard interface for monitoring. It doesn't include hashrate and a number of other important properties that you would expect from an ASIC miner. This is why it show up in Awesome Miner with just some information.

This worked fine with the first generation of these miners, but then they decided to no longer support this way of monitoring their miners.

[patrike]

https://www.dropbox.com/s/rpnbqhv17lcytdu/Captura%20de%20pantalla%202019-05-08%20a%20las%2020.39.05.png?dl=0

Hello PAtrike I leave you a capture with URL format to not occupy space in the post.

It is a small problem with the native OC, I already realized a while ago but now they are asking me a lot in the telegram group and I decided to notify them.

As you will see in the capture in a rig of 6 RTX 2080, all buy at the same time in the same batch, same model, same bios. I mean 6 exactly the same cards.

How can it be that applying a native OC profile, some have the highest core, and others the lowest core ?, and even the voltages change but that does not worry me much, the voltage does not touch it.

But if it is very rare, that if I apply an OC, some cards remain in 1600 and others exceed 1750 of the clock, when all supposedly the same OC is applied to it. As a result it happens that many times the miner fails and restarts, it is not serious but annoying and the only way is to lower the OC of the whole rig, at the cost of losing power to have stability.

I did the test with Aftherburner and being all the same, they were all at the same core speed. That does not happen with the native OC, which seems to apply some cards if not others, and I do not understand.

The great advantage of the native OC is its ease, but I already made it clear that the work with fans does not work, and you will see the amount of complaints that you will have in summer, I only use Aftherburner for the control of fans.

Check the programming of the native Oc. Because I can understand that if I have a rig with several brands, that's what happens. But having the same model bought at the same time in the same batch, with the same bios, in the same machine. Because some rise more the core and others do not?

What I do not want is to use the MSI server again for the OC.

Given that everything else is the same in terms of mining algorithm and software, it would be interesting to see if there are any differences in the GPU clocking settings when Awesome Miner reads them from the nVidia driver.

Can you open the GPU clocking dialog in Awesome Miner and click the View GPU Details button to generate a full report of the GPU settings. Please do this once after you set the clocking with MSI Afterburner and once after you set the clocking with Native Overclocking. Any differences in these two reports?

I do the tests you want, but I can not understand it with the automatic translation. If you give me a capture of that option, I'll understand. But I do not get to understand it well, sorry

I will first do a few more tests myself. I will get back to you if I need more information. Thanks for your questions about this.

I think I need some guidance from you or someone else with MSI Afterburner skills here related to how to lock the Core clock based on the behavior described above.

What Awesome Miner and most nVidia clocking tools do is to set the Core Clock Boost, which is a way to increase or decrease the Core Clock frequency relative a base line. It's an offset like -50MHz or +75MHz. The nVidia GPU boost feature will then use this as input when setting the Core Clock speed, and this speed can change any second based on many factors.

I've tested with nVidia P104 and nVidia 2080. No matter how I set the Core Clock setting in MSI Afterburner, it still behaves like when I'm clocking via Awesome Miner with a Core Clock speed that isn't constant during mining. If I use algorithms like Neoscrypt, I see Core clock variations all the time. If I use memory heavy algorithms like Ethereum or Phi2, the Core clock is however much more stable. Same behavior no matter if I change the Core Clock via Awesome Miner or via MSI Afterburner.

Did I miss something in MSI Afterburner to get another behavior? Are there any other clocking tools like nVidiaInspector that also would behave like MSI Afterburner or is MSI Afterburner the exception here?

I know that the core can vary a bit, that is normal, it is not exact all the time.

That's not the problem. The problem that using 6 equal cards, some always have the higher core than others. They all oscillate a bit inside your watch. But it is not the same to oscillate between 1600-1650 all the time, and that other similar cards are oscillating between 1720 and 1770. Always the same cards.

I mean, I know that the core can oscillate a bit, I see it in the cards, but some are placed in a higher core and oscillate there, and others are in a lower core oscillating there. When the OC is the same for all and they are exactly the same card purchased in the same lot.

If you look again at my capture that you leave, you will see that for example the memory frequency is exact on all the cards. But you will see cards in 1600 core and oscillate there, and others that do not fall below 1720 oscillating there.

I would understand that, if they were cards of different brands, because I myself have rigs with multi brand cards, and there I can not comment. I comment the case when all the cards are the same, and accepting their oscillation of Core, some for whatever reason, they are placed higher and others below, a difference of +100 in core I do not see it right. In Aftherburner I saw the oscillation too, but they were all in a range of core closest to each other.

In any case, I only report what happens to me and to other people in my telegram group. If it can be fixed well, if not, then we will continue like this, I will not remove the native OC because I like it a lot, except for the control of FAN, which is why I use Aftherburner.

If this can be improved then better. If this is so and you can not do anything, then I'm satisfied. I love native OC, I only intend to help with my observations and I can not always guess what I say.

Also thinking a bit, I do not know to what extent the chipset of the motherboard can influence in this sense, in its internal handling of the PCI.

Anyway, if you Patrike, after investigating it, believe that everything is fine, because it is already there, I accept it, it will be like that.

In general there can be variations on a chip level between GPU's even if it's the same model and brand. This goes for both GPU's and CPU's and is also the reason why some GPU's/CPU's can clock higher or get lower temperature than others - even if it's the exact same model. In overclocking competitions they hand pick their CPU's for a reason. For GPU's you can actually see the "ASIC Quality" value in the TechPowerUp GPU-Z tool, on the Advanced tab (although I don't know how accurate this number is).

Anyway, thanks for all feedback. Although there could be something Afterburner do different than Awesome Miner here, I don't think we will be able to find out what that would be. In general it also looks like the clocking set by Awesome Miner works fine.

Also thanks to @moppidoo and @joseph32 for all good information and feedback.

[patrike]

Version 6.3.8 (Development preview of 6.4)
 GPU mining
  - The mining software can be configured to run with Admininstrator privileges. Configurable in the Properties of the miner, Environment section.
 Features
  - When adding predefined pools, the feature to automatically setup a Managed Miner will prompt for host to run the mining (if multiple hosts are available) and also prompt for mining software to use (if multiple mining software supports the algorithm)
 User interface
  - The New Pool button in the main window includes the feature to add predefined pools
 Integration
  - Added Nicehash CuckooCycle pool. Currently only supported by NBMiner.
  - Added Zpool region for Japan
 Mining software
  - WildRig Miner 0.16.1
  - NBMiner 23.2
  - TT-miner 2.2.3

To get access to development versions, open the Options dialog in Awesome Miner. In the General section, enable Check for development versions. Then go to the Menu and click Check for updates.

Direct download links if needed:
https://www.awesomeminer.com/download/setupdev/AwesomeMiner.msi
https://www.awesomeminer.com/download/setupdev/AwesomeMinerRemoteService.msi