Fiery

CPU throttling is a technique used by modern Intel processors to prevent themselves from overheating. The CPU detects when it gets close to TJMax (maximum operating temperature basically), and then it starts stopping its execution pipelinesfor a moment. That pipeline stopping trick is what they call throttling. 38% means for 380 milliseconds out of 1 second the pipeline was stopped, so the CPU did an actual processing work only 62% of the time.

Those items measure the values for logical drives (like C: or Z:) Disk activity measures the values for physical drives. One physical drive may have 0, 1, 2 or more logical drives assigned to.

Only full per-key RGB keyboards are supported by the AIDA64 RGB LED module. And with an integrated big LCD screen, it wouldn't make much sense to hassle with the individual keys anyway.

We haven't yet found a reliable way to may phyiscal drives to drive letters. You can peek into the Task Manager though, to find that out. The only difference is that Task Manager calls the first disk Disk #0, while AIDA64 calls the same disk Disk #1.

The only way to achieve that right now is by making sure the GPU fan is spinning. You can only configure the GPU fan RPM item when the fan is spinning.

Yes, you're right. When the GPU provides a zero RPM reading, it's not easy to decide whether it's because you've got a passively cooled video card, or because the fan is not spinning at the moment. As soon as it spins up, the reading will be displayed. And when it stops, the latest zero RPM reading should be displayed from then on.

Looks great, thank you for the feedback!

Yes, you can simply extract the ZIP package into the existing installation folder of AIDA64. Let it overwrite the existing files. That process will retain both your existing configuration settings and your entered license. BTW, it's not a new approach at all. We've been using it for 15 years already

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