-
Posts
12405 -
Joined
-
Last visited
-
Days Won
550
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
MSI Gs75 Stealth overheating? Or thin laptop syndrome
Fiery replied to Austin Mickelson's topic in Hardware monitoring
Such high temperatures are not normal for desktop computers, but mobile computers -- especially thin & light laptops -- have too little space inside the chassis to put the thermal levels down. So for such mobile computers it's sadly normal to have over 80 Celsius operating temperatures. -
temp Request for Temperature Alerts for Battery dependant of Configuration
Fiery replied to Giorgio's topic in Android Forum
That's an interesting idea, thank you! We'll consider working on it next year. -
AIDA64 not updating battery charge rate on Xperia Z5 premium
Fiery replied to IA64's topic in Android Forum
That's due to a platform constraint. The standard Android Battery API itself doesn't update the values in a greater frequency. -
AFAIK it's not possible to access audio DAC's on Android devices from an app.
-
Mobile computers tend to work at higher thermal rates than desktop computers. A PCH temperature of 84 Celsius is not considered critical for a mobile computer.
-
It's explained on the following page: https://www.aida64.com/licensing
-
Awesome, we will fix that as well as another one about Corsair RGB LED keyboards in the next AIDA64beta Thank you for your help!
- 21 replies
-
- feature request
- rgb led
-
(and 3 more)
Tagged with:
-
Detecting sensor information... (Asus ROG Strix B450-F Gaming)
Fiery replied to lukebro's topic in Hardware monitoring
Yes. One of your AquaComputer devices may have a problem providing the necessary packets that AIDA64 requests for. Such issues could cause several seconds delays in the AIDA64 sensor code -
Thank you! We'll have to do some research to find out how the VR VCC Temperature (SVID) reading can be measured. Meanwhile, it would be great if you could download the EVGA E-LEET X utility (Version 1.0.6) from EVGA's website, create and send us a report using it. Such E-LEET reports include very useful information on the sensor layout of EVGA motherboards. Thank you in advance!
-
Thank you! We will add the missing motherboard VRM sensor readings as well as remove the unnecessary EC1 and EC2 temperatures in the next AIDA64 beta update. Meanwhile, it would be great if you could download the EVGA E-LEET X utility (Version 1.0.6) from EVGA's website, create and send us a report using it. Such E-LEET reports include very useful information on the sensor layout of EVGA motherboards. Thank you in advance!
-
There are certain Corsair hardware which can be used along with other monitoring software without issues.
-
Thank you for pointing out the bugs for us
- 21 replies
-
- feature request
- rgb led
-
(and 3 more)
Tagged with:
-
Here's the above mentioned new build: https://www.aida64.com/downloads/latesta64xebeta
- 21 replies
-
- feature request
- rgb led
-
(and 3 more)
Tagged with:
-
Thank you! Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. If it's possible, please submit an updated SMBus Dump (Full) dump as well, because we can see a chance to add more sensor readings for your motherboard.
-
GPU and Cores Temp error, X570 chipset thermal reading
Fiery replied to Zeusxinzo's topic in Bug reports
We're planning to roll out the next stable update in September. -
fixed: Incorrect sensor labels (MSI MPG X570 Gaming Plus)
Fiery replied to BillieJackFu's topic in Bug reports
Awesome, thank you for your feedback! -
Detecting sensor information... (Asus ROG Strix B450-F Gaming)
Fiery replied to lukebro's topic in Hardware monitoring
Do you have any Aqua Computer-made devices connected? Like Aquaduct, Aquaero, AquaStream, D5 Next, Farbwerk, Quadro? -
I've sent you a private message about this.
-
The folks at Corsair are telling you the truth. What they wouldn't tell you is that the ball is rolling in their court. In their previous software (called Corsair Link) they used to implement the necessary standardized synchronization mutexes that allowed their software to work with all major 3rd party monitoring software out there, like AIDA64, CPU-Z, HWiNFO, HWMonitor, SIV, etc. What happened is they discontinued using those mutexes and let the collisions happen, and continue to let them happen despite the fact that multiple developers (including us of course) have been pestering them for over a year now. I don't think it's wise to stick to their position of one and only one software to rule all Corsair hardware (ie. Corsair iCUE), but it's their position and they seem to want to stick to it no matter what. BTW, partial access to their hardware is not possible I'm afraid. BTW #2, it'd also be possible to allow only iCUE to access Corsair hardware, but expose the sensor readings coming from various Corsair hardware to 3rd party applications. It would require Corsair to develop a new SDK or expand their existing iCUE SDK. I'm not sure if they're working on this or whether they have any intentions to work on this.
-
fixed: Incorrect sensor labels (MSI MPG X570 Gaming Plus)
Fiery replied to BillieJackFu's topic in Bug reports
Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. -
GPU and Cores Temp error, X570 chipset thermal reading
Fiery replied to Zeusxinzo's topic in Bug reports
X570 temperature is shown as PCH Diode temperature in AIDA64. But you need to use the latest AIDA64 beta build to have that reading: https://www.aida64.com/downloads/latesta64xebeta -
We're still waiting for a resolution that would come from Corsair about synchronizing their software with 3rd party application like AIDA64.
-
No, since the components are connected together. In such situations it's best to update the BIOS, return to default settings (no overclock), and ease up on the memory timings if possible (like change Command Rate 1T to 2T).
-
No, we've found that info online.
