Fiery

Thank you for the feedback. If you consider the audio issue a potential bug in AIDA64, then please let me know what items are missing from which page of AIDA64? Motherboard / Chipset page? Multimedia / HD Audio page? Or both pages?

AIDA64 has several features to let you use AIDA64 sensor readings in 3rd party applications. You can active those features in AIDA64 / main menu / File / Preferences / Hardware Monitoring / External Applications. Those features are of course compatible with both Windows 7 and Windows 8. Regards, Fiery

Thank you. While your video card is under load (not idling), please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. Copy-paste the results into this topic. Thanks, Fiery

I meant to find out whether it's only an appearance issue, and the icon still works fine -- but you already confirmed those Can you please check where the shortcut of the icon points to exactly? Is it C:\Program Files (x86)\FinalWire\AIDA64 Extreme Edition\aida64.exe ?

No idea... Probably only MSI knows.

Thank you. Unfortunately the GPU VRM reading provided by CHL8266 is invalid in both cases.

Thank you. Can you please try to enable both mentioned RAID options? Even when the controller is not running in RAID mode, those options may help to find the right code path for the SATA controller enumeration by AIDA64

Your card have 2 chips (Nuvoton and CHiL), and they provide 3 readings in total, but AIDA64 only shows the 2 readings for the Nuvoton chip. If you could post 2 new nVIDIA SMBus Dumps, one when the card is at idle and running relatively cool, and another one where the card is after a heavy load (like after running 3DMark or a 3D game), we could check the VRM temperature readings (provided by the CHiL chip), because there's a chance on your card that reading is not stuck like on most GTX580/GTX680 cards.

Maybe it calls the GPU temperature (the one that AIDA64 labels as "GPU") as GPU Memory; and it calls the GPU Ambient temperature as GPU VRM?

In theory the onboard CHiL CHL8266 power controller chip could also monitor a temperature reading (GPU VRM), but on GTX580 and GTX680 cards that reading is stuck at a fixed value, so AIDA64 doesn't display that temperature reading. I have no idea where GPU Memory could come from though

Thank you. Your cards feature a Nuvoton sensor chip that provides 2 temperature readings (GPU and GPU Ambient) on top of the GPU Diode reading that is provided by the GTX680 GPU chip itself.

Maybe your particular GTX680 card does have a sensor chip -- while most GTX680 cards do not. Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic. Using that dump we can check what's up about sensor chips and other readings on your video card

1) Have you tried it with the latest AIDA64 beta release? (v2.70.2267) 2) What version of AMD Catalyst driver do you have installed? 3) Can you please try it with AMD Catalyst 13.1 driver? (latest WHQL release) Thanks, Fiery

1) Do you have both RAID options enabled in AIDA64 / main menu / File / Preferences / Stability? 2) Have you tried it with the latest AIDA64 beta release? (v2.70.2267) 3) Do you use Win7 64-bit SP1? 4) What driver do you have installed for the Marvell controller? (version+build) Thanks, Fiery

GTX680 cards do not feature a sensor chip. On video cards you need a sensor chip to monitor such temperature readings as GPU ambient, GPU memory or GPU VRM.

Thank you, we've adjusted sensor information to suit your board. We've also removed the bogus +5V and +12V readings, since apparently your motherboard doesn't monitor those voltage rails. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2267p3nb4ktwzjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

We'll try to, although it looks like a serious AI Suite malfunction (bug) rather than an AIDA64 issue. When you uninstall a particular software suite like AI Suite, that has a lot of components and services, it is quite basic expectation to have them remove every components and services when you uninstall it. If it leaves some background service running on the system, that may raise a lot of issues with 3rd party software that may rely on those broken services So if possible, please try to convince Asus to fix AI Suite, while we're trying to implement a workaround on our side (AIDA64).

Thank you. That confirms that ATKEX calls still work properly in AIDA64 when AI Suite is installed.

On mobile systems CPU temperature and motherboard temperature are usually read using ACPI calls. Such ACPI calls may provide inaccurate or "frozen" (fixed) values when the ACPI layer is not properly implemented. In such cases it's best to ignore those values, and focus on the core temperature readings.

So the icon is there, but it is not the AIDA64 icon, but a generic icon? We've seen such issues, but only when the AIDA64 shortcut pointed to a remote path (UNC path). The icon still works fine then, just doesn't look right. Does the icon behave similarly on your system?

Doesn't it have a PC Health Status or H/W Monitor page in the BIOS Setup? Even entry-level boards have that

Thank you for the data. Can you please check what values does BIOS Setup report for +5V and +12V rails? That info will help us to calibrate voltage readings. Thanks, Fiery

I'm sorry, but we haven't yet installed any Windows using a USB drive, so I cannot help you about that. Maybe other users will chime in and give you guidelines.

Thank you, that's a great info! We'll try to get a DeLock hw soon. At least they're distributed around here, although that particular model is not available right now

I'm afraid there's no such debugging feature in AIDA64 that could "catch" such a weird issue However, can you please try the following: 1) Leave the new BIOS in the board (do not downgrade to 0704) 2) Install AI Suite II (latest release) 3) Restart the system 4) Start AIDA64, make sure to have the Asus ATKEX option enabled in main menu / File / Preferences / Stability. If you alter that option, then you need to restart AIDA64. 5) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. That way we could check what happens with AI Suite installed. That seems to be the only way on this board (with the new BIOS) to make AIDA64 stable, since when AI Suite is installed, AIDA64 skips its low-level EC (Embedded Controller) communications and instead call an AI Suite component (ATKEX) to gather sensor readings. However, there's a slim chance with the new BIOS our ATKEX code fails to work for some reason. Having the ISA Sensor Dump on hand may enable us to verify that theory. Thanks, Fiery