Andrew Pafitis Posted April 24, 2021 Share Posted April 24, 2021 I just got in the new 6.8" super wide BeadaPanel the other day and it's great when it's connected, but sometimes (not always) when coming back from sleep it goes to the screensaver and Aida64 shows "Error: LCD init failed" in the LCD preferences. Disabling and re-enabling BeadaPanel support does nothing, but if I terminate Aida64 and relaunch it reconnects just fine. Attaching some dump files if it helps. Let me know if there's anything else I can provide to help chase down this bug. devdump.txt usbdump.txt Quote Link to comment Share on other sites More sharing options...
Andrew Pafitis Posted April 28, 2021 Author Share Posted April 28, 2021 @Fiery just want to make sure this gets seen, should i open a ticket instead? Quote Link to comment Share on other sites More sharing options...
Andrew Pafitis Posted April 30, 2021 Author Share Posted April 30, 2021 Please help, it seems that this does occur after every time I wake from sleep. The only solution is restarting Aida64. For a $120 panel, I would really like this working as intended. Quote Link to comment Share on other sites More sharing options...
Andrew Pafitis Posted April 30, 2021 Author Share Posted April 30, 2021 whatever, i set up a script to kill and relaunch aida64 and use Hibernate Trigger to launch it on resume from sleep. aida relaunches before the beadapanel fully boots up but it connects straight away when it does. seems to work well. Quote Link to comment Share on other sites More sharing options...
Andrew Pafitis Posted January 26, 2023 Author Share Posted January 26, 2023 i reinstalled windows and tried to reimplement the kill script to force a restart of aida64, but for some reason the kill script doesn't work this time. anyways, @Fiery i found this other post mentioning "lcd init failed" where you asked for a usbdump file so i started poking around. i took a usbdump file when it failed, after restarting aida when it was successfully connected, and after restarting a second time to be sure. i compared values from the 3 files and think believe i understand the problem here. Under the section [ DevClass / USB Devices ] I found that the usb beadapanel device instance ID was logged as 20, however restarting aida64 the usbdump shows an instance id of 19 and is properly connected and displaying stats on my panel. Restarting aida64 the second time, panel connected again, and usbdump also still showing device instance id of 19. I have a whole bunch of usb devices connected through several usb hubs, so I'm not sure of the exact root cause for the IDs to change, but it seems possibly related to usb selective suspend and when the pc wakes from sleep where the usb devices are reconnecting, where it seems the pc reindexes the usb devices (panel now at 19) but aida64 is looking for the index that was saved prior to going to sleep (20), and thus failing. Is there any way to force aida64 to reindex the usb devices after waking from sleep, at some interval, or anything else without having to force a restart of the entire application? usbdump-init failed.txt usbdump-ok.txt usbdump-ok2.txt Quote Link to comment Share on other sites More sharing options...
Fiery Posted February 2, 2023 Share Posted February 2, 2023 On 1/27/2023 at 12:45 AM, Andrew Pafitis said: i reinstalled windows and tried to reimplement the kill script to force a restart of aida64, but for some reason the kill script doesn't work this time. anyways, @Fiery i found this other post mentioning "lcd init failed" where you asked for a usbdump file so i started poking around. i took a usbdump file when it failed, after restarting aida when it was successfully connected, and after restarting a second time to be sure. i compared values from the 3 files and think believe i understand the problem here. Under the section [ DevClass / USB Devices ] I found that the usb beadapanel device instance ID was logged as 20, however restarting aida64 the usbdump shows an instance id of 19 and is properly connected and displaying stats on my panel. Restarting aida64 the second time, panel connected again, and usbdump also still showing device instance id of 19. I have a whole bunch of usb devices connected through several usb hubs, so I'm not sure of the exact root cause for the IDs to change, but it seems possibly related to usb selective suspend and when the pc wakes from sleep where the usb devices are reconnecting, where it seems the pc reindexes the usb devices (panel now at 19) but aida64 is looking for the index that was saved prior to going to sleep (20), and thus failing. Is there any way to force aida64 to reindex the usb devices after waking from sleep, at some interval, or anything else without having to force a restart of the entire application? Thank you for your test runs and the dumps. And the issue is not related to USB device indexing, but rather the way the WinUsb API takes control of the arrival of USB devices after waking the computer up from sleep. Apparently the WinUsb initialization fails if it is called to early after wakeup. We'll implement a cycle to repeat the init procedure 10 times with delays between the trials in a hope that it will provide WinUsb more time to perform the init properly and give control over the BeadaPanel screen to AIDA64 more reliably than now. I will post a message once the new beta build becomes available for download. Quote Link to comment Share on other sites More sharing options...
Fiery Posted February 13, 2023 Share Posted February 13, 2023 @Andrew Pafitis 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. Let me know how it works. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.