Fiery

You only need to have Asetek LC sensor support enabled in order to have H115i Pro readings.

We're already working on enabling drag & drop Stay tuned........

That motherboard info doesn't say much to be honest Do you know the actual motherboard model you've got? Please try to click through the sub-pages of ACPI, e.g. ASF!, DMAR, etc, and see if after clicking one of them, an error message is shown.

Some of the security patches are for SMT/HyperThreading enabled systems And yes, in several cases certain workloads do indeed work best without SMT/HTT.

Thank you. Make sure to close Corsair's iCUE software and Corsair's Link software before starting AIDA64. Corsair's own monitoring software is not designed to work well with 3rd party monitoring software running the same time. Also, make sure that you have Asetek LC sensor support enabled (checked) in AIDA64 / main menu / File / Preferences / Stability.

I suppose when you check AIDA64, iCUE is closed, right? Maybe iCUE changes the fan PWM settings before quitting and/or when you open it. We've checked with default settings on our H150i Pro device, and both fan RPMs and pump RPM are identical across AIDA64 and iCUE.

The VP8 reference results now depend on the Windows type, BIOS version, and the security patches you may or may not have applied on your current Windows system. Also, the VP8 benchmark doesn't scale well on 6+ core CPUs. Due to those issues, we're considering retiring the VP8 benchmark in the next AIDA64 update, along with introducing a new benchmark method. Here's the AIDA64 v5.98.4800 VP8 benchmark score we've just measured using an i7-8700K CPU, in a Gigabyte Z370 Aorus Gaming 7 motherboard and Windows 10 64-bit. The motherboard had the latest BIOS (F7) flashed, and Win10 had all patches applied to date (Win10 build number 10.0.17134.286). 6751

Thank you for your suggestions. We'll work on them in the upcoming weeks, and will send you updates via this topic.

I'm glad you've found it, but for other users it would still be useful to mention that it is available as the Alerting feature that you can configure in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Alerting.

What is the exact difference between the measured values, at various fan speeds? Maybe there's a 0.5x or 0.33x ratio that has to be applied to the readings?

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Corsair Link Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Also right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Thank you for the dumps. I'm not sure what's happened, but we'll fix this issue in the next AIDA64 beta due in a few days from now. I'll post a message into this topic once the new beta build is available for download.

What is the exact Registry path of the keys you're referring to?

The VP8 benchmark of AIDA64 is indeed highly affected by some of the vulnerability patches of this year.

HWiNFO and HWMonitor might fit the bill.

We'll try to improve on that. It's not easy, since there're hundreds of sensor readings, coming from various sources (like CPU, chipset, onboard devices, HDD, SSD, video card(s), etc). You can only see a few of them, but the capabilities of AIDA64 is much wider than what you can experience on one system. Maybe the best way would be to enable re-arranging items on the Sensor page?

We will fix the issue in the next AIDA64 beta update due next week.

That's normal. We've had to disable BCLK polling due to serious collisions with Windows 10 kernel that is also polling BCLK since the latest Win10 update of 1803. Now BCLK is only measured once, and then the measured value will be used in subsequent CPU clock measurements. Note that the current CPU clock will still be accurately measured, it just wouldn't fluctuate due to BCLK measurement fluctuations.

