All Activity

Every time that I start or restart my computer, the sensor panel is in a random position. I have a 5 inch screen which I have positioned the sensor panel to. I have checked all of the options to make the sensor panel stay there, including "Keep SensorPanel the topmost window", "Prevent SensorPanel from being minimized:, and "Lock panel position". I have tried unchecking them, also, and every combination of checked and unchecked, but yet...

The answer is, it shows up once connected.😉

This is awesome.. love it! Any chance to get that in 1024x600 ? @Blanco95

Thank you very much. But may be it would be better to rename AIO Pump to CPU2 as in structure I mentioned above (as in similar software)? If not tnan better to place AIO Pump on the second place after CPU and Chassis will be on the third place.

It would be good if we can monitor 12V-2x6 using wireview pro II. Their software https://drive.google.com/drive/folders/1E1v5aGnlJQh_4cmwfB8p4dRpypCYsF8g allows you to export the stats into hwinfo. Just wondering if we can get that into aida for custom sensor panels.

This is happening to me as well, and I am also on the latest beta as of 1/22/2026. Whenever my main display goes to sleep (which is often to prevent burn-in while away from my desk) the SensorPanel resets its location from where it is assigned (a 1920x480 screen in my tower). My OLED as listed within windows as my primary display. No combination of un-pinning, locking panel position, or panel size seems to work, so with every boot or wake I have to go into preferences and update the location of the panel. When I open the preferences SensorPanel section it shows the correct panel in the 'pin to panel' drop down, despite being on the wrong display.

Panel display 1280x800 EURO BLACK V2.tulcd

I used to meet Windows 11 resume issue when I connecting BeadaPanel to AIDA64 on my laptop. Though I did not know whether this was caused by my Lenovo laptop hardware or it was a common software issue yet. I had reported my issue on this thread.

In order to have support for your GPU, you need to upgrade to the latest AIDA64 version of 8.20: https://www.aida64.com/downloads/latesta64xe

I can't get almost any information on my GPU (MSI 5080 Suprim) such as GPU Utilization, GPU Temperature, Clock Speed, Memory Usage,... What can I do to get these info? I sent a full report via Aida64.

Still having issues, after trying multiple usb cables and ports sometimes when resuming from sleep it'll return a usb init error requiring both a plug/unplug of the device and a restart of aida64 which will be completely unresponsive as long as the beadapanel is plugged in. It's not consistent, usually only happening 1/4 times roughly but it is still happening.

Thank you for your feedback!

yes it's working!! it's fantastic!! i m planning to do (and share) a theme later thanks

I have the hardest time trying to decide on a good design based on the 5 panels I did so far. So, I asked my wife which one she preferred. This is the one she picked. Not as busy as some others, but since my prime concern is really overheating something, this one does all I really need. If the logo at the top is unfamiliar this panel goes on a "Taichi Lite" based unit. trial 5.spzip

Thank you for the detailed follow-up - this is extremely helpful 👍 Based on the logs you shared, I can now say with confidence what’s happening. I have sent you a direct message to keep you informed with more details! What I’m doing next I’m already working on improvements to make SynQPanel more defensive in this exact situation, including: Stronger validation before XML parsing Safer early-abort paths when corruption is detected Ensuring malformed shared-memory reads can never reach rendering code This will be part of an upcoming update. Thank you again for taking the time to report this and share logs. This kind of feedback is invaluable, especially while SynQPanel is still growing. 🙏

What was happening just before the crash? The error occurred while the computer was idling; it happened twice. First at 4:31 am and a second time at 7:39 pm the same day (first log file will not upload, exceeds upload limit) Version of AIDA64, 8.20.8110 Beta Whether shared memory was enabled, yes SynQPanel-20260119_018.log

great news!!! Thx

Hi there, First of all, thank you for the opportunity to test the program and verify its functionalities. During the testing period, I noticed that the panel sensor is not correctly displaying the memory type. It is a DDR3-1600, but the program shows it as DDR4-1600. I am testing the latest version available on the website. Sincerely, Rafael

new 515x1920 https://aida64skins.in/all-templates/product/p_3376828

Thank you for reporting this, and I’m really glad to hear you’re enjoying SynQPanel ❤️ I’m sorry it failed on you - that kind of crash is frustrating, and I appreciate you taking the time to share the details. The exception you’re seeing (System.AccessViolationException) usually means the app tried to access memory that was no longer valid. In SynQPanel’s case, this is almost always related to native interop, such as: AIDA64 shared memory access SkiaSharp / graphics rendering Sensor data becoming unavailable or changing unexpectedly while being read It’s not a .NET logic error and it’s not something caused by normal usage. To help narrow this down, could you please let me know (or send via PM if you prefer): What was happening just before the crash? (e.g. opening a profile, switching panels, resizing, minimizing to tray, closing the app, etc.) Without that change: Is the app working properly? Was AIDA64 running at the time, and if so: Version of AIDA64 Whether shared memory was enabled When exactly error occurred (Installing, launching etc.)? If possible, please check this folder after the crash and let me know if a latest log exists: %LOCALAPPDATA%\SynQPanel\ i.e. C:\Users\<USERNAME>\AppData\Local\SynQPanel\logs Latest Log Files can be very helpful. I’m actively improving stability around shared memory access and rendering, and reports like this are extremely valuable - especially this early, while the user base is still small. Thanks again for your support and patience. I’ll do my best to get this fully understood and addressed.

I love your software. It did fail on me with the following error message: Application: SynQPanel.exe CoreCLR Version: 8.0.2325.60607 .NET Version: 8.0.23 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

Is it normal, that AIDA64 shows a very limited LCD selection? Just ordered a G.Skill WigiDash and am wondering why G.Skill does not show up in the LCD section in AIDA64 preferences. I am using the latest version of AIDA64 and the G.Skill WigiDash did not yet arrive. Does it show up when connected?

OK, I understand.

Yes, but the serial numbers there are detected using a different driver call.

But the NVMe drives are shown correctly (i.e. with serial nr between brackets/parentheses) in the Storage/ATA section though? And another issue: NMVe drives are not listed yet in the Summary/Storage section.