Fiery

Thank you for the feedback

Make sure to 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. After the restart, go to AIDA64 / main menu / File / Preferences / Stability, and enable (check) the option called Wake GPUs up at AIDA64 startup. Then restart AIDA64, and check if the temperature is there on the Sensor page. Regards, Fiery

Modern Haswell and Broadwell core based Intel processors tend to operate at very high temperatures under heavy load. That's just normal for those processors, and your results fall into the normal range as well. So you have nothing to worry about. Regards, Fiery

I'm afraid without trial and error, we won't be able to solve this The AIDA64 sensor code is over 100,000 lines long, and without a hint on where the issue may be, it's very hard to find it without trying several tests on the machine in question. It would be quite easy if the machine was here, in our labs, or if you were able to run several more tests that may cause a crash or BSoD. With a server it's always a headache to find the root cause of such issues

Corsair AXi PSUs are not supported by the AIDA64 hardware monitor module. Only HXi and RMi PSUs are supported, and only when they are directly connected via USB (not via Corsair Link Commander). Regards, Fiery

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 me know if it helps. Thanks, Fiery

You can download the mentioned new AIDA64 beta update from: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

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 me know if it helps.

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.

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.

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.

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.

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