Fiery

We've implemented disk activity measurement in the latest AIDA64 beta update available at: http://www.aida64.com/downloads/latesta64xebeta Please note that the Performance tab of Windows Task Manager seems to measure the read and write speeds not in the classic MB/s or GB/s measurement units. It uses a divisor of 1000 instead of 1024, and that leads to displaying higher values than AIDA64. We stick to using the classic divisor and classic interpretation of MB/s and GB/s. Also note that the current hardware monitor module of AIDA64 supports up to 10 disk drives when measuring disk activity. If you have more drives and would like us to expand the limit of 10 drives, let me know.

The mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta Please note that the Performance tab of Windows Task Manager seems to measure the read and write speeds not in the classic MB/s or GB/s measurement units. It uses a divisor of 1000 instead of 1024, and that leads to displaying higher values than AIDA64. We stick to using the classic divisor and classic interpretation of MB/s and GB/s. Also note that the current hardware monitor module of AIDA64 supports up to 10 disk drives when measuring disk activity. If you have more drives and would like us to expand the limit of 10 drives, let me know.

Yes, it should be CPU VRM voltage. You can put it on the voltage graphs -- and in the same time to the Statistics chart -- in the System Stability Test if you press the Preferences button on the bottom of the window --> Voltages.

Please restart AIDA64, to make sure the latency issue comes back. Do not use the HWMon Modules trick for this test. Just right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling Dump. Please copy-paste the full results into this topic, or attach it as a TXT file to your post.

No, the OSD Panel module doesn't support any separators or other dummy sensor items. The way we see it: the OSD is for quick & easy configuration, if you just want to display various values without hassling too much to design and customize the layout. If you need advanced configuration options, custom layout, multiple columns, graphs, bars, gauges, then you can use the AIDA64 SensorPanel instead of the OSD: http://forums.aida64.com/topic/667-share-your-sensorpanel/ Regards, Fiery

Can you see the missing voltage on the Computer / Sensor page of AIDA64? And if yes, then what is the label for that value on that page?

Yes, you can display various sensor values and other measurements on the G13 LCD, using the Logitech G15/G19 LCD module of AIDA64. Regards, Fiery

With the smiley I've meant to indicate that it's something that's very close to getting implemented. In fact, it will be included in the next AIDA64 beta update due in a few days from now. You'll be able to monitor physical drive activity (%), read speed (MB/sec) and write speed (MB/sec) as well. Stay tuned

Thank you for letting us know about the resolution.

Thank you for the info. Do you have your drives connected to the 2 primary SATA ports, the ones providing SATA3 interface?

We've tested it with a X79 motherboard with a SSD in AHCI mode, running Windows 10 64-bit (both TH1 and TH2) and RSTe 4.3.0.1223, and it worked fine for us. Did you have no issues before installing RSTe? Where did you download RSTe installer from? Is your SATA controller now has a driver installed with a version number 4.3.0.1198 and dated 5/21/2015?

Yes, we've transitioned to the new SHA-2 signed kernel driver in Build 3540. But the odd thing is that for other Win7 64-bit users it still works fine, up to and including the latest beta. So there must be a confusion or configuration issue in your Windows installation that prevents the new kernel driver to be loaded, and apparently even the legacy kernel driver cannot be loaded anymore. I'm not sure what can be done, other than making sure to uninstall and remove all traces of AIDA64 from your system, and start all over again. Please note that running different AIDA64 builds after each other -- without restarting Windows -- could mess up Windows drivers stack. So it may be best to backup all your settings (especially the files called AIDA64.INI and PKEY.TXT), remove all AIDA64 instances from your system (you can keep the ZIP packages), restart Windows, and install the latest AIDA64 stable build (5.50.3600). If it works, then you can try upgrading to the latest beta update.

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.