Fiery

We've never tried it without installing LGS, so it would be an interesting experiment. Place the LgLcdApi.dll file into C:\LgLcdApi\SDK\LCD\x86 folder. Then using Registry Editor (REGEDIT.EXE) you need to add a new Registry value named InstallDir (type String) under: HKEY_LOCAL_MACHINE\\Software\Logitech\Logitech Gaming Software Set the value of InstallDir to: C:\LgLcdApi That should make AIDA64 find the DLL and try to load it. We will then see whether it works or needs further components installed.

4) You can contact Gigabyte Support. There's a slim chance you can convince them to take steps to help us implement support for your device in AIDA64. It would be a lot easier if Gigabyte sold the controller separately too... As for 1), I'd leave it for others to come up with a good alternative. From a developer's standpoint I don't like any of them, since they raise different struggles. In other words, from the standpoint of interacting with such fan controller hardware, there's no perfect solution, and that was to put it mildly Of course if you don't want to monitor them, or can (and want to) rely on their manufacturer supplied software, they are great products.

Thank you. Something strange is going on there. I suspect another monitoring software or service keeps polling the SMBus of your video card, and that collides with AIDA64, which eventually causes the lockup. Do you think might have such a software running in the background?

I've replied you in your other topic. This topic closed.

There is interest. In fact, here's the bug fix for the issues about BeadaPanel LCDs: https://www.aida64.com/downloads/latesta64xebeta Regards, Fiery

Thank you for checking it. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta I hope it now works 100% fine.

It looks like it's more an issue about the enumeration of sensor devices in AIDA64. When you go to the Computer / Sensor page of AIDA64, does it work properly?

We've done several test runs about it, but somehow the serial connection of Pertelian X2040 is unstable under Windows 10. We've tried to play around with the timings, delays, uses special tricks, but all it could achieve is a little bit better operation -- but not a 100% fix.

Please note that on many devices the standard Android Battery API is inadequately implemented, and fails to provide proper charge counter information for the battery. If you want, you can hide the incorrect charge counter information from the Battery page by unchecking the charge counter option in the AIDA64 Settings.

Awesome, thank you!

I'm afraid we have no technical documentation or any material on Gigabyte Fan Commander, so we cannot implement support for it. Unless of course someone can point us to the right direction with the necessary technical guidelines.

When running in trial mode, AIDA64 always pops up a message box at startup where you can enter your product key. You can also go to main menu / Help / Enter Product Key.

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. Thanks, Fiery

Thank you for the feedback!

It's called the Windows video driver Timeout Detection and Recovery delay (TdrDelay). You can adjust it using Registry Editor (REGEDIT.EXE). You can find it at the following path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers Look for TdrDelay there. It should be set to 8 right now (previously set by AIDA64).

Thank you! Please upgrade to the latest beta version of AIDA64 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.

Thank you! Please upgrade to the latest beta version of AIDA64 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.

Not yet.

GT Cores power measurement is only available when your CPU has an active iGPU. DRAM power measurement is only available for certain Intel processors too. We cannot add those just like that when the measurements are not available. Uncore power is calculated and shown even when GT Cores or DRAM power cannot be measured.

It's only a guess.

You can do that, but first you need to enable Enable CPU throttling measurement in AIDA64 / main menu / File / Preferences / Hardware Monitoring.

I'm afraid we still cannot reproduce the issue and so we have no way to fix it up.

Thank you! Can you please try the ATI SMBus Dump again, but this time make a photo that would show the bottom status bar of AIDA64 window as well? Where it says "Trying ATI I2C Device GPU #1 / B..."

In /SAFE mode AIDA64 will not enumerate PCI devices, SMBus devices and sensors using low-level hardware access. In /SAFEST mode AIDA64 will not load its kernel driver and not read SMART information from HDDs and SSDs. It's the safest way since then AIDA64 will work like any other user-mode software. Only you can decide whether the consequence of using those parameters (ie. the lack of information that will be missing from the reports) is fine with you, or you'd rather let AIDA64 use its full detection capabilities and interrogate hardware more thoroughly by omitting to use of /SAFE and/or /SAFEST.

I'm not sure, since we don't deal with such matters. Probably someone at forums like XtremeSystems could help you about that.