Fiery

On Nehalem and later Intel processors, the TJMax value is SKU specific, and is encoded into a MSR (Model Specific Register). Hence it can be detected, and no need to use static presets or hard-encoded values. However, it also means that the TJMax value may vary between individual parts, so it's not guaranteed that e.g. your i7-6900K would use the same value as your friend's seemingly similar i7-6900K part. Regards, Fiery

Thank you! Can you please mention one or two of such memory intestive program?

Awesome! :)

Please let us know exactly which ForceWare release do you have installed, and what Windows do you have running on your computer. Thanks, Fiery

I'm afraid no, because AIDA64 doesn't support monitoring NAS devices. Regards, Fiery

We don't have such an option for the main window of AIDA64. We have that option for only the OSD Panel and SensorPanel. Regards, Fiery

Thank you

Great, thank you

You're right, it looks a bit odd. We'll rename those to Fan #1, Fan #2 and Fan #3 respectively, in the next AIDA64 beta update. Thank you, we're trying to do our best

Thank you for the feedback and the updated dumps

Thank you for the feedback

The above mentioned new AIDA64 beta update is now available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

The above mentioned new AIDA64 beta update is now available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

What video card do you have, and what version of Windows and Crimson drivers do you have installed?

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Finally, right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Please also describe how many fans do you have connected, which ones are visible by AIDA64 right now, and the approx. RPM of the missing fans. Thanks, Fiery

Thank you for the feedback! North Bridge should be the temperature of the AMD 990FX north bridge chip

We will add the missing temperatures in the next AIDA64 beta update due later this week. I'll post a message into this topic once the new beta becomes available for download.

We will fix that issue in the next AIDA64 beta update due later this week

I'm afraid there aren't many active (currently sold) devices on the market that falls into that category So we generally recommend using an old Android tablet or iPad for such purpose. But I'm glad you've managed to make it work with a more relaxed update frequency

Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works Thanks, Fiery

Please make sure to disable the option Asus ATKEX sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64. It should enable the missing temperatures. Regards, Fiery

Connection speed is fixed. It shows 100 Mbps for a 100 Mbps LAN connection, 1000 Mbps (1 Gbps) for a gigabit LAN connection, etc.

It happens on i965 chipsets, when the BIOS locks down access to MCHBAR. It means chipset information cannot be read. There's no fix for this, unless the motherboard manufacturer unlocks access to MCHBAR by altering the BIOS. Regards, Fiery

That confusion was caused by a bug in the LCD rendering module of AIDA64. We will fix that in the next AIDA64 beta update Thanks, Fiery