All Activity

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.

Yes, somehow the new native NVMe driver doesn't provide serial number at all, or provides a different serial number than the drive has got. We're not sure why that is, our best guess is that there's a driver bug that Microsoft has to fix up.

Thanks again! Meanwhile, I noticed another small issue under Storage/Physical Drives: my NVMe drives don't show their serial number between brackets/parentheses there (like my SATA drives do). EDIT - another issue: NMVe drives are not listed yet in the Summary/Storage section.

Thank you for your feedback! We will fix the mentioned issue in the next AIDA64 beta update.

Just look at the upper right corner of the page and find the search field and type in the size you want like this https://forums.aida64.com/search/?q=515x1920&quick=1&type=forums_topic&item=13296 It always surprises me that people don't see that, I found it my second time here

Thanks, Native NVMe drives are now visible in most Storage sections 👍 EDIT: Native NVMe drives are not visible under Storage/Windows Storage with this new beta.

515x1920 --480x1920 aida64skins.in https://aida64skins.in/all-templates/product/p_3376806

@Benni231990 @FatBoyNL @Tomorrow @Miroslav Tuhársky We've implemented native NVMe support in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta

We've implemented native NVMe support in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta

@Cybrdude We've implemented native NVMe support in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta

A hibát javítottuk a legújabb AIDA64 béta kiadásban: https://www.aida64.com/downloads/latesta64xebeta

We've implemented support for WeAct displays in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let us know how it works.

The above mentioned new AIDA64 beta update is now available for download: https://www.aida64.com/downloads/latesta64xebeta

That screen in USB mode is not supported by AIDA64 yet. We do have plans to implement support for it later this year though.

Such issues are usually caused by a mixup in the OpenCL layer of Windows. A full video driver cleanup + reinstall should solve it.