All Activity

Hello, Updated to v8 and PCH temp sensors disappeared so I rolled back to v7.70.7500 but now RAM temp has disappeared. The settings Preferences>Stability>DIMM thermal sensor support is Enabled. Is there anything else that needs to be enabled? This is what I have currently enabled Load kernel driver Low-level MSR operations (may cause system lockup in rare cases) Low-level PCl bus operations (may cause system lockup in rare cases) Low-level sensor operations (may cause system lockup in rare cases) Low-level SMART operations (may cause system lockup in rare cases) Asus AT KEX sensor support (Asus ROG) Corsair HXi/RMi sensor support DIMM thermal sensor support Embedded Controller (EO support Embedded Controller (EC) bank switching GPU sensor support GPU fan speed measurement Windows 11 CPU utilization measurement workaround This is on an : Asus ROG Maximus Dark Hero / GSkill Trident Z5 Please let me know if you need any other information. Thanks in advance.

I've sent you a private message about this.

1920 x 480 Little nod to one of the best sci-fi franchises ever made which is now finally on it's way back after many years adrift. Can't wait. Cheers 👍 Vim009.spzip Fonts.zip

I've created this account just to comment and ask as a new interested user. Is $65.95 the discounted price for AIDA64 Extreme? I am not sure if I'm seeing the discount on the checkout page or not. If it is not, then what is the discount price I should be seeing?

Well, this is normal because turzx is using an outdated serial protocol that has a low data transfer rate and speed, and that USB cable is actually a demonstration and is playing the role of converting USB to serial port.

The campaign is ongoing right now 🙂

Hi, I'm new to all of this and this is my attempt. I wanted a Cyberpunk sensor panel and needed one to fit my 720 x 1920 internal screen but couldn't actually find anything so thought I'd give it a go. This is only version 1, I know I need to go back and straighten everything up. This borrows heavily from some of the other Cyberpunk panels on this forum so a massive thank you to the original creators. They were a huge inspiration.

Hey all, still trying to learn this software... here's my attempt.

With FPS for games. NEO.tulcd

NZXT CAM locks the sensors when it is launched first, but if another process has them locked the software (NZXT CAM) will still read them and function. I created a workaround powershell script that uses the free Libre Hardware monitor to "lock" the sensors, then NZXT CAM is launched, then AIDA64. Using this method I can have both NZXT CAM and AIDA64 using the sensors. At the end of the script it terminates the Libre Hardware monitor process as it is no longer needed. I then created a windows task scheduler job to run the script at user login, below is the script if anyone was interested in something similar. (I tried to document everything in the script.) # This script will allow the sensors for NZXT AIOs to be used in AIDA64 while NZXT CAM software is running. # # The NZXT CAM software will lock access to the sensors if it launched before AIDA64. # If the sensors are already locked when NZXT CAM is launched, the software will still load and access the sensors. # Unfortunatly AIDA64 will not lock the sensors if it is launched first, so another free software "Libre Hardware Monitor" is used for this. # # The followings steps are run in the script: # ------------------------------------------- # - Libre Hardware monitor is launched, this will soft lock the NZXT sensors. # - The script delays for 5 seconds to allow time for Libre Hardware monitor to finsih loading. # - NZXT CAM software is launched. # - AIDA64 is launched. # - The script delays for 5 seconds again to allow time for everything to load. # - Libre Harware monitor is no longer needed once everything is loaded, so the script ends the program. # Libre Hardware Monitor can be downloaded from the following link. # https://github.com/LibreHardwareMonitor/LibreHardwareMonitor # To run from windows task scheduler # ---------------------------------- # - Open Task Scheduler (taskschd.msc) # - Click Create Task # General Tab: # - Name: Startup Script (Or whatever) # - Check Run only whne the user is logged on # - Check Run with highest privileges (admin rights) # Triggers Tab: # - New Trigger > At log on > Any user (or your user account) # Actions Tab: # - Action: Start a program # - Program/script: powershell.exe # - Arguments: -WindowStyle Hidden -ExecutionPolicy Bypass -File "C:\Path\To\startup.ps1" # - Save > enter your password if prompted. # Start Libre Hardware Monitor to lock the NZXT sensors Start-Process "D:\LibreHardwareMonitor\LibreHardwareMonitor.exe" -WindowStyle Minimized # Sleep 20 seconds to let the program initialize Start-Sleep -Seconds 20 # Start NZXT CAM with "--startup" parameter # Program produces output when called from a script, "-RedirectStandardOutput" is used to send it to NULL. Start-Process "C:\Program Files\NZXT CAM\NZXT CAM.exe" -ArgumentList "--startup" -RedirectStandardOutput "NUL" # Start AIDA64 Start-Process "C:\Program Files (x86)\FinalWire\AIDA64 Extreme\aida64.exe" -WindowStyle Minimized # Sleep for 30 seconds Start-Sleep -Seconds 30 # Terminate Libre Hardware Monitor as it is not needed to run anymore. $proc1 = Get-Process -Name "LibreHardwareMonitor" -ErrorAction SilentlyContinue if ($proc1) { Stop-Process -Id $proc1.Id -Force }

Hello. I have a 7-inch USB-C IPS display. It works under Windows 11 and is displayed in Device Manager. I downloaded the driver from lcdwiki.com. How can I use this display externally with AIDA64? It's not showing up under "LCD" for me. Thank you for your help. usbdump.txt

Thanks. Got the Black Friday 2025 deal this morning and was very pleased to see that the regular renewal discount on top of that just made an even sweeter deal for me 💝👍

Hello, Will there be a Black Friday sale this year? I haven't seen any announcements in the newsletter. Thanks.

i can confirm that only the GPU TDP% is the problem, so yes adding a new option in stability page would resolve it 👍

I pasted and attached the requested data. 🙂

Nvidia GPU Registers ------[ Versions ]------ Program Version : AIDA64 Extreme v8.00.8026 Beta LLKD Version : 1021 BenchDLL Version: 4.7.924.8-x64 Windows Version : Microsoft Windows 11 Pro 10.0.26220.7271 (64-bit) GetProductInfo : 0x00000030 ------[ Video Adapters ]------ PNY RTX 5080 [10DE-2C02 / 196E-1432 / Rev A1] ------[ Video Driver ]------ nvldumd.dll||32.0.15.8180|||nvldumdx.dll||32.0.15.8180 ------[ nVIDIA GPU #1 @ mem D8000000 ]------ Video Adapter = PNY RTX 5080 GPU Code Name = GB203-400-A1 PCI Device = 10DE-2C02 / 196E-1432 [Rev A1] GPU Clocks = 2595 / 0 / 0 MHz Memory Clock = 15201 MHz GPU Base Clock = 13500 kHz Shader Base Clock = 13500 kHz Memory Base Clock = 13500 kHz nvidia-000000 = 1B3000A1 [GB203] nvidia-022400 = 00000000 nvidia-022430 = 00000007 nvidia-022434 = 00000006 nvidia-022438 = 00000004 nvidia-02243C = 00000004 nvidia-022440 = 00000004 nvidia-08A000 = FFFFFF8F nvidia-100714 = 00002424 nvidia-101000 = 00400080 nvidia-10100C = 02013000 nvidia-120070 = 00100401 nvidia-120074 = 00000004 nvidia-120078 = 00000007 nvidia-122634 = 00000000 nvidia-300000 = FFC00E4C nvidia-310000 = 54F0211F nvidia-700000 = 00000000 ------[ nVIDIA GPU #1 / ForceWare Properties ]------ Memory Type = 16 (GDDR7) Memory Vendor = 1 (Samsung) Memory Bank Count = 1 Memory Bus Width = 256-bit GPU / MC / VE / BI Load = 5 / 1 / 0 / 100 VPE Count = 0 Shader Pipe Count = 7 Shader SubPipe Count = 42 Total SP Count = <unknown> Total TPC Count = 0 Total SM Count = <unknown> Core Count = 10752 ROP Count = 112 Partition Count = 4 (mask: 0000000F) Fan RPM = <unknown> Fan Duty Cycle = <unknown> All Fans RPM & Duty = 0 RPM / 0 RPM / 0 % / 0 % Core Voltage = <unknown> Core Rail Voltage = 925000 uV Current Pstate = 5 PerfCap Reason = 4 (Reliability Voltage) Ventura State = <unknown> Physical Frame Buffer Size = 16693824 KB Virtual Frame Buffer Size = 16694272 KB Total / Free Video Memory = 16694272 KB / 14611080 KB ------[ nVIDIA GPU #1 / ForceWare Clocks (old) ]------ Perf. Levels = 5 Active Profile = 4 curr-core/shader/mem-0 = 180 MHz / 0 MHz / 405 MHz curr-core/shader/mem-1 = 180 MHz / 0 MHz / 810 MHz curr-core/shader/mem-2 = 225 MHz / 0 MHz / 7001 MHz curr-core/shader/mem-3 = 225 MHz / 0 MHz / 15001 MHz curr-core/shader/mem-4 = 225 MHz / 0 MHz / 15201 MHz [Active] orig-core/shader/mem-0 = 180 MHz / 0 MHz / 405 MHz orig-core/shader/mem-1 = 180 MHz / 0 MHz / 810 MHz orig-core/shader/mem-2 = 180 MHz / 0 MHz / 7001 MHz orig-core/shader/mem-3 = 180 MHz / 0 MHz / 14801 MHz orig-core/shader/mem-4 = 180 MHz / 0 MHz / 15001 MHz [Active] ------[ nVIDIA GPU #1 / ForceWare Clocks (old) ]------ Perf. Levels = 5 Active Profile = 4 curr-core/shader/mem-0 = 180 MHz / 0 MHz / 405 MHz curr-core/shader/mem-1 = 180 MHz / 0 MHz / 810 MHz curr-core/shader/mem-2 = 225 MHz / 0 MHz / 7001 MHz curr-core/shader/mem-3 = 225 MHz / 0 MHz / 15001 MHz curr-core/shader/mem-4 = 225 MHz / 0 MHz / 15201 MHz [Active] orig-core/shader/mem-0 = 180 MHz / 0 MHz / 405 MHz orig-core/shader/mem-1 = 180 MHz / 0 MHz / 810 MHz orig-core/shader/mem-2 = 180 MHz / 0 MHz / 7001 MHz orig-core/shader/mem-3 = 180 MHz / 0 MHz / 14801 MHz orig-core/shader/mem-4 = 180 MHz / 0 MHz / 15001 MHz [Active] ------[ nVIDIA GPU #1 / ForceWare Clocks (new) ]------ Perf. Levels = 1 Active Profile = 255 curr-core/mem-0 = 2805 MHz / 15201 MHz orig-core/boost/mem-0 = 2295 MHz / 2730 MHz / 15001 MHz ------[ nVIDIA GPU #1 / ForceWare Clocks (new) ]------ Perf. Levels = 1 Active Profile = 255 curr-core/mem-0 = 2662 MHz / 15201 MHz orig-core/boost/mem-0 = 2295 MHz / 2730 MHz / 15001 MHz ------[ NVAPI GPU Handles ]------ GPU Count = 1 GPU #1 = 0000000000000100 ------[ nVIDIA GPU #1 / Thermal Settings V2 ]------ Sensor Count = 1 Sensor #0 / Controller = GPU Internal Sensor #0 / Target = GPU Core Sensor #0 / Current Temp = 42 Celsius ------[ nVIDIA GPU #1 / Thermal Settings V1 ]------ Sensor Count = 1 Sensor #0 / Controller = GPU Internal Sensor #0 / Target = GPU Core Sensor #0 / Current Temp = 42 Celsius nvidiagpureg.txt

Nvidia SMBus Dump ------[ Versions ]------ Program Version : AIDA64 Extreme v8.00.8026 Beta LLKD Version : 1021 BenchDLL Version: 4.7.924.8-x64 Windows Version : Microsoft Windows 11 Pro 10.0.26220.7271 (64-bit) GetProductInfo : 0x00000030 ------[ Video Adapters ]------ PNY RTX 5080 [10DE-2C02 / 196E-1432 / Rev A1] ------[ Video Driver ]------ nvldumd.dll||32.0.15.8180|||nvldumdx.dll||32.0.15.8180 ------[ nVIDIA GPU #1 / B00-CR1F = 00 ]------ ------[ nVIDIA GPU #1 / B00-CR49 = 00 ]------ ------[ nVIDIA GPU #1 / B01-CR1F = 00 ]------ ------[ nVIDIA GPU #1 / B01-CR49 = 00 ]------ ------[ nVIDIA GPU #1 / B02-CR1F = 00 ]------ ------[ nVIDIA GPU #1 / B02-CR49 = 00 ]------ ------[ nVIDIA GPU #1 / B03-CR1F = 00 ]------ ------[ nVIDIA GPU #1 / B03-CR49 = 00 ]------ ------[ nVIDIA GPU #1 / B04-CR1F = 00 ]------ ------[ nVIDIA GPU #1 / B04-CR49 = 00 ]------ Total : 4.1 sec GPU1-B00: 0.3 sec GPU1-B01: 0.3 sec GPU1-B02: 0.3 sec GPU1-B03: 0.3 sec GPU1-B04: 2.6 sec nvidiasmbusdump.txt

Any idea when it will be released?

Yes… TRUST ME, this is seriously exciting INSANE! I don’t know everything yet, but what I’ve heard so far is nothing short of MIND-BLOWING. Just look at this: ✨ Full support for .sensorpanel, .spzip, and .rslcd files ✨ Multiple sensor panels can now be viewed at the same time ✨ Smooth animations, with support for GIFs and even video files (seems like video is currently limited to .rslcd, but still growing and amazing!) ✨ Customizable decimal precision for sensor values - whether you want 1.234 V, 1.23 V, 1.2 V, or even just 1 V ✨ New way of editing and handling Sensor panels These guys are working really hard behind the scenes, Day/Night sleepless haha to make sensor panel handling experience SMOOTH and LOVABLE!!

OK, THX! I just tried to figure out, how this relates to other benchmark results. But at least it works now and I have a basis for comparison.

We only provide deep insights into our algorithm under NDA. What I can tell you is that we use a block-random algorithm that both AMD and Intel approves as a proper method to measure memory latency on their platforms.

@xAJx I apologize for the delayed response. Our Support Dept notified me that they replied you in email.

It's not the same kind of transparency.

The fact that over a decade later nothing has been done to address this when the feature is readily available in your OSD is wild.