Fiery

We've just made the new GPU stress testing feature public in the following AIDA64 beta release: http://www.aida64.co...14gcn7wyrhdzzip It can be used to put stress on one or more GPUs in the system, by utilizing the GPGPU computation capabilities of OpenCL API. A couple of things to note about this new feature: 1) First of all, it is in a beta stage right now. We'd like to hear your feedbacks about it, and collect any improvement ideas. We will only roll out this new feature in an AIDA64 stable release in the first half of 2012. This feature will be disabled in any upcoming new stable releases of AIDA64 that will be rolled out in 2011. 2) Even this first public beta is capable of putting computation threads on multiple GPUs; supports CrossFireX, SLI and AMD DualGraphics configurations; supports mixed GPU configurations (one ore more nVIDIA GPUs + one or more AMD GPUs) under Windows 7; and of course it supports AMD APUs (Llano, Brazos, Trinity) as well. Putting stress simultaneously on an APU and one ore more discrete GPUs is also supported. OpenCL-capable IGP chips and mobile GPUs are supported. Multi-GPU video cards (e.g. GeForce GTX 590 and Radeon HD 6990) are supported. 3) Any OpenCL devices can be stressed, but right now it's not possible to select which devices to stress. Hence all GPU-type OpenCL devices that can be found in the system will be stressed simultaneously. 4) CPU-type OpenCL devices are not supported. We don't plan to support them, since for CPU stressing we have our own solution, the usual 64-bit System Stability Test module. 5) You can check the list of available OpenCL-capable devices on the Display / GPGPU page in AIDA64. All GPU-type devices listed there will be stressed by the AIDA64 System Stability Test. 6) Due to the way GPGPU implementations work, stressing the GPU also puts stress on other system components, e.g. system memory, CPU caches, CPU cores, and PCI Express links. Hence it's normal to have considerable CPU utilization while running the GPU stress test, even when CPU and FPU tasks are not enabled on the System Stability Test interface. 7) Due to OpenCL not being capable of providing a device utilization measurement, AIDA64 System Stability Test is not able to show the GPU load% while the stress test is running. It is however possible to check the GPU load in other places in AIDA64, e.g. on the Display / GPU page, or on the OSD Panel or SensorPanel. 8) We currently have no plans about supporting other GPGPU layers (e.g. CUDA, Stream, Direct3D CS) for GPU stressing purposes. 9) The current GPU stress module doesn't implement error-checking or results validation, hence any computation issues or glitches will not be detected or reported. 10) On old nVIDIA MCP chips (e.g. MCP73) the current GPU stress test may not work properly. We suspect it is due to a ForceWare driver bug or improper OpenCL support in ForceWare drivers. We'll investigate this issue later this year. Please let us know what do you think about this new feature, and what improvements would you like to see about it. Thanks, Fiery

AIDA64 already implements Areca RAID support, but it may or may not work with the latest Areca controllers. We have plans to improve the Areca and LSI RAID module of AIDA64 next year. Regards, Fiery

The SensorPanel Manager window should already remember its last window position. Isn't that the case on your system? BTW, the bar frame colour configuration on multiple items will be fixed in the next AIDA64 beta release due sometime later this week.

No, I haven't. I wrote above: "In the next AIDA64 beta we'll widen the bar limit fields to 6 characters." That will extend the maximum limit value to 999999 KB/sec. We'll check that, thanks!

In the next AIDA64 beta we'll widen the bar limit fields to 6 characters. As for the alignment, you can sort of do it now, although it's a bit tricky If you select Embedded as bar place, then: 1) If you have both the value and unit enabled, then you can increase the width of the unit to move the text to the center of the bar (horizontally). 2) If you only have the value enabled (and the unit disabled), then you can benefit from an irregular configuration of adjusting the total item width to a much lower value than the bar width. So if you have e.g. a 300-pixel wide bar, try to set the item width to 150 pixels only. It will effectively move the text to the center of the bar (horizontally). I know these aren't perfect solutions, but you may be able to attain a better SensorPanel layout before we can implement a more advanced alignment configuration. As for the new bar styles, we do have plans about them

