Fiery

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

That is not really ignorance, but more a failed understanding of how AIDA64 memory bandwidth benchmarks work. Even hardware manufacturers (I won't name drop here) fall into that trap from time to time. What's important to know about our memory bandwidth benchmarks is that even though they are multi-threaded, it doesn't mean that they will always utilize all available cores or logical processors (threads) to measure bandwidth. We use a clever automatic calibration process that finds the optimal number of CPU resources to attain the highest possible memory bandwidth scores. The whole UMA vs. NUMA score issue would look different if AIDA64 always utilized all 16 cores (or 32 threads) of AMD Threadripper processors.

I'm glad you could resolve it, because we couldn't find out what's wrong on our end. We've tried to replicate the issue, but the only idea we came up with -- and even that one was a weak one -- is that your internet connection to our server (that provides the external IP info) is very slow for some reason. As for alerts: the existing AIDA64 Alerting module doesn't support changing label colours when an alert is fired. You can have a warning message box popped up, your computer shut down or an audio alert fired (played).

In our opinion that information is very helpful, especially when the system has multiple drives of the same model. Why would you want to hide that information?

Thank you. We've fixed the issue 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. Let me know how it works.

Thank you for the dumps. We've fixed the issue 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. Let me know how it works.

No, it's not. But here's the one that is https://www.aida64.com/downloads/latesta64xebeta

We haven't noticed it yet, and no other US based AIDA64 users complained yet. We've asked our ISP, but they also haven't found any issues. So it could have been (it could be) something under the ocean or such

"Waiting for Sync" is not displayed by AIDA64, so the issue must be in either the Android platform (about email submittal), or in the email app you use to send the report out.

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.