Fiery

Thank you for the feedback

I've sent you an email about the SMBus issue. As for the benchmark reference results setting, that's exactly how it should work.

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

Thank you. 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. Let me know how it works.

Thank you. 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. Let me know if it helps.

We've fixed the CPU utilization measurement issues in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works

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

Thanks a lot! Please try the latest AIDA64 beta available at: https://www.aida64.com/downloads/latesta64xebeta If it still crashes while scanning the SMBus, please let me know the new device index where it stops.

If you could check what's the device that's scanned when the system turns off, we can filter that device out. Previous MSI boards with Z170 and X99 chipset are sensitive for scanning at device 21h, 22h and 23h, so we skip those devices there. We haven't received any guidelines from MSI about Z270 boards, so we somehow have to discover if there are sensitive devices there too

I suppose the BIOS is doing some magic on your MSI motherboard

The difference between how NB clock is measured on the Overclock page vs. on the Cache & Memory Benchmark panel, is that the latter will disable the power management facilities (namely EIST a.k.a. SpeedStep and C1E a.k.a. Enhanced Halt State) of the CPU before measuring the clock speeds. Maybe MSI motherboards alter the behavior of the NB, ie. adjust its operating frequency in a proprietary way when those power management features are disabled? As for the SPD bank switching issue, it looks a lot like a BIOS issue.

I'm afraid we have no idea what could work incorrectly about the NB clock measurement. How do you know it's an issue limited to MSI motherboards? As for the SPD issue, for some reason your memory modules cannot perform SPD bank switching. Bank switching is necessary to read the full 512-byte SPD block of DDR4 memory modules. Can you please check if CPU-Z is also affected?

Please note that in order to detect the missing details, the camera ID information had to be previously encoded into the Android profile of the device. When the manufacturer of the devcie (in your case Sony) didn't encode the info there, then sysinfo apps cannot read or detect it.

Please avoid starting multiple topics for a single issue. I've replied in your other topic. This topic is locked.

We're not 100% sure that AMD is right about that chart. So we're holding off applying a fix, and asked AMD for more information and clarification. You can however apply the -20 Celsius offset if you want: go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction, press the New button below the chart, select CPU Diode from the list of temperature readings, leave Ratio at 1, enter -20 into the Offset field, and press OK. You will need to remove that correction entry once we implement a native fix in AIDA64 for the tCTL offset issue.

Can you see the GPU clock and memory clock info on the Display / GPU page?

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.