Fiery

Done

Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. 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

Zenith Extreme has no public BIOS that would support the new Asus ACPI WMI interface yet.

If you've changed both the motherboard and the memory modules, and you still have issues, then it can either be the CPU or the PSU. Hard to tell from here though As for conhost.exe, it's strange, since AIDA64 never calls or links that particular executable file.

Grouping cannot be 100% consistent about icons, because for example, on systems featuring an Intel iGPU the CPU GT Cores temperature will have a different icon

Yes, it's normal for a thin laptop. The drop of CPU core clock speed is normal for low-TDP processors like mobile CPUs, especially for the ones put into thin cases. The CPU has to obey the tight TDP limit, and under heavy stress the only way to do so is to lower the working core clock frequency. The other constraint is the thermal issue: once it crosses the limits, the CPU will either throttle or keep lowering the CPU clock speed to prevent the system from overheating.

1) Fixed it, thank you. 2) We'll bump VBAT Battery voltage down a line to make it look slightly better. 3) The groups (sections) cannot be renamed permanently. 4) System Stability Test uses a separate sensor module, so the changes you apply to the Computer / Sensor page will not affect the System Stability Test. Thank you for your feedback. Please keep 'em comin'

Awesome, thank you for the feedback

You can adjust sensor readings in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction.

Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know if it helps.

Here's the first AIDA64 beta where you can rename labels on the Computer / Sensor page. Right now it only works if you click on the label to edit it in-place. So there's no right-click context menu or main menu item to perform the renaming. https://www.aida64.com/downloads/latesta64xebeta Let me know how it works Please note that if you want to revert back to the default label, just clear the label (empty string) and press Enter. Also note that we've had to rewrite the whole code behind the Sensor page in order to implement the label renaming feature, so the order of the readings could be slightly different than previously. And also there's a slim chance that we've left minor bugs in there -- which I'm sure you'll catch

It looks like an OpenGL related issue, since AIDA64 detects OpenGL at startup. Does CPU-Z work on your device right now? Is your S7 the regular global model SM-G930F?

What you need to do is: 1) Download the driver ZIP package that you've linked, and extract it to your system somewhere 2) Connect the SPF-87H to one of the USB ports of your computer 3) Start AIDA64, go to main menu / File / Preferences / Hardware Monitoring / LCD / Samsung 4) Tick the checkbox called Enable Samsung SPF LCD support 5) AIDA64 will make the SPF-87H device to switch from mass storage mode to mini-monitor mode, which will change the device that you can see in the Device Manager to the one that you need to install the downloaded driver for 6) Open Device Manager, and install the driver that you've downloaded in step #1 7) Once the driver is installed, close AIDA64, open it again, go to main menu / File / Preferences / Hardware Monitoring / LCD / Samsung 8) Tick the checkbox called Enable Samsung SPF LCD support again. This time it should start working and display the blue splash screen on the SPF-87H screen Let me know if you run into any troubles. Please note that we've gone through that list of to-do's using a SPF-75H screen of ours using the latest 64-bit Windows 10 build (17134.112) earlier today in order to make sure the supplied driver can still be installed properly.

You can import those files in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / OdoSpace / LCD Items.

Thank you for your feedback. The system restart is sometimes necessary, because after upgrading to a new AIDA64 build Windows could get confused about the changes in our kernel driver.

Sounds great, thank you!

I'm afraid I lost track of the potential issues about your systems Do you have any remaining issues or potential bugs? As for the AX1500i, what is the exact reading that you miss that you have on RM650i?

Please upgrade to 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.

I've never seen a WiFi connected monitor. You may be better off using an Android tablet for such purposes.

It's a non-public BIOS update ... right now. It should be out there soon.

Can you tell us what exactly happens when you launch AIDA64? And also please describe your hardware configuration, e.g. motherboard model, CPU type, video card(s).

Thank you. It seems the issue is that your UPS reports a constant Power Load percentage value of 23%, regardless of the load on the UPS. While it reports a different Power Load value with or without the monitor connected. The second, varying power load value (measured in Watts) comes from multiplying the Output Voltage and Output Current measurements. As you can see, the Output Current varies between 0.4 Ampers and 1.0 Ampers, and AIDA64 then correctly calculates the Power Load Wattage value from them. Please note that in your particular case the Power Load percentage and Power Load in Watts values have no association, since they are detected using separate (different) calls via UPS HID. My conclusion is that your UPS may have an issue reporting the right (accurate) Output Current values, and that makes the Power Load (in Watts) values look odd.

Thank you, but I'm afraid that was the USB PSU Dump, and not the Battery Dump

With only a few exceptions (per 23 years really) beta builds of our software are just as high quality and dependable as stable builds. So feel free to use always the latest beta build, since it provides the greatest level of hardware and software recognition.

No, it's just to let you find from which source a certain sensor reading comes from.