Fiery

H100i GTX uses Asetek LC protocol, and not Corsair Link. So disabling Corsair Link sensor support will not make any difference. You can however set your configured fan duty cycle (%) in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Set Asetek fan speed to avoid AIDA64 altering the fan duty cycle to maximum (100%). The readings provided by the AXi PSU may be unstable because another software (besides AIDA64) is also polling the PSU for sensor readings, and that may collide with AIDA64 doing the same polling. Try to close every other monitoring software, including background processes. As for the CPU fan header, I suppose it should be related to the motherboard sensor logic, so please let me know what motherboard you've got, and we can start to investigate from there

I suppose the issue may be because your PSU provides erratic readings for voltages. It doesn't cause an actual problem though. If suddenly the +3.3V rail would provide 12 Volts or the +12V rail would provide 5 Volts, your system would immediately lock up And those erratic readings may just be caused by a collision between AIDA64 and another software polling your PSU. Do you have any other software installed that may poll the PSU?

I'm afraid the issue is still in the Mad Catz Strike7 SDK or the Strike7 drivers themselves. This is something Mad Catz has to resolve on their end.

Since 1998, we traditionally use the company name of nVIDIA as nVIDIA. It comes from their logo where they use a small "n" and the rest of the letters are capital. Some people spell it as NVIDIA, others spell it as Nvidia, and others say it is nVidia. So there's no general consensus on this. Of course most companies prefer to use all capital letters to make their company name stand out, like SONY, TOSHIBA, etc. Regards, Fiery

Thank you. We've fixed the issue in the following new beta version of AIDA64 Extreme: 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.

The issue may be caused by unstable readouts provided by the Emdedded Controller part of the sensor solution of your motherboard; or because of another monitoring software running in the background. Please note that it doesn't have to be something you can see running, it could well be a background service that is monitoring the system constantly. AI Suite tends to leave such a service behind, even after uninstalling it.

AIDA64 probably hasn't got updated before to the latest beta, and that caused the headaches. I'm glad it works fine now

Yes, that hotfix is best to have, in order for AIDA64 to work properly.

Are you using Windows 7 64-bit? If yes, then do you have the SHA2 security hotfix KB3033929 applied?

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

Thank you for the feedback, I'm glad we've managed to solve this

Our FX-8350 based, Dual Channel DDR3-1866 system that uses slightly different RAM latency settings (9-10-9-27 CR2) than yours can push: Memory Read: 26426 MB/s Memory Write: 17328 MB/s Memory Copy: 22802 MB/s Memory Latency: 61.6 ns

I've sent you a private message about this.

The results look fine to me, considering your system spec. Regards, Fiery

It could happen when the time measurement of the System Stability Test gets mixed up for some reason. Try to restart Windows and try it again. I'm sure that will fix it

Thank you for the feedback

Thank you for your feedback. We'll keep looking into this issue, even though I suspect we may not be able to solve it on our end

No problem, thank you in advance

Please let me know what way would you like AIDA64 to be automated about that process. Like you would define a scheduled task on the administrator's workstation that would launch AIDA64 using a command-line option like /CLEANDB that would remove outdated reports from the database?

It seems this is an issue that plagues AX1200i PSUs, but it still works properly with AX760i. AX1200i seems to report 0 Ampers and 0 Watts for the +5V and +3.3V rails in many cases, and that prevents AIDA64 from calculating the total PSU power draw. We'll have to gather more feedbacks on other AXi Series PSUs to see what's going on. It would be interesting to see if Corsair Link software can show a stable power draw reading for all voltage rails on AX1200i...

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. This one should work with both Corsair Link v3.x and v4.x. 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

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

I don't think so. What could happen is a faster battery discharge when you keep AIDA64 running in the background to monitor your notebook. Monitoring hardware uses a few percentage of CPU load, and that causes higher overall system power draw than without it.

AIDA64 information pages are not structured like that. They use a linear layout. The Overclock page uses 2 columns with text, so there's no room or place for graphs or other special visual elements. We've developed the CPU Clock Monitor for that purpose