I would like to report an issue introduced in the latest update.

Issue Description: After updating from v8.25.8200 to v8.30.8300, S.M.A.R.T. "Current" values are no longer displayed for any of my storage drives (including SATA HDDs and SATA SSDs).

Troubleshooting Done:

• Checked File > Preferences > Stability and confirmed that "Low-level SMART operations" is enabled.

• The issue persists after restarting the application.

Comparison: CrystalDiskInfo and other monitoring tools can read and display all S.M.A.R.T. values normally for the same drives.

System Environment:

• AIDA64 Version: Extreme v8.30.8300

• OS: Windows 11

Thank you for your continued support and for investigating this regression.

The monitoring for "Flow" does not indicate minimum and maximum values

Thanks

My system: MSI MPG X870E Carbon Wi-Fi motherboard, Corsair PSU, Ryzen 9 9950X, ASUS RTX 5090, ASUS ROG RYUJIN 360 Cooler, 192 GB G.Skill DDR5 RAM, 4x4TB Samsung MVNE SSDs, 4x24TB Western Digital & Seagate HDDs

What is the problem?

I Found a bug from the 9950X3D2 CCD0 Clock Speed

AIDA64 reads allways the Clock Speed from CCD1 and not CCD0 when i start a Game or Programm it only works in the Idle

I Made a Screenshot when i run a Game and i use the lastest Beta Version 8227

Quote

"I compared kerneld-x64.sys between v5.99 and v8.25. In 5.99 the driver uses MDL method: IoAllocateMdl + MmBuildMdlForNonPagedPool + MmMapLockedPagesSpecifyCache. In 8.25 these were replaced with ExAllocatePoolWithTag + ExFreePoolWithTag. The pool memory allocated during OSD session is likely not freed properly on driver unload, causing BAD_POOL_CALLER BSOD."
Method used in version 5.99 (problem-free):
IoAllocateMdl → MmBuildMdlForNonPagedPool → MmMapLockedPagesSpecifyCache
These three functions work together with the MDL (Memory Descriptor List) method. It is a secure, controlled method for accessing physical memory. Windows manages this method very well.
Method changed in version 6.x+ (problematic):
ExAllocatePoolWithTag → ExFreePoolWithTag
In the new version, the MDL method has been completely removed and replaced with direct kernel pool memory management. The problem is exactly this: When AIDA64 is closed while the OSD panel is open, the memory allocated with ExAllocatePoolWithTag is either not freed or is double-freeed. The Windows kernel detects this and calls KeBugCheckEx → BSOD.

I've recently meet some trouble with aida 64.

I'm using ROG Ryujin II with a LCD display, and ROG provided aida 64 version 6.85.6326 in its platform so I'm using it.

I successfully put some monitoring info on that LCD but since then the aida 64 crashed all the time, so I checked the windows logs, it seems like Kernelbase.dll is the faulting module, and every time it crashed there will be 5 logs shown in the system logs.

Here with those 5 logs of recent crashing event.

1.

Faulting application name: aida64.exe, version: 6.85.6326.0, time stamp: 0x2a425e19
Faulting module name: KERNELBASE.dll, version: 10.0.22621.1265, time stamp: 0x032d4ece
Exception code: 0xc0000409
Fault offset: 0x0011b600
Faulting process ID: 0x0x4AA8
Faulting application start time: 0x0x1D94A0DB460B446
Faulting application path: C:\Program Files (x86)\FinalWire\AIDA64 Extreme\aida64.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: fa17c196-4ce5-4e8f-b1f4-d24c8e043358
Faulting package full name: 
Faulting package-relative application ID: 

2.

Fault bucket , type 0
Event Name: BEX
Response: Not Valid
Cab Id: 0

Problem signature:
P1: aida64.exe
P2: 6.85.6326.0
P3: 2a425e19
P4: KERNELBASE.dll
P5: 10.0.22621.1265
P6: 032d4ece
P7: 0011b600
P8: c0000409
P9: 00000015
P10: 

3.

