-
Posts
11554 -
Joined
-
Last visited
-
Days Won
489
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
fixed: Sensor readings for EVGA Z170 Classified K (E178)
Fiery replied to Arctucas's topic in Hardware monitoring
The above mentioned new AIDA64 beta update is available at: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works -
We've tried it under Windows 10, and it shows disk activity with a polling resolution of 100 millisec, so it works as expected. What Windows version do you have installed?
-
SSD/HDD OSD items/labels messed up after wake from sleep
Fiery replied to eldata's topic in Hardware monitoring
Do you have a smart PSU or a USB-connected sensor device like Aquaero or Corsair Link? -
You have to adjust the update frequency for the feature you're using. If you're using those disk related items on SensorPanel, then you need to adjust the update frequency for the SensorPanel. And no, we don't use the disk performance API incorrectly.
-
You can configure update frequencies in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Update Frequency. If that doesn't help, it means the data provided by Windows is not updated at a poll rate you'd expect.
-
SSD/HDD OSD items/labels messed up after wake from sleep
Fiery replied to eldata's topic in Hardware monitoring
The issue is because for some reason your SATA controller fails to provide stable readings for drive model ID, serial number and revision. That will then cause AIDA64 to fail sorting out redundant entries in the SATA drives list. Example of the issue, as you can see in the SMART dumps: "PN CS1311 120GB SSD" vs. "PNY CS1311 120GB SSD" and "Samsun SSD 850 EVO 250G" vs. "Samsung SSD 850 EVO 250GB" Please try to update Intel RST drivers. Hopefully that will sort this issue out. -
Transparency cannot be done for only the background of the SensorPanel. The OSD Panel transparency is done for the whole window, including the contents, not just for the background.
-
Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor 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 --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Also, please create a screen show of Asus' own hardware monitoring utility, of the page where it shows the temperature and voltages readings. That way we could have a reference list of readings that we could use to calibrate the temperatures and voltages in AIDA64. In case you cannot find such Asus utility, then please create a photo of the H/W Monitor page of the BIOS Setup (UEFI Setup) for the same purpose Thanks, Fiery
-
fixed: Some GPU sensors don't show up (GTX 1080)
Fiery replied to Hitman_Agent_47's topic in Hardware monitoring
Thank you for your feedback -
It's not a critical issue at all, especially when the overheating situation is very short and very limited (1% is almost 0% ) There's nothing to worry about there
-
fixed: Sensor readings for EVGA Z170 Classified K (E178)
Fiery replied to Arctucas's topic in Hardware monitoring
Thank you, and yes, it's all fine so far. The problem is: the sensor solution is quite complex on this motherboard, so we need a bit more time to figure out everything. Please give us 2 or 3 more days to come up with a new AIDA64 beta -
fixed: Some GPU sensors don't show up (GTX 1080)
Fiery replied to Hitman_Agent_47's topic in Hardware monitoring
Have you tried it with the latest AIDA64 beta as well? http://www.aida64.com/downloads/latesta64xebeta -
Stress test Fpu+Gpu=instant crash
Fiery replied to KaOsphere's topic in Benchmarking, system performance
The FPU+GPU combined test causes the whole system to draw the maximum amount of power. In your case it most likely causes the overstressing of a faulty motherboard VRM or other PCB component, or perhaps the PSU is about to give in. If you have a replacement PSU on hand, try it with that one first. If it doesn't help, then it would be important to closely inspect all motherboard components, especially the capacitors. -
SpeedFan is not our software, so I'm not able to tell you why it measures too low temperatures. But the difference could come from the wrong usage or wrong detection of TJMax temperature.
-
fixed: Sensor readings for EVGA Z170 Classified K (E178)
Fiery replied to Arctucas's topic in Hardware monitoring
Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor 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 --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Also, please create a screen show of EVGA's own utility (E-LEET) to have a reference list of readings that we could use to calibrate the temperatures and voltages in AIDA64. In case E-LEET fails to support your motherboard, then please create a photo of the H/W Monitor page of the BIOS Setup (UEFI Setup) for the same purpose Thanks, Fiery -
I'm afraid not. Windows 10 UWP still lacks the necessary APIs to measure clocks and temperatures.
-
That's what the Dell SMI interface reports for your fans We'll remove those readings in the next AIDA64 beta update.
-
That's because AIDA64 reads GPU temperature directly from the GPU, while GPU-Z goes through ForceWare drivers to obtain the GPU temperature reading. And ForceWare seems to use a +5 Celsius offset on the raw temperature reading. If you believe +5C offset should be applied on the AIDA64 reading, you can configure it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction.
-
I'm afraid we cannot diagnose this issue remotely. If you're afraid of the drive may be malfunctioning, then try to return it under warranty. But any case, make sure to perform a full backup as soon as possible, and discontinue storing important data on that SSD of yours.
-
CPU Current and Power (Asus Rampage V Extreme)
Fiery replied to tistou77's topic in Hardware monitoring
Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller 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. Thanks, Fiery -
Aida64 5.70.3800 reports 3 modules of KINGSTON Savage instead of 4 modules
Fiery replied to grabibus's topic in Bug reports
It could be a number of issues. Maybe Speccy uses different timing settings on the SMBus communication layer. Without having the motherboard on hand, I'm afraid I cannot tell you more about this. Our SMBus module works fine with other X99 motherboards. -
I have no idea what SPF-71E is, but I assume that it also lacks Mini Monitor Mode, just like SPF-71ES
-
SSD/HDD OSD items/labels messed up after wake from sleep
Fiery replied to eldata's topic in Hardware monitoring
Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> ATA 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. Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Then please create those dumps once more, after the AIDA64 OSD gets mixed. We need all 4 of those dumps to see what's going on after sleep on your system Thanks, Fiery