The new AIDA64 update implements VAES optimized AES benchmark, adds monitoring of sensor values on EVGA Z10 LCD keyboard, and supports the latest AMD and Intel CPU platforms as well as the new graphics and GPGPU computing technologies by both AMD and nVIDIA. New features & improvements - Microsoft Windows 10 October 2018 Update support - VAES optimized AES benchmark - EVGA Z10 LCD support - Improved support for ARM64 systems - Thermaltake Riing Plus sensor support - Improvements for AMD B450 and X470 chipset based motherboards - Corsair H80i Pro, H100i Pro, H115i Pro, H150i Pro sensor support - Support for Matrix Orbital EVE LCD displays and OK OLED displays - Vulkan 1.1, WDDM 2.4 support - GPU details for AMD Radeon RX 560X, Radeon RX 570X, Radeon RX 580X 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 - Proper DPI scaling to better support high-resolution LCD and OLED displays - AVX-512 optimized benchmarks for Intel Skylake-X and Cannon Lake CPUs - AVX and FMA accelerated 64-bit benchmarks for AMD A-Series Bristol Ridge and Carrizo APUs - AVX2 and FMA accelerated 64-bit benchmarks for AMD Ryzen Pinnacle Ridge, Raven Ridge, Summit Ridge, and Threadripper processors - AVX2 and FMA accelerated 64-bit benchmarks for Intel Broadwell, Kaby Lake, Kaby Lake-X, Skylake and Skylake-X CPUs - AVX and SSE accelerated 64-bit benchmarks for AMD Nolan APU - Optimized 64-bit benchmarks for Intel Apollo Lake, Braswell, Cherry Trail, Denverton, Gemini Lake processors - Preliminary support for Intel Knights Mill HPC CPU - Improved support for Intel Cannon Lake CPU - Advanced SMART disk health monitoring - Hot Keys to switch LCD pages, start or stop logging, show or hide SensorPanel - Asus, Corsair, Logitech, Razer RGB LED keyboard, mouse and mousepad support - Asus ROG RGB LED motherboard and video card support - AlphaCool Heatmaster II, Aquaduct, Aquaero, AquaStream XT, AquaStream Ultimate, Corsair Commander Pro, EVGA iCX, Farbwerk, MPS, NZXT GRID+ V2, NZXT Kraken X52, PowerAdjust 2, PowerAdjust 3 sensor devices support - Corsair AXi, Corsair HXi, Corsair RMi, Enermax Digifanless, Thermaltake DPS-G power supply unit sensor support - Support for EastRising ER-OLEDM032 (SSD1322), 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, LGA-2066, Socket AM4, Socket TR4 motherboards - Improvements for Intel Cannon Lake PCH chipset based motherboards - 20 processor groups support - Support for USB 3.1 peripherals - Extended ACPI table decoding - Advanced support for 3ware, Adaptec, AMD, Areca, HighPoint, Intel, JMicron, LSI, Marvell RAID controllers - RAID member enumeration for Intel NVMe RAID arrays - ACPI 6.1, CUDA 8.0, NVMe 1.3, OpenCL 2.1, OpenGL 4.6, OpenGL ES 3.2, SMBIOS 3.1.1, VirtualBox v5.0, WDDM 2.3 support - Corsair Neutron XT, Crucial BX100, Crucial BX200, Crucial M600, Crucial MX200, Crucial MX300, Intel Pro 5400s, Kingston HyperX Predator, Kingston HyperX Savage, Kingston SSDNow UV300, Kingston SSDNow UV400, Lite-On MU II, OCZ Trion 100, OCZ Vector 180, Plextor M6V, Samsung CM871, Samsung PM851, Samsung PM871, SanDisk Plus, SanDisk Ultra II, SanDisk X400, SanDisk Z400s, SK Hynix SC300, WD Blue SSD support - GPU details for AMD Radeon Rx 300, RX 400, RX 500, R9 Fury Series - GPU details for nVIDIA GeForce GTX 950, GeForce GTX 960, GeForce GTX 980 Ti, GeForce GTX 1000 Series, GeForce GTX Titan X, Quadro M3000M, Quadro M5000M, Quadro GP100, Tesla M60, Tesla P6, Tesla P100, Titan Xp [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (italiano) ] [ Press Release (magyar) ] [ What's new in AIDA64 v5.98 ] [ Download ]

Thank you for your feedback

Thank you. Here's the fix for your motherboard as well as other motherboards that are affected by the same anomaly. https://www.aida64.com/downloads/latesta64xebeta

Thank you for your detailed reply, it was a huge help for us to dig down deeper, replicate and then fix this issue. Here's the fix: https://www.aida64.com/downloads/latesta64xebeta

On Nehalem family processors it's detected using a CPU register. So there're no pre-defined values. Older processors (like Core 2 Duo) the CPU didn't have the Tjmax value encoded in a register, so we have to use pre-defined values.

We will fix the issue early next week.

It looks awesome! I hope we can keep working together on implementing support for even more Matrix Orbital products in AIDA64