Fiery

Please note that even after uninstallation, AI Suite tends to leave behind its NT services that are still running after Windows restart, and still collide with hardware monitoring applications like AIDA64. You have to manually remove those services. Regards, Fiery

The mentioned values (CPU core temperatures, CPU utilization, fan duty cycles) aren't related to AI Suite at all. You can verify what values AIDA64 exports to other applications if you enable the Registry exporting as well (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / External Applications), open the Registry Editor (REGEDIT.EXE), and navigate to HKEY_CURRENT_USER\Software\FinalWire\AIDA64\SensorValues.

Sometimes loading AIDA64 at Windows startup could take a while. It is because Windows' driver subsystem prefers statically loaded (installed) kernel drivers over dynamically loaded kernel drivers. AIDA64 uses dynamically loaded kernel drivers to assure it is 100% portable between Windows installations and different computers as well, and also it makes it easier to update the software automatically.

Thank you for the data and the photo. I'm afraid so far we cannot find the registers responsible for the fan speeds Would it be possible to create 2 more ISA Sensor Dumps, one when the fans are definitely stopped (not spinning), and the other while the fans are definitely spinning? That would help us to find the registers by comparing the dumps to each other. Thanks, Fiery

1) AIDA64 exports all core temperatures via WMI. It all depends on the other application (that takes and displays those readings from WMI) which values does it read from there. 2) AIDA64 exports fan duty cycle settings as well. See #1 3) Units are not exported to WMI, but the type and ID fields can be used (by the other application) to figure out the unit and display it. With temperatures, voltages and fan RPMs it's easy, since you only have to use the type field. With system readings (like CPU utilization, CPU clock, CPU multiplier, etc) you have to make the other application a bit more clever by checking the ID field as well.

AIDA64 (regardless of whether you're running the trial version or the unlocked licensed version) can publish those values that are listed on the External Applications page in the Preferences. Please note that the list there is only applicable to the current underlying system you're using. So if you take AIDA64 to another computer, running another operating system, the list of values may be longer or shorter, depending on the number of sensor items that particular computer supports. Regards, Fiery

Their SDK evolves a bit slower than we'd expected

I'm not sure what you're talking about. First of all, it's not possible to configure a 60 seconds update frequency for the SensorPanel. And even if you configure a very long update frequency (of e.g. 30 seconds), when you hide and show the SensorPanel using the right-click menu of the System Tray icon, it will disappear/appear immediately, regardless of the update frequency setting.

Yes, but Direct3D does some very odd things AIDA64 doesn't show a lot of information on Direct3D video adapters, simply because those values do not seem to make any sense. Microsoft keeps revamping and tweaking Direct3D, but it's still not there yet to reflect the proper hardware capabilities. It's best to rely on the directly measured/detected values.

Quite frankly, only nVIDIA knows what those values represent exactly. AIDA64 only reads those values, it doesn't do any conversion or other modification to the values ForceWare provides. Regards, Fiery

GPU temperature may be measured as zero when the GPU goes to sleep, that's normal

Try to enable the option Wake GPUs up at AIDA64 startup in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64. If it still doesn't bring the GPU temperature readout back, then it could be a driver (ForceWare) issue that we won't be able to fix on our end Regards, Fiery

Please also create a new ISA Sensor Dump using the latest AIDA64 Extreme beta release available at: http://www.aida64.com/downloads/aida64extremebuild3006q7kg9jxrptzip In this beta we've added a new section to the ISA Sensor Dump that dumps a special Embedded Controller MMIO region that may help us to understand where and how your notebook stores the sensor readings.

No worries, we've already ordered the keyboard. As soon as it arrives, we'll start working with the current SDK. We've also sent Mad Catz an inquiry about the potential issues and missing parts we've found analyzing the first SDK release. If they respond in a timely manner and the SDK is useful in its current form afterall, then the 3 months I've mentioned above for the stable implementation may be a lot shorter to get a beta stage Strike7 implementation in AIDA64

As I've stated above: "One thing that doesn't seem to work is putting images under the dynamic keys. We suspect it is due to a bug in the SwitchBlade SDK. We've asked Razer through their forum about this, and will push them to fix it up if it is indeed a SDK bug." So far we haven't been able to fix this on our end, since it indeed seems like a SDK bug that Razer has to fix on their end.

The message means the stess testing module of AIDA64 has found a small issue while running the test. When I say small issue, I mean a glitch that is small enough not to cause a catastrophic system halt, via a BSoD, system lockup or unexpected system restart. Of course a minor instability is still an instability, so you have to tweak your system settings to make sure your PC returns to being stable.

Thank you for the data. Your notebook definitely has a new kind of sensor solution that is unknown to AIDA64. Can you please check how many temperatures and fan speeds can you see in the laptop's diagnostics, and is there any voltages there as well? If it's easier, then please take a photo of how that app looks like, and attach it to a forum post. Thanks, Fiery

It's already available since AIDA64 v4.00 (November 2013).

It means one of your input devices (mouse or keyboard, typically) has a broken DirectX Input support in their Windows drivers. It's usually not a big deal these days, so you can ignore that issue. In case you want to stress your system to see how it copes with heavy load, you can use the AIDA64 System Stability Test (main menu / Tools / System Stability Test). http://www.aida64.com/solution/system-stability-test

Thank you for the feedback. So you mean now, after reinstalling AIDA64 v4.50, everything works fine, including the Sensor page? That would be great news

Thank you for your replies. Can you please check whether the lockup occurs if you click on the Motherboard / Chipset page?

Dedicated is supposed to be the on-board video memory, while dynamic should be the remote memory, allocated in the system memory. In case you've got a CF configuration, then there's a chance Direct3D reflects video memory usage by adding up the two 3GB memory regions.

Windows video drivers may use local (on-board video card) memory, or remote (portions of system RAM) memory, depending on what their requirements are. I suppose in your case the on-board memory has been exhausted, so the game started to allocate system RAM to store textures. That is normal these days, you don't have to worry about it -- unless of course the game slows down when it exhausts video card memory. Regards, Fiery

1) Do you have Asus AI Suite installed? 2) What was the previous version of AIDA64 that worked fine? 3) Have you tried AIDA64 v4.50 only once, or anytime you try to use it, it freezes when accessing sensors?

We have a lot of things on our long-term roadmap, including the idea of having multiple SensorPanels in AIDA64. I cannot provide a definitive schedule though, since we tend to prioritize such plans based on a rate of requests coming from our users. If a lot of guys start to demand a specific feature, we put them higher on our list of things to do.