Fiery

CPU Package should include GT Cores and IA Cores power. Regards, Fiery

The source of the reading is added because when you've got an external sensor device (e.g. Aquaero), it becomes tough to identify which temperature or fan reading comes from which device. "Motherboard" in this case means the reading comes from a sensor chip integrated on the motherboard. As for renaming, it's not planned for the Sensor page, since you can already do that with the OSD Panel, SensorPanel, LCD (etc). It's not convenient to use the Sensor page for long term monitoring purposes. It's there to let you have a quick overview of the values AIDA64 can measure. But in most cases you don't need all measurements, and/or want to rearrange or reformat the readings -- and that's where you would want to switch to using the mentioned AIDA64 modules (e.g. SensorPanel) instead. Regards, Fiery

Thank you We'll keep working on it in the next few beta updates.

Please check the latest AIDA64 beta of Build 4068: https://www.aida64.com/downloads/latesta64xebeta Let me know if it helps.

Thank you. Please let us know when your new build is ready. Let's hope it will solve this issue. If not, we'll keep hunting for the bug

In the latest AIDA64 beta, we've implemented a new option in the Preferences of System Stability Test. It let's you prevent your computer from going to sleep while the stress test is running. Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

Please check the latest AIDA64 beta of Build 4068: https://www.aida64.com/downloads/latesta64xebeta It should work better with X99 chipset based systems now, and hopefully will not force you to use the Refresh button

Thank you for the bug report. We'll build a similar configuration and try to reproduce the issue in order to fix it up.

Thank you for the info. Let's hope in the 2nd hardware revision ASRock can fix the issues about accessing the sensor chip under Windows. There's a good chance A-Tuning Utility doesn't support H270M Pro4 because of that hardware issue...

Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

What processor and motherboard do you have, and what version of Windows are you using? We're not planning to enable that, since you can already do that using the SensorPanel module of AIDA64.

That's normal, and is due to the fact that AIDA64 uses OpenCL to stress the GPU(s) in the system. And OpenCL works through the Direct3D display layer. When you use a demanding OpenCL kernel, it could cause the display to lag.

Yes, that's a known issue of the new Catalyst drivers. We'll implement a workaround in the next AIDA64 beta update, that will effectively remove the nonsense voltage value BTW on R9 290X video cards, AIDA64 shows the GPU Vcore as "GPU VRM".

I don't know, I'm sorry

Thank you. We're not ready to give up yet Please also post a Super I/O Dump. You can find it in the same right-click menu where ISA Sensor Dump is.

Thanks a lot! I've sent you another private message

Thank you. Does it mean you've got only one of those SSDs connected to the JMB363 controller, and you've got the other one connected to the internal SATA controller of your chipset?

Thank you. I've sent you a private message about this issue.

Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Please post a new ISA Sensor Dump. We've extended that dump to better suit the special sensor solution of your motherboard. If it's possible, please also create a screenshot (photo) of how the sensor readings look like in the BIOS Setup (a.k.a. UEFI Setup), so we can have a better understanding on what values your motherboard can measure. Thank you for your help.

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

I'm not sure why the CPU drops to 3.50 GHz. It's not supposed to do that, as long as the base frequency is properly configured as 3.60 GHz by the BIOS at bootup.

Please give us a few more days to diagnose this issue. I'll get back to you in this topic soon. Thank you for your patience, and for the data you've submitted above

That is actually due to an AIDA64 bug We will fix it in the next AIDA64 beta update due in a few days from now.

Those pages show static information, which was detected or measured at the time you start AIDA64. The CPU core frequency displayed there are influenced by both Turbo Boost and the power management (power-saving) features of your CPU, namely SpeedStep and C1E (Enhanced Halt State). Dynamic clock measurement is available on the Computer / Overclock page, and the AIDA64 CPUID Panel (main menu / Tools / AIDA64 CPUID). I'm not sure what CPU-Z is doing. Please note that it's not our software, so we don't have a full understanding on what it does or what bugs it might have about clock measurement

Thank you. Was the 4x4GB kit also DDR4-3200 and also made by Corsair?