Fiery

Corsair Link Software keeps evolving, and we're adjusting AIDA64 to suit the latest CL Software version. If you install the latest CL Software and the latest AIDA64, they should be able to work together, without a collision. The next version of CL Software will be even more secure about avoiding collisions. Corsair Link sensor support refers to the CL Framework. It's when you have a CL Commander central unit and you hook your devices onto it -- rather than hooking up the same devices via direct USB connection. When you have devices connected via USB, the CL Framework is not utilized at all, and so altering the Corsair Link sensor support option does nothing. I know, it's quite confusing that both the CL Software and the CL Framework are called CL, but that's Corsair's choice on the technical term.

Do you mean we should add those 3 lines to the SSE response that starts with: HTTP/1.1 200 OK Content-Type: text/event-stream Cache-Control: no-cache

I'd start with: 1) Update motherboard BIOS to the latest one 2) Set memory module timings to a more relaxed setting, dictated by the classic SPD block rather than the XMP (Extreme Memory Profile). If that still doesn't help, then I'd try it with 2T Command Rate (tCR or tCMD) setting as well. If none of those help, it could still be a faulty memory module, a dying motherboard or a faulty PSU. Not easy to diagnose such issues though If you have a chance to borrow a reliable PSU, it would worth checking that too. Regards, Fiery

If you use a background image, then you have to adjust its size to make sure it is the same dimension than your SensorPanel. Magnification is not supported by the SensorPanel.

I'm afraid it's not possible to measure RAM clock speed under Android. Regards, Fiery

You can adjust the SensorPanel dimensions (width and height in pixels) in AIDA64 / main menu / File / Preferences / Hardware Monitoring / SensorPanel.

Thank you for the feedback

Please give us a few days to diagnose this issue, and to come up with a more detailed chipset detection code for Skylake. I'll get back to you in this topic once a new beta update to AIDA64 is available for you to try

We've already implemented the necessary synchronization techniques to make sure AIDA64 can work together with Corsair Link Software. If it still doesn't work as expected, then you can do the following: 1) Disable Asetek sensor support in AIDA64 / main menu / File / Preferences / Stability. That way however you will lose the sensor readings coming from H115i. 2) You can try tweaking the Asetek fan speed value in AIDA64 / main menu / File / Preferences / Hardware Monitoring. You only need to adjust the first percentage value in case you have a single water cooler. You may find a setting that would produce the same RPM output that you've configured in CL Software. 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.

Thank you for letting us know about your workaround. We've tried to replicate the issue on our own test systems, but without a luck. I don't like to say it, but I really have no idea what's wrong on your system. Could be a timing issue, a BIOS pecularity or even a driver bug.

You can measure disk read speed and write speed, but not as a percentage (activity) value, but the amount of data being transferred in bytes/sec. AIDA64 supports all those readings, so you don't have to rely on the activity % value. You can simply rely on the Disk N Read Speed and Disk N Write Speed values

Not possible, since the activity percentage is reported as idle % actually. So when e.g. it is being reported as 29% idle, AIDA64 will show 71% activity.

Max/avg temperature highly depends on the type of computer, the kind of processor you use, the type of system case, the amount of overclocking you've applied, etc. etc. So there's no generic rule there. If you want to put temperatures further down, then the only way to go forward is to improve the ventilation of the system case, and/or to install water cooling. On the software level the only way is to reduce clocks and voltages.

Usually there are 2 questions that the AIDA64 System Stability Test should answer: 1) Is the system stable, even while running a very demanding task? 2) Is the system overheating under very high load? In your case, issue #1 is cleared, since the computer didn't show any abnormal behavior while running the test. As for #2, I can't see anything critical among those maximum temperature readings, so all is well. You can go on by analyzing minimum and maximum voltages, but in case they were hitting critical levels during the stress test, your computer would have locked up or Windows thrown a BSoD. Regards, Fiery

Without administrator privileges several readings cannot be provided. That's because communicating with sensor chips requires a kernel driver, and only administrators can load a kernel driver. Administrator privilege is required for a bunch of other readings too, like SPD memory module information, GPU details and chipset details (e.g. memory timings, DRAM:BCLK ratio, etc).

