-
Posts
11334 -
Joined
-
Last visited
-
Days Won
476
Content Type
Profiles
Forums
Events
Everything posted by Fiery
-
Thank you for the info. 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
-
I'm glad you've managed to resolve it. In HWMonitor where can you see the WHEA error info? I've checked and I cannot find anything related to it there. Can you perhaps post a screenshot to show us what you're looking for?
-
Sadly we cannot find anything useful in there But since you've mentioned SIV, try to contact its author (Ray) as well. Ray is very eager and skilled in digging down deeper when it comes to supporting exotic and unique hardware.
-
We don't have a direct solution for that problem, so you gotta find a way to bridge the gap between SCOM and the existing External Applications or Logging facility of AIDA64.
-
CPU Current Value disappears (Asus ROG Maximus XI Hero)
Fiery replied to tw33k's topic in Bug reports
What motherboard and CPU do you have? -
Of course, it will!
-
We've fixed the device icons in the following new AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta
-
fixed: Windows Defender not detected by AIDA64 Extreme
Fiery replied to Partha's topic in Bug reports
Sadly, via WMI the same incorrect information is returned, e.g. last AV signature update in 2016, etc. Anyway, here's a new AIDA64 beta where we've fixed what we could: https://www.aida64.com/downloads/latesta64xebeta -
fixed: AIDA64 doesn't show voltage values, except CPU (ASRock B250 Pro4)
Fiery replied to viestell's topic in Bug reports
We've fixed the sensor readings for your motherboard in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works. -
We've implemented the requested feature in the latest AIDA64 beta: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works
-
I'm afraid we don't maintain such a list of devices.
-
fixed: Windows Defender not detected by AIDA64 Extreme
Fiery replied to Partha's topic in Bug reports
Thank you for the bug report. I'm not sure if it's possible to detect Windows Defender on recent Win10 builds, but we'll improve on it in the next AIDA64 beta in order to show some details on the Windows Defender installation. The virus database date seems to be off though, so we need to do more research on that matter. -
I've asked our worldwide distributor Abseria Ltd to contact you directly about this matter. They will let you know what options you've got. I'm 100% sure you can find a way to acquire the licenses with the advertised discount of -50% for educational organizations and students.
-
Not all GPUs can provide a GPU power reading value in Watts.
-
The Statistics tab is designed to measure sensor readings while the AIDA64 System Stability Test is running. And while a stress test session is running, the average CPU usage is usually exactly 100% You can use the Logging facility (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging) to measure sensor values as well as CPU utilization while gaming.
-
It is sadly normal, but somehow doesn't happen on all Windows installations. It happens because sometimes the Windows driver cache gets invalidated when a software tries to load a dynamic kernel driver. When that happens, Windows gets extremely sluggish for a few minutes, exactly what you experience on your system. AIDA64 uses a dynamic kernel driver (and not a fixed, installed kernel driver) to provide the maximum flexibility and make sure that what we call portable version is really portable. I know it's not a real solution and probably not even a consolation for you, but the issue doesn't seem to happen under Windows 10, so by the time you upgrade to that OS, it will most likely be resolved.
-
32-bit architecture means that even though you have a 64-bit CPU, the Android platform installed on your device is the 32-bit flavour.
-
If I were you, I would try to warm up for SensorPanel instead of waiting for an improvement that may never come
-
Here's the new AIDA64 Engineer beta build: https://www.aida64.com/downloads/latesta64eebeta
-
Missing MOS temp on MSI Z370M Gaming Pro AC (MS-7B44)
Fiery replied to NaijaBushBoy's topic in Hardware monitoring
Thank you. 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 how it works.- 3 replies
-
- msi
- sensor panel
-
(and 1 more)
Tagged with:
-
CPU clocks drop during System Stability Test
Fiery replied to agraham's topic in Hardware monitoring
Overheating protection has multiple layers, and one of those is to lower the clocks when throttling is not enough to protect the CPU from overheating. -
Minimize to systray in Win10 anniversary update fails !!!
Fiery replied to shinavn's topic in Bug reports
It's normal. You cannot enable them both because that would mean that you cannot restore AIDA64 when it's minimized to the System Tray. -
I don't think Hardware Info implements the sensor mutexes that are necessary to synchronize that software with ours. Try to inquire Hardware Info technical support about the industry standard mutexes like: Access_ISABUS.HTP.Method Access_SMBUS.HTP.Method Access_EC etc.