All Activity

Thanks for the explanation! Case solved then; I didn't realize that those SMART columns had always been empty for NVMe drives in the past.. 🫣

We couldn't make the existing module more reliable yet. We're still working on it...

Any updates?

Those columns are not relevant for any NVMe drives, not just ones driven by the Native NVMe layer of Windows.

It actually looks very great

Hello, I receive the following message immediately when starting a GPU stress test with Aida64: "the instruction at 0x00000 referenced memory at 0x00000. The memory could not be written." When I perform all other test via Aida there are no problems. I also have no problems when benchmarking the GPU in other benchmarks/games. I used to be able to stress the GPU via Aida, not sure why suddenly I receive the above message. I ran Windows memory test without any problems as well. CPU: 9950X3D GPU: RX 9070 XT OS: Win 11 Memory: DDR5 2x32GB Many thanks in advance. //Matt

When the Native NVMe mode/feature has been enabled in Win11, the lists named "Threshold", "Value" and "Worst" are still empty on the SMART page.

Moin kann man das so lasen

Please describe the issue about Native NVMe SSDs.

Hi Fiery, sorry for the late reply. Latest beta does indeed fix this issue for standard NVMe and SATA SSDs, but not for 'Native NVMe' SSDs. Could you please look into this again?

I'll be the first to second Beada's request! I have a BeadaPanel 5P and a 6P. I've developed my own personal app which uses the 6P and have AIDA64 using the 5P. But it's VERY hard to get them to work together since AIDA64 tries to grab both displays rather than a specified one. This means if AIDA64 is running, I can't start my app. Or if my app is running, AIDA64 will run but reports a WinUSB error on the panel(s) and won't use it. In this case, I've been quitting AIDA64 then power cycling the 5P. Then restarting AIDA64 now allows it to connect to the remaining panel for some reason. (I can provide more details if necessary since I'm leaving out some details.) My app specifically connects to the 6P (or "BeadaPanel 1280x480") and has the ability to select the panel from a list. This proves it's both easy and possible for AIDA64 to do the same thing.

Some BeadaPanel users connect multiple devices to their computers but only want AIDA64 display info on a specific device. Currently, AIDA64's LCD configuration page does not offer an option to select a BeadaPanel device. Without this feature, AIDA64 randomly selects a BeadaPanel device and sends the display data to it, which can potentially conflict with other BeadaPanel applications in the system. It would be much more elegant if AIDA64 allow users to choose device from a list. If the AIDA64 team plans to implement this feature, I recommend using the device serial number as a unique ID to identify devices. This is a solid way to distinguish WinUSB devices in a Windows systems.

600X1024 AIDA64 Neon Tower Sensor Panel Futuristic Digital Monitoring Skin 100 position gauges!!! https://aida64skins.in/aida64-neon-tower-sensor-panel

Wrong thread. This thread is for sharing. That was a purchased Sensor Panel. Panels offered for monetary gain are to be shared and advertised in another thread. Share and advertise in it. Please dont give this thread a dis-service.

AMD RED DEVIL 600x1024 High-precision 100 Position gauges !!!! https://aida64skins.in/amd-red-evil-

Hi everyone, I'd like to know if it's possible to add a graph to the dashboard to monitor the Windows 11 backup percentage. Let me explain: I use the Veeam Agent program to perform daily Windows backups, and to see the backup percentage, I have to go to the Windows tray and select the Veeam Agent icon to see the backup percentage. I was wondering if it's possible to add that percentage directly to the dashboard? It would be easier to see the backup status immediately. Thanks for anyone who can help me.

Downloaded on May 3rd and lost my GPU sensors today, downloaded the beta came out may 4th and fixed it. Thanks years later.

no worries, ill just continue to use the steam FPS counter for DX9

He does a great job, I have 19 of his panels

Thanks for the reply, I thought it was just the Cache (uncore, memory controller) and not all Cache That helps me focus my testing.

It stresses all cache levels plus the execution units of the CPU to some degree. It's not possible to tell which cache level(s) at fault when an error occurs.

Look what Surjeet make to me.. Awesome 2560x720

I've moved your topic to Brainstorming. We initially focused on DirectX 11 and DirectX 12, as these are the most commonly used graphics APIs in modern games today. DirectX 9 is a more complicated territory. Proper DX9 support often requires DLL injection or hooking techniques, which we would prefer to avoid, as they may trigger anti-cheat systems or cause compatibility issues with certain games. Vulkan is also becoming increasingly important, especially with modern engines and cross-platform titles, so adding Vulkan support is one of our next priorities. We understand it would be ideal to support as many graphics APIs as possible, and we are absolutely open to user feedback. Depending on demand and the available technical solutions, we may revisit additional API support in the future.

I know DX9 is ancient at this point, but is there any chance of adding DX9 to the FPS counter? edit: i realized after i posted this that it should have gone in the brainstorming section.

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