Fiery

Thank you. Apparently the 4 fan registers corresponding to Chassis #n fans are all zero after waking up from sleep. We suspect it's because the BIOS fails to properly re-initialize the sensor registers after the computer comes back from sleep. I would have suggested you to update the BIOS, but you seem to be using the latest version of it. Apart from asking Asus about this, and reporting them about this potential BIOS bug, I'm not sure what can be done to get around this issue

The missing drives could be because of Aquasuite. The latest version of that software seems to open drives exclusively, and monitors them in a way that makes other software unable to access the drives

Thank you. We'll check it on a similar Sandy Bridge configuration soon.

Thank you. 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, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Please repeat that dump after the computer wakes up from sleep and the fans already disappeared. Thanks, Fiery

We've checked the foobar2000 SDK, but it seems quite complicated to use. For such a minor improvement we simply find it too awkward and complex to deal with. Maybe we're looking at the wrong bits and pieces though, so if you (or someone else) can provide a short source code to detect the information you're looking for, we'd be happy to implement it. I'm afraid we have no plans about an audio visualizer for AIDA64.

We've checked the foobar2000 SDK, but it seems quite complicated to use. For such a minor improvement we simply find it too awkward and complex to deal with. Maybe we're looking at the wrong bits and pieces though, so if you (or someone else) can provide a short source code to detect the information you're looking for, we'd be happy to implement it.

Thank you for your feedback

T Thank you, the issue will be fixed in the next AIDA64 beta update due next week

Do you mean the fans labelled by AIDA64 as Chassis #1, Chassis #2, Chassis #3 and Chassis #4?

Thank you, that was very helpful. I've sent you an email about further details

Aquasuite opens the drives and gains exclusive access to them, so that explains why AIDA64 cannot access the drive activity statistics. Aquacomputer needs to fix their service to enable concurrent access to drive activity statistics. Regards, Fiery

No, we cannot replicate the issue on our own test systems. Have you verified the priority settings on your computer? Also, I don't think the difference between Windows 7 and Windows 10 across your computers is the key to this issue. It's rather the hardware difference. Can you please tell us more about your Windows 10 computer? Motherboard model, CPU type, video card(s) model?

Thank you for the feedback

Thank you for checking the latest beta. Please let us know what exact motherboard and video card you've got, and whether you have any external (USB) storage devices connected, or any RAID arrays defined. We'll build a similar configuration and try to replicate the issue.

I'm afraid we currently have no plans to implement a fan control feature.

I'm afraid we still haven't found a way to get around the sensor communication issue affecting H270M Pro4 and Z270M Pro4 motherboards. It seems to be a hardware issue that may be possible to fix via a BIOS Update. We will only know for sure that the issue is fixed once ASRock starts offering its own monitoring utility (A-Tuning Utility) for these motherboards too. That utility is already available for other Z270 and H270 chipset based motherboards, but not for H270M Pro4 and Z270M Pro4.

We've added the missing bits & pieces in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Can you please check if the process priority settings are properly set while you're running the stability test? The main process (AIDA64.EXE) should be using Normal priority class, while the SST process (AIDA_BENCH64.DLL or AIDA_BENCH32.DLL) should use Below Normal priority.

AIDA64 currently doesn't support command-line based automated benchmarking. If you're interested in having that feature enabled, please send me a private message about the details on your envisioned project and the number of AIDA64 licenses you have (or you're about to) acquire to complete the task. Thanks, Fiery

If the drive has a very smart controller that desperately tries to hide the fact that the capacity is less than the advertised value, then for a while the Random Write + Verify test may not report any issues. Especially when the performance is that freakishly low With such an underperforming drive you would have to let the Random Write + Verify test run for at least 2 days to draw any meaningful conclusion. Good old fraudulent pendrives which perform adequatly (like 20-30 MB/s) are usually caught by the test in a matter of minutes, sometimes few seconds only. But it's always best to let the Linear Write + Verify test to complete to 100%, since that's the only sure way of knowing that the drive can be filled 100% with data, and all data is fully retained (stored) by the drive.

I'd simply return the device and ask for a full refund due to a suspected fraud. I wouldn't try to fix the drive at all. Even if you could format it to its "right" capacity, the performance would still be abysmal.

AIDA64 uses standard SMBus SPD commands to communicate with DIMM thermal sensors. There's no alternative way I'm afraid. And we sadly have absolutely no insight into how AI Suite works exactly about SMBus communication, and what and how Asus updated on the way it interacts with SMBus devices between AI Suite II and AI Suite 3 releases. Your new motherboard may simply have a SMBus based devices that AI Suite 3 now polls, and your old motherboard had no such device, so AI Suite II needed not to use its SMBus layer at all.

You can switch off (hide) individual graph lines by removing the tick from their respective checkbox

We've checked, and the high disk traffic is caused by the Logitech LCD API that AIDA64 uses to display sensor values on your G19 keyboard LCD. As you can see on your screen shot, LCore.exe (Logitech LCD Core) also shows the same anomaly. Make sure to ask Logitech about this, since only they can fix this in their LCD API. Thanks, Fiery

Thank you. You're still using the latest AIDA64 stable version. But since your motherboard was released to the market recently, it's not supported by that AIDA64 version. You may need to manually upgrade to the latest AIDA64 Extreme beta build available for download at: https://www.aida64.com/downloads/latesta64xebeta Just download the ZIP package and extract all its content into the existing installation folder of AIDA64. Let it overwrite any existing files. Your previous settings and entered license will be retained. After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Alternatively, you can try to perform the automatic update again. Just make sure to enable updating to beta versions first, in AIDA64 / main menu / File / Preferences / General (the option is near the bottom of that page).