Fiery
-
Posts
11546 -
Joined
-
Last visited
-
Days Won
489
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
Have you tried to add some items to your LCD layout in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / LCD Items? The blue box that informs you about the preview resolution will only disappear when you have at least one item on your LCD layout.
-
Whats the time interval used to calculate CPU utilization?
Fiery replied to Ruuwa's topic in Hardware monitoring
You're right, the minimum update rate of the CPU utilization measurement in the log files is 1 second. Do you want us to improve that rate to make the measurements more accurate on your system? -
Please verify if you used the same account to buy the IAP (the "Remove Ads" in-app product) than what you've used to install AIDA64 from the Play Store. We've already seen issues about using multiple Google accounts. Also, make sure to install all updates from the Play Store, and reboot your device. In some cases that alone helps to get Google Play Services to sync its caches with the information stored on Google's own servers. Please note that we don't manage IAP or any kind of purchases. Everything is handled and managed by Google Play Services, and so when such a mixup happens, it's not because there's a bug in our app, but due to a mixup in Google Play Services. We would love to help you in such cases, but we have basically zero insight into how IAP is handled by Google, and we have the same zero control over managing the purchases :-(
-
Only the Arc Gauge supports that, but that is only available with the RemoteSensor and Logitech Arx modules.
-
I see, but we still do not want to go down that path. Users complain already about not properly 1-second update rate for time on the SensorPanel and LCD, imagine how upset they would be if the animation wasn't fluid and/or wasn't consistent (ie. irregular pace in updates).
-
It can only be supported if the digital photo frame can accept bitmap image (bitmap frame) transfers via its USB connection. AFAIK only Samsung SPF displays and AX206 hacked picture frames support that.
-
We've checked, and unfortunately we haven't found any classic ways of obtaining those values from the video card iCX must use a custom communication protocol, but we have no idea how it works and how to handle it.
-
Not really. The AXi firmware seems quite bad quality anyway (for example: the USB protocol is quite unreliable, so a lot of workarounds have to be implemented in a 3rd party software just to read the raw sensor values out of the PSU), so I'm sure Corsair did their best to get around all the issues. The remaining issues are not major ones, so I'm pretty sure they wouldn't want to deal with them.
-
Whats the time interval used to calculate CPU utilization?
Fiery replied to Ruuwa's topic in Hardware monitoring
When you configure a 1 sec update rate, then the actual CPU utilization value will reflect the average CPU utilization over a 1 second period. -
We've done test runs and research about those values, but they didn't look good. The input power simply was inaccurate. And the output power and efficiency are calculated values, using such formulas that vary over different PSU SKUs. It's simply not scientific enough for us to deal with
-
I don't think 500 millisec would be an issue, but 100 millisec may cause stuttering or frame drops while gaming. Try it, and you will see whether you can notice any difference (you will probably not )
-
Yes, but the update rate doesn't include the sensors polling time that can take anything between 50 to 500 milliseconds, in rare cases even more. But still, even if we're talking exactly 100 milliseconds update rate or 10 FPS, it's way inferior to what is considered "fluid" these days...
-
1) Yes, the whole circle represents the 24 hours of a day, so on 6:00am it will show 25% "progress", and at 4:00pm it will show 66% "progress". 2) I don't think we'd want to go down that path.
-
There's no high temperature in that log. There was also no high CPU workload during that logging session. The maximum CPU utilization was below 30%. If you leave your computer idle, and wouldn't put any considerable load on the CPU, you won't be able to find out what causes overheating.
-
I appreciate your kind words. We'll keep pushing the development of AIDA64 in order to deliver more quality releases in the future too. As for socket temp... well... I'm not quite sure how to label these things We generally recommend watching all CPU related temperatures, and use the highest one as your reference. With Ryzen "X" (XFR-capable) processors cooling is crucial, so it's worth experimenting with various system loads, and watch and log all the temperatures during a certain workload to find out whether the current cooling solution can and should be improved.
-
When you have 1 second update rate configured, the actual update rate will be somewhat higher. It's because AIDA64 waits 1 second between updates, but one update may take 50 to 500 milliseconds, depending on how many slow interface hardware (sensors mostly) you've got in your system. So the actual update rate will be between 1050 and 1500 milliseconds. If you want to get to exactly 1 second update rate, you need to experiment lowering the update rate from 1000 milliseconds to 900, 800, 700, etc, until you reach the exactly 1 second update rate. As for gaming, I think it may be caused by the Game Mode feature of Win10 Creators Update. It may allocate far less CPU cycles to background tasks -- like AIDA64 sensors polling -- than before. You can overcome that issue by turning Game Mode off, and/or by increasing the priority level of the AIDA64 main process (AIDA64.EXE) using Task Manager. The latter is not very convenient, but it's worth checking out. BTW, we've checked your support ticket, but it only included an AIDA64 report snippet, without actual comment or problem description. We can't really do anything about such tickets But we can definitely investigate this issue here, on the forums, I'm here to help you out.
-
AIDA64 uses 90%+ cpu on one core 100% of the time (Xeon E5-2620 v3)
Fiery replied to m411b's topic in General Discussion
Let's see first whether the OSD Panel is the culprit. Maybe there's an item on your panel that operates outside the sensor module and causes the slowdown. Please let me know what happens after you turn the OSD feature off. If it solves it, and once you turn it back on, the issue comes back, then we need to dig down deeper and check out the 4 items you have on your OSD. We'll then try to replicate the issue on our own Xeon E5 v3 based test system. -
We've enabled graph and gauge configuration for the Time item in the following new AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta The resolution for the time value is 1 second, so for the gauge you may want to specify a minimum of 0 and maximum of 86399 to have a full day scale.
-
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
-
Search/Filter General/Label tab when adding new sensors
Fiery replied to one2three's topic in Brainstorming
It's a bit difficult to implement it, but we'll give it a try. Please give us a week or two to work it out. -
The problem with the single value is that to my understanding the throttling cause is not reported as an "either", but as a bit field combo, so there's a possible state of power limit + voltage limit in the same time, or even power limit + temperature limit + voltage limit. So reporting that would either need discreet values -- which would blow up the number of sensor items considerably --, or would require us to report the values as a string (text form). The latter solution would however make it impossible for you to put indicator LEDs on your panel...
-
In order to find out which component is overheating during the stress test, enable the Logging facility in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging. And BTW, that 216 Celsius reading is clearly a bogus value. No component in your computer would be able to operate at over 100-120 Celsius
-
SensorPanel doesn't support that kind of a placement, I'm afraid.
-
With a less than 10 FPS update rate it wouldn't look all that great IMHO.
-
We're not currently working on this feature idea. Maybe sometime in the future...
