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

It will cause some swapping, but it is only a problem if you use a SSD. If you want to avoid swapping, then just use 512 MB per thread.

It's best to use as many RAM as possible. Just set it to 1 GB per thread for a total of 8 GB system memory. Regards, Fiery

Thank you. It seems your fans are connected to the IPMI BMC chip, instead of the onboard Nuvoton Super IO & sensor chip, so you can see the measured fan RPM values on the Computer / IPMI page instead of the Computer / Sensor page.

Thank you for the feedback

Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2656b7hl0kzgtszip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If the problems persists, then please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic.

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

Currently it's not supported in AIDA64. For each process running, what property (or properties) would you like to see on the SensorPanel? CPU utilization? Memory utilization? Handles count? Threads count? Something else than those? Thanks, Fiery

It may happen when the stress test process crashes, without providing any feedback to the System Stability Test window. Is your computer overclocked or specially tuned?

Maintaining a list of reference systems could be problemous, because unlike classic x86/x64 CPU and FPU benchmarks, results of OpenCL benchmarks heavily depend on the software environment. OpenCL benchmark results may vary between video driver updates, may change when you go from Windows 8 to Windows 8.1, etc.

Only Gigabyte knows the answer to that

Thank you, the issue will be fixed in the next AIDA64 beta release.

In Windows 8.1 DPI scaling has been revamped one more time (after revamping it in Vista, and then again in Win8). It seems the new interface doesn't provide meaningful values, or at least we haven't yet figured out which API call to use to detect the native resolution of the display. We'll do our best, but we eventually may be forced to simply drop the idea of detecting native resolution, and simply use the logical resolution setting Windows provides via standard API calls. You can always check the native resolution of your monitors on the Display / Monitor page

Here's another new AIDA64 beta update that further improves the new GPGPU Benchmark Panel layout and handling: http://www.aida64.com/downloads/aida64extremebuild2656b7hl0kzgtszip

No, I'm afraid AIDA64 is designed in a way that it shouldn't leave any files behind, except for its configuration files (like AIDA64.INI, AIDA64.SST.INI). It doesn't automatically save a report of your system configuration. Regards, Fiery

The easiest way is to backup the file called AIDA64.INI that you can find in the installation folder of AIDA64. Alternatively, you can export your SensorPanel settings into a SensorPanel configuration file by right-clicking on the SensorPanel --> SensorPanel Manager --> Export (button). Please note that only AIDA64 v3.20 is fully compatible with Windows 8.1. If you use AIDA64 v3.00 or older versions under Windows 8.1, not all features will be available due to Windows 8.1 blocking the kernel driver of older AIDA64 releases due to compatibility issues. Regards, Fiery

I'm afraid that information is only available under Windows XP. You can see that on the Storage / Windows Storage page there. Regards, Fiery

Here's a new AIDA64 beta update that further improves the new GPGPU Benchmark Panel layout and handling: http://www.aida64.com/downloads/aida64extremebuild2651ztbq8cv4pfzip

If you don't have AI Suite installed, and you're sure all its remaining components (services) are removed properly, then you should disable ATKEX support. But please note that AI Suite tends to leave its components installed and running in the background, even after you've uninstalled it