AIDA64 identifies the parts and operating state of a computer. It reads processor, motherboard, memory, storage, graphics, network, driver, operating-system, and sensor data, then groups the results into detailed pages and reports. It can also compare selected processor and memory operations or place components under sustained load. This goes beyond the basic Windows device list because AIDA64 reads model-specific registers, firmware data, timings, temperatures, voltages, and health records. It reports what the hardware exposes; it does not repair a failing device or prove that a synthetic score matches performance in every program.
Read the inventory
The page tree separates hardware, software, display, storage, network, and operating-system details. AIDA64 can reveal the exact motherboard model, memory-module data, storage interfaces, display modes, driver files, and installed components without opening the case. The summary page is useful for orientation, while the deeper pages expose properties needed for a driver update or hardware change.
Some fields depend on firmware tables and device controllers. A missing sensor value does not always mean the sensor is broken; the board may not expose it through a supported path. A reported marketing name can also differ from the physical label when a vendor reuses an internal identifier.
Watch live sensors
AIDA64 can poll temperatures, fan speeds, voltages, clock rates, power readings, and drive health. Selected readings can appear in a SensorPanel, on-screen display, tray icons, logs, or external displays. Update intervals matter: very fast polling creates more activity, while a slow interval can miss a brief temperature or clock spike.
Hardware monitoring reaches below ordinary Windows counters. Low-level SMBus, SMART, PCI, RAID, and GPU calls can conflict with old controllers or another vendor utility. Rare systems may slow down, lock, show warnings, or interfere with fan control. Disabling the conflicting module restores stability but also removes the readings obtained through that path.
Compare benchmark runs
The benchmark pages measure memory bandwidth and latency plus selected CPU and floating-point workloads. Reference entries place the score beside other configurations. These are synthetic measurements, so they are useful for comparing the same machine before and after a memory-timing or clock change. They do not reproduce the storage, graphics, and software behavior of a complete real task.
Run comparisons under matching conditions. Background updates, power limits, thermal throttling, memory channel changes, and a different processor clock can move the score. A higher number from one short run is weak evidence if the second configuration used a cooler start or a different power plan.
Stress selected parts
System Stability Test can load the CPU, floating-point unit, cache, memory, disks, and graphics processor separately or together. Selecting one subsystem helps narrow a failure. Combining several raises total power and heat and can expose a cooling or power-supply problem that an isolated test does not trigger.
AIDA64 displays temperatures and related graphs during the run, but the operator must decide when to stop. Excessive temperature, clock collapse, visual corruption, or system errors require attention. A stress test intentionally creates a heavier sustained load than normal browsing, and leaving it unattended can turn a cooling problem into a shutdown.
Build focused reports
Report Wizard can collect all pages, a preset profile, or a custom selection into a file for inventory or support work. A full report can contain serial numbers, computer names, installed software, network details, and other identifying data. Review the selected sections before sharing it outside the organization.
AIDA64 editions differ in audit, remote, and commercial functions, so a guide for one edition may name a page that another installation does not contain. The underlying inventory remains most useful when the report records the exact machine state and the operator keeps the date and test conditions with it.
