Fiery

Please do not mix AIDA64 and EVEREST files in the same folder. Put them into different folders, and let them manage their own files. The only thing you may want to mix is copying the old EVEREST.INI file that holds your existing Preferences settings, rename it to AIDA64.INI, and copy it to AIDA64 folder. That way you can migrate your EVEREST settings into AIDA64.

1) Are you sure? We've just tested it, and we have all three OPTx temperatures in the Registry. Have you enabled the relevant items in AIDA64 / main menu / File / Preferences / Hardware Monitoring / External Applications? 2) We'll fix that in the next AIDA64 beta release. As soon as it's ready, I'll post a note into this topic Thanks, Fiery

Thank you for the feedback. It's definitely the Areca RAID members enumeration then. The old version (5.02.1750) had no support for Areca RAID arrays at all, and in this case no support means no headaches We'll check our code and either we'll fix it, or we'll implement a workaround, or we'll completely remove the Areca-related code. I'll let you know in this topic how it goes.

On your friend's computer someone has already downloaded an AIDA64 trial version over a month ago, and gave it a try. Maybe he already uninstalled it, and already forgot about it Now the 30-day trial period is over, hence you cannot use the trial version any longer. Regards, Fiery

I was just wondering the used EVEREST version, because we've implemented Areca RAID controller support in EVEREST Build 1824. In case you use an older version, then it would be great if you could give it a shot with EVEREST v5.50.2100: http://www.lavalys.com:8081/everestultimate-discontinued-550-o1kx4dyabh.zip You don't need to perform a full upgrade of EVEREST. Just download this ZIP file, extract it to an empty folder (it can even be a new folder on your Windows Desktop), and run EVEREST.EXE. In case this one hangs, it means the issue is with the Areca RAID members enumeration. Thanks, Fiery

Do you have all AIDA64 files in the AIDA64 folder? I suspect AIDA64.DAT file is missing -- maybe more files too.

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1165vs6mnwy3qxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If it's possible, please post the dumps above again, with this version. Also, using any setting for nVIDIA GPU SMBus access, please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic. Thanks, Fiery

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

We've implemented the requested hardware monitoring items. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1165vs6mnwy3qxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Thank you for the dumps. We've fine-tuned the fan speeds measurement on your motherboard. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1165vs6mnwy3qxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

We've managed to stabilize the NB and SB temperature measurement on your motherboard. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1165vs6mnwy3qxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1165vs6mnwy3qxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. In this beta we've added the following new sensor items on GeForce GTX 580: - GPU fan duty cycle (%) - GPU +12V voltage - GPU VRM voltage - GPU VRM current - GPU VRM power Let me know how it works. Thanks, Fiery

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

Thank you for the info, we'll work on that. However, on Maximus II boards we have absolutely no documentation or info on how OPT temperatures are coded in the register. The BIOS of that board simply ignores any readings above 110, so it simply does not support any negative temperatures. You mentioned -1 Celsius is coded as 129 (signed integer), but can you also please check how -2 and -3 Celsius is coded? -2C = 130 and -3C = 131 perhaps? Thanks, Fiery

I think it could be the Areca controller. What version of EVEREST Ultimate Edition do you have that has no issues with the controller? Thanks, Fiery

As you found it, AIDA64 already has an option (main menu / File / Preferences / Stability / nVIDIA GPU SMBus access through nVIDIA ForceWare) to switch to NVAPI usage instead of direct nVIDIA I/O. If it's possible, 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 the data in that dump we could check what's going on with the fan in NVAPI mode. It would be an additional help if you could perform the same dump with direct nVIDIA I/O setting (nVIDIA GPU SMBus access through nVIDIA ForceWare = disabled/unchecked). Before issuing those dumps, make sure to close other hardware monitoring software, to avoid any collisions. Thanks, Fiery

A couple of BIOS settings are displayed on the Motherboard / BIOS page for capable motherboards. But a generic BIOS settings readout is not possible, since all motherboards use a custom BIOS layout, and motherboard manufacturers don't publish their BIOS layouts

Everytime a user enters a product key that cannot be not found in the EVEREST Customer Database, or when any other issues happen while validating the existing EVEREST license, we always indicate our support email address where we welcome a report of such issues. In fact, when a product key cannot be found in the EVEREST Customer Database, an automatic message is dispatched to our Support Department, and our support staff will contact the user shortly to fix the issues. We don't turn our backs to anyone, quite the contrary. If you got mad during the upgrade process, we are truly sorry about it, but we firmly believe we do everything in our power to make sure every EVEREST customers are transitioned and properly serviced. It's not our fault that the EVEREST Customer Database that we got from Lavalys has serious issues, e.g. for reasons we cannot fathom a lot of customers are simply not included in the database. In such case further manual process is required to verify the validity of the EVEREST license.

In most cases such things happen when the low-level hardware monitoring module of AIDA64 collides with another monitoring software, e.g. SpeedFan, HWMonitor, Asus PC Probe II, etc. Are you running any other software, made by Asus or a 3rd party that measures temperatures or voltages?

Thank you for letting us know

I suppose it may be something to do with how AIDA64 handles the sensor chip of your motherboard. 1) 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. 2) 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. That data should help us to find out what went wrong since EVEREST Thanks, Fiery

We'll check it out, and we'll try to implement SSL SMTP support in the next AIDA64 update. Thank you for the idea. Regards, Fiery

According to past user feedbacks, those users who want to disable debug info will always want to have that disabled, hence they use the option in the Preferences to get rid of the debug info, and then they forget about it ever existed So I don't think it would be useful to add the debug info checkbox to the Report Wizard. Regards, Fiery

You cannot re-save a MHTML file. AIDA64 is there to save the report to MHTML file, and the file that AIDA64 creates should work. If you edit the file or save it again from your browser, the results may be unexpected If you want to edit a MHTML file, please edit it in a text editor (ie. edit the HTML source).

We had intermittent issues with our servers yesterday, so that may have caused the issues. I hope it won't happen again