Fiery

Thank you. We would be happy to contact HP directly, and receive the necessary programming details under NDA. But, in order to do that, we need a person to contact there, since HP is a huge company

As long as the readings in AIDA64 make sense, and they look accurate, then no need to go the extra mile and compare all values against the ones provided by the Corsair Link Dashboard . As for the fan, what we did is set the fan duty cycle in Corsair Link Dashboard to a higher value, waited until the fan started spinning and Corsair Link Dashboard started to show a non-zero RPM reading, then closed the Dashboard, and checked the fan RPM in AIDA64. It worked fine on our test systems, along with the other readings.

Are you sure when your RAM drive is too small that Windows itself can measure its performance? To me it looks like Windows fails to provide performance readings for small drives. BTW, when you disconnect or connect (ie. hot-plug) a disk drive, AIDA64 should already be able to detect the change. So such delay shouldn't be necessary, as long as the drive performance is provided by Windows.

We've implemented flow rate measurement for both Koolance and T-Balancer devices in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta The values are measured as raw values, as they are provided by the sensor device. To make them make a bit more sense, and also to convert them to LPH (Liter Per Hour), you need to use the Correction feature in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction.

Thank you for the data. Fan speed should be available, but it will only appear on the Computer / Sensor[/b page when the fan is spinning. Efficiency is calculated using pre-defined constants that vary across PSU models. It doesn't seem like something that involves a lot of science, so we are not so keen on implementing that reading

The mentioned new AIDA64 beta is available for download at: http://www.aida64.com/downloads/latesta64xebeta Let us know how it works

The mentioned new AIDA64 beta is available for download at: http://www.aida64.com/downloads/latesta64xebeta Let us know how it works

The mentioned new AIDA64 beta is available for download at: http://www.aida64.com/downloads/latesta64xebeta Let us know how it works

Thank you for your reply. I'm afraid we also haven't found any interface in Razer SwitchBlade UI SDK that could let us select a profile

The latest AIDA64 Extreme beta fixes that up too. I've noticed that you're using AIDA64 Business. If you'd like to get a new beta update to AIDA64 Business, please send me your AIDA64 Business product key in private message, and I'll send you a download link back.

Are you sure the drive was connected to Windows properly when you started AIDA64? Does it appear as a regular physical drive in Windows Disk Management? Does the RAM disk appear as a regular physical drive on the Storage / Physical Drives page in AIDA64?

In AIDA64 you can use the Correction feature to calibrate any sensor reading. Just go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction to try it out. What AIDA64 (from its next beta update) will do is simply read the raw flow meter reading from T-Balancer (as well as Koolance) devices that you will have to calibrate with the Correction feature.

No, it's only related to the driver that a particular SATA controller uses. Drivers can differ between Windows installations, and even a newer driver of the same kind (e.g. Intel RST) can bring substantial changes. As for the BSoD: when a SATA driver gets confused about the drive interrogation commands that AIDA64 sends, the BSoD comes up at AIDA64 startup, while the AIDA64 splash screen says "Scanning RAID Devices" or "Scanning SMART Devices".

Wow, that is an awesome looking SensorPanel It must have been a hell of a job to construct that layout, well done!

I'm not sure what you mean by that AIDA64 should already support Poweradjust devices, along with all other Aquaero devices that provide sensor readings. In case the measured values are off, you can calibrate them using the Correction feature of AIDA64. Just go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction.

Without RAID SMART support enabled, AIDA64 can only read temperatures from those drives that appear as regular IDE-compatible drives in Windows. With RAID SMART support enabled, any special cases are also supported. You can leave RAID SMART support enabled if you don't experience any stability or performance issues that way. It's not harmful to have it enabled. There's an option to let you disable it only because in some rare cases RAID SMART support can make a SATA driver throw a BSoD. But you would have noticed that already if your system suffered from such an issue

The option is still there in the INI file (named HWMonSPLCDJPEGLimit), you can adjust it from there. We do not plan to add it to the AIDA64 Preferences, since we don't think that option should be used generally. Yours is still a special case, but you can still control the JPEG file size limit via the INI file. Happy New Year!

Maybe ULPS is not enabled in Catalyst (Crimson) under Windows 10 due to technical or other issues? Win10 uses WDDM 2.0, and that brings major changes in video drivers too. Maybe AMD will enable ULPS only in future video drivers under Win10.

We will add the requested new sensor items in the next AIDA64 beta update due next week I will post a message into this topic once the new beta is available for download. Regards, Fiery

In the next AIDA64 beta update (due next week) we will fix that by renaming Fan #1 and Fan #2 on Sabertooth Z87 and other capable Asus motherboards to Assistant #1 and Assistant #2. That way you'll be able to measure all fan RPMs with AIDA64. I will post a message into this topic once the new beta is available for download. Till then, Happy New Year! Regards, Fiery

Only such a picture where all chips can be identified. So it would have to be a high-resolution + high-quality picture, which is hard to capture when the motherboard is already built into a PC chassis. But, if you could find chips on your motherboard that can be EC (Embedded Controller) or sensor chips, that would be great. If could be a tough job though, and if you find an EC -- which I think you would --, it would still be of little help considering the issue that I've explained above. There's a slim chance you could find a classic sensor chip as well as an EC, and in such case we might be able to solve it without the assistance of HP. But, we've seen thousands of different motherboard sensor chip solutions, and yours doesn't look anything like any of those, so I don't think there's a sensor chip there afterall, but only an EC. I really wouldn't want you to go through all the chips you can find on your motherboard to try and find an EC or sensor chip, but if you have plenty of time, a good eye-sight, and you'd like to contribute in an attempt to solve this issue, then we would of course appreciate your help on this.

The SSD? No. The SATA controller where the SSD is connected to? Maybe Polling SMART information is done via calls to the SATA/IDE controller driver, and there anything could go wrong. Fortunately it's very rare that things go wrong, but it could happen.

The old AIDA64 version handled ULPS in the very same way as before we've applied the 2 workarounds in the recent betas. The only difference may have been that an old AIDA64 version may have been unable to report anything about R9 Fury Series And when it comes to an unknown GPU, AIDA64 will not read anything from it, so it won't cause any issues when ULPS is active. As for Windows 10, it's hard to tell. I personally have made the upgrade on all my personal computers, but it doesn't work flawlessly. I still believe Windows 7, even at its RTM state was a more mature and more roboust OS. Windows 10 will soon get to that level of maturity, but it's just not there yet. If it weren't useful for AIDA64 development purposes, I would have waited until the Redstone Update (Spring 2016) for moving to Win10. One thing absolutely great about Win10 though is the UWP app development using Visual Studio 2015. It's just very smooth, and it makes app development light-years easier than before (using Win8.1 + VS2012). But, it's sadly a niche "market". Most app developers are still not interested in making Windows apps, and I suspect most of them won't change their minds before next summer (the earliest).

Thank you for trying to contact HP. What we would need is: technical documentation or proper programming guidelines on how to handle the Embedded Controller chip in order to read out temperatures, voltages and fan speeds. Even a very limited, very focused set of information would be a great help. Just to explain our situation with a bit more details... There's a big difference between mobile systems (notebooks, laptops, tablets) and classic desktop computers (desktop PCs). With desktop PCs temperatures, voltages and fan speeds are usually measured by a sensor chip that is integrated to the motherboard. Such sensor chips are usually manufactured by either Fintek, ITE or Winbond/Nuvoton. Handling those sensor chips are quite easy, since they are well documented, they follow industry standards, and there aren't tons of variations of them. Contrary to that, mobile systems are usually equipped with Embedded Controllers that are reprogrammable to suit the vendor's (in your case: HP) needs. So even by having documentation on the chip itself wouldn't help at all to figure things out. Embedded Controllers can work very differently even across models of the same computer brand, and there's no industry standard way of handling them. The only good thing about them is that some computer vendors (namely Apple, Asus, Dell, and Sony) came up with their own standards, so with such mobile computers reading sensor information out is almost as easy as with desktop computers. But the rest of the mobile world is a big pain, and in most cases we can only figure out how to read sensor values from the Embedded Controller if we can gain access to a physical system for a few days at least. And even though your system is a desktop PC, it looks and acts like a mobile system: it's not equipped with a sensor chip, but an Embedded Controller of some sorts. So it falls under the same "painful" category as mobile computers about this issue...

We will implement the requested feature in the next AIDA64 beta update due next week. I will post a message into this topic once the new beta is available for download.