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

AIDA64 Business shouldn't be updated without the administrator's intervention, because upgrading to a newer versoin may affect the whole network audit infrastructure built around AIDA64. The upgrade process should always be done by the admin, who can QC the new AIDA64 update, to make sure it is flawless. For this purpose alone, most AIDA64 Business customers rarely upgrade to new releases, and they tend to skip all beta updates as well. And when they do upgrade, they prefer to perform the upgrade on their own computer, to let them check the new version out before rolling it out to the whole corporate network. We will definitely need to improve the new way of handling AIDA64 Business downloads, and will of course incorporate your insights to make sure you can access the new download packages as easily as possible. The whole "request a trial" procedure was designed for new visitors, who will try AIDA64 Business for the first time. We'll make sure the system is also useful for returning visitors and existing customers. As soon as new features and improvements are available, Mice007 will let you know here in this topic about it

1) Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> ATA Dump. Copy-paste the full results into this topic. 2) Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic. 3) Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic. Make sure to use AIDA64 v4.00 to create those dumps. Alternatively, instead of copy-pasting the texts, you can attach the TXT files to your forum post. Thank you in advance

When you've got an AIDA64 Business installed on your system, and you've got a valid license, then you can use the automatic update facility to upgrade to new releases. You don't need to deal with ZIP file downloads or upgrade process at all. Same applies to other AIDA64 editions, of course. As long as you've got a valid license, upgrading to new versions is done automatically.

From AIDA64 v4.00, the Business edition is no longer available as a direct download. Instead, we ask you and other users interested in our business products to request a 30-day test license at: http://www.aida64.com/request-trial Regards, Fiery

The new AIDA64 release introduces a complete set of multi-threaded OpenCL GPGPU benchmarks to measure computing performance of modern graphics processors and APUs. The latest AIDA64 update also implements optimized benchmarks for AMD "Kaveri" and Intel "Bay Trail" processors, and supports the latest AMD Radeon and nVIDIA GeForce graphics accelerators. New features & improvements OpenCL GPGPU Benchmark Suite Optimized 64-bit benchmarks for AMD "Kaveri" and "Bald Eagle" APUs Razer SwitchBlade LCD support Optimized benchmarks for Intel "Bay Trail" SoC Improved support for Intel Atom C2000 "Avoton" and "Rangeley" SoC Preliminary support for Intel Quark X1000 "Clanton" SoC Improved support for OpenCL 2.0 Support for VirtualBox v4.3 and VMware Workstation v10 OCZ Vector 150 and Samsung XP941 SSD support GPU details for AMD Radeon R5, R7, R9 Series GPU details for nVIDIA GeForce GTX 760 Ti and GeForce GTX 780 Ti [ Press Release (English) ] [ What's new in AIDA64 v4.00 ] [ Download ]

I'm glad I could help Regards, Fiery

I'm sorry to hear about your issues. Please note that you're not alone: we've already received 2 other bug reports that seem to be related to your issue. The common component of the 3 PC configurations in question is that they all have a Radeon video adapter. It seems the issue may be related to hardware video playback acceleration, since the other 2 bug reports specifically stated that the system lockup only comes up while watching Flash videos using hw acceleration provided by AMD Catalyst drivers. One of the persons facing this issue have tried it with different Windows versions, and with different Catalyst versions, but it didn't make a difference. And since the other person mentioned that GPU-Z also causes a lockup sometimes, and you mentioned that HWiNFO also causes the same lockup, the conclusion could be that the lockup must come up when measuring or detecting a certain property related to Radeon GPUs, such as GPU utilization, GPU clock rate, etc. What we've tried here in our labs, on our own Radeon video adapters, is installing Win7 64-bit, Win8 64-bit and Win8.1 64-bit, with a few Catalyst releases, and installed various Radeon GPUs like HD 7790, Kabini (iGPU), Richland (iGPU), R9 290X, HD 7970 in various Intel and AMD chipset based motherboards. We've tried to play Flash videos and HTML5 based videos using Youtube, tried to play 720p and 1080p MKV videos, but no matter what we've tried, we couldn't reproduce the lockup And since a lot of guys own a Radeon video card, and most of them watch videos from time to time, the rarity of the lockup makes us believe that either another hardware component or a special system setting may be behind of the issues. Maybe multiple system properties had to be polled together to make the video driver go crazy or such. It's not easy to come up with more specific ideas than that What I can ask you to try, while not being able to reproducing the bug here is the followings: 1) Try to disable as many items on the OSD Panel as possible. As a try, just leave the GPU clock there, and see if it makes a difference. Then try to enable only the GPU Diode temperature, and see if it helps. 2) If the previous tries don't make a difference, then try to leave everything enabled on the OSD Panel, but disable the GPU items in the System category (like GPU Clock, GPU Memory Clock, etc). Right-click on the bottom status bar of AIDA64 main window --> HWMon Modules --> GPU. That will effectively disable the complete GPU temperature+voltage+fan monitoring facility of AIDA64, but will leave the generic GPU detection module active. Try to start a video and see if the lockup happens or not. 3) Do the same as in #2, but now enable the GPU Clock monitoring among the OSD items. Those tests may lead to a conclusion about whether GPU clock monitoring or the GPU sensor module causes the lockup. Thank you for your time Regards, Fiery