Fiery

Yes, it works fine. Although, we're not quite sure if you can trust the CPU Package power reading. It seems to provide strange readings, even though we use it the right way.

Which temperature readings go missing when your CPU is overclocked?

Thank you, we'regetting closer Can you please check what happens if you keep SensorPanel enabled/showing, but you disable the CPU Utilization item(s) -- I suppose you have some of those on the panel (?)

Thank you, we'll add that in the next AIDA64 beta update

AFAIK, the power in and power out values are not quite accurate on Corsair AXi PSUs, and that's why we don't measure them. Efficiency is calculated using a formula, and the formulas we've seen didn't seem too easy to use, e.g. they required special correction values specific to various PSU models, etc. As for your UPS, please right-click on the bottom status bar of AIDA64 main window --> System Debug --> Battery 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. Thanks, Fiery

How many network adapters can you see listed on the Network / Windows Network page? Does it match the number of NICs you can see among the LCD items list?

Thank you. I suppose you have some of the hardware monitoring modules enabled while running the Stabilty Test. Is it the OSD Panel, SensorPanel, or both maybe? We're trying to replicate the issue on our own Skylake test machine, but no luck so far... We probably need to make our config look even more similar to yours.

It depends on what subtest(s) you enable. If you only enable FPU, then you can reach the maximum CPU temperatures. It's because the FPU subtest uses heavy AVX and FMA floating-point code, and that is the method to use on modern processors to get them heat up the most. However, that may not be the best method to hunt down computing errors or RAM CRC errors. If your intention is error-checking, then it's best to enable CPU+FPU+RAM+Cache substests altogether. That way your processor will not run as hot as with the FPU subtest alone, but the workload will be much more diverse, and so potential computing glitches will be revealed much easier. In most cases we recommend at least a few hours of FPU stressing, in order to check if the CPU and chassis cooling solution are both adequate. Then, if it passes, it's best to run the CPU+FPU+RAM+Cache subtests as well, for a few more hours. Optionally you can also enable HDD and GPU stressing in this second round, although in most cases it will take precious CPU cycles away from the other 4 subtests. Of course if you have time and you want to be 100% thorough, in a 3rd round you can check all subtests and put a few more hours into yourstress testing session

Thank you! The issue will be fixed in the next AIDA64 beta update due next week. I'll post a message into this topic once the new beta is available for download.

Thank you. Those 2 voltages are not monitored by your motherboard. You can adjust those voltages, but not monitor their current values.

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. Make sure to use the latest AIDA64 beta build v5.80.4093: https://www.aida64.com/downloads/latesta64xebeta

For Core 2 processors I'd consider that a serious issue. Make sure to improve the CPU cooling and/or case cooling of your computer. A Core 2 processor should never throttle and heat up that much, even under heavy stress.

Thank you for your feedback

Thank you for the feedback. Are you using Windows 7 64-bit SP1 with all the hotfixes applied?

Thank you for your feedback

Please send me your old email address and full name in private message, and I'll send you your AIDA64 product key.

Thank you. We've fixed it up in the latest AIDA64 Extreme beta update available at: https://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. Thanks, Fiery

Thank you. We've fixed it up in the latest AIDA64 Extreme beta update available at: https://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. Thanks, Fiery

We've implemented sensor support for ASRock H270M Performance, H270M Pro4 and Z270M Pro4 motherboards in 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.

The above mentioned AIDA64 beta update is now available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

Thank you. Is it buggy no matter if you're trying to play video or audio files?

Thank you! What was the value of the 2 missing voltages when you created those dumps? What label can you see displayed for those values in the BIOS Setup? Are you sure the values can be monitored, not just configured/adjusted? Can you please submit a photo of the BIOS Setup screen where you can see those 2 voltages monitored?

It's not possible right now. We may enable that in the near future though, along with RTSS OSD label styling.

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.. Thanks, Fiery

I think the issue may be the limitations of RTSS, which is 256 characters for the whole text to be displayed on the RTSS OSD.