Fiery

Please create a screen shot of the Computer / Sensor page of AIDA64 the next time the Aux temperature appears there. Alternatively, you can just copy-paste the full content of the Sensor page into this topic, using the right-click context menu on the Sensor page. Thanks, Fiery

Thank you for the data. Do you have any NZXT or other water coolers connected to your system? AIDA64 seems to be able to pick up a special DLL from C:\Program Files (x86)\NZXT\CAM\SiUSBXp.dll, and it would be useful to get rid of that DLL to rule it out as a potential issue. If you no longer use such a water cooler that would require the CAM software, then please try to uninstall CAM and check if it helps about the USB issue about AIDA64.

Not yet

No problem at all, we're here to help

Do you have the option DIMM TS sensor support enabled in AIDA64 / main menu / File / Preferences / Stability? If yes, then try to disable it, restart AIDA64, and let me know if the issue persists. If yes, then you can try disabling individual hardware monitor modules using right-click on the bottom status bar of AIDA64 main window --> HWMon Modules. In order to access the bottom status bar, you may need to enable it first in AIDA64 / main menu / View. Please let me know how it goes. BTW, do you have Asus AI Suite installed?

If it's not there, it means the file is already unblocked, so everything is good to go

That's puzzling. There's something about your Windows installation that prevents AIDA64 from loading its new SHA-2 signed kernel driver. You can try renaming KERNELD.X64 file to KERNELD.X64_ , and also renaming the legacy kernel driver file KERNELD.V64 to KERNELD.X64

It may also help if you simply use the Unicode MySQL ODBC Connector driver, and not the ANSI one.

If you have Windows 7 64-bit installed, then make sure to apply the following security patch to make AIDA64 v5.50 work: KB3033929

That sounds odd. Try to download the beta ZIP package, and extract it into a new, empty folder, and see if it runs from there. Also try to right-click on AIDA64.EXE in the File Explorer --> Properties --> Unblock --> OK. BTW, what Windows version do you have installed?

Have you performed the upgrade properly? Did you copy all files from the ZIP beta package into the existing installation folder of AIDA64, and overwrote any existing files? Somehow AIDA64 (the new beta version) cannot load its kernel driver on your system, which could be due to a few issues, like: 1) Lack of kernel driver files in the folder where AIDA64.EXE resides in. 2) Lack of necessary (administrator) privileges at the user who starts AIDA64.EXE

Try to restart your computer, and it should fix it up. Regards, Fiery

Are you sure you're not mixing Mbps (Megabit per second) and MB/s (MegaByte per second) ? 1 MB/s = 8 Mbps.

Please let me know what motherboard do you have, what Windows version do you have installed, and what drives do you have connected to which SATA/RAID controller. And also, in what mode do you use that controller? Thanks, Fiery

We currently have no plans to extend the list of sensors where we provide information on fan duty cycle. It's actually not that useful a value, and could be very misleading if someone relies on it. Because even if duty cycle is e.g. 75% or 100%, the fan could be stopped or clogged.

Those readings should also be available for all nVIDIA GPUs in the system. But, they may be unavailable for the secondary GPU because it is sleeping at the time AIDA64 tries to collect sensor information for it. It's not something that's easy to get around: you can try configuring your sensor items while putting a constant load on the secondary GPU, to make sure ForceWare drivers prevent it from going to sleep. Or, you can temporary disable the sleep mode for the secondary GPU -- I'm not sure if it's possible though.

Duty cycle is not available for most sensor readings, that's just normal. One of the USB sensor or PSU sensor modules of AIDA64 could cause that. You can try disabling the sensor devices that you know don't have connected to your system in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. If that doesn't help, then please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump, and copy-paste the results into this topic. Also, make sure to use the latest beta version of AIDA64 available at: http://www.aida64.com/downloads/latesta64xebeta

Thank you for the feedback

I will drop a message into this topic once the new beta is available for download.

Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let us know if it helps. If not, then please let us know more about your hardware and operating system.

I know what popup you meant. I was talking about a different window, the one that is the Properties box of the AIDA64.EXE file that you can access in File Explorer after right-clicking on AIDA64.EXE. You don't have to start AIDA64 to access that window.

Support for K7 anti-virus and firewall products will be implemented in the next AIDA64 beta update due in a few days from now.

Thank you for the feedback, I'm glad it works fine now. You can avoid that by right-clicking on the AIDA64.EXE file in File Explorer --> Properties --> Unblock (put the tick in the checkbox) --> OK. Example:

We haven't changed anything about the OpenGL module, so it should work similarly across the two AIDA64 versions you've tried. Try to reinstall AIDA64 v5.50, restart Windows, and it may just help.

The mentioned new AIDA64 beta -- including the GPU fan issue fix -- is available for download at: http://www.aida64.com/downloads/latesta64xebeta I'm glad you could resolve the Device Manager issue