Overview
AIDA64 tells you exactly what is inside a machine, down to the memory module part numbers, the storage controller firmware, the display panel model and the voltage regulator layout. For anyone diagnosing hardware, buying used equipment, auditing a fleet or working out why a machine throttles, it answers questions no built in system panel will touch.
The sensor side is the part that stays open on a second monitor. Temperatures, fan speeds, voltages, clock frequencies, power draw and utilisation are read from every sensor the board exposes, logged to a file over time, shown on an external display or a connected panel, and used to trigger alerts when a value crosses a threshold. Throttling shows up here long before it shows up as a complaint.
The stability tests push processor, memory, cache, storage and GPU either separately or together, which is how a new build or a suspect machine gets validated. Alongside them sit the benchmark set for comparison against reference results, and the network audit tools that inventory every machine on a network into a report covering hardware, installed software, licences and configuration.
What it does well
Deep hardware detail
Identifies components down to module part numbers, controller firmware, panel models and board layout, well past what the system tools report.
Sensor monitoring
Every exposed temperature, fan, voltage, clock and power reading, logged over time with thresholds and alerts.
Stability testing
Targeted stress on processor, memory, cache, storage and GPU individually or combined, with monitoring running alongside.
Benchmarks
Memory, cache, processor and disk benchmarks with reference results for comparison against known hardware.
Network audit
Inventories machines across a network into a report covering hardware, installed software, licences and configuration.
Changes in this build
- Hardware database updated for the current processor, chipset and GPU generations.
- Sensor support added for recent motherboard controller chips.
- Stability test rebalanced for high core count processors.
- Report generator gained additional export formats for audit output.
- Fixed incorrect readings on some drives reporting non-standard sensor data.
What is in the package
- AIDA64 installer covering all four editions, 32-bit and 64-bit
- Sensor monitoring and logging modules
- Stability test and benchmark suite
- Network audit and reporting tools
- Multilingual interface files, 40 languages
System requirements
| Processor | Any x86 or x64 processor |
| Memory | 512 MB |
| Graphics | Any GPU with a current driver |
| Storage | 150 MB free |
| Display | 1024 x 768 minimum |
| System | Windows 7 through Windows 11 |
Installation
- Extract the archive to a local folder.
- Run setup and select the edition you want, or install the full set.
- Apply the included configuration step before the first launch.
- Allow the sensor driver to load when prompted, monitoring needs it.
- Open the sensor panel and confirm readings appear before running a stability test.
Before you start
Run the stability test with monitoring visible and stop it if temperatures climb past a safe point.
The sensor driver needs administrator rights, monitoring is limited without it.
Network audit needs credentials on the target machines, it will not enumerate them otherwise.
Questions about this title
Which editions are included?
All four, selectable during setup or installed together.
Does it monitor temperatures?
Yes, every sensor the board exposes, with logging and alerts.
Can it stress test a new build?
Yes, processor, memory, cache, storage and GPU, separately or together.
Does it audit a network?
Yes, into a report covering hardware, software and licences per machine.
About this listing
This entry was checked on a clean install of Windows 7 / 8 / 10 / 11 (32-bit and 64-bit) before it was published, and it is rechecked whenever the package is rebuilt. The figures on this page come from the site index rather than from the publisher, so the download count is what people here have actually pulled.
If a mirror stops answering, use the contact form and it gets replaced. Reports about a specific title are handled faster than general messages because they name the file, the mirror and the point at which the transfer stopped.
Requests for a different version, a different language build or an older release go on the requests page. Older versions of a title are usually still held even when only the current one is listed.