Faulting application name: aida64.exe, version: 6.85.6326.0, time stamp: 0x2a425e19
Faulting module name: KERNELBASE.dll, version: 10.0.22621.1265, time stamp: 0x032d4ece
Exception code: 0xc0000005
Fault offset: 0x0011b600
Faulting process ID: 0x0x4AA8
Faulting application start time: 0x0x1D94A0DB460B446
Faulting application path: C:\Program Files (x86)\FinalWire\AIDA64 Extreme\aida64.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 9e16f1cd-88c3-4e56-a1dd-7ace8c091f03
Faulting package full name: 
Faulting package-relative application ID: 

4.

Fault bucket 1396837986615496417, type 5
Event Name: BEX
Response: Not Valid
Cab Id: 0

Problem signature:
P1: aida64.exe
P2: 6.85.6326.0
P3: 2a425e19
P4: KERNELBASE.dll
P5: 10.0.22621.1265
P6: 032d4ece
P7: 0011b600
P8: c0000409
P9: 00000015
P10: 

5.

Fault bucket 1860161643233845964, type 1
Event Name: APPCRASH
Response: Not Valid
Cab Id: 0

Problem signature:
P1: aida64.exe
P2: 6.85.6326.0
P3: 2a425e19
P4: KERNELBASE.dll
P5: 10.0.22621.1265
P6: 032d4ece
P7: c0000005
P8: 0011b600
P9: 
P10: 

Could you please help me to solve this? Thanks.

If you need more information please reply me.

I use the Aquacomputer “high flow next” and have also activated the “Aquaero Sensor” under “Stability”.

I can also display the flow rate on the sensor panel.
However, the “Water quality” is also displayed under “Computer > Sensors”.
I would also like to display this on the sensor panel.
How do I do this and is it currently even possible?

Kind regards 
Alex

------------------------------------

Deutsch

Hallo liebes Team,

Ich nutze den Aqua Computer „High Flow Next“ und habe unter „Stabilität“ auch den „Aquaero Sensor“ aktiviert.

Die Durchflussrate kann ich mir auch auf dem Sensor Panel anzeigen lassen.
Aber die „Wasserqualität“ kann ich nur unter „Computer > Sensoren“ einsehen.

Ich würde diese gerne auch auf dem Sensor Panel anzeigen lassen.
Wie mache ich das und geht das überhaupt zur Zeit?

Liebe Grüße 
Alex

I am opening a new topic because I did not receive any reply on my previous post, and I wanted to rewrite the issue more clearly and more completely in a single message.

My problem concerns a sensor assignment issue in AIDA64 SensorPanel.

I manually assign a SensorPanel item to GPU Hot Spot.
At first, the sensor and displayed value are correct.

However, the assignment does not remain stable.
At random times, the SensorPanel item reverts to CPU GT Cores instead of staying assigned to GPU Hot Spot.

So the issue is not strictly related to closing and reopening AIDA64.
It can also happen during normal use.

An important detail is that the issue seems to affect SensorPanel only.
In the OSD panel, the value remains correct.

I also checked the expected GPU Hot Spot value with HWiNFO, and it is correct there as well.

So from the user side, the problem is not that the GPU Hot Spot sensor is missing or unreadable in general.
The problem is that SensorPanel does not keep the correct sensor assignment and can randomly revert to CPU GT Cores.

I reproduced the same issue on the following versions:

• AIDA64 Extreme 8.20
• beta build 8213 (aida64extreme_build_8213_nz6msf5bdx)
• AIDA64 Extreme 8.25

So the problem is present on both stable and beta versions, including after a clean reinstall.

System

• Motherboard: ASUS ROG Strix Z790-A Gaming WiFi D4
• CPU: Intel Core i7-14700K
• RAM: 32 GB DDR4-3600
• GPU: Sapphire Radeon RX 9070 XT Pulse
• OS: Windows 11 Pro 25H2 (build 26200.8037)

At this point, this looks like a SensorPanel sensor assignment persistence / reassignment issue, rather than a general sensor reading problem.

I can provide screenshots if needed.

Thank you.

 Version:                                            AIDA64 v6.92.6600/br

