Fiery

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...34ws9p7dqgnzzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. If it is still slow, then please post a new RAID Dump made using this version. We've added a bit more debug info to the dump. Thanks, Fiery

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1834ws9p7dqgnzzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Laptops feature such components that are designed to run constantly very hot. So having a notebook processor that heats up to 70-75 Celsius under load is normal. Mobile GPUs can work even beyond 100 Celsius under load. So unless your notebook switches off or throws a BSoD while playing a 3D game, it is fine. BTW, both modern processors and modern GPUs have automatic overheating protection to protect themselves from exceeding temperatures. Regards, Fiery

SMART info is available for Intel 520 drives, you can see that on the Storage / SMART page in AIDA64. I guess what you're missing from the Computer / Sensor page is the temperature measurement. I'm afraid Intel 520 SSD does not feature a temperature diode. For most SSDs it's not necessary to have a temperature diode, since they produce much less heat than hard disk drives. BTW, in order to get proper SMART attribute descriptions on Intel 520 drives, make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...29hfc3rql8jtzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

Temperatures, voltages and fan speeds are listed on the Computer / Sensor page in AIDA64. You can use the left treeview style menu to walk around pages. In order to test your computer's stability, you can go to main menu / Tools / System Stability Test. In there you need to select the subtests (e.g. FPU, CPU, RAM) you wish to run, and then press the Start button. In case during the Stability Test your computer locks up (freezes), restarts, throws a BSoD, or displays an error message, then your computer is indeed instable. You can use the FPU subtest only (and untick the rest of the subtests) to check the thermal solution of your system, ie. if it overheats under heavy load or not. You can use a combination of the subtests (e.g. you can enable them all) to test your system for hardware malfunction. Regards, Fiery

Thank you for the data. Did the RAID Dump take a long time as well, or only AIDA64 startup takes 30 to 60 sec to complete? In case the RAID Dump is also slow, then please let us know which of the methods take long time. The name of the method that is under execution is always displayed on the bottom status bar of the RAID Dump window. Thanks, Fiery

I guess one of the USB passthru methods of AIDA64 (that is required to acquire SMART attributes from USB drives and USB disk enclosures) cause the controller chip in your USB enclosure to stop working. If you have time and willing to try a few things to narrow it down to one specific USB passthru method, then we can compile and send you a special AIDA64 release that allows you to try the passthru methods one by one and find the "guilty" method to let us disable it on your device.

It's not that straightforward, since detecting video memory size and detecting used memory works very differently. And when a video adapter uses off-board memory as well (UMA, HyperMemory, TurboCache, etc), then the video memory size detected by AIDA64 may not equal to the actual total video memory available for the GPU.

I'm afraid so far we haven't found a reliable method to monitor GPU video memory utilization percentage. Regards, Fiery

The old "Aux" temperature is now what AIDA64 reports as "CPU" temperature. It's the same reading. And please understand in AIDA64 we're just trying to report the same sensor values (or even more sensor readings if possible) as what the BIOS Setup or the manufacturer's own hardware monitoring software measures. If the measured temperature(s) match e.g. MSI Control Center, but they still don't make much sense to you, then it's not the fault of our software, but maybe your hardware measures incorrect or unreal values

It's up to you Our beta releases are usually just as stable as a stable release, so no risk on using a beta.

Can you see an exact 10C offset both at idle and under heavy system load? If so, then you can use the Correction feature of AIDA64 to substract 10C from the CPU temperature (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction). Does MSI Control Center measure MOSFET temperatures? Or you referred to BIOS Setup temperature readings there?

Please make sure to compare CPU and Motherboard temperatures against MSI Control Center. We're certain the current solution should match MSI Control Center values. The 10 other temperatures are the MOSFET temperatures. Most monitoring software cannot measure them

Thank you for letting us know about the solution. It will hopefully help others who face similar issues. Regards, Fiery

I'm afraid certain AMD processor models, especially the latest FX Series are infamous for providing very low core diode temperature readings, usually way below ambient temperature at idle. So you may want to ignore the core diode temperature readings.

Thank you for the feedback. AFAIK your motherboard cannot measure the regular voltages (+5V, +12V), so that's why we've removed those bogus readings. You can check in the BIOS Setup whether your motherboard is capable of measuring a specific voltage rail or not.

Thank you. We'll contact Intel and try to talk to Eric about Quick Sync detection in AIDA64. However, as Intel seems to be unusually closed on the Quick Sync topic, we may not be able to get the necessary low-level information. I'll let you know in this topic once we have an update.

I'm afraid Intel haven't really published any low-level information about Quick Sync, or at least so far we couldn't find any useful info on how to detect that feature. Do you know any software (either made by Intel or a 3rd party) that can show any information on Quick Sync? Thanks, Fiery

No problem

That indeed sounds weird. But in case Asus Probe shows the same, then the sensor most likely provides incorrect readings. I'm not sure if it makes sense to correct it, but if you wanna do that, then you can enable Correction in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction. Regards, Fiery

In the BIOS Setup processors are unable to execute halt cycles to put their clocks down in order to cool themselves down. Hence if in the BIOS Setup you can see 20+ Celsius, but AIDA64 measures 15-19C, it may be correct. Please compare AIDA64 values against MSI Control Center values. Regards, Fiery

As Squall Leonhart suggested, under Windows Vista and Windows 7 you can find the scheduled task that starts AIDA64 at Windows boot using Task Scheduler. Please check if the task is there, and if it is enabled. There's a chance NIS removes the task, or prevents AIDA64 from creating the task. Regards, Fiery

It looks like the AIDA64 Remote Control Server had some issues on the workstations. We'll check what's going on, although as I can see you already have up on AIDA64 If you reconsider sometime, then you can fix such issues by removing the DLL file that causes the issue (AIDA_RCS.DLL). That will of course disable the Remote Control feature, but at least you can evaluate the other features without such error messages. Regards, Fiery

System instability is something you cannot measure using a mathematical formula or a specific detection method. Some of the instability issues can be revealed by only AIDA64, some others can only be revealed by Prime, and some can be revealed by any of them. BTW, AIDA64 System Stability Test has multiple subtests. Sometimes an instable system can be put to "its knees" by only using the FPU subtest (and leaving the rest of the tests disabled), while in other cases you should enable all subtests to reveal the instability. It takes a lot of time to check out how stable your system is, but if you can achieve a high clocks via overclocking, then it worth the efforts to play around with stability tests Regards, Fiery

It is definitely a conflict between Asus AI Suite II and AIDA64. We've already contacted Asus a while ago, and asked them to implement the now industry standard mutexes that many sysinfo and diagnostics software use (e.g. AIDA64, HWiNFO32/64, CPU-Z, HWMonitor, SpeedFan, SIV, etc) to make sure their low-level code doesn't collide with each other when you use multiple of such software in the same time. But Asus don't seem to care about that at all. So in case you observe any collisions between such 3rd party software and AI Suite II, then I'm afraid it can only be solved if you put a bit of pressure on Asus to improve their software. Regards, Fiery