Fiery

I think it is due to a BIOS programming issue. Maybe it programs the measurement unit field incorrectly, and that's why you get too low readings. We'll add OCZ Deneva 2 and Talos 2 SSDs in the next AIDA64 beta release due in a few days

1) What motherboard and CPU do you have? 2) What version of Windows do you have installed? 3) Are the disappearing WDC drives are internal drives or external (e.g. USB) drives? Thanks, Fiery

I'm not sure if the incorrect temperature readings are due to a motherboard failure, a motherboard sensor chip failure, a BIOS issue or a mixup in software/OS installation. And BTW, for such small issue I wouldn't change a motherboard. There are plenty of other sensor readings you can rely on

Thank you for your understanding and your support We try to get more and more AIDA64 users to subscribe to our newsletter -- that is the method to gain access to such special promotions

For some reason, on your motherboard both motherboard and CPU temperature readings are invalid. Even Asus AI Suite reads invalid values (check the Asus ATK0110 section in the dump above). We cannot fix such issues from AIDA64 -- but fortunately you will still have the core temperature readouts to let you track the CPU temperature Regards, Fiery

Go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / OSD / OSD Items, select any of the items (or multiple items using Ctrl key), and press the Configure button. You can change label, font name, font size and font style of any OSD item that way. Regards, Fiery

It could be due to a pecularity of the IMC (integrated memory controller) of your processor. Maybe the benchmark hit a bottleneck, or there's a memory interface instability at DDR3-2400 using the seemingly strict memory timings you've configured. Can you please post a similar screen shot, with the memory running at DDR3-1866? Thanks, Fiery

Steam would be just another platform where you could acquire a license for AIDA64. It doesn't mean the current Online Store would be discontinued

The hardware failure message specifically means the stress testing module detected a CPU processing error. It may be caused by a CPU execution glitch, a cache issue or if something happened while the data "travelled" from the memory into the CPU. It's not easy to diagnose such issues, and I'm afraid it's not possible to be more specific. However, please note that the hardware failure message has nothing to do with the measured thermal state, voltage levels or fan speed status of your system. Those measured values are only shown for you as a reference, and when they go out of a specific range, the test will not stop. The test will only stop if the overall system state becomes so critical that a detectable hardware failure occurs. But even that it quite rare, since most unstable systems would throw a BSoD, freeze, or make an instant system restart when a hardware failure occurs. You can hardly ever see a hardware failure message, since the odds of a single CPU processing error is much lower than such a system stability issue that completely crashes and halts the execution pipeline of the CPU (when the CPU simply resets itself along with a sudden system restart). As for Process Lasso, I'm not sure what exactly does it do that it can manage to interfere with other processes and cause a CPU processing glitch in them, but it sounds quite dangerous, so it would be best if you stayed away from having it running while using the AIDA64 System Stability Test Regards, Fiery

I'm sorry, but we have no plans to offer such added flexibility to the SensorPanel. We've specifically made it possible to use a background image so that you can draw such image that you're looking for, and apply it to the background. I believe by offering something in between the 2 existing SensorPanel background configuration options (solid background color, background image) would be redundant. Regards, Fiery

The 4x6 font used by Rivatuner and Afterburner isn't a real font, but a sort of a hand-drawn emulated font that only supports a single code page and is limited to a fixed set of characters. I'm afraid we currently have no plans to implement such a thing in AIDA64. Regards, Fiery

Please note that if you use the AIDA64 ZIP packages to upgrade or downgrade to another version, then all your existing settings and license files will all be retained. If you however are still unsure about that, then just extract the ZIP content into a new, empty folder, and run AIDA64 from there. But it's still very important to extract the whole ZIP content into a folder, since only that way you can use all capabilities of AIDA64, including e.g. its kernel driver and data files. You can also perform a backup of your existing SensorPanel and OSD settings anytime, if you backup the AIDA64.INI file from your AIDA64 installation folder. As for the GPU stress test... Refinement is of course possible, but it doesn't change the fact that using a GPGPU workload it is only possible to load GPUs in the way AIDA64 currently does. In the future we may come up with another solution that would also stress the primary GPU via an additional Direct3D workload as well, but on iGPU systems like Haswell it wouldn't bring more overall CPU load than the current solution, simply because the way the CPU and iGPU power domains are designed. For example, on high-end Haswell parts you can achieve the highest power draw and highest thermal stress by not using the iGPU at all. So on Haswell it doesn't really matter how the GPU stressing works

Please try it at stock settings, without any overclocking. If it works fine that way, then your system is unstable when you have it overclocked

