Fiery

You can disable automatic updates in the Preferences / General, and manually check for updates in main menu / Help. Please note that the daily (or weekly, or monthly, whichever you configure) checking for updates only downloads a small amount of data. The "big chunk" of data only downloaded if you opt to perform the update. Regards, Fiery

EIST = Enhanced Intel SpeedStep Technology, so you have it disabled in the BIOS. What I meant to say above is that even though the BIOS doesn't populate the ACPI tables, it leaves the EIST bit enabled in the processor. For EIST to work properly, you need to have the EIST bit enabled in the processor, and also populate the necessary ACPI tables. Without the ACPI tables the operating system (Windows) cannot know how to switch between performance states. In your case the ACPI entries are missing (I guess), but the processor EIST bit is still enabled. It means the processor could switch between EIST states, but without operating system support it will not. So it still means the EIST feature is not utilized, even though the processors "thinks" it is enabled.

I'm not sure why the Event Log shows that info. But AIDA64 detects EIST state using the industry standard method, documented by Intel. It goes via CPU MSR (Model Specific Register) 1A0. I suppose your processor has that bit enabled for some reason, but the BIOS removed the EIST-related ACPI entries to effectively have EIST disabled under Windows. It's a small discrepancy in the BIOS. Of course in an ideal world the BIOS should also take care of disabling the EIST bit in MSR 1A0 Regards, Fiery

Please make sure to use the last, most recent license key we've provided. In case things might get mixed up even by doing so, please drop me a private message and we'll sort it out Thank you for your continuous support.

Thank you. We've started working on adding SAPI support. I'll drop a message into this topic once a new AIDA64 beta with SAPI details is available for download.

Yes, I'm afraid that could be a collision between GameGuard and AIDA64. Have you tried to disable GPU sensor support in AIDA64 / main menu / File / Preferences / Stability? Please note that you need to restart AIDA64 after altering the Stability options, and you need AIDA64 v2.30 (latest version) to use that option. Do you experience similar issues when running other monitoring software like HWMonitor or GPU-Z? Thanks, Fiery

We haven't noticed any such issues on our own GTX680 card, although it's not made by EVGA, but is a Gigabyte GV-N680D5-2GD-B. We also haven't yet received any bug reports about GTX680 cards yet. I'm not sure whether this RSoD is related and limited to EVGA's own GTX680, or is it a ForceWare issue. We have been experiencing weird issues with ForceWare 296.xx drivers on some of our older GeForce test cards, so quite frankly, I wouldn't be surprised if the RSoD would be a ForceWare bug. Especially since AIDA64 reads almost every bit of GPU details and GPU sensor information via ForceWare driver calls on GTX480 and later GeForce video adapters... Please note that you can disable GPU sensor support in AIDA64 latest version (v2.30) in main menu / File / Preferences / Stability. That way you would of course lose GPU sensor readings, but maybe it would help to get rid of the weird RSoD issue, and you could still continue using the other sensor readings offered by AIDA64. BTW, do you have the option nVIDIA GPU SMBus access through nVIDIA ForceWare enabled on the same Stability page in the Preferences? Thanks, Fiery

On several ASRock motherboards there are more fan headers on the motherboard, controller and monitored, than the available sensor chip cooling fan registers. On such motherboards ASRock solved the issue by connecting two fans to a single fan register, using a fan mux switch. That effectively means a 3rd party application can read only one of the fans that are muxed on the fan register. On your particular motherboard there are 7 fans connected to 5 fan registers, hence two fan pairs are muxed. One of them apparently is Chassis Fan 1 which is muxed with Chassis Fan 2. In order to use AIDA64 without starting ASRock Extreme Tuner you will have to connect all fans to a non-muxed fan connector, or use the other member of the muxed pairs. I guess by moving your fan from Chassis Fan 1 connector to Chassis Fan 2 would fix this up in your case. BTW, the other muxed fan pair on your motherboard is CPU Fan 1 and CPU Fan 2, so you gotta be careful about using the fan there. The "safest" fan headers, the ones where you don't have to worry about muxing are Chassis Fan3, SB Fan1 and Power Fan. I hope this helps you to use AIDA64 to its full capabilities without relying on other software Regards, Fiery

It would require a separate hook module for DX9, DX10, DX11, OpenGL, etc. I'm afraid it's simply too much efforts for us this time.

A "key from a friend" usually means a pirate license key. A license that you purchase you wouldn't normally pass on to any friends You don't have to renew your license every year, since the usage period is unlimited. You will however be able to upgrade to new AIDA64 releases only until the maintenance period of your license expires. You can use the last version you are entitled to upgrade to for an unlimited time. The maintenance limit for the base license (which costs USD 39.95) is 12 months. You can purchase a longer, 2-year or 3-year license for USD 59.95 and USD 79.95 respectively. It is recommended to renew your license or purchase a longer maintenance license if you tend to change the hardware in your computer frequently. That way, if you can keep your AIDA64 installation fresh and up-to-date, you can assure it always supports your latest hardware components. Please note that a single AIDA64 license can be used on up to 3 computers by a single person. It means, if you have a desktop computer and a notebook as well, you can use AIDA64 on both computers with the same license key, and you don't have to purchase 2 licenses.

You have an illegal (pirate) license entered. Please consider purchasing a valid license from us, or remove AIDA64 from your computer. Only with a valid (legal) license you can use the fully automated internet update feature. Regards, Fiery

Your license key is written into the PKEY.TXT file. But, please note that at an update both your license and configuration settings (AIDA64.INI file) will be retained. Regards, Fiery

We don't use the Copy Debug Info to Clipboard feature that much. We prefer AIDA64 users to create separate ISA Sensor Dumps and/or SMBus Dumps, and those dumps are not localized. And actually, for us it's not that much of a problem to receive reports, report segments or page dumps in foreign languages. We'll add the requested new line to the language modules

Can you please attach a screen shot that shows what PowerChute detects about your UPS? Alternatively, please let us know the missing value(s), so we can check if they are present in the UPS dump somewhere. Thanks, Fiery

Ours is the regular Asus HD7970-3GD5. I guess the cards you have may have different power circuitry and slightly different VRM design and VRM configuration, but they all have the same VRM chip. We'll try to get a different HD7970 card to see if it has the VRM communication issue.

We'll do more test runs, but so far we haven't been able to reproduce the issue Maybe it's the actual video card model that matters? I mean ours is the Asus HD7970. Maybe your Gigabyte HD7970 produces the issue, but the Asus HD7970 you and us got is trouble-free? Have you done such tests to see if they both act the same when they are in your system as a standalone video card?

I'm afraid we have no plans on FPS monitoring for 2012 Regards, Fiery

1) What kind of SQL server do you use? If it is a Microsoft SQL Server, then please let us know the edition and service pack revision as well. 2) Do you have 32-bit or 64-bit Win7 installations, or mixed? Did they all have SP1 applied? 3) Do you have any special client software or driver (like MySQL Connector/ODBC) installed on your WinXP systems, or Win7 systems, or both kind of systems? 4) If it is a Microsoft SQL Server, then do you use Windows authentication or SQL based authentication or mixed? Thanks, Fiery

Yes, we'll get there, eventually. Please note that we have a tremendous amount of todo's on our table. What you and other AIDA64 users publicly request on this forum is only a part of the "story". Every week we get dozens of requests via other sources like email support and direct correspondance between customers, manufacturers, review site owners, industry professionals, etc. We're also passively present on other forums where people talk about overclocking, tweaking, modding, benchmarking, to see what they say about AIDA64 and other diagnostic software. We gather thoughts, ideas, requests, complaints, bug reports from all sources, and then we have to make a priority order between them. With that I'm not saying that a particular request is less important than another, but based on available development resources, prospected development and testing time, potential customer response, and various other factors, we still have to put some requests ahead of the rest. And quite frankly, the SensorPanel is already too difficult and quirky to be handled by most AIDA64 users. Adding a few more layers wouldn't help about that. We will do that of course, but for example when more users ask us about making the Desktop Gadget feature more advanced than the number of users who asked the same about the SensorPanel meant that we had to deal with the Desktop Gadget improvements first. We expected the SensorPanel -- which was initially requested by quite a few AIDA64 users -- to be a huge hit, but it seems to generate less buzz than the initial number of requests suggested. I'm not saying no gauges or graphs would be implemented in the SensorPanel, but first we may have to rethink the whole SensorPanel feature to make it more user-friendly. We've already added the Simple Sensor Item to help configuring and handling the SensorPanel for less-experienced users, but it only marginally helped. So there's a lot to do around the SensorPanel, and we may have to make radical changes before adding more "juice". I hope you understand that, and give us a bit more time

These days, when CRT monitors are on the verge of extinction, we don't think refresh rate is an information that should be considered for the hardware monitoring module of AIDA64. As for resolution, it is an important information, but I'm not sure why would you want to add that into the G19 LCD? Can you please explain? Maybe you use a dynamic desktop resolution, or control your system remotely via a KVM switch? I'm just asking, because the hardware monitoring module of AIDA64 was designed to gather and display dynamically changing/updated data, like temperatures, fan speeds, CPU load, etc. While the desktop resolution or refresh rate is not something that changes at all. A typical computer user tend to keep the desktop resolution intact for years (especially on LCD monitors), as long as the underlying hardware (video adapter, monitor) is kept the same. Regards, Fiery

We'll check if it's possible to gather such data from Windows. Do you know of any software that can display such information? Thanks, Fiery

Mobile processors generally can stand much higher temperatures than desktop processors. As long as the bottom graph doesn't show any non-zero throttling activity, your processor is feeling fine 90 Celsius is a bit high even for a mobile processor, but please note that what AIDA64 System Stability Test puts on your system is the worst case scenario. Most cases, even when you're running a power demanding task on your system, the overall system stress is still much lower than what AIDA64 System Stability puts on your system. Regards, Fiery

Business Edition is licensed based on the number of computers you have in your enterprise. In case you audit client's PCs, and it's not easy to tell how many computers are there in question, then please make sure to contact our distributor ABSEIRA, explain your situation, and ask them to clarify how many licenses do you need to purchase to cover all your clients' computers. You can contact them at: info AT abseira.com

We've done some test runs today on a similar configuration, but found everything working as expected. The only thing I can think of is reverting back to the original DB - Access.mdb file you can find in AIDA64 installation package. Make sure to verify if there is an Unblock button in the file's Preferences. If there's one, then push the Unblock button.

The new AIDA64 release revamps the Desktop Gadget module, further enhances its Uninterruptible Power Supply and Smart Battery monitoring capabilities, and implements full support for the complete AMD Radeon HD 7000 GPU family and the latest generation Intel SSD drives. New features & improvements - Enhanced UPS support - Revamped Desktop Gadget - Preliminary support for Intel “Haswell” APU and Intel “Lynx Point” PCH - Preliminary support for Intel “Penwell” SoC - Intel 520 and Intel 710 SSD support - GPU details for AMD Radeon HD 7000 Series and nVIDIA GeForce 600 Series [ Press Release ] [ What's new in AIDA64 v2.30 ] [ Download ]