Fiery

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.

We've decided to let the Preferences / Hardware Monitoring / Update Frequency page settings go down to 500 milliseconds in 100 ms steps, so you (and other power users) will not have to deal with .INI file editing and other hurdles Please upgrade to the latest AIDA64 beta release available at: AIDA64 Extreme: http://www.aida64.com/downloads/aida64extremebuild2731phyzl2fjwbzip AIDA64 Engineer: http://www.aida64.com/downloads/aida64engineerbuild2731rvxwfcqtdhzip Let me know how it works for you

Thank you. 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.

Thank you! 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 how it works

Can you please create a photo of the voltage, temperature and fan speed values in the BIOS Setup? It would provide us with a reference, and would help a lot to tune the voltage measurements in AIDA64. Thanks, Fiery

Thank you for letting us know. Quite frankly, we had no idea what could have been wrong. Even with an active iGPU and no video card installed, latency scores aren't supposed to be that high as they were on your system. But I'm glad you managed to resolve it, and now you've got proper scores in AIDA64 benchmarks Regards, Fiery

The FPU subtest of AIDA64 System Stability Test is designed to drive processors to their absolute limits. That's why it uses state-of-the-art techniques like AVX and FMA instructions. Before Haswell hit the market, we considered throttling processors (while running the Stability Test) unstable. However, with Haswell we all simply have to get used to the fact that due to the FIVR (integrated VRM) the CPU can indeed throttle under heavy load, and still work stable. So if you're okay with those high temperatures, or you believe the FPU subtest of the Stability Test is too extreme and wouldn't align with your normal, everyday usage scenario, then just ignore the throttling and use your CPU at 4.7 GHz. However, in case your system turns off due to the high temperature while e.g. running a 3D game, then you should consider improving your system cooling Regards, Fiery

In order to use the low-level features of AIDA64 (like sensor measurements), you need administrator privileges. It is always best to run AIDA64 as the admin user. Your particular usage scenario may not be suitable to launch AIDA64 at startup via its built-in feature. You can try to disable launching AIDA64 at startup in AIDA64 Preferences, and manually create a Scheduled Task to launc AIDA64 at Windows bootup. That way you can select the Windows user to use when launching AIDA64 for example, and enter your user password as well. Regards, Fiery

Thank you, we'll switch the fans in the next AIDA64 beta release. The new readings are: CPU temperature, +3.3V voltage, and iGPU voltage (if iGPU is enabled).