Please note that upgrading to a new beta release ZIP package should be performed properly, and not just clicking on the AIDA64.EXE icon after opening the ZIP package Open the new beta release ZIP package, and extract its whole content to the existing AIDA64 installation folder. Let it overwrite any existing files. Then restart Windows to make sure that every files got replaced properly. As for the PCIe link state: that is absolutely normal. Modern GPUs save power by switching down their PCIe link rates when they GPU is not under load. As for the GPU stress test: it is also normal AIDA64 utilizes a heavy generic computing (GPGPU) workload via OpenCL. The OpenCL driver of the GPU goes through Direct3D and the video driver, and such heavy workload causes the video driver to become less responsive. Future implementations of HSA and special queuing tricks promise to improve on that issue, but please understand that it's a video driver and OpenCL driver limitation, and so we cannot fix that from AIDA64. As for Furmark: it is true that via Furmark or other full-scene 3D stress testing application you could stress the video card a bit more heavily than with a GPGPU workload. It is due to the fact that a 3D scene uses the GPU computing engine, the shaders, the rastering engine and the video memory in the same time, while a GPGPU workload uses mostly just the computing engine. However, unlike a 3D scene, with a GPGPU stress test you can stress all available GPUs in the system simultaneously, and also you can drive the CPU, caches, system memory and storage devices to their maximum in the same time.

Thank you. The dump looks quite strange to be honest. It looks as if your external drive returns the SMART and ATA ID data of one of your internal drives. Are you sure that with previous AIDA64 releases, the SMART data that was read out was actually for the external drive? Could you please try to downgrade to AIDA64 v3.00 or v3.20, and check the Storage / SMART page? Please check whether you can see similar SMART output for your external drive and one of the other drives, or whether all SMART data is exclusive/unique. Meanwhile, we'll try to get such an external drive that you own to perform test runs on our own. Thanks, Fiery

I think it's best not to believe that only a specific set of companies implemented such backdoors in their software. IMHO all US-based software and web companies were "forced" to do so. Or at least the ones handling a considerable amount of users data. Being it the US Government or other countries' governments, you can be 100% sure that they monitor bad guys (and as a side-effect, good guys as well) with whatever tools and tricks they can get their hands on. It's just a freaky post-2001 world where we have to live in

Thank you, but v4.00.2700 had no fixes related to the system freeze on GCN2 Radeons. The freezing came up very rarely, so it's only a fortunate coincidence that v4.00.2700 "fixed" it on your system And meanwhile we've discovered and fixed another issue that affected all Radeons, and caused a memory leak. So it would be best if you all of you could upgrade to the latest AIDA64 Extreme beta release available at: http://www.aida64.com/downloads/aida64extremebuild2706dylfhkpnzjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

What Windows version do you have installed? BTW, the old topic was about a few occasions when Symantec Endpoint Protection virus database date wasn't properly detected. So instead of showing Endpoint Protection as being up-to-date, AIDA64 incorrectly reported its virus database as being outdated. In your case -- unless I misunderstood your post -- Endpoint Protection database date is detected properly, but AIDA64 fires an alarm about outdated virus database because it also checks Windows Defender database date -- which is indeed outdated. Please let me know if I misunderstood your post Thanks, Fiery

We've finally been able to reproduce and fix the bug that caused a lockup on AMD Bonaire (HD7790, R7 260X) and Hawaii (R9 290, R9 290X) cards, and came up while playing GPU-accelerated media content. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2704v4dpkbg8cxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

We currently have no such plans. Instead, we're pushing it hard to add more and more useful features to AIDA64, to make sure our existing and loyal customers would feel extending their license is justified.

For a mobile computer, at idle, those temperatures are just fine, no need to worry about them. Regards, Fiery

We've just tested it with AIDA64 v4.00, on a Xeon E3-1245 v3 CPU (default clocks, stock settings) in a Supermicro X10SAE motherboard, under Win7 64-bit SP1, and got a minimum of 2.8W reading for CPU Package power. Under heavy load (AIDA64 System Stability Test with only FPU subtest enabled) it went up to 73W. Please try it with AIDA64 v4.00, and let me know if it helps.

The "Initializing page" is a page caption that is hidden on those windows, so it will never appear. We'll remove the caption (set it to an empty string) to avoid confusion. Thanks, Fiery

One of the limitations of the current Intel iGPU solution But they fight it successfully by implementing caches in the iGPU.

We were sort of forced into finding other sources of revenue, due to the shrinking PC market. If we want to keep up the pace of development, to offer more and more features, by keeping up the quality of the software, then we have to make sure our revenue wouldn't shrink along with the PC market. Even with a more and more capable software, it's tough to convince AIDA64 users to acquire a license, and still, after so many years, only a fraction of the users are willing to acquire a license, regardless of the price tag it carries. Hence, we have to use advertising to find other sources of revenue, and that's where Google offers come into play. We've picked Chrome out of the many options simply because we here at FinalWire reckon Chrome is a useful and capable software. I wouldn't wanna name other options, but all of those had annoying features, and generally speaking would have been a much less useful product for the user than Chrome. If you are an existing customer to us, then you have several options to avoid dealing with those ads: 1) You can use the ZIP package instead of the setup package when upgrading to a new AIDA64 version. Only the setup package implements the Google offers. 2) You can use the built-in automatic update feature of AIDA64. It updates itself without you having to download any packages manually, as long as you have a valid license. No downloads, no ads that way. BTW, the Google offers have certain rules to make sure they don't become too annoying for the users. They aren't offered everytime you launch the setup package. I suppose you unchecked the checkbox the first time you've installed AIDA64 v4.00: now try to run the same setup package again, and you'll see that the offer will not come up anymore And even at the next AIDA64 release the offers will not come up on your system again. Regards, Fiery