Fiery

On the SensorPanel make sure to use a more frequent update rate. 500 milliseconds should be safe, but you can even go down to 100 millisec.

We haven't changed anything about that particular sensor item between 4321 and 4329 beta builds. If it still works incorrectly, please create a screen shot of he issue and post it.

Thank you, the issue will be fixed in the next AIDA64 beta update due in a few hours from now

If you want to focus on the real cores and ignore the secondary (virtual) cores of SMT/HyperThreading, you simply need to skip every second logical processor.

Since the RAM acts up not only with AIDA64, but also with another stress testing software, I suspect it may just be some kind of compatibility issue between your RAM modules and your motherboard. You may want to ask Gigabyte to resolve the issue in the next BIOS update.

Does it get stuck after the report creation process is complete, or somewhere in the middle?

We've checked, and we couldn't reproduce the issue on our 5820K based test system (with HTT disabled). The next time it occurs on your system, please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR 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

Anytime

1.8V is not VID at all, but some bogus value

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

That happens when the sensor item is no longer available. Do you still have the UPS connected to your computer?

We've done some experiments on that, but it wasn't successful. If the BIOS fails to properly initialize the thermal controller, PCH Diode temperature cannot be measured by Windows software or any other method

The video driver reset takes a second or two, and after it is done everything should go back to normal. Except for the GPU subtest of the AIDA64 System Stability Test which will be stopped after the video driver reset. So in case a permanent blackscreen is exhibited, it may be due to a video driver reset issue in the first place, but then the video driver cannot recover due to -- in most cases -- a hardware stability issue. In other words: if you cannot get the display output working after the video driver reset, it's a hardware malfunction. Such malfunction can be due to a number of reasons, including excessive overclocking (and/or overvoltage), overheating, video memory stability issues (or overheating), PCI Express communication breakdown, etc.

And we've done that in the latest AIDA64 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.

The mentioned new AIDA64 beta update is 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.

We've added the requested new hot key 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.

1) If you're a power user, then I suppose shifting the indexes by one shouldn't be a problem 2) Please make a screen shot (or report, or copy-paste) of the Storage / Physical Drives page of AIDA64 at both states (when it's OK; and when the anomaly occurs).

Thank you, that's great to hear

Power out is calculated using the same formula as power efficiency. Efficiency = power out / power in. And out of those 3 values only the power out value can be directly measured or detected on most PSUs.

I'd still say: I don't think it would qualify your motherboard for a RMA, but it may worth a try to call the store where you bought it.

The best idea is to use an old classic LCD display (monitor) that you can connect via DSub or DVI cable, and extend your Windows Desktop onto it. Then you can sack the Samsung LCD module and use the much smoother working SensorPanel instead. If you want to re-use your Samsung LCD layout on your SensorPanel, then simply export the LCD layout (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / LCD Items) and import it back to your SensorPanel using the SensorPanel Manager. You can launch the SensorPanel Manager via the right-click context menu on the SensorPanel.

It could be the uncommon setting of disabled HyperThreading. Just in case, we'll check that scenario with our i7-5820K CPU.

Thank you for your feedback. Quite frankly, I would have done the same, ie. to sack the HDD with the "weird" working firmware and use a different HDD model instead.

Thank you. We'll remove the CPU Core voltage reading on Gigabyte X299 motherboards, and use CPU VID voltage as Vcore from now on.

Thank you. Can you please try to configure the same fan duty cycle (%) value in AIDA64 / main menu / File / Preferences / Hardware Monitoring that you have configured in Corsair Link Software? Check the "Set Asetek fan speed" checkbox, and set both % values to the fan duty cycle of your choosing.