Fiery

Does AIDA64 stop responding when it tries to send an alert, or is it a regular issue that affects AIDA64 even when the alerting facility is not activated?

That's because if you have AI Suite installed, debug information will issue an ATKEX call for AI Suite to send the sensor info it measures to AIDA64, so AIDA64 could insert it into the debug output. When the ATKEX call is issued, AI Suite reconfigures the sensors on your motherboard.

On your motherboard AI Suite reconfigures the sensor chip, effectively altering the CPU temperature readouts. We used to have a workaround in AIDA64 for that situation, but it caused a lot of confusion amongst AIDA64 users, so we've removed it. Please note that the lower temperatures (that AIDA64 shows before running AI Suite) are the ones measured by the sensor chip, so we would treat them as the "real" ones actually... Regards, Fiery

I'm sorry, but we don't offer such license. BTW, even Windows itself has no such license Also, most anti-virus and security software have no lifetime license.

Actually, usage period is not limited in AIDA64 licenses. What's limited is the maintenance (support) period, the time until you can upgrade to newer releases of AIDA64. The regular AIDA64 license covers 1 year maintenance, so for 1 year you can benefit from updating to new AIDA64 releases, and you receive free technical support as well. After that period expires, you can still use the last AIDA64 version you could upgrade to, for an unlimited time. So for example, if you bought a 1-year license in September 2011, you got AIDA64 v1.85 with that purchase. You could then upgrade to AIDA64 v2.00, v2.20, v2.30, v2.50 and v2.60 free of charge. And you can keep using AIDA64 v2.60 for an unlimited time, but you cannot upgrade to future releases of AIDA64 v2.70, v3.00, v4.00 (etc) anymore. Please note that there're longer maintenance period licenses, for 2 years and for 3 years, with considerable discounts compared to the price of the 1-year license. It's also possible to renew (extend) an existing AIDA64 license at 70% of the new license prices. More info at: http://www.aida64.com/licensing-aida64 Regards, Fiery

Thank you for your support.

Currently it's not possible to alter the priority of AIDA64 main process. Why would you want to do that BTW? Regards, Fiery

Thank you. Can you please right-click on the "Motherboard" group in the left menu in AIDA64 --> Quick Report --> Plain Text. Copy-paste the full results into this topic.

Those are system devices that don't require a special driver to be installed. Drivers for those devices should be part of Windows, and should have been automatically installed when Windows itself is installed. Regards, Fiery

I'm sorry for those difficulties. Our support team said they've contacted you, so I hope things are going in the right direction from now on. Regards, Fiery

Right-click on the magenta text to delete it Same goes for any SensorPanel items: you need to use the right-click context menu to remove, edit or move an item.

Windows kernel's memory management is a mystery, so I personally would be interested to read a proper article that explains all those -- seemingly -- anomalies. AIDA64 reports what Windows kernel reports, so if you guys reckon those values don't add up, then it's only Windows kernel to blame or inquire

1) Do you use Win7 SP1 64-bit? 2) Have you ever had Asus AI Suite installed? Even when you uninstall it, some pieces (drivers, services) may be left off, causing collisions with AIDA64 in the background. 3) Are you running any other monitoring software while using AIDA64? Thanks, Fiery

Thank you. Does it mean you don't get BSoD only if you uninstall SSD ToolBox application? BTW, to assure AIDA64 doesn't go through Intel RST/RSTe drivers to get RAID member drives data, you need to disable both RAID options in AIDA64 / main menu / File / Preferences / Stability. That should make AIDA64 fully stable, even with SSD ToolBox running.

It could be due to a background process, service or driver that also polls motherboard sensors, and collides with AIDA64 and other monitoring software as well. Maybe even though you uninstall ET6, some components (a service or a driver) are still left installed. If those components are still running hidden in the background, they can still collide with AIDA64

1) Do you use AIDA64 v2.60? (latest version) 2) Is your system overclocked or otherwise tuned or altered from its default clock and timing settings? 3) Do you use the memory modules your computer was shipped with? Thanks, Fiery

Slight variations are absolutely normal, in either directions. 11.88V means it's only 1 percent deviation from 12.00V, so it's nothing to worry about Anything above 5% would be an issue, and most likely would cause the system to produce various anomalies like BSoD or lockups.

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2139dz0wrgyqtnzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If it still provides inadequate sensor details, then please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. Thanks, Fiery

AIDA64 has specific sensor adjustments for your motherboard, while Hardware Monitor Pro doesn't have such capability. Regards, Fiery

I'm sorry for the late response. We'll definitely get to trying to figure out if it's possible to measure NPU load on your card, but first we need to get a test hardware to check it out. I'll let you know in this topic when we have a definitive answer to the "Is it possible to do that in AIDA64?" question

Actually, there's no way to know, detect or "sense" which component is behind a computational failure. If you look at the way data is processed by the processor, a glitch could be anywhere inside the CPU or RAM. And a failing (weak) PSU could cause a range of issues due to providing unreliable voltage rails that may cause glitches in any part of the computer that uses electricity

There's no way to tell which exact component is behind the failure. In most cases however it is caused by either the PSU, CPU or RAM. Also, you gotta make sure the hardware failure is not caused by overheating, so it's best to watch the temperature graphs and the throttling graph. If temperatures are not too high, then at least you could easily rule out overheating.

We've already fixed a BSoD issue in AIDA64 v2.60. Maybe there's a new one related to RSTe 3.5? Do you use the WHQL release of RSTe 3.5?

That's great news, thank you!

We've implemented custom gauge states -- for both SensorPanel and Logitech LCD -- in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2139dz0wrgyqtnzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. It can be used to customize the current gauge states to implement tiny gauge sizes, and also to make a gauge design for fan speeds (that starts with red states and go up to green states). We'll work on the rest of the requested features.