AIDA64 identifies Nova Lake-S: what the beta reveals and what Intel has yet to confirm

4 min read
PantheraLeo1359531 / Wikimedia Commons, CC BY 4.0. 2025 reference hardware photograph; does not represent an 617.42 controller test. Resized and converted to WebP. Image source. License.

AIDA64 Extreme 8.40.8510 beta, released on October 5, adds identification for Intel Core Ultra 5, 7, and 9 processors in the 4xxx series, described in its release notes as Nova Lake-S. This signals that diagnostic tools are preparing to recognize the family. The news is about the software: the changelog does not provide a list of Intel retail processors, prices, or a release date.

The same update adds sensor support for the ASUS Eurux GR120, Corsair HXi Shift power supplies, and the ASUS ROG Astral RTX 5090 32G PF. It also fixes support for Aqua Computer Ampinel and filters out invalid current readings from Astral sensors. These changes are less attention-grabbing than the name of a future CPU, but they matter to people who use the app to monitor their systems.

Identification, measurement, and performance are different things

Identifying a processor means matching the information it exposes to a name and characteristics the program can recognize. This capability can be added before a product is available in stores. By itself, it does not show how many models will arrive, what clock speeds they will have, or which motherboard each one will need.

Measurement presents another challenge: correctly interpreting the readings provided by sensors. If a version displays an invalid value, a high figure on screen is not enough to conclude that the hardware is consuming that much power. The filtering fix included in this beta is a reminder that monitoring software may also need adjustments.

Performance, finally, requires running a workload and measuring the result. A «Core Ultra 9 4xxx» identification string is not a performance test. Comparing processors requires information about the configuration, memory, power limits, BIOS version, and specific task. Without that data, the detected name can easily become a conclusion that the changelog does not support.

How to use a diagnostic beta responsibly

A beta can be useful when you need recognition for recent hardware or a sensor fix that has not yet appeared in the stable version. Before comparing readings, note which version you are using and keep the conditions the same. Changing the application, workload, and power profile all at once makes it hard to tell where a difference comes from.

For example, a momentary temperature spike does not describe behavior during a long export. It helps to record the duration, maximum, and workload progression. If an impossible or inconsistent reading appears, checking it against another source within the system is more useful than immediately blaming a component.

AIDA64’s announcement adds a piece to the Nova Lake-S picture, along with several concrete diagnostic improvements. Intel must provide the product lineup and specifications, and those must be backed by identifiable measurements. This beta helps users better monitor compatible hardware; it is no substitute for either.

By evovo Team