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.

You can subscribe to the AIDA64 Newsletter at: https://www.aida64.com/goto?p=newsletter

Did you keep your "old" DDR4 memory modules when you've upgraded your CPU? Did you only change the CPU or the motherboard too?

Thank you for the feedback

In case DIMM temperature readings fluctuate by showing a weird anomaly, then it is most likely due to a collision on the SPD SMBus. Are you running any other hardware monitoring, tweaking or overclocking software in the background?

Only the latest AIDA64 beta build implements full support for GeForce GTX 1080 and GTX 1070. Make sure to upgrade to it: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

GPU1 should be your primary GPU. Do you have more than one GPUs in the system? If yes, then make sure to enable the option Wake GPUs up at AIDA64 startup in AIDA64 / main menu / File / Preferences / Stability.

It should already be available as GPU Clock in the list of items you can place on your LCD.

Thank you for the feedback

The above mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta

The mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works

The above mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor 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 --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Also, please create a screen show of Asus' own hardware monitoring utility, of the page where it shows the temperature and voltages readings. That way we could have a reference list of readings that we could use to calibrate the temperatures and voltages in AIDA64. In case you cannot find such Asus utility, then please create a photo of the H/W Monitor page of the BIOS Setup (UEFI Setup) for the same purpose Thanks, Fiery

1) That's an issue of character set differences between Windows and the LCD device. We usually recommend against using the degree character simply because it takes precious space away from useful readings. If you have a 4x20 LCD, it's only 80 characters to display something useful. I wouldn't waste any characters on a degree character 2) Same issue as #1: alphanumeric LCDs should be used to display vital information, not just static labels.

You only need to worry -- slightly -- in case your CPU throttles under heavy load. You can check the throttling state (in %) in AIDA64 / main menu / Tools / System Stability Test.

CPU Package is not Tcase. It's what was explained on the other forum. Processur (or "CPU") is provided by the sensor chip integrated on your motherboard. I can't comment on Intel XTU, since it's not our software. It may use an offset value of minus 5 Celsius on the actual CPU Package reading though. But that's just a theory.