Fiery

It's already available in AIDA64: https://forums.aida64.com/topic/2636-remotesensor-lcd-for-smartphones-and-tablets/ Regards, Fiery

What version is zero? Do you mean -2 from the latest stable update? Do you mean stable update or beta package? Before your post we've had the following few releases: Beta Update 3725 Beta Update 3720 Beta Update 3718 Beta Update 3716 Beta Update 3709 Beta Update 3703 Stable Update 3700 Of course we can go even further back, if you want.

I'm glad it works now, and thank you for letting us know about the resolution

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

We'll check it out. Although, please note that for the optimum performance it's best to install Samsung's own NVMe driver for Samsung NVMe SSDs, and Intel's own NVMe driver for Intel NVMe SSDs.

That should work with AIDA64 just fine. Go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Sure, and check the checkbox. If it says Init OK, then you can build your LCD layout in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / LCD Items.

Do you mean you want to purchase a Sure LCD, or that you want to use an existing Sure LCD with AIDA64?

We've checked, and it works fine for us, with a 1000 MB sized RAM disk. Hot-plugging it also works properly. If you need a previous beta, please let me know which ones are you interested in, and I'll send them to you.

Haswell processors operate at very high temperatures, and can easily throttle under heavy load. 90+ Celsius is normal for them.

Our benchmarks are not open-source. If you use Google, you can find a lot of information on how to build a proper memory benchmark. Start here: https://www.cs.virginia.edu/stream/ref.html http://zsmith.co/bandwidth.html Regards, Fiery

It's a very specific request, so we will only implement it when a few more users also request it.

What version of AIDA64 is able to access the drive in its current state? I'm just asking because the drive activity measurement feature was implemented only a few weeks ago, and we haven't touched that feature since then. So it would be quite weird if there were difference between how the "old" AIDA64 and the current one works. BTW, the graph you've linked shows the drive in its 10 GB capacity state. You've previously mentioned that when you configure the drive to 10 GB size, it works with AIDA64. So make sure to configure it to 4 GB, and check Task Manager again. I'm pretty sure the issue is not AIDA64 itself, but due to a Windows limitation based on drive size. Also, what RAM disk software are you using? We can try to reproduce the issue on a test system of ours.

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".