Fiery

Thank you for the feedback

Thank you, the next beta release of AIDA64 will fix that issue. The actual thing changed between those Everest builds were the ForceWare interface support for GF100 based cards. Hence with Everest v5.50.2100 the SMBus access was always done directly. --- We've done some more test runs on our Gigabyte GTX470 test card, and it seems the issue is related to the ForceWare driver calls, and so it is not a bug related to AIDA64 I'm afraid That effectively means performing direct SMBus access, to avoid ForceWare interface performance issues. Further improvement can be achieved by disabling the option "GPU fan speed measurement" in AIDA64 / Preferences / Stability, when GPU fan monitoring is not required.

1) Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. 2) 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. 3) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. Thanks, Fiery

Thank you. So it seems AIDA64 measures the same weirdly low CPU temperature as Asus' software It may be a hardware implementation issue.

We've implemented GPT support in the following new beta release of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1333ty4wmqx2hczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

In case you mean the core temperatures, then maybe you need to adjust the TJMax temperature to a higher value in AIDA64 / main menu / File / Preferences / Hardware Monitoring. Regards, Fiery

Thank you, we've implemented the temperature readouts in the following beta release of AIDA64: http://www.aida64.com/downloads/aida64extremebuild1333ty4wmqx2hczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Please note that there's a slim chance the measured CPU temperature is lower by a fixed value (e.g. by 10 Celsius) than the actual one. In such case, both at idle and under load a certain offset will be shown compared to the actual CPU temperature. In case you have an Asus temperature monitoring software on hand, you can verify the CPU temperature using that. Thanks, Fiery

Thank you, we've fixed the +12V reading in the following beta release of AIDA64: http://www.aida64.com/downloads/aida64extremebuild1333ty4wmqx2hczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

If you want to override the automatic settings used to calculate core temperatures, go to AIDA64 / main menu / File / Preferences / Hardware Monitoring, and adjust TJMax temperature to 100 Celsius. Regards, Fiery

1) Close AIDA64 2) Start REGEDIT.EXE (Registry Editor) 3) In the left panel navigate to: HKEY_CURRENT_USER\Software\FinalWire\AIDA64 4) In the main panel search for OSDPosX and OSDPosY, and modify their values both to 0 5) Then try to move the OSD Panel to the right side of the desktop. Regards, Fiery

Even though AIDA64.EXE is a 32-bit application, the benchmarks and the System Stability Test are fully ported to 64-bit, and they are in the AIDA_BENCH64.DLL module. Legacy 32-bit benchmarks and the 32-bit version of the System Stability Test are held in the AIDA_BENCH32.DLL module.

Debug information is there to help us diagnose various issues, and to implement support for new hardware. You can turn off debug info in AIDA64 / main menu / File / Preferences / Report. Regards, Fiery

Are you sure the issue is with AIDA64? Maybe TMS-200 software fails to update the shared memory content after waking up from sleep. BTW, we've tested it with an Asus P8P67 motherboard and a TMS-200, under Win7 64-bit SP1, and this system doesn't seem to be affected by this issue.

I'm sorry, but we're not planning to provide such deep customizations for the hardware monitoring items Regards, Fiery

Apparently the temperature diode of your SSDs do not work -- or there's no temperature diode in them at all. That's unfortunately a common issue of many SSD drives.

Thank you for the feedback

Currently, you cannot select it from AIDA64. And we're not sure how Logitech drivers specify or decide the order of the devices. AIDA64 simply connects to the Logitech LCD API (interface), enumerates devices, and uses the first one it finds. In case it's possible, please try to set the primary device in Logitech's software.

I think some of your requirements may be fulfilled with the Audit Manager and Change Manager features of AIDA64 Business Edition. Anyhing more specific than that would require a custom query tool to be developed. Regards, Fiery

Thank you for the feedback

No. That means AIDA64 takes the readings directly from the onboard sensor chips, using low-level port I/O. On your motherboard AIDA64 doesn't access the BIOS for sensor readings at all.

Thank you. That indeed confirms your drive is a cut-down version of the UJDA775 combo drive

They are stored in the AIDA64.INI file in the AIDA64 installation folder. E.g. C:\Program Files\FinalWire\AIDA64\AIDA64.INI Regards, Fiery

On the G1.Assassin AIDA64 reads temperatures as: Mobo = ITE IT8720 super I/O chip / temp 0 (register 0x29) CPU = ITE IT8720 super I/O chip / temp 1 (register 0x2A) Temp 2 = ITE IT8720 super I/O chip / temp 2 (register 0x2B) Temp 1 = Winbond W83L786 sensor chip / temp 0 (register 0x25) Temp 3 = Winbond W83L786 sensor chip / temp 1 (register 0x26)

Even when I Google on "HP 398149-131" it returns a lot of hits where they claim this drive can burn CD. We've removed UJDA775 from the optical drive database of AIDA64 to avoid confusion. When you have a chance, please start AIDA64, open the "Storage" group in the left menu, right-click on "Optical Drives", select Quick Report --> Plain Text. Copy-paste the full results into this topic. Thanks, Fiery

Then please also compare the temperatures measured by AIDA64 against the temperatures measured by EasyTune6. It should provide you an insight into whether AIDA64 is at fault, or your motherboard measures temperatures a bit weirdly