Fiery

The drop in VP8 scores are due to the security patches rolled out in the past 13 or so months.

Purged him. Thank you

Please try it with the latest ForceWare release of 418.81 WHQL.

It could be because the video driver is so busy that it cannot handle the mouse cursor movement

AIDA64 already supports controlling the RGB LEDs of Asus motherboards via the Asus Aura SDK

Using AIDA64 v5.99, 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

Thank you for your feedback!

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> USB PSU 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 --> Corsair Link Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

GPU test is normal to make the mouse cursor sluggish, since the OpenCL driver goes through Direct3D and so it directly affects the smoothness of the video driver. As for the FPU test, it's the most demanding task that our stress test (and also out of many other stress tests) puts on your system. When the FPU test is running, your processor draws the maximum power and generates the most heat. If the PC restarts during the FPU test, especially when it happens immediately after starting the test, it usually means there's a power delivery issue in the system. In most cases it's because the PSU (power supply unit) cannot provide enough power to feed the processor under heavy load and/or the motherboard has a faulty component on it. If you can, try to borrow another, ideally higher specified (more powerful) PSU, and try your system using that. If it makes the FPU test run just fine, your current PSU is the culprit.

It means your system memory is not stable at 3000 MHz setting. You can try to fine-tune the memory timings or adjust the memory voltage to make it stable.

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.