-
Posts
11545 -
Joined
-
Last visited
-
Days Won
489
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
[RESOLVED] System hang with Odospace and 6800 XT
Fiery replied to SnarlingFox's topic in Bug reports
Thank you for your feedback! If you mean the GPU clock disappears/reappears, then it's normal for 6800 XT / 6900 XT video cards. It's due to the fact that the new AMD GPU generation introduced a very deep sleep where the driver reports zero MHz GPU clock to AIDA64 -- which is considered an invalid reading and triggers the relevant SensorPanel/LCD item to disappear. We'll need to come up with a workaround for that issue. -
Thank you for your kind words. What is listed on the Chipset page are the nominal values for the hardware, and not measured values. They cannot be shown on the SensorPanel. Our Capellix device has arrived, and we're already working on it. Give us a few more days to have something to try
-
Thank you! Can you please check if perhaps the issue comes up after your computer returns from sleep?
- 24 replies
-
- sensorpanel
- image
-
(and 6 more)
Tagged with:
-
fixed: Missing Aquasuite data into AIDA64 (High Flow Next)
Fiery replied to sactomori's topic in Hardware monitoring
High Flow Next is fully supported by the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta- 23 replies
-
- high flow next
- high flow
-
(and 3 more)
Tagged with:
-
Thanks for you feedback
-
overheating HP EliteBook 840 G7 overheat detected
Fiery replied to rodi1i's topic in Hardware monitoring
It depends on a number of factors, but mostly it depends on how the laptop cooling is implemented. -
1) AFAIK 5VSB and 12VSB are not measured by your motherboard. 2) The mentioned 3 fans are already measured for your motherboard. Please check if they're there on the Computer / Sensor page of AIDA64. 3) We're planning to roll out the new beta in a few days from now. 4) It's very difficult and time consuming to support every single high-end motherboard in AIDA64. We do our best, but such motherboards with a complicated sensor layout are always a big challenge.
-
While I see your point and understand where you're coming from, we're still not interested in either averaging anything, or relying on SDK's when it's not absolutely necessary.
-
fixed: Sensors readout not correct and missing (Asus ROG Strix B550-XE Gaming)
Fiery replied to civato's topic in Bug reports
Thank you for the dumps! The issue will be fixed in the next AIDA64 beta update. I will post a message into this topic once the new beta becomes available for download. -
Steelseries Apex 7 / TKL Keyboard LCD Unplug Issue
Fiery replied to Michael O's topic in Bug reports
No, it's not, since the SteelSeries LCD module supports hot-plug. Do you have other SteelSeries-made USB devices connected perhaps? -
I'm afraid we ran out of ideas on how to improve the EC interaction
-
Measuring or monitoring anything during benchmarking is a bad idea since it would negatively affect the benchmark result. Therefore all AIDA64 background monitoring activities have to be paused while a benchmark is running.
-
Adding states in a custom SensorPanel gauge
Fiery replied to Takis Arsenis's topic in Hardware monitoring
You can use custom state images, but you cannot expand the number of states. -
Please note that unlike notebook PC batteries, Android devices do not feature sophisticated smart batteries. It sadly means that battery wear level or battery health estimations cannot be measured or computed.
-
We've removed the links since they contain references to illegal (pirate) product keys of AIDA64. Since the transaction of you purchasing a hardware also involves distributing illegal product keys for our software, it's not our responsibility to assist you in this issue. Try to contact the seller and ask for technical support from them. If you'd like to continue using AIDA64 by purchasing a legal license key from us, please let me know in private message. This topic -- due to its course about illegal content involved -- has to be locked here.
- 1 reply
-
- help aida64
- problem
-
(and 1 more)
Tagged with:
-
You can reset your OSD settings by closing AIDA64, navigating to AIDA64 installation folder, opening AIDA64.INI (settings file) in Notepad (or any other text editor of your choice), and removing all lines starting with OSDItem_ Please note that the explained process will delete all your customization about your OSD Panel. I'm not sure if I understand your issues about the sensors monitoring and whether it's separate from the OSD Panel reset issue. Is the missing +3.3V rail the only problem, or you have multiple issues that you're looking to solve? Edit: We will fix the missing +3.3V voltage reading issue in the next AIDA64 beta update.
-
On the SensorPanel just use the mouse right-click context menu --> SensorPanel Manager --> Export to save your layout into a file. You will be able to select the folder and file name.
-
overheating HP EliteBook 840 G7 overheat detected
Fiery replied to rodi1i's topic in Hardware monitoring
Laptops are quite different from desktop computer in the sense that they have much less room to prevent the CPU from overheating when there's a very demanding task running on the system. Throttling is considered normal on many laptops therefore, and as long as the computer provides the expected system performance, you have nothing to worry about. Especially since what AIDA64 does in its stress test is truly the worst case scenario in terms of power draw and the resulting heat production. -
Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Corsair Link Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
-
I think you can achieve that by enabling Logging in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging as well as the option on that page called Log started and stopped processes. The latter option should indicate when you start and close a game as long as you do that by launching its main executable file and then closing the process at the end of gaming.
- 1 reply
-
- 1
-
Do you use RTSS as it is installed a part of MSI Afterburner? If yes, then what version of Afterburner are you using? What game (or games) do you experience the issue in?
-
AFAIK it's not possible to use separate screensaver settings for multiple monitors.
-
Since it's a regular monitor that appears under Windows as a secondary monitor that you can extend Windows Desktop onto, you can simply use the AIDA64 SensorPanel module with it. This however requires that you connect the monitor directly to your PC and not to your Pi 4.