Fiery

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.

The French language module will be updated in the next AIDA64 beta build. As far as I can tell, you cannot avoid putting more and more pressure on us about implementing the feature of renaming labels on the Computer / Sensor page That would solve many of your existing issues about sensor labels I guess. We'll jump on it now, it's already too much pressure

Thank you for your feedback. No, ATKEX is a different interface, so that setting does not have any affect on Asus WMI.

Here's the first AIDA64 beta that supports the new Asus WMI sensor interface: https://www.aida64.com/downloads/latesta64xebeta You can enable/disable Asus WMI sensor support in AIDA64 / main menu / File / Preferences / Stability. It is enabled by default. It requires a BIOS interface, so it will only work in case the motherboard BIOS supports Asus WMI. If it doesn't, and you flash a new BIOS that does support it, AIDA64 will automatically switch to using the WMI interface right away. The current implementation supports Asus Crosshair VI Hero, Crosshair VII Hero and Zenith Extreme motherboards. Other motherboards are partly or fully supported by the current implementation. When a certain motherboard is not fully supported, make sure to 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. That dump will enable us to fine-tune the Asus WMI implementation and adjust it to support new motherboards. We've tested the current implementation with the following motherboard + BIOS combinations with success: - Crosshair VI Hero / 6201 - Crosshair VII Hero / 0702 Everyone: please let us know how it works on your motherboards

Most non-ATA-compliant storage devices do not feature a proper model ID that would let us add them to our storage device databases. And it's already very difficult and time consuming to maintain the HDD and SSD databases, so we're not really keen on piling up even more tasks over that already huge pile of things to do every day...

Make sure to 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.

Just a sidenote: a process can load a DLL (in this particular case the one for NVAPI) which can issue kernel driver calls (exactly what happens in this case) which can then cause a BSoD. Sometime it's difficult to go through that chain of calls to find the culprit

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> Battery 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

Since the issue affects any software that uses NVAPI (nVIDIA's own API), it should be pretty easy to reproduce it in nVIDIA's own labs. We can however be of assistance if asked. We're always open to work with hardware manufacturers, but nVIDIA is not famous for being open to such cooperations I'm afraid.