Rapaz , se eu te falar que a minha 3080 bateu 97° , e o clock dela tava em 1500. O cooler dela não tava funcionando, nao sei o que deu, e não apitou nada. Reiniciei o pc e voltou ao normal, agora não passa mais de 70° jogando. Achei bem estranho
-
Prezados usuários,
Por questões de segurança, a partir de 22/04/2024 os usuários só conseguirão logar no fórum se estiverem com a "Verificação em duas etapas" habilitada em seu perfil.
Para habilitar a "Verificação em duas etapas" entre em sua conta e "Click" em seu nick name na parte superior da página, aparecerá opções de gestão de sua conta, entre em "Senha e segurança", a primeira opção será para habilitar a "Verificação em duas etapas".
Clicando alí vai pedir a sua senha de acesso ao fórum, e depois vai para as opções de verificação, que serão as seguintes:
***Código de verificação via aplicativo*** >>>Isso permite que você gere um código de verificação usando um aplicativo em seu telefone.
***Email de confirmação*** >>>Isso enviará um código por e-mail para verificar seu login.
***Códigos alternativos*** >>>Esses códigos podem ser usados para fazer login se você não tiver acesso a outros métodos de verificação.
Existe as 3 opções acima, e para continuar acessando o fórum a partir de 22/04/2024 você deverá habilitar uma das 03 opções.
Tópico para tirar dúvidas>>>>https://forum.adrenaline.com.br/threads/obrigatoriedade-da-verificacao-em-duas-etapas-a-partir-de-24-04-2024-duvidas.712290/
Atencionamente,
Administração do Fórum Adrenaline
[TÓPICO DEDICADO] MSI Afterburner - dúvidas, dicas e informações
- Iniciador de Tópicos forsakkenSoul
- Data de Início
Rapaz , se eu te falar que a minha 3080 bateu 97° , e o clock dela tava em 1500. O cooler dela não tava funcionando, nao sei o que deu, e não apitou nada. Reiniciei o pc e voltou ao normal, agora não passa mais de 70° jogando. Achei bem estranho
Deve ter sido algum tipo de bug ou no próprio Windows mesmo mas fica de olho porque 97* é perigoso.
Testei na minha RTX 2070 e não deu certo, mesmo marcando a opção as fans ficam rodando.Saiu a última beta do MSI Afterburner e agora adicionaram a opção "Override zero fan speed with hardware curve" que resolve o problema do 0 rpm não ativar ao setar uma curva personalizada pelo programa. Testei aqui e o 0 rpm agora tá funcionando sem problemas com a curva personalizada.
Quem quiser baixar:
MSI AB / RTSS development news thread
You don't need to close RTSS, reread my reply and remove the profile for this game you've created. It doesn't support any hooks and you're causing this...forums.guru3d.com
Ali independe da curva personalizada que você faz nas fans será?
Acho que se sua placa nã suporta 0 rpm mode não tem como mesmo. O problema que eu citei só acontecia nas placas da série 3000 onde a Nvidia setou um mínimo de 30% em todas as placas ao definir uma curva personalizada.
Se eu desativo o MSI Afterburner e deixo o controle da rotação pelo firmware as fans ficam em 0 RPM quando a GPU está em idle, então acredito que ela suporte 0 rpm mode.
mas porque ela fez isso?
Não sei quanto à série 2000 tudo que sei é que eu estava com esse problema na minha 3060 Ti e essa nova versão beta com essa opção resolveu isso.
Não faço a menor ideia, alguns dizem ser por medida de "precaução" pra que usuários evitem fritar as placas acidentalmente deixando as fans desligadas.
Aqui após trocar o Ryzen 3600x por um 5800x não aparece mais a opção para monitorar a temperatura do processador.
Já reinstalei o Afterburner, atualizei os drivers do chipset, mas anda resolveu.
Alguma ideia do que possa ser ?
Já reinstalei o Afterburner, atualizei os drivers do chipset, mas anda resolveu.
Alguma ideia do que possa ser ?
Instale o HWINFO64 e use ele para monitorar a temp do CPU no Afterburner.
Muitíssimo obrigado, resolvido !
Fica de olho pra isso não acontecer de novo. Essas memórias GDDR6X trabalham no limite da temperatura. Qualquer exagero elas podem sim fritar ou eventualmente apresentar problemas de curto.
Por isso que é sempre bom jogar com MSI AB ligado e ficar de olho na temperatura sempre.
--- Post duplo é unido automaticamente: ---
Qualquer coisa vá em Settings > Monitoramento > Sensores. Dai você habilita os sensores de CPU.
As placas da série 30xx vêm por padrão com um bloqueio de Zero RPM via software. Dessa forma, o desenvolvedor do afterburner fez essas duas funções com o propósito de "burlar" o bloqueio da nvidia.alguém saberia me dizer oque faz estas duas funções marcadas na foto? e em qual situações elas são efetivas?
Se você quiser utilizar uma curva custom com zero rpm, marque a caixa override zero fan. Além disso, coloque o primeiro pontinho abaixo da linha pontilhada conforme minha imagem de exemplo:
Nesse exemplo, quando a temperatura da GPU bater 65º a fan irá rodar em 50%. Abaixo de 65º a fan fica em modo zero rpm.
Joia irei testar isso neste momento, obrigadoAs placas da série 30xx vêm por padrão com um bloqueio de Zero RPM via software. Dessa forma, o desenvolvedor do afterburner fez essas duas funções com o propósito de "burlar" o bloqueio da nvidia.
Se você quiser utilizar uma curva custom com zero rpm, marque a caixa override zero fan. Além disso, coloque o primeiro pontinho abaixo da linha pontilhada conforme minha imagem de exemplo:
Nesse exemplo, quando a temperatura da GPU bater 65º a fan irá rodar em 50%. Abaixo de 65º a fan fica em modo zero rpm.
O estranho é que aqui , ligo o pc, e as fans estão paradas... stresso a placa, quando ela atinge 50 graus, ela aciona as ventoinhas, foi assim que programei... até ai, tudo certo...As placas da série 30xx vêm por padrão com um bloqueio de Zero RPM via software. Dessa forma, o desenvolvedor do afterburner fez essas duas funções com o propósito de "burlar" o bloqueio da nvidia.
Se você quiser utilizar uma curva custom com zero rpm, marque a caixa override zero fan. Além disso, coloque o primeiro pontinho abaixo da linha pontilhada conforme minha imagem de exemplo:
Nesse exemplo, quando a temperatura da GPU bater 65º a fan irá rodar em 50%. Abaixo de 65º a fan fica em modo zero rpm.
porem quando paro de estressar a vga, a temperatura cai dos 50º e as ventoinhas ainda ficam girando 41% e a placa cai rápido de 62º para 34º pq as fans não desligam
estou usando assim
-----------------------------
EDIT
>>>>>>>>>>>>>>>>Descobri que ao usar o nvidia broadcast, ele manter os clock altos mesmo em idle.. é isso faz que as fans fiquem acionadas mesmo estando abaixo da temp que programei, aqui esta para ficar zero rpm até chegar 50º e mesmo assim as fan ficam girando em 35º... enfim acho que ou teremos que esperar um editor de bios, para ativar stop fan ou lançarem uma att broadcast que solucione consumo alto do sistema.
Última edição:
MSI Afterburner 4.6.6 Download
MSI Afterburner 4.6.6 download - Guru3D and MSI have been working hard on AfterBurner, we released an updated Beta revision of Afterburner; this application successfully secured the leading position on graphics card utilities in relation to monitoring and tweaking. We are the only official...
www.guru3d.com
Para quem roda Windows e usa o HWINFO64 para monitorar o PC, a nova versão 7.0 virá com uma limitação bem chata:
Dear users,
Today, I'd like to share with you some important changes coming to HWiNFO (especially HWiNFO64) in the near future. For many years it was possible to maintain this project as an unconditional freeware model and cover the expenses and effort with some income from advertisements and voluntary donations. As some of you have maybe noticed, during the recent months and years HWiNFO has received many new features and frequent updates, not just to keep up with latest hardware and technologies and many of those features are truly unique. This was only possible by devoting a huge amount of time and effort to this project. The user base has grown significantly, which also resulted in a substantial increase in support and feature requests. Moreover, this also means an increase in additional direct/indirect expenses required to keep this project going and provide more comfortable experience.
Due to all these facts (and some others), running this project at the current pace became no longer possible with the full freeware model. So I needed to make some important decisions to secure the future of HWiNFO. The upcoming changes were carefully evaluated and defined so that the impact on personal users will be minimal.
PLEASE READ THIS ENTIRELY BEFORE POSTING QUESTIONS OR REACTIONS.
So what exactly is going to happen soon:
- Using HWiNFO64 for commercial purposes will require purchasing a commercial license. Personal use will remain free.
- Introduction of HWiNFO64 Pro - a licensed version of HWiNFO64 offering additional features and commercial use (with a proper license).
- HWiNFO64 Pro will additionally support: command-line interface for automatic reporting and sensor logging.
- Shared Memory Interface (SHM) in HWiNFO64 (non-Pro) will be run-time limited to 12 hours. HWiNFO64 Pro will not have such limit.
- To compensate for the SHM limitation, the interface details will be made fully public, so that anyone can interface with HWiNFO to read all sensor data. See below FAQ for more details.
- Default value of the "Shared Memory Support" configuration option will change from Enabled to Disabled. See below FAQ for more details.
- Remote Sensor Monitoring will be limited to 5 machines in HWiNFO64. HWiNFO64 Pro will have a higher limit.
Various license types for HWiNFO64 Pro will be available:
- Personal: Non-commercial use only. For private users requiring Pro features, or those who just want to contribute to the project.
- Engineer: Allows commercial use. User-based licensing.
- Corporate: Allows commercial use. Computer-based licensing.
Each license will include a 1-year maintenance period that will allow to upgrade to new versions released within this period at no additional cost.
Some Frequently Asked Questions that you might wanted to ask:
Q: When will this change happen?
A:The final date has not set yet, it is expected to happen in the next couple of weeks starting with version 7.0. On Mar-09-2021 HWiNFO version 7.00 was released.
Q: What will the licenses costs?
A:Exact pricing has not been finalized yet. Check the Licenses page for further details.
Q: What will happen to versions prior to 7.0, can we use them as we do now?
A: Nothing will change for versions prior to 7.0, they will remain full freeware.
Q: What will happen after expiry of the license maintenance period?
A: Versions issued before the license expiry date will continue to work as licensed copies. Versions released after that date will require a new (renewed) license. This will be available for licensed users with a discount.
Q: Will it be possible to use HWiNFO64 in commercial environment for evaluation?
A: Yes, a 14-day evaluation period will be allowed.
Q: I'm using HWiNFO64 for personal (non-commercial) purposes and don't need any of the Pro features. Will I need to purchase HWiNFO64 Pro?
A: No. You might consider upgrading to Pro in case you're using HWiNFO64 with some SHM-based addon or application and require uninterrupted monitoring via SHM for extended periods (>12 hours).
Q: I'm using HWiNFO64 for personal purposes and don't use the above mentioned limited features (or I'm OK with those limits). Will there be anything else forcing me to upgrade to Pro?
A: Nothing. No nag screens, no reminders. It's your choice whether you stay with HWiNFO64 or upgrade.
Q: I'm using HWiNFO64 for personal (non-commercial) purposes together with an application pulling data from HWiNFO64 via SHM. Will I need to purchase HWiNFO64 Pro?
A: You're not required to purchase HWiNFO64 Pro. If the SHM is used for limited time periods (i.e. to watch stats in game), or if you're OK with manually enabling it after 12 hours, you can stay with the non-Pro version.
Q: What plugins and extensions will be affected by the SHM limitation?
A: All that make use of the SHM interface to pull data from HWiNFO64: HWiNFOMonitor, Rainmeter plug-in, Prometheus Adapter, Aquacomputer Aquasuite, MSI Afterburner via the HWiNFO plugin, Elgato Streamdeck, TThrottle, etc. RTSS support built-in HWiNFO will not be affected.
Q: What were the reasons behind limiting the SHM also for personal users?
A: Current requirement for allowing other applications to use SHM is that the product must be an unconditional freeware while keeping the interface details closed. The main reason behind this is not to allow commercial products to make use of (and earn from) a freeware product. However this was difficult to meet for many projects - open-source projects to keep a part of code closed, or projects that were somehow related to commercial products or were earning even indirectly. Moreover, some subjects have attempted to circumvent the SHM restriction and use it for commercial purposes by utilizing illegal methods. So the new SHM model is uniform without implementation restrictions and allows full disclosure of the interface. I also believe that a 12-hour limit on SHM is sufficient for most personal users and will deter some of the commercial usage.
Q: How is the 12-hour limit to SHM enforced in HWiNFO64 and what will happen when it's exceeded?
A: The countdown starts once the sensors and SHM is started. After 12 hours a notification will be shown and SHM will be deactivated. It can be manually activated again, then a new 12-hours countdown will start.
Q: Why will the default value of the "Shared Memory Support" configuration option change from Enabled to Disabled?
A: This is to avoid disturbing users that don't use the SHM (a majority) with the automatic SHM deactivation notification.
Q: I want to create a commercial application that would read sensor data from HWiNFO via SHM. Will I be allowed to utilize the SHM?
A: Yes, according to new conditions you're allowed to do so. HWiNFO32/64 version 7.0 or later shall be used on the client side.
Q: What will happen to HWiNFO32 or HWiNFO for DOS, will there be any changes too?
A: No changes. Both will continue as freeware for both non-commercial and commercial use, SHM will not be limited in HWiNFO32. HWiNFO32 is designed to support legacy systems since Windows 95 and it's not recommended to be used on modern 64-bit systems due to many (yet still increasing) limitations of 32-bit applications.
Q: Do you plan to add more Pro features?
A: Yes, definitely. Some of those features will mean additional expenses on my side, so the Pro license justifies this.
Q: Will any of these changes impact the HWiNFO SDK?
A: No, the HWiNFO SDK is a separate and flexible product designed for commercial purposes. Many users have been requesting features similar to the SDK (i.e. automated report generation or sensor logging) for commercial purposes. HWiNFO64 Pro will addresses these requirements with commercial use in mind.
Q: Have you considered other ways of covering the effort and costs so that HWiNFO64 would remain free?
A: Yes, there are many ways. But most of them are aggressive and would be met with a strongly negative user experience and opinion (i.e. installer bundles). I have been accused a few times that HWiNFO must be doing some nasty tricks in the backyard when it's freeware (e.g. collecting and selling personal data)
This has never been the case and user privacy is of utmost importance here. HWiNFO collects only system/hardware-specific data and this remains with the user. Moreover it's easy to check that HWiNFO is not transmitting any data over internet.
Q: I don't like this change, it should be free!
A: We don't live in communism and have to pay our bills.
Thanks for your support!
Martin
Today, I'd like to share with you some important changes coming to HWiNFO (especially HWiNFO64) in the near future. For many years it was possible to maintain this project as an unconditional freeware model and cover the expenses and effort with some income from advertisements and voluntary donations. As some of you have maybe noticed, during the recent months and years HWiNFO has received many new features and frequent updates, not just to keep up with latest hardware and technologies and many of those features are truly unique. This was only possible by devoting a huge amount of time and effort to this project. The user base has grown significantly, which also resulted in a substantial increase in support and feature requests. Moreover, this also means an increase in additional direct/indirect expenses required to keep this project going and provide more comfortable experience.
Due to all these facts (and some others), running this project at the current pace became no longer possible with the full freeware model. So I needed to make some important decisions to secure the future of HWiNFO. The upcoming changes were carefully evaluated and defined so that the impact on personal users will be minimal.
PLEASE READ THIS ENTIRELY BEFORE POSTING QUESTIONS OR REACTIONS.
So what exactly is going to happen soon:
- Using HWiNFO64 for commercial purposes will require purchasing a commercial license. Personal use will remain free.
- Introduction of HWiNFO64 Pro - a licensed version of HWiNFO64 offering additional features and commercial use (with a proper license).
- HWiNFO64 Pro will additionally support: command-line interface for automatic reporting and sensor logging.
- Shared Memory Interface (SHM) in HWiNFO64 (non-Pro) will be run-time limited to 12 hours. HWiNFO64 Pro will not have such limit.
- To compensate for the SHM limitation, the interface details will be made fully public, so that anyone can interface with HWiNFO to read all sensor data. See below FAQ for more details.
- Default value of the "Shared Memory Support" configuration option will change from Enabled to Disabled. See below FAQ for more details.
- Remote Sensor Monitoring will be limited to 5 machines in HWiNFO64. HWiNFO64 Pro will have a higher limit.
Various license types for HWiNFO64 Pro will be available:
- Personal: Non-commercial use only. For private users requiring Pro features, or those who just want to contribute to the project.
- Engineer: Allows commercial use. User-based licensing.
- Corporate: Allows commercial use. Computer-based licensing.
Each license will include a 1-year maintenance period that will allow to upgrade to new versions released within this period at no additional cost.
Some Frequently Asked Questions that you might wanted to ask:
Q: When will this change happen?
A:
Q: What will the licenses costs?
A:
Q: What will happen to versions prior to 7.0, can we use them as we do now?
A: Nothing will change for versions prior to 7.0, they will remain full freeware.
Q: What will happen after expiry of the license maintenance period?
A: Versions issued before the license expiry date will continue to work as licensed copies. Versions released after that date will require a new (renewed) license. This will be available for licensed users with a discount.
Q: Will it be possible to use HWiNFO64 in commercial environment for evaluation?
A: Yes, a 14-day evaluation period will be allowed.
Q: I'm using HWiNFO64 for personal (non-commercial) purposes and don't need any of the Pro features. Will I need to purchase HWiNFO64 Pro?
A: No. You might consider upgrading to Pro in case you're using HWiNFO64 with some SHM-based addon or application and require uninterrupted monitoring via SHM for extended periods (>12 hours).
Q: I'm using HWiNFO64 for personal purposes and don't use the above mentioned limited features (or I'm OK with those limits). Will there be anything else forcing me to upgrade to Pro?
A: Nothing. No nag screens, no reminders. It's your choice whether you stay with HWiNFO64 or upgrade.
Q: I'm using HWiNFO64 for personal (non-commercial) purposes together with an application pulling data from HWiNFO64 via SHM. Will I need to purchase HWiNFO64 Pro?
A: You're not required to purchase HWiNFO64 Pro. If the SHM is used for limited time periods (i.e. to watch stats in game), or if you're OK with manually enabling it after 12 hours, you can stay with the non-Pro version.
Q: What plugins and extensions will be affected by the SHM limitation?
A: All that make use of the SHM interface to pull data from HWiNFO64: HWiNFOMonitor, Rainmeter plug-in, Prometheus Adapter, Aquacomputer Aquasuite, MSI Afterburner via the HWiNFO plugin, Elgato Streamdeck, TThrottle, etc. RTSS support built-in HWiNFO will not be affected.
Q: What were the reasons behind limiting the SHM also for personal users?
A: Current requirement for allowing other applications to use SHM is that the product must be an unconditional freeware while keeping the interface details closed. The main reason behind this is not to allow commercial products to make use of (and earn from) a freeware product. However this was difficult to meet for many projects - open-source projects to keep a part of code closed, or projects that were somehow related to commercial products or were earning even indirectly. Moreover, some subjects have attempted to circumvent the SHM restriction and use it for commercial purposes by utilizing illegal methods. So the new SHM model is uniform without implementation restrictions and allows full disclosure of the interface. I also believe that a 12-hour limit on SHM is sufficient for most personal users and will deter some of the commercial usage.
Q: How is the 12-hour limit to SHM enforced in HWiNFO64 and what will happen when it's exceeded?
A: The countdown starts once the sensors and SHM is started. After 12 hours a notification will be shown and SHM will be deactivated. It can be manually activated again, then a new 12-hours countdown will start.
Q: Why will the default value of the "Shared Memory Support" configuration option change from Enabled to Disabled?
A: This is to avoid disturbing users that don't use the SHM (a majority) with the automatic SHM deactivation notification.
Q: I want to create a commercial application that would read sensor data from HWiNFO via SHM. Will I be allowed to utilize the SHM?
A: Yes, according to new conditions you're allowed to do so. HWiNFO32/64 version 7.0 or later shall be used on the client side.
Q: What will happen to HWiNFO32 or HWiNFO for DOS, will there be any changes too?
A: No changes. Both will continue as freeware for both non-commercial and commercial use, SHM will not be limited in HWiNFO32. HWiNFO32 is designed to support legacy systems since Windows 95 and it's not recommended to be used on modern 64-bit systems due to many (yet still increasing) limitations of 32-bit applications.
Q: Do you plan to add more Pro features?
A: Yes, definitely. Some of those features will mean additional expenses on my side, so the Pro license justifies this.
Q: Will any of these changes impact the HWiNFO SDK?
A: No, the HWiNFO SDK is a separate and flexible product designed for commercial purposes. Many users have been requesting features similar to the SDK (i.e. automated report generation or sensor logging) for commercial purposes. HWiNFO64 Pro will addresses these requirements with commercial use in mind.
Q: Have you considered other ways of covering the effort and costs so that HWiNFO64 would remain free?
A: Yes, there are many ways. But most of them are aggressive and would be met with a strongly negative user experience and opinion (i.e. installer bundles). I have been accused a few times that HWiNFO must be doing some nasty tricks in the backyard when it's freeware (e.g. collecting and selling personal data)
This has never been the case and user privacy is of utmost importance here. HWiNFO collects only system/hardware-specific data and this remains with the user. Moreover it's easy to check that HWiNFO is not transmitting any data over internet.Q: I don't like this change, it should be free!
A: We don't live in communism and have to pay our bills.
Thanks for your support!
Martin
Alguém manja aí do que é preciso?? No MSI AB não achei essa opção, mesmo liberando monitoramento e controle na configuração.
Até instalei o HWINFO pra ver se pelo plugin daria pra monitorar e nada de aparecer. Tô ficando sem ideias, mas sei que dá. Já vi vídeos no tube de gente mostrando o consumo. To querendo fazer undervolting e quero conferir se está efeito.
Até instalei o HWINFO pra ver se pelo plugin daria pra monitorar e nada de aparecer. Tô ficando sem ideias, mas sei que dá. Já vi vídeos no tube de gente mostrando o consumo. To querendo fazer undervolting e quero conferir se está efeito.
Você quer monitorar enquanto joga ou de forma remota para alguma outra atividade?
pra quem se interessar.
Seria enquanto jogo. Mas já consegui! Valeu. Estava fazendo undervolting e queria ver se compensava. De fato, compensa. 70W a menos e mesmos frames. Uau!
Boa noite. Existe algum lugar que tenha perfis OSD já prontos? Pra eu não ter que configurar manualmente de um por um.
Na mesma página, um pouco acima, explica como.