Portuguese - Brazil

 [ Generic Monitor (DM238) [NoDB] ]

    Propriedades do monitor:
      Nome do monitor                                   Generic Monitor (DM238) [NoDB]
      Identificação do monitor                          DTN2380
      Modelo                                            DM238
      Data de fabricação                                Semana 21 / 2024
      Número de série                                   1M44587010001
      Tamanho de visão máximo                           527 mm x 296 mm (23.8")
      Razão de aspecto da imagem                        16:9
      Freqüência horizontal                             30 - 83 KHz
      Freqüência vertical                               48 - 75 Hz
      Clock Máximo do Pixel                             250 MHz
      Gamma                                             2.20
      Suporte do modo DPMS                              Active-Off
 

I recently purchased a 2.1" LCD display from SmartCool that is designed to work with AIDA64.

The unit works correctly when it starts properly, but I am having a recurring issue:

• After I put my computer to sleep and wake it up, the LCD powers on but remains on a black screen.

• When I try to launch AIDA64 afterward to troubleshoot, AIDA64 stops responding / crashes.

Current workaround (temporary)

The only way I can get it working again is to:

1. Close AIDA64

2. Unplug the LCD display from the internal USB header

3. Reopen AIDA64

4. Plug the LCD back in

After that, the display starts working again.

My setup

• Windows 11

• AIDA64 v8.20.8126 beta

• LCD connected to internal USB header

• Motherboard: ASRock X470 Fatal1ty (if needed, I can provide exact model variant)

What I’ve already tried (no fix)

I have already tried the common troubleshooting steps suggested in forums and discussions, including:

• Closing any other LCD control software so only AIDA64 is running

• Disabling USB selective suspend in Windows power settings

• Disabling “Allow the computer to turn off this device to save power” for USB hubs in Device Manager

• Disabling Fast Startup in Windows

• Testing different USB header/port behavior (where possible)

• Reinstalling/relaunching AIDA64

• Using the beta version of AIDA64

I’ve seen that others have reported similar issues, but I haven’t found a confirmed fix yet.

If anyone has a solution (or specific settings in AIDA64 / BIOS / USB configuration that fixed this), I’d appreciate the help.

Thank you.

Aida will fail if the LanmanServer service is disabled. Blank page if the service is running and there are no opened files. Need some "stub"...

I guess the Sensopanels are fixed now-they don't work 😛

I bought a WigiDash for the sole purpose of using it as an Aida64 display.

The problem: Aida64 8.20.8100 Extreme (trial from the Aida64 website, portable zip version) supports only a few displays and the Gskill is not among them. I found an earlier version, 7.40, with support for the Wigidash which I tested and it works well, but with 8.20 it is is nowhere to be found. I tried running the WigiDash manager before Aida64 (a suggestion I found in the Wigidash manual), to no avail, Gskill never shows up in the "LCD" section of Aida64 settings.

Is the support gone or am I missing something obvious?

A side question: Are there any reasonable (5-7") displays for Aida64 which aren't just basic HDMI/DP external displays with all of the downsides it brings?

Thank you for any reply. Please excuse me if I put this in the wrong section.

The only modification I've made is setting animation.ini backlight value to 0 so it's not displaying media when the pc isn't on.

Also I've noticed that beadapanel isn't even natively under the LCD options anymore, I have to search for it to find it which was not an issue in an older version I was using before updating to try and fix this issue.

Now I have next structure and how it has to be:

CPU       --->  has to be CPU2 (the first case fan connected into AIO Pump Fan Connector)

Chassis #1    --->  has to be CPU (CPU fan connected into CPU Fan Connector)

Chassis #2    --->  has to be Chassis (the second case fan connected into Chassis Fan Connector)

In other monitor softwear all fans sensors are displayed correctly.

I hope for your help.

yhank you in advance.

isasensordump.txt

Problem: Aida64 7.70.7500 was able to retrieve, among other things, the RAID and Smart information of the Adaptec ASR 8805. The necessary stability checkmarks are turned on but Aida64 8.00.8000 and later versions do not show the Smart data of the disks connected to the Adaptec ASR 8805. See the screenshots of the 2 Aida64 versions running the same aida64.ini file and the missing information.

raiddump_aida64 8.00.txt raiddump_aida64 7.70.txt smartdump_aida64 8.00.txt smartdump_aida64 7.70.txt

Am raising this with both AIDA and Stardock - but with AIDA64 running the Start 11 start menu malfunctions.  No sure which side is the root cause but thought best to raise with both!

I've posted about this on Reddit here