Fiery

Meanwhile, we've fine-tuned a few bits about your devices, so please try the latest AIDA64 Extreme beta available at: http://www.aida64.com/downloads/latesta64xebeta Let me know if there're still items missing. If that's the case, then please submit a new Aquaero dump Thank you. (We're still waiting for Aqua Computer's response, so that's why things may still be missing or inaccurate)

That's an interesting idea indeed. We however currently have a lot of other things on the table, so I cannot promise anything about this particular feature request. Regards, Fiery

Yes, that should already work.

Those issues are due to bugs in the Strike7 SDK or driver. Please report them to Mad Catz, and hopefully they will fix it up.

You've already got some decent scores there. Usually, the way to improve the scores is using more agressive memory timings, and/or increasing the memory clock, and/or increasing the CPU core clock, and/or increasing the uncore (integrated memory controller block of the CPU) clock.

Please post a screen shot of the benchmark result for both machines, for both AES and PhotoWorxx. We would like to check what the status bar of AIDA64 main window indicates about the benchmark method used, and the TSC frequency measured. Please also post a shot of the Cache & Memory Benchmark panel results. FYI, memory and cache performance have a big impact on the PhotoWorxx scores, so it would be useful to see if the memory subsystem performs on your Broadwell as expected. Also, on the 5010U system, right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic. If you prefer to communicate in email, or share screen shots only in email, please send me your email address in private message.

It's not easy to directly compare those processors, since the 5010U runs at 300 MHz lower base frequency than the 3110M, and also has a much lower TDP. BTW, are you using AIDA64 v5.00? (latest version) Regards, Fiery

AlphaCool LCD support requires the AlphaCool LibUSB drivers to be installed. Just install the AlphaCool software bundle, and it should install the driver too.

Thank you for the feedback. The indexing issue is because your CPU may support up to 3 DIMM slots per memory channel

Please find the mentioned update to AIDA64 Extreme at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

If the mentioned device is connected to a fan header, and AIDA64 can measure it as a regular fan, then no conversion is possible. However, in case you connect it to a device that can measure it directly as a flow meter (in LPH), then we can display that natively, using LPH measurement unit.

Thank you, we'll fix that issue in the next AIDA64 beta update due in a few days from now. Regards, Fiery

In order to achieve a sort of a lifetime license, it is already possible to purchase a 3-year license and extend it with 3 more years by renewing it before the initial 3 years expires. I know that it's not exactly a lifetime, since it's "only" 6 years, but if you consider how much technology evolves in 6 years ... who knows, maybe in 2021 there will be no PC or Windows PC anymore, or you won't be interested in dealing with AIDA64 anymore 6 years ago Android was only taking off, and we've been just amazed by the very first iPhone As for "licensing programs for schools, universities, charities or charitable purposes", our worldwide distributor ABSEIRA already offers 50% discount for such organizations: http://www.aida64.co.uk/aida64-prices Regards, Fiery

Do you mean the flow rate for your Koolance flow meter is shown as a fan RPM in AIDA64? Or you mean the flow rate is completely missing from the list of measured values? Thanks, Fiery

They're a bit high if those are the idle temperatures. But since it's a mobile computer, it may just be normal, considering the compact case size of most mobile computers. If the phenomenon of too much fan activity is a recent issue, then try to have your exhaust vent ports cleaned at a Toshiba service center (I think you have a Toshiba notebook there ) Regards, Fiery

AIDA64 exports both units and values for all type of readings. It's the fault of the other (importing) software if it only picks up some of the units. Or, in this case, I suppose Aquasuite assigns units based on type of values, and doesn't use the units provided by AIDA64 through WMI. Regards, Fiery

Other software read the temperatures of the physical cores. However, temperature readout of Intel's DTS solution is quite responsive, so even if you read the temperature multiple times in quick successions for the same core, the values will be different in most cases. So the difference between a physical core and a virtual core is only by accident, they don't actually reflect separate temperature sensors

They should be listed as Temperature #1, Temperature #2 and Temperature #3. However, in case you've got some other sensor devices in your system (like Aquaero), the values may be overwritten by the values read from that device. Please let me know if you think that's the case.

Thank you for the data. Please let me know how the missing temperature readings are called in the UEFI Setup.

Please note that the "missing" cores are virtual cores only. They are not physical cores, and so they cannot have an on-die temperature sensor.

Area Graph is a variant to the classic Line Graph. Both have both vertical and horizontal grid lines.

Are you sure you're using the right AIDA64 edition? Are you using AIDA64 Extreme, AIDA64 Engineer or AIDA64 Business?

You can download it from: http://download.aida64.com/resources/lcd/razr-v1.10.rzlcd Or if you prefer it in a ZIP compressed archive, then it's at: http://download.aida64.com/resources/lcd/razr-v1.10.rzlcd.zip

I suppose PCI bus segmenting has been introduced in the v6.0 NT kernel with Windows Vista. AIDA64 wasn't prepared to handle PCI bus segments before, but the latest beta fixed that up. Thank you for the feedback, I'm glad it works fine now

By default AIDA64 scans only the first 8 PCI buses, for safety reasons. Many older systems could go wild if you try scannig 256 PCI buses. AIDA64 uses additional information from the Registry to find out whether the actual system may have more than 8 PCI buses with devices. BTW, the code snippet you've quoted there has some other issues too You're not supposed to scan all PCI functions of a device by default.