Yes, GPU-Z can do it, but we have no idea how it does it. We thought it does it via ADL, but it's not the case. We'll try to research more, but I can't promise anything at this time

AIDA64 is still capable of monitoring such voltages, but please note that not all motherboards are capable of monitoring such voltage rails. Or maybe you mean the BIOS Settings section of the Motherboard / BIOS page? It should still be there, although please note that BIOS Settings cannot be detected on all motherboards, but only on Asus motherboards and on ones that supports Intel XTU. Regards, Fiery

I'm afraid AIDA64 can only write the real clock to the Registry.

Please drop a message at our reseller ABSEIRA about this matter: info AT abseira.com (replace AT with @) BTW, the minimum package is 5 licenses for Business Edition, for US$79.95. Regards, Fiery

AFAIK there's no way to check the status of a HDD The best solution would be if HDD manufacturers made it possible to read SMART attributes (incl. disk temperature attribute) while the drive platters are not spinning. Technically, it would be possible, but no HDD manufacturer makes that possible

You need to raise the Disk temperature polling frequency in AIDA64 / main menu / File / Preferences / Hardware Monitoring to avoid AIDA64 keeping the drives awake. Regards, Fiery

The effective frequency for the current (actual) memory clock is displayed on the Display / GPU page.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. Based on the dump we can check what's wrong with the DIMM TS sensor module of AIDA64 and fix it up Thanks, Fiery

I'm afraid I cannot promise anything, since ASRock's fan mux solution is quite peculiar and tough to handle from 3rd party applications like AIDA64

I guess the difference come from the fact that AIDA64 displays the real clocks for DDR memories, not the effective clock. DDR(1), DDR2 and DDR3 memories run at half the advertised frequency, so e.g. a DDR3-1600 module is actually running at 800 MHz real clock. DDR4 and DDR5 modules run at quarter the advertised frequency, so e.g. a DDR5-3200 module is actually running at 800 MHz real clock. Regards, Fiery

Our reseller ABSEIRA will contact you shortly about this. Regards, Fiery

I guess 3-pin would be better, although we don't have first-hand experiences on 7-Volt fans.

Thank you for the screen shots. Discharge Rate is only available when the UPS switches to DC power. We'll check if it's possible to measure the power draw via Smart Battery API calls.

I've posted a reply to your other topic. Please avoid starting multiple topics for the same issue. This topic closed.

On Radeon video adapters AIDA64 can measure video memory utilization only under Windows XP. Do you have Windows XP on both your machines? Thanks, Fiery

It's not possible to reset your trial period, but you can request our Sales Department (sales AT aida64.com) to create a 30-day license for you that you can use to fully evaluate AIDA64. In your email to the Sales Department please specify the product you're interested in (AIDA64 Business Edition or AIDA64 Extreme Edition), your name, and your email address. BTW, you may need to enable RAID SMART support in AIDA64 / main menu / File / Preferences / Stability (and restart AIDA64) to activate disk drive temperature monitoring on your system. Regards, Fiery

We'll work on it Do you mean the Discharge Rate that is already reported in AIDA64 / Computer / Power Management page? If you mean something else, then please show us on a SIW screen shot if possible

I'm sorry, but we don't plan to implement FPS monitoring anytime soon. As for the rest (like Winamp, Skype, Media Player) I believe they're out of the scope of our software. Winamp, Skype and other 3rd party software should implement built-in support for G15/G19 LCD, or Logitech itself should provide a plugin in the Logitech G-Series LCD driver package. In fact, as far as I know, Logitech already provides support for at least Winamp, indicating the place in the song playing. Regards, Fiery

Maybe it was due to some other BIOS settings caused either EIST, C1E or C-States to become enabled without you actually enabling it. As for the gadget issue. Please explain it in more details. Do you use the Sidebar Gadget feature of AIDA64, or the SensorPanel? Does the whole gadget/window disappear, or it just stops listing the values? Thanks, Fiery

Thank you for posting that