Fiery

Such issues could happen when one or more drives disappear from the system due to them going to sleep or get disconnected from the system for other reasons. AIDA64 will then re-enumerate the available drives and the drives indexes could well change. It's quite difficult to get around such issues unless you can make sure to have all drives available all the time (by e.g. disabling disk drives sleeping and other power saving tricks). Core Temp should have no problem working together with AIDA64. Asus GPU Tweak -- just like other Asus monitoring software like AI Suite -- may cause collisions though.

On Gigabyte Z390 Aorus Master Chassis #7 fan is CPU_OPT fan. We'll fix the fan labels for your motherboard in the next AIDA64 beta update.

Thank you for your kind words. Happy new 2019!

On a case by case basis we can increase that value. For what LCD device do you need more than 4 pages?

AIDA64 doesn't support providing the necessary buffer size, so you gotta do some test runs to find out what buffer size you need to use to comfortably fit all items you've selected.

Is the same high VRM temperature reading reported by the UEFI Setup (BIOS Setup) or ASRock's own monitoring utility?

1) "CPU" is measured by the motherboard sensor chip, while "CPU Diode" is measured by the CPU itself using its on-die thermal diodes. We generally recommend using the latter, since it doesn't depend on the motherboard or the motherboard sensor chip. 2) It depends on the motherboard model. It may be an invalid (bogus) reading either. What kind of motherboard do you have?

Such a change is most likely intentional, so the new temperatures are the valid ones. If you have doubts about that, I'm afraid I have no further technical details on it, so I cannot weigh in on this

VRM1 and VRM2 temperatures are measured and reported by the onboard VRM/PWM controller chip, usually made by CHiL or IRF.

Apart from losing a few sensor readings, you don't lose any functionality in AIDA64 by disabling EC support. EC latency is only a problem if you're running a software that polls EC registers. And those are typically hardware monitoring tools like HWiNFO, HWMonitor, SIV, SpeedFan, etc. Other kind of software would never go as deep as to talk to the EC, since they have no information to gather from the EC at all.

I've sent you a private message about this.

Please try to create a Sensor Profiling Dump right after you start AIDA64. Hopefully it won't freeze then.

Thank you, we've added this display to AIDA64.

Please show me the code you're using to open the shared memory incl. the mapping and unmapping sections. If you prefer to keep your code from the public, you can send it to me in private message as well.

As I've explained it in your other topic, please contact me in private message and describe what you have configured as e-mail settings in AIDA64 / main menu / File / Preferences / E-mail.

Try to disable RAID features as I've explained above.

You're right, our implementation of the VRM temperature turned out to be inadequate. We'll fix it up in the next AIDA64 beta update.

Do you have any special images placed on your SensorPanel layout, or any custom gauges?

1) It would be best to first check what might cause the high CPU usage. Try to right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling 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 --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Generally speaking, certain Asus motherboards could operate with a very high EC (Embedded Controller) latency that would cause AIDA64 sensor module to load the CPU for several milliseconds. You can check if your motherboard is affected by that anomaly by disabling EC support in AIDA64 / main menu / File / Preferences / Stability. Make sure to restart AIDA64 after altering that option. Also note that by disabling EC support you will lose a few sensor readings like CPU OPT fan RPM. 2) It's not really a huge issue, especially if you almost never max out the CPU usage across all cores. If you only load the first 2 or 3 CPU cores using Photoshop, Windows will automatically switch AIDA64 to use one of the other cores to update the sensor readings and the SensorPanel.

Thank you for the info, it's very useful! We'll fix the fan labels in the next AIDA64 beta update. I'll post a message into this topic once the new beta becomes available for download.

I'm afraid that anomaly is due to the way the standard Windows UI element ListView works. We have no control over that behavior.

You can check the list of available network adapters in both cases on the Network / Windows Network page of AIDA64. I think the issue may be because one of the network adapters gets removed by Windows for some reason. Maybe a WiFi adapter that gets disabled and enabled sometimes?

No restrictions on the shared memory access in the trial version. Have you tried to perform the shared memory reading operation by using elevation?

Please contact me in private message and describe what you have configured as e-mail settings in AIDA64 / main menu / File / Preferences / E-mail.

It is most likely because your notebook has an old Intel RST RAID drivers installed, and the driver gets confused by the RAID enumeration commands that AIDA64 issues. You can however disable the RAID enumeration if you don't have any RAID arrays defined in your system by going to the AIDA64 installation folder and editing the file called AIDA64.INI. Try to find the following 2 lines in it (by using e.g. Notepad): LowLevelRAIDEnum=1 LowLevelRAIDSMART=1 And modify those lines to make them look like this: LowLevelRAIDEnum=0 LowLevelRAIDSMART=0 If you don't have an AIDA64.INI in there, then create a new one (a text file) and put the following lines in the file: [Generic] LowLevelRAIDEnum=0 LowLevelRAIDSMART=0