Thank you, it would be great if you could push your luck about this issue. On our part, the only missing piece of the puzzle is the Vcore reading. It would be very useful to know exactly what register of which sensor device holds the Vcore reading, and what formula shall we use to calculate the actual voltage measurement value. Currently on the EVGA E178 motherboard (that you've got) AIDA64 uses register 0x0C (MSB) and register 0x0F (LSB) of the secondary Nuvoton NCT7802Y sensor chip (at SMBus device 0x2F) to measure Vcore, and it calculates the voltage value by using the following formula: RawRegisterReading x 0.002 x 0.9808

Our Windows 10 UWP app doesn't currently handle more than one GPU. But, the Surface Book is more than capable of running classic Win32 software like GPU-Z and AIDA64 Extreme Give it a try: http://www.aida64.com/downloads Regards, Fiery

Thank you for the report. It seems the Skylake IMC ECC state detection method that AIDA64 currently uses isn't the proper one. We'll try to find a new method and get back to you soon in this topic.

You're right We'll remove it in the next AIDA64 beta update.

Thank you, but since we're not even sure if we're using the right register for Vcore reading, I would be hesitant to apply an offset on the reading. You can however apply a Correction offset in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction.

Thank you for the feedback

AIDA64 v5.75 provides support for the latest hardware, including the recently announced nVIDIA Pascal and AMD Polaris graphics processors. The update also comes with benchmarks optimized for the newest Intel processors. The latest AIDA64 update implements optimized benchmarks for the upcoming Intel Kaby Lake processors, and supports the latest graphics and GPGPU computing technologies by both AMD and nVIDIA. New features & improvements - AVX2 and FMA accelerated 64-bit benchmarks for Intel Kaby Lake and Broadwell-E/EN/EP/EX CPUs - Microsoft Windows 10 Redstone RS1 Insider Preview support - Improved support for AMD Zen Summit Ridge CPU - AquaStream Ultimate and NZXT GRID+ V2 sensor support - Improved Corsair Link sensor support - Kingston SSDNow UV400 SSD support - Preliminary support for AMD Radeon RX 470 and Radeon RX 480 GPUs - GPU details for nVIDIA GeForce GTX 1070, GeForce GTX 1080, Tesla P100 What's new since AIDA64 v5.00 - AVX and FMA accelerated FP32 and FP64 ray tracing benchmarks - Vulkan graphics accelerator diagnostics - RemoteSensor smartphone and tablet LCD integration - Logitech Arx Control smartphone and tablet LCD integration - Microsoft Windows 10 TH2 (November Update) support - AVX2 and FMA accelerated 64-bit benchmarks for Intel Broadwell and Skylake CPUs - AVX and SSE accelerated 64-bit benchmarks for AMD Nolan APU - Optimized 64-bit benchmarks for AMD Carrizo APU - Optimized 64-bit benchmarks for Intel Braswell and Cherry Trail processors - Preliminary support for AMD Bristol Ridge and Stoney APUs - Preliminary support for AMD Raven Ridge APU - Preliminary support for Intel Apollo Lake, Broxton, Kaby Lake CPUs - Preliminary support for Intel Cannonlake, Goldmont, Skylake-E/EN/EP/EX processors - Advanced SMART disk health monitoring - Corsair K65, Corsair K70, Corsair K95, Corsair Strafe, Logitech G13, Logitech G19, Logitech G19s, Logitech G910, Razer Chroma RGB LED keyboard support - Corsair, Logitech, Razer RGB LED mouse support - AlphaCool Heatmaster II, Aquaduct, Aquaero, AquaStream XT, Farbwerk, MPS, PowerAdjust 2, PowerAdjust 3 sensor devices support - NZXT Kraken water cooling sensor support - Corsair AXi, Corsair HXi, Corsair RMi, Enermax Digifanless, Thermaltake DPS-G power supply unit sensor support - Support for Gravitech, LCD Smartie Hardware, Leo Bodnar, Modding-FAQ, Noteu, Odospace, Saitek Pro Flight Instrument Panel, Saitek X52 Pro, UCSD LCD devices - Portrait mode support for AlphaCool and Samsung SPF LCDs - SensorPanel and LCD: right-to-left bars, static label control strings - 0.01 Celsius temperature measurement resolution for select sensor items - System certificates information - Support for LGA-1151 motherboards - Support for USB 3.1 peripherals - Extended ACPI table decoding - Advanced support for Adaptec and Marvell RAID controllers - Autodetect information and SMART drive health monitoring for Intel and Samsung NVMe SSDs - ACPI 6.1, CUDA 7.0, OpenCL 2.1, OpenGL ES 3.2, SMBIOS 3.0, VirtualBox v5.0 support - Corsair Neutron XT, Crucial BX100, Crucial BX200, Crucial MX200, Kingston HyperX Predator, Kingston HyperX Savage, Kingston SSDNow UV300, Lite-On MU II, OCZ Trion 100, OCZ Vector 180, Plextor M6V, Samsung CM871, Samsung PM871, SanDisk Ultra II, SanDisk Z400s, SK Hynix SC300 SSD support - GPU details for AMD Radeon Rx 300 and R9 Fury Series - GPU details for nVIDIA GeForce GTX 950, GeForce GTX 960, GeForce GTX 980 Ti, GeForce GTX Titan X, Quadro M3000M, Quadro M5000M, Tesla M60 [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (italiano) ] [ Press Release (magyar) ] [ What's new in AIDA64 v5.75 ] [ Download ]

No problem at all It's always good to learn more about how overclocking affects the detection and system monitoring modules of AIDA64.

Heavy memory overclocking could cause anomalies on the memory bus that could prevent a stable DIMM TS temperature readout. If you could try returning your memory modules to their stock clock speed (well, the stock speed of the CPU, DDR4-2400 would be even better as a test), and check it that way, it would be very helpful.