Fiery

Thanks. Maybe a long shot, but can you please try the following: 1) Disable Turbo Boost (you can do it in AIDA64 / CPU Tweakings, I'm sure you know where to find that ), and check if it makes any difference. 2) If #1 doesn't make a difference, then please try to run AIDA64, and manually adjust the CPU affinity (using Task Manager), and so lock AIDA64 to the 2nd logical processor, then the 3rd logical processor. Please let us know if it makes any difference. Thanks, Fiery

It will stop working one year after the free license was created. Yes, you do. A full purchased license of AIDA64 can be used perpetually. It will not expire at all. The only thing that will expire is the support & updates (maintenance) period, but you will only notice that if you try to upgrade to a new AIDA64 version that your license doesn't permit. If you don't upgrade to a newer version after the maintenance period is expired, AIDA64 will keep working with its full functionality.

Yes, that's how we imagine it. The user can choose whether to use the classic Win2000 icons, the XP-style icons, or the Win7-style icons. Currently only the first two are supported.

1) What processor is it? 2) Do you have C1E or SpeedStep enabled? 3) Do you have Turbo Boost enabled (if your CPU is Turbo-capable)? Thanks, Fiery

Generally speaking, write benchmark tests shall not be used on SSD drives, unless the measurements are done for specific purposes like it is for a hardware review article, or there's a suspicion about hardware malfunctioning. Linear Write fills the whole disk space once, so unless it is performed in loop mode, it's nothing critical for a SSD, since it only writes every flash memory block just once. The Buffered Write test however constantly writes the beginning first few sectors of the SSD "surface", so it shall not be used on flash memory based devices at all, unless it's absolutely necessary. Random Write and Average Write Access tests write random sectors on the SSD "surface", so they are not much harmful, unless of course you use them a lot, or if you use loop mode and let it go "all night long" We'll add a special warning for the Buffered Write test, specifically about SSD drives, so it would strongly advise against using that particular test on SSD drives. Thanks, Fiery

Yes, our beta releases are just as stable and high quality as our stable releases. Of course, from time to time slight issues may slip in a beta, but they usually only affect a single piece of hardware or a very small group of users. Regards, Fiery

The only way to verify if it is a correct value is by checking it a couple of times a day. If it always shows the same degrees Celsius value, then it is stuck and so it doesn't report a valid value. At least 1-2 Celsius variation should be shown.

It looks quite cool (the opposite of hot) to me, so it's fine Anything under 60-70 Celsius should be considered normal temperature for a SSD.

It means the Retired Block Count data is non-zero. It doesn't mean there's anything wrong with the SSD, but from time to time it's advisable to watch if that data grows, and how rapidly is it growing. Regards, Fiery

As far as we know, Corsair Dominator modules do not feature DIMM TS chip yet.

Thank you for the dump. I'm sorry, but I cannot see any DIMM TS (Thermal Sensor) capable memory modules in your system. Are you sure your memory modules implement a thermal sensor chip? If yes, then do you have any software that is capable of measuring temperatures of your memory modules? Thanks, Fiery

We cannot publish all information in details at this early stage. Currently, our release schedule puts AIDA64 v2.00 later this year, probably in early December, with a brand new hardware monitoring visual panel implemented, sort of an "OSD on steroids". AIDA64 v3.00 will only come in 2011, probably in Q2 (April or May). We plan to implement e.g. OpenCL benchmarks and OpenCL System Stability Test in 2011, most likely by v3.00 release. Between those cornerstone releases, we will release at least 2 or 3 stable updates, where we implement support for the latest hardware components (video cards, motherboards, processors, SSD drives, etc) released between the major updates. We are also in the process of implementing Intel AVX support in our memory and FPU benchmarks, to optimize them for the upcoming Intel "Sandy Bridge" processor. However, the unveiling of the AVX-optimized benchmarks depends on Intel's release schedule of their new processors based on the "Sandy Bridge" core.

Obtaining the 32x32 icons is not a problem, but as you can see, AIDA64 uses 16x16 icons e.g. in the page menu on the left of its user interface, and also in MHTML reports and on most information pages as well. But since we'll implement Win7 icons as an option, if someone doesn't like how they look, he can revert back to WinXP-style icons.

Currently AIDA64 supports the following DIMM TS manufacturer IDs: 001F 0054 00B3 104A 1131 1B09 In case you have a memory module that is not supported yet, then please start AIDA64, right-click on the bottom status bar of its main window --> Sensor Debug --> SMBus Dump (Full). And copy-paste the full results into this topic. Based on that output we can add new DIMM TS manufacturers to AIDA64. Regards, Fiery

Thanks for the feedback

As our Terms and conditions state at ... http://www.aida64.com/free-upgrade-aida64 ... we provide an AIDA64 license free of charge with a 12 months expiry. So the AIDA64 license you got today can be used until October 10, 2011. However, the license can be used only for AIDA64 v1.00. If in the future you find e.g. AIDA64 v2.00 or AIDA64 v3.00 appealing, and you will wish to upgrade to it, then you will need to buy a full new AIDA64 license to upgrade from AIDA64 v1.00 to a new version of it. We don't clone the EVEREST license, and we don't provide an AIDA64 license with the same limitations. We only provide a chance now to switch to AIDA64 free of charge, because AIDA64 is the future, and we want to give EVEREST customers a chance to benefit from the new features of AIDA64. This is not a "one-way street", you can switch back to EVEREST if you want, since your purchased EVEREST license is retained even after acquiring a free AIDA64 license. I hope this clarifies it Regards, Fiery

Thank you. Please clarify: you can see all 6 disk drives listed properly on the Storage / ATA page in AIDA64, but you cannot see either one of them on the Storage / SMART page? If that's the case, then please try to run HD Sentinel, and check if it can provide SMART data for your drives, or not: http://www.hdsentinel.com Thanks, Fiery

1) Do you experience the same lockup on other systems as well, or it only happens on this particular notebook? 2) Does the lockup happen when you go to the following AIDA64 pages in the left page menu? - Computer / Summary - Computer / Sensor - Motherboard / CPU - Motherboard / SPD - Motherboard / Chipset - Display / GPU Please let us know which page(s) cause a similar lockup. We need to narrow it down to a specific module of AIDA64, so we can start investigating from there. Thanks, Fiery

Thank you for you comments Quite frankly, we didn't implement Windows 7 icons, because in most cases AIDA64 displays icons in their 16x16 pixel version, and in 16x16 most Windows 7 icons look a bit pale (all gray and blue) and too similar to each other. We find Windows 2000 and Windows XP icons easier to identify, and more colorful, especially in 16x16 version. We wanted to wait until someone asks for Win7 icons, but now that you have, we may give this another thought As an optional feature it may work out well. I'll let you know in this topic when we implemented this feature. Regards, Fiery

Thank you. I can see three 1.5TB WD drives, and three 2TB WD drives there. Can you please clarify what drives do you have in your system, and how are they organized into RAID array(s), and if there're separate, individual drives as well?

AIDA64 is named that way, because the performance-oriented modules (the benchmarks and the System Stability Test) are ported to native 64-bit (x86-64), and it also has a 64-bit kernel driver to perform low-level hardware access. AIDA64 benefits from 64-bit x86 extensions where the difference between 64-bit and 32-bit really matters. The main module, the application itself (AIDA64.EXE) is still 32-bit, but since the beauty of x86-64 capable processors is that they provide virtually no performance hit from running 32-bit applications under 64-bit operating systems, this is not really an issue or drawback. This way, compatibility with legacy (32-bit only) processors and legacy (32-bit) Windows installations is fully retained. Regards, Fiery

It is still fully supported. You need to enable the Sidebar support in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Vista Sidebar. Then you need to add the AIDA64 Gadget to your Sidebar (Vista) or Desktop (Win7) manually. Regards, Fiery

Thanks. Please start AIDA64, right-click on the bottom status bar of its main window --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic. Maybe we already have a RAID member enumeration method that can be used for this controller as well Thanks, Fiery

Thanks! That looks identical to our TMS-200 test device. Have you tried closing the TMS application? Unfortunately the hardware implementation of TMS-200 doesn't provide a way for 2 (or more) applications to access the TMS-200 device simultaneously

Thank you And in the future please feel free to use this forum (or our Support Ticket System) to submit your questions or potential bug reports to us.