Fiery

Thank you for the feedback

The ATA spec treats the ECC bytes field obsolete for over 15 years now, so it's not since the previous spec release

Thank you for the feedback

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

We've done a few test runs with various GeForce cards, and it seems GPU clock gets stuck at 3D rates only when you keep the AIDA64 System Stability Test running and just untick the GPU subtest. That keeps the OpenCL context still open, although not executing any OpenCL kernels (computing tasks). In such case ForceWare keeps the GPU running at high clock speeds for whatever reason, and only lets the clocks drop down to power saving (low) rates when you press the Stop button on the System Stability Test window. That's because when you push the Stop button, AIDA64 closes and invalidates the OpenCL context. While AMD Catalyst drivers vary GPU clocks based on actual GPU load (utilization), ForceWare drivers seem to work based on OpenCL/Direct3D/OpenGL contexts. That's just a different approach, although quite frankly we would prefer to have drivers all work by GPU utilization

AIDA64 isn't really geared towards making an inventory of special networked devices like TVs, amplifiers or DVD/Blu-ray players. We may work on that later on, but it's not on our short-term roadmap right now. Regards, Fiery

Thank you for your kind words. We keep optimizing and improving the G19 support, so make sure to use AIDA64 v4.00 (latest release), where it consumes less CPU cycles to refresh/update the G19 screen. Regards, Fiery

I suppose you mean the Used Video Memory and Free Video Memory hardware monitoring items. Yes, they're available on e.g. the OSD Panel, but those items aren't available on a per-GPU basis, and they're only available on nVIDIA GPUs. Those items should be there on your 750M as well, as long as ForceWare is properly installed.

It seems the latest ATA specification (and a few preceding revisions as well) treats the ECC bytes register field as obsolete. We'll remove that information from AIDA64 to avoid confusion. Thanks, Fiery

Since Vista Windows virtualizes video memory spaces, so it's not possible to detect or measure free video memory size. It is still available under old Windows releases (Windows XP, Windows Server 2003 and Windows 2000). Regards, Fiery

You can use ALT+T to stop the test Regards, Fiery

1) The email you've got back in December stated that the renewal discount is only valid until December 31, 2013 2) Our online sales are handled by cleverbridge AG, so I'm afraid you can only pick from their payment options. Most of our customers prefer PayPal, maybe you've got an account there? Regards, Fiery

On the System Stability Test window there's a tab called Statistics. That records the minimum and maximum temperatures. While running a game, you can record minimum and maximum values by enabling Logging (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging). Regards, Fiery

I'm pretty sure it's the fan that has a faulty bearing or some other issue. You have to have the fan replaced to make the noise go away. Since your computer seems to be quite modern, it may still be under warranty. Try to ask the shop about the issue, they may have already found similar issues with notebooks like yours. Regards, Fiery

I'm sorry, but not yet. We have frozen the development of the native 64-bit binary, and will only continue working on it later this year or sometime next year.

Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2731phyzl2fjwbzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

AIDA64 doesn't alter the P-States (Performance States) configuration of the video driver or the video card itself, so if the clock gets stuck, it is the fault of the video driver (ForceWare). Regards, Fiery

The SST window expects the actual stress testing thread to either quit (because it reports that a hardware error detected, or because the test was stopped by the user) or cause a system malfunction (BSoD, lockup, system restart). Currently there's no facility in AIDA64 to watch the stress testing thread and stop the test if it crashes. The SST window however should report that in the log listview as "Stability Test: Failed". As for logging, you can activate that in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging. If you select the log items for CPU utilization, then you can see when the stress testing thread crashed or stopped.

The FPU test puts a very heavy stress on the processor, both load-wise and thermal-wise. It is a very unique test in a sense that not many other stress tests or applications are capable of pushing your processor that far -- using AVX, AVX2 and FMA instructions indeed helps AIDA64 to achieve that level of stressing. Whether you deem it is useful for your particular usage scenario or not is completely up to you to decide If you use AIDA64 to measure your temperatures while running applications or games, and you can see much lower temperatures than what you did while running the AIDA64 FPU stress test, then you may have some headroom in upping the CPU clock and/or voltage. BTW, since only a handful of applications and benchmark software currently utilize AVX2 and FMA instructions, it is not easy to compare the amount of stress AIDA64 puts on your Haswell processor at this time. But as soon as the new instruction sets become more popular, and software vendors keep pushing their optimization efforts even further, you will be able to see very heavy load being put on your processor while e.g. encoding a video stream. So in our opinion AIDA64 FPU stress test is very much relevant, since it faces your CPU with the worst case scenario imaginable. If it can stand that, then it's a good configuration (ie. both hardware and software settings are proper). Regards, Fiery

In case the crashes occur not just with AIDA64, but while running other software as well, then your system may have stability issues that you need to diagnose.

Try to delete the icon on your Windows Desktop, restart Windows, and manually create a shortcut for the AIDA64.EXE file by right-clicking on the file in Windows Explorer --> Send To --> Desktop (create shortcut). Regards, Fiery

Such thing might happen when the SST thread crashes due to system instability. In case it doesn't happen when you slightly loosen on the overclock settings, then it is definitely the fault of the hardware Regards, Fiery

In which module of AIDA64 do you see the Fahrenheit option having no effect? On the Computer / Sensor page? Or the OSD Panel? Or the Desktop Gadget? Thanks, Fiery

Thank you for the feedback, I'm glad it works flawlessly on your motherboard now Have a very Happy Xmas and a Great Prosperous New Year!

Thank you for the feedback! +1.2V was an invalid reading previously, so we've removed it.