The next-generation AIDA64 is around the corner 🥳

[Fiery]

We're happy to report that we've just rolled out the first beta build of the next-generation AIDA64:

https://www.aida64.com/downloads/latesta64xebeta

The new AIDA64 will be rolled out as v8.00 stable update in September.  Until then, please feel free to check it out as a beta build.  We consider this first build already quite stable, but we'd love to hear your feedback too.

As for what you can expect of AIDA64 v8.00, here's the list of improvements:

• native 64-bit binaries, new compiler, faster startup and operation
• OpenCL support for nVIDIA GeForce RTX 5000 Series GPUs to unlock GPGPU benchmarks and GPU stress testing
• dynamic DPI scaling (a.k.a. per-monitor DPI awareness)
• improved and fixed handling of multiple monitors, especially with mixed DPI settings
• Unicode string handling, improved localization, fixed Windows codepage discrepancy issues
• Windows PE v3.0+ support
• Windows 11 style icons (coming later in the summer)
• SPZIP file format for more compact and better manageable SensorPanel layouts
• discontinued support for all 32-bit Windows versions and Windows XP x64

In case you find any issues while using the new generation AIDA64, please report them here, in this topic.

Please note that under Windows Vista, Windows 7, Windows 8 and Windows 8.1, you may have to install Microsoft Visual C++ Redistributable for Visual Studio 2015 (x64) in order to use the new AIDA64 version.

Before upgrading to this build, make sure to backup your settings, e.g. your AIDA64.INI file in the AIDA64 installation folder.  This is especially crucial in case you use SensorPanel.  The next-generation AIDA64 revamps handling SensorPanel positioning and sizing in mixed DPI screen setups.

[COSTAJUNIOR]

Before installing this update, I went to the FinalWire/AIDA64 Extreme folder and looked for the AIDA64.INI file to back it up, as you mentioned, but I couldn't find it. Could you help me with this?

[JariKoi]

[tistou77]

Thanks, faster startup inded and no problem for the moment

The .ini file was kept during the upgrade, for me

[JariKoi]

 

I've encountered a problem with this new beta update where if I want to move panel from one screen to another, it stutters or doesn't move at all when I try to drag it with mouse.

[COSTAJUNIOR]

1 hour ago, JariKoi said:

Thanks a lot! I found out that the files aren't showing their extensions. It only shows 'aida64

[Fiery]

1 hour ago, tistou77 said:

Thanks, faster startup inded and no problem for the moment

The .ini file was kept during the upgrade, for me

Yes, the .ini file and its content is kept of course, but when it comes to mixed DPI setups, SensorPanel settings may be altered a bit at the first time you edit something on your SensorPanel.  We tried to make it as smooth as possible, but just to be on the safe side, it's best to backup your settings before switching to the next-generation AIDA64.

[Fiery]

1 hour ago, JariKoi said:

I've encountered a problem with this new beta update where if I want to move panel from one screen to another, it stutters or doesn't move at all when I try to drag it with mouse.

Try to move it a bit harder   Joking aside, when you use different scaling on your monitors (for example, 100% with your secondary, smaller display; and 200% on your main 4K display), Windows will apply per-monitor DPI awareness on the windows you grab from one display to another.  And the switch from one DPI to the other causes a bit of a stuttering when you move the window across the monitor edge (so to speak).  It's a bit like if the window would want to stick to the old monitor, the one you move the window away from.

[NereusH]

the latest update removes sensors for 12vhpwr individual pins (voltage as well as current) and memory temperatures for Asus Astral 5090 cards. Please look into it.

[Fiery]

4 minutes ago, NereusH said:

the latest update removes sensors for 12vhpwr individual pins (voltage as well as current) and memory temperatures for Asus Astral 5090 cards. Please look into it.

Thank you for your feedback!  In AIDA64 please press Ctrl+D --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Also press Ctrl+D --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Thanks,
Fiery

 

[NereusH]

3 minutes ago, Fiery said:

Thank you for your feedback!  In AIDA64 please press Ctrl+D --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Also press Ctrl+D --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Thanks,
Fiery

 

For GPU registers - 

------[ Versions ]------

Program Version : AIDA64 Extreme v7.99.7801 Beta
LLKD Version    : 1019
BenchDLL Version: 4.7.917.8-x64
Windows Version : Microsoft Windows 11 Pro 10.0.26100.4202 (64-bit)
GetProductInfo  : 0x00000030

------[ Video Adapters ]------

Asus ROG-Astral-LC-RTX5090-O32G-Gaming [10DE-2B85 / 1043-89EC / Rev A1]

------[ Video Driver ]------

nvldumd.dll||32.0.15.7652|||nvldumdx.dll||32.0.15.7652

------[ nVIDIA GPU #1 @ mem F0000000 ]------

Video Adapter = Asus ROG-Astral-LC-RTX5090-O32G-Gaming
GPU Code Name = GB202-300-A1
PCI Device    = 10DE-2B85 / 1043-89EC [Rev A1]

GPU Clocks   = 1192 / 0 / 0 MHz
Memory Clock = 14001 MHz

GPU    Base Clock = 13500 kHz
Shader Base Clock = 13500 kHz
Memory Base Clock = 13500 kHz

nvidia-000000 = 1B2000A1  [GB202]
nvidia-088000 = BADF1100  []
nvidia-08A000 = FFFFFF8F

------[ nVIDIA GPU #1 / ForceWare Properties ]------

Memory Type             = 16 (GDDR7)
Memory Vendor           = 1 (Samsung)
Memory Bank Count       = 1
Memory Bus Width        = 512-bit
GPU / MC / VE / BI Load = 7 / 8 / 0 / 53
VPE Count               = 0
Shader Pipe Count       = 11
Shader SubPipe Count    = 85
Total SP Count          = <unknown>
Total TPC Count         = 0
Total SM Count          = <unknown>
Core Count              = 21760
ROP Count               = 176
Partition Count         = 8 (mask: 000000FF)
Fan RPM                 = <unknown>
Fan Duty Cycle          = <unknown>
All Fans RPM & Duty     = 0 RPM / 0 RPM / 0 % / 0 %
Core Voltage            = <unknown>
Core Rail Voltage       = 805000 uV
Current Pstate          = 0
PerfCap Reason          = 4 (Reliability Voltage)
Ventura State           = <unknown>

Physical Frame Buffer Size = 33389120 KB
Virtual  Frame Buffer Size = 33389568 KB
Total / Free Video Memory  = 33389568 KB / 31096704 KB

------[ nVIDIA GPU #1 / ForceWare Clocks (old) ]------

Perf. Levels   = 5
Active Profile = 4

curr-core/shader/mem-0 = 225 MHz / 0 MHz / 405 MHz
curr-core/shader/mem-1 = 225 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 / 13801 MHz
curr-core/shader/mem-4 = 225 MHz / 0 MHz / 14001 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 / 13801 MHz
orig-core/shader/mem-4 = 180 MHz / 0 MHz / 14001 MHz [Active]

------[ nVIDIA GPU #1 / ForceWare Clocks (old) ]------

Perf. Levels   = 5
Active Profile = 4

curr-core/shader/mem-0 = 225 MHz / 0 MHz / 405 MHz
curr-core/shader/mem-1 = 225 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 / 13801 MHz
curr-core/shader/mem-4 = 225 MHz / 0 MHz / 14001 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 / 13801 MHz
orig-core/shader/mem-4 = 180 MHz / 0 MHz / 14001 MHz [Active]

------[ nVIDIA GPU #1 / ForceWare Clocks (new) ]------

Perf. Levels   = 1
Active Profile = 255

curr-core/mem-0 = 2692 MHz / 14001 MHz

orig-core/boost/mem-0 = 2017 MHz / 2580 MHz / 14001 MHz

------[ nVIDIA GPU #1 / ForceWare Clocks (new) ]------

Perf. Levels   = 1
Active Profile = 255

curr-core/mem-0 = 2692 MHz / 14001 MHz

orig-core/boost/mem-0 = 2017 MHz / 2580 MHz / 14001 MHz

------[ NVAPI GPU Handles ]------

GPU Count = 1

GPU #1 = 00000100

------[ nVIDIA GPU #1 / Thermal Settings V2 ]------

Sensor Count = 1

Sensor #0 / Controller   = GPU Internal
Sensor #0 / Target       = GPU Core
Sensor #0 / Current Temp = 32 Celsius

------[ nVIDIA GPU #1 / Thermal Settings V1 ]------

Sensor Count = 1

Sensor #0 / Controller   = GPU Internal
Sensor #0 / Target       = GPU Core
Sensor #0 / Current Temp = 32 Celsius
 

For SMBus - 

------[ Versions ]------

Program Version : AIDA64 Extreme v7.99.7801 Beta
LLKD Version    : 1019
BenchDLL Version: 4.7.917.8-x64
Windows Version : Microsoft Windows 11 Pro 10.0.26100.4202 (64-bit)
GetProductInfo  : 0x00000030

------[ Video Adapters ]------

Asus ROG-Astral-LC-RTX5090-O32G-Gaming [10DE-2B85 / 1043-89EC / Rev A1]

------[ Video Driver ]------

nvldumd.dll||32.0.15.7652|||nvldumdx.dll||32.0.15.7652

------[ 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   :    1.4 sec
GPU1-B00:    0.2 sec
GPU1-B01:    0.2 sec
GPU1-B02:    0.2 sec
GPU1-B03:    0.2 sec
GPU1-B04:    0.2 sec

[BHSY]

 

[Fiery]

16 hours ago, NereusH said:

For GPU registers - 

[...]

Thank you! We've fixed the issue in the latest AIDA64 beta update available at:

https://www.aida64.com/downloads/latesta64xebeta

 

[edgecrusher13]

The new update caused my LCD monitoring screen to go blank.  My wife's as well (we have the same AlphaCool LCD.)  Rolling back to a previous version brought our displays back, including our custom monitoring setups.  What can I do to preserve our LCD sensor screen setups prior to updating again?  Is it as simple as copying the aida64.ini and replacing after the update, or do I need to backup the screen settings somehow?

[Fiery]

13 minutes ago, edgecrusher13 said:

The new update caused my LCD monitoring screen to go blank.  My wife's as well (we have the same AlphaCool LCD.)  Rolling back to a previous version brought our displays back, including our custom monitoring setups.  What can I do to preserve our LCD sensor screen setups prior to updating again?  Is it as simple as copying the aida64.ini and replacing after the update, or do I need to backup the screen settings somehow?

I don't think this is a configuration issue.  You need to make sure to have LibUSB properly installed.  I suppose your setup lacks the 64-bit DLL for LibUSB but has the 32-bit version only.  Try to download the 64-bit LibUSB DLL and place it in the AIDA64 installation folder.

If you cannot find or download the 64-bit DLL, drop me a private message and I will send it to you.

As for backing up and restoring your LCD settings, all you gotta do is copy the AIDA64.INI configuration file.  It includes your LCD and SensorPanel layouts as well as most other settings.

[edgecrusher13]

14 minutes ago, Fiery said:

Try to download the 64-bit LibUSB DLL and place it in the AIDA64 installation folder.

I was able to find/download libusb0.dll (64bit.)  Is this the correct file?

[Fiery]

17 minutes ago, edgecrusher13 said:

I was able to find/download libusb0.dll (64bit.)  Is this the correct file?

Yes, it is.

[edgecrusher13]

That worked, thank you!!

[Fiery]

Just now, edgecrusher13 said:

That worked, thank you!!

Awesome 😎

[NereusH]

11 hours ago, Fiery said:

Thank you! We've fixed the issue in the latest AIDA64 beta update available at:

https://www.aida64.com/downloads/latesta64xebeta

 

Thank you for the quick fix. Works fine now !