Fiery

We've fixed the RSoD issue in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1911np6gm0bjczzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Meanwhile we've performed a few test runs with various RAID settings and configuration on our own X79 test system. With RST Enterprise 3.0.0.3020 WHQL driver AIDA64 startup is indeed noticably slow, although the delays we've experienced were no longer than 5 seconds. With RST Enterprise 3.0.1.7016 WHQL driver AIDA64 startup was much quicker, with no noticable delays due to RAID scanning. So if it's possible, please use the latest RSTe WHQL driver of 3.0.1.7016. Hopefully it fixes the issues on your system. If not, then you can still disable the RAID member enumeration in the AIDA64 Preferences

Please try to enable the option RAID SMART support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it helps. If not, then please let us know more about your system configuration, e.g. motherboard model, IDE or AHCI or RAID mode selected for your SATA controller, any RAID arrays defined, AIDA64 version? Thanks, Fiery

Thank you for the tests. If you don't plan to use RAID arrays in your system, then you can simply disable RAID member enumeration in AIDA64 / main menu / File / Preferences / Stability. In case you cannot get AIDA64 to load due to this issue, then go to AIDA64 installation folder, and create a new AIDA64.INI file by writing only these 3 lines into it: [Generic] LowLevelRAIDEnum=0 LowLevelRAIDSMART=0 BTW, since at Intel RAID scanning we're doing everything "by the book", and full SMART details are unavailable even when it loads up fine, all we can hope for is that Intel will soon release a proper, fixed RST Enterprise driver. BTW #2, have you tried to use the latest Intel RST Enterprise driver 3.0.1.7016 WHQL? Maybe it would help about the slowdown. --- As for the quad-channel memory bandwidth results, they are actually accurate. The single-threaded memory bandwidth performance -- that AIDA64 currently measures -- doesn't scale when going from 2-channel to 4-channel configuration on X79 systems. We're already working on multi-threaded memory bandwidth benchmarks: they will be able to properly measure the performance improvement due to 3+ memory channels. Regards, Fiery

Rampage IV Extreme uses a peculiar bank switching mechanism on its EC (Embedded Controller) chip. Due to the collision between AI Suite 2 and 3rd party applications, potentially it would be dangerous to switch EC banks from AIDA64. Hence AIDA64 only reads the sensor values available in the default EC bank (which is bank #0).

AIDA64 still implements full support for Win95/98/Me and Windows NT 4.0. It has a Win2000 icons style which has 16-colour icons as well as 256-colour icons. We consider that a pretty solid support for those obsolete operating systems. Please note that the combined percentage of Win95 + Win98 + WinMe + NT4.0 users out of the total AIDA64 users base is less than 0.01%. It means we cannot afford to put more development resources into such obsolete systems, but instead we need to focus on the current Windows variants, and for the upcoming Windows 8 and Windows Server 8. Regards, Fiery

Thank you for the feedback. We have a product cycle that dictates 5 or 6 stable releases per year. The next stable releases is currently scheduled to mid- or late May.

I'm sorry for the mixup. Here's a new AIDA64 Business Edition beta update: http://www.aida64.com/downloads/aida64businessbuild1907d3cjh4swzlzip

Thank you for the feedback

That issue has already been resolved in the latest AIDA64 release: http://www.aida64.com/downloads/a64xe After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

What version of AIDA64 are you using? Thanks, Fiery

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1906y8rltnhfczzip 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/aida64extremebuild1906y8rltnhfczzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

1) Do you have AIDA64 running on your remote computer(s) and accepting incoming connections? 2) You need to use the /R option to create a report of your local computer. To create a report of one or more remote computers, you need to use the /RMTREPORT command-line option instead. Regards, Fiery

No problem

Please note that that only applies to pre-Fermi (pre-GTX480) cards. On Fermi and Kepler architecture cards (GeForce 400, 500, 600 Series) it is recommended to leave the nVIDIA GPU SMBus access through nVIDIA ForceWare option enabled, since it should guarantee that no collision occurs with other software reading GPU sensor information.

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.