Fiery

Only the platform developer (ie. the manufacturer of your device) knows what they stand for.

Bars can be rotated by specifying a width that is smaller than the height

It wasn't removed. Try to restart Windows and check the sensor readings again.

In Windows Device Manager probably there's a PCI Express or power management option for either the SATA drive or the SATA controller where your SSD is hooked up to. Altering that option should help to prevent the SSD from going to sleep.

I suppose it's simply because your video card can monitor only a single thermal reading.

What kind of video card do you have, and what version of ForceWare video driver do you have installed?

Yes. Upgrading to a new beta is as simple as that. You can let it overwrite any existing files. It will retain your existing settings (it won't overwrite or remove AIDA64.INI file) as well as your existing license.

Yes. But it's not relevant how you call it, since GT1030 (just like many other GPUs) have only a single thermal diode on the GPU die.

GT1030 only provides a single GPU temperature reading. You can call it "GPU", "GPU Core" or "GPU Diode", it's the same thing for GT1030. The thermal reading is provided by the ForceWare video driver, and measured by an on-die thermal diode located on the GPU die.

AFAIK ForceWare 417.71 is the latest WHQL driver for GT 1030: https://www.techpowerup.com/download/nvidia-geforce-graphics-drivers/

Most video cards only provide a single GPU thermal reading.

TDR delay is automatically fixed by AIDA64. The OpenCL driver is not installed properly, so you gotta make sure to uninstall ForceWare and install the latest ForceWare WHQL driver package to make sure the OpenCL stack is properly installed.

Based on your edit comment, do you still miss an aligment issue or trick? Or is everything good now?

Thank you for posting your results. RTX 2080 Ti has a theoretical single-precision floating-point (FP32) performance of 11.7 GFLOPS at 1350 MHz (base clock), or 13.5 GFLOPS at 1545 MHz (boost clock), or 14.2 GFLOPS at 1635 MHz which is indicated by the video driver of your video card. In case your video card can push its GPU clock further than the indicated 1635 MHz due to GPU boost, the resulting 17.2 GFLOPS could well be accurate.

Thank you. Based on that it's difficult to find the right registers to measure the fan RPM on your notebook (which may or may not be possible in the first place). If it's possible, please submit a report from AIDA64 / main menu / Report / Submit Report To FinalWire, and check (enable) all 3 dumps (Sensor Debug, Embedded Ctrl, ACPI DSDT) on the report submit window.

Thank you!

Thank you for your kind words.

Thank you. GPU-Z doesn't report GPU TDP% at all on your video card. What it reports is the GPU Load that is measured as GPU Utilization by AIDA64, on e.g. the Display / GPU page.

Thank you. I think the issue may be the Asus WMI ACPI interface that was introduced on a few Asus AM4 motherboards so far, including yours. You can try to disable using that interface, but then other issues will appear At this point I'm not sure what can be done on our end, since neither of the available sensor solutions would work 100% reliably on your motherboard.

Thank you for your feedback

No, it hasn't happened yet.

Please let me know what's displayed as "Sensor Type" on the Computer / Sensor page of AIDA64.

Thank you for the data! We've implemented sensor support for EVGA Z390 Dark in the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.

We've removed VRM temperature reading on both ASRock B450 Pro4 and B450M Pro4 in the latest AIDA64 beta build available at: https://www.aida64.com/downloads/latesta64xebeta

We've removed VRM temperature reading on both ASRock B450 Pro4 and B450M Pro4 in the latest AIDA64 beta build available at: https://www.aida64.com/downloads/latesta64xebeta