Fiery

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

Since you purchased your license less than a year ago, your license is still active (the maintenance period is not yet expired). Hence you are eligible for a free upgrade to AIDA64. You don't have to pay anything. You can upgrade to AIDA64 at: http://www.aida64.com/everest-upgrade Regards, Fiery

Okay, this topic went too far IMHO, and I'm not blaming anyone here specifically. I don't see a point to continue this, and I believe I've already provided a proper reply to the issue. Topic closed.

Right after your Everest purchase you should have received an email with your Everest product key. If you cannot find that email, then please contact our Licensing Department at: upgrade AT aida64.com (replace AT with @) In your email make sure to indicate your full name and the date of purchase.

Even 0.400V would be very low for a voltage reading Can you see the same reading in the BIOS Setup?

Okay, then it's only 2 fans, and the other 2 are for the pumps. But it doesn't change the fact that your motherboard can monitor Power Supply Fan, using a dedicated fan header on your motherboard. In case your BIOS Setup measures the same value as AIDA64 does, then either you have a fan connected to that fan header, or your motherboard measures a phantom fan speed there. In which case (if it's a phantom fan speed) you can simply ignore that fan reading. You can blame AIDA64 for measuring a phantom fan speed, but when your motherboard in the BIOS Setup measures the same fan speed, then it's definitely not the fault of AIDA64. AIDA64 simply shows the same readings as your motherboard's BIOS Setup does, so I don't see a problem with AIDA64 there.

The GPU core voltage in AIDA64 is measured using ForceWare driver calls, so it must be accurate

In case the BIOS Setup provides the same value for Power Fan Speed, then I suppose the reading is fine in AIDA64. The reason why the reading may be unstable is either the fault of the motherboard's fan speed measurement logic, or the fault of the cooling fan. Certain low-speed cooling fans tend to have a problem reporting their actual RPM speed in a stable and reliable way. You don't have to worry about that, especially when your computer has 4 other cooling fans spinning nicely

It's very low, so I'd say it is a phantom reading that should be ignored. If you have the same reading in the BIOS Setup, then I may be wrong

Please try to download the latest beta version of AIDA64 Extreme Edition, and try it with that too: http://www.aida64.com/downloads/aida64extremebuild1158cbv3slyk8nzip In case that still doesn't accept your key, then please send an email to our Sales Department: upgrade AT aida64.com (replace AT with @) BTW, make sure to download the right edition of AIDA64. If you had a key for EVEREST Ultimate Edition that you exchanged for an AIDA64 key, then you need to use AIDA64 Extreme Edition, and not AIDA64 Business Edition. Also make sure to have the right date configured on your system. Sometimes (e.g. after a system crash, or after a bad overclocking try, etc) the date may reset to e.g. January 01, 2008. You have to make sure you have the right date set in Windows before you can enter the key in AIDA64. Thanks, Fiery

Thank you. We've checked, but unfortunately we cannot find documentation (datasheet) for your clockgen chip. Hence we cannot implement PCI or PCI-E clock measurement for your motherboard Regards, Fiery

Fugitive: please try to be a bit more polite with fellow forum users who try to help you by clarifying the situation with your hardware When a motherboard fan header says "PSU FAN", then in most cases AIDA64 will also call the fan RPM that fan header measures as "Power Supply" fan. But that doesn't mean it is the fan speed of the PSU, since you can connect e.g. the CPU fan onto the "PSU FAN" fan header, and your system will work just fine 1) What motherboard do you have? 2) Do you experience the same issue in the BIOS Setup? 3) Do you experience the same issue with a manufacturer-supplied hardware monitoring software as well? E.g. if you have an Asus motherboard, then the manufacturer-supplied hardware monitoring software is called Asus PC Probe II. If you have a Gigabyte motherboard, then the manufacturer-supplied hardware monitoring software is called Gigabyte EasyTune6. etc. Thanks, Fiery

Yes, that's the proper way. If you do so, your entered product key (license key) and also all your Preferences adjustments will be retained at every upgrades. You can also upgrade from a stable version to a newer stable version, or from a beta version to a new stable version using the same method. AIDA64 stable versions are also available as portable .ZIP packages. Regards, Fiery

Thank you for the tip, we'll work on improving the GTX580 sensor support.

Thanks for the feedback

Thanks for the feedback

AIDA64 Beta Build 1158 is out: http://www.aida64.com/downloads/aida64extremebuild1158cbv3slyk8nzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let us know if it still refuses to accept your AIDA64 product key. Thanks, Fiery

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1158cbv3slyk8nzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. BTW, the slowness was due to a bug in Intel's Rapid Storage Technology drivers. We've already notified Intel about this issue. Thanks, Fiery