Fiery

We will add RIL serial number information to the next AIDA64 for Android app update.

Thank you for the data. The issue will be fixed in the next AIDA64 stable update due on Tuesday.

Thank you for the feedback. Please note that the quoted pecularity was actually a feature called ZeroCore Power, not a bug Probably AMD disabled it on your card with the latest Catalyst update to avoid various issues.

Which one of the above proposed 4 ideas would you use? We've tried idea #2 on BlackWidow Chroma, but it didn't seem like something you would actually want to use The big numbers were hard to read, even from a distance. The other 3 ideas seem to be more practical. K70 and K95 do not feature a SDK, and their API is not documented either. However, there seems to be some useful information on the web about how to access them directly, so we'll give that a try

Have you restarted your system after disabling ULPS? Or you've disabled it a while ago? If you disabled it a while ago and since then you've updated Catalyst, then there's a chance ULPS got re-enabled by Catalyst. Anyway, if you're 100% sure ULPS is disabled, and that Multi-GPU support is enabled in AIDA64 / main menu / File / Preferences / Stability, then please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers, and copy-paste the results into this topic. Also right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI SMBus Dump, and copy-paste the results into this topic.

Yes But please give us cca. 2 or 3 weeks, since currently we're very busy working on the upcoming update to AIDA64 that will cover such things like Windows 10, Skylake, Nolan, etc I'll get back to you in this topic once we have an update. Thanks, Fiery

Not yet

AIDA64 will only measure those values in a CrossFire setup when ULPS is disabled. With ULPS enabled accessing the registers for the secondary adapter could cause a system crash. Do you have ULPS disabled?

To me it doesn't seem to be a voltage issue. But I'm not sure what could it be It's not easy to diagnose such issues remotely, but maybe someone else here on the forums will have an idea...

Thank you. Yes, I can confirm that "Aux" is the CPU temperature on your motherboard. We'll fix the labelling issue in the next AIDA64 update

Most likely "Aux" will be the CPU temperature. What motherboard do you have?

It largely depends on the actual Turbo Boost multiplier and power limit settings. The FPU subtest of the AIDA64 System Stability Test is very demanding, so in most cases the CPU cannot use its highest Turbo multiplier due to TDP constraints. Regards, Fiery

We've explained it a number of times already on this forum Those values are reported by Windows, via standard Win32 API calls. In case the numbers incorrect or inaccurate, it's only the fault of the Windows kernel, and not AIDA64. BTW, even when you disable pagefile, Windows will still manage a swap space. It's one of the dirty tricks of Windows, and I'm not even sure why is that or why is it useful for Windows to do that. Regards, Fiery

When you install Alphacool_USBDisplay_Driver_v21.exe, it will place the driver files in the C:\Program Files (x86)\Alphacool\USBDisplay\Driver folder.

We've just tested Windows 10 Build 10240 (64-bit) with an AlphaCool 240x128 display on an unreleased Intel platform, and it worked flawlessly. The only trick is: install.exe of the AlphaCool driver package doesn't work properly, so you have to manually install the driver using Device Manager.

We've just tested Windows 10 Build 10240 (64-bit) with an AlphaCool 240x128 display on an unreleased Intel platform, and it worked flawlessly. The only trick is: install.exe of the AlphaCool driver package doesn't work properly, so you have to manually install the driver using Device Manager.

We're currently very busy implementing full support for the upcoming Intel Skylake CPU, and also for Windows 10 RTM, but after then (2 weeks from now) we'll jump on the Adaptec issue.

AFAIK AlphaCool LCDs work fine under Win7 64-bit, so they should also work under Win10. Worst case we can generate a libusb0 driver anytime, and sign it using our digital signature.

AFAIK AlphaCool LCDs work fine under Win7 64-bit, so they should also work under Win10. We've managed to order one of each 3 picoLCD variants last year. It may worth a try contacing their sales to inquire the about the next time they start selling it again. BTW, although not exactly the cheapest option, but the Aquaero 5 and Aquaero 6 Series LCD can also be used in AIDA64. You can also use a Samsung SPF digital frame with AIDA64.

This is getting a bit frustrating now You previously stated that Build 3445 worked fine on your SPF-107H. The latest beta version (Build 3479) works exactly the same as 3445 in regards to how it sends the keep-alive packet. So it only sends it once, when AIDA64 initializes the libusb0 device. Your issue seems a bit like if the frame was forgetting about receiving the keep-alive packet after a few hours, or some other USB communication issue occuring. Can you please check what happens if you revert back to AIDA64 v5.20.3400? (latest stable build) Would it work the same as the latest beta? (3479) Or would it disconnect the frame after a few seconds? BTW, the message "Before update remove some files from disk" looks a bit suspicious to me. What kind of update does it mean? Maybe it refers to firmware update? Because if it does, then there must be a hardware issue, since AIDA64 never sends a firmware update command via the libusb0 connection. If the USB packet gets compromised, then it could be because of a USB cable failure, or an intermittent communication problem between the SPF device and the USB controller of your motherboard. If you happen to have multiple USB controllers on your motherboard, like one for USB 2.0 and another for USB 3.0, then it would be useful to know if the issue goes away (or gets better or worse) by switching to a USB port that belongs to the other USB controller. It would also be great if you could try it with a different USB cable as well. BTW #2, this whole SPF issue would be a lot easier to investigate if there were only one variant of a particular SPF device model. But since there're multiple versions of SPF-87H and 107H as well, even if we bought e.g. a 107H of our own, it may or may not be the exact same model that you've got, and so it may not be useful at all to try and reproduce the issues you're experiencing. The whole Samsung SPF model portfolio is a big mess, and it's quite a challenge for us to support all the different models and variants with a single code base, and preferably without you having to play with setting various options. But, if nothing else works, and we can be 100% certain that it's not due to an intermittent hardware failure in your case, then we can implement a new option about the keep-alive packet, to let you configure the keep-alive packet sending interval.

AIDA64 for Android app currently doesn't support placing any readings on the notification bar. We are currently gathering ideas about various ways to export or display sensor readings, e.g. floating window, notification bar, Android Wear, sending the readings to AIDA64 running on a Windows PC, sending the readings to AIDA64 running on another mobile device, etc. Regards, Fiery

Thank you, please continue reporting any issues, and also post your ideas on future improvements related to Samsung SPF support

We've added support for Modding-FAQ USB-LCD Lowcost Edition, as described at: http://www.modding-faq.de/index.php?artid=615 You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Modding-FAQ. You can find the new AIDA64 beta update at: http://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD or VFD device that is currently unsupported by AIDA64. BTW, Saitek X52 Pro and Pro Flight Instrument Panel displays are also supported now by the latest AIDA64 beta. Regards, Fiery

This could well go under the Brainstorming forum, but I thought I'd ask your opinion in the Hardware Monitoring forum instead, since many enthusiasts using SensorPanel, LCD and OSD Panel modules tend to visit this forum frequently. So, we're considering implementing support for Corsair K65 RGB, Corsair K70 RGB, Corsair K95 RGB, Logitech G910 Orion Spark and Razer BlackWidow Chroma RGB keyboards. By individually lighting keys and being able to use custom color for each key, some fancy effects can be achieved. Question is: how should we utilize such capabilities of RGB keyboards? A few ideas we've already come up with: 1) The row or column of F-keys (function keys), G-keys, number keys, or even the numeric keypad or the main QWERTY block may be used as a horizontal or vertical bar. It may be perfect to show such readings like CPU utilization or GPU utilization. I think it would look best if it went from green to red, but it may be possible to use individual colours for min/limit1/limit2/max, just as with the LCD and SensorPanel Sensor Item bars. 2) The main QWERTY block of alphabet keys may be used to show 2, 3 or maybe even 4 big numbers, although the non-regular matrix of keys may make it look a bit odd. And of course, you might have to look at it from a bit of a distance to read the numbers quickly. 3) By combining the F-keys, number keys and the numeric keypad would enable showing 2-digit numbers directly. So for example, 24 Celsius CPU temperature may be represented as lighting up F2 key (to stand for "2"), and number 4 key together in the same time. Considering the F-key row is right on top of the number key row, this solution should be easy to read and interpret. Using the numeric keypad may not be the best idea though, since it would be too far from the location of the other digit (F-key row or number row). 4) It may be possible to put the status of a temperature, voltage or fan speed reading on a single key, without showing the actual readout value. So e.g. the "C" key would be lit green when the CPU temperature is cool, yellow when it's above 50 Celsius, orange when it's above 60 Celsius, and red when it's above 70 Celsius. Similarly, motherboard temperature would be indicated on the "M" key, HDD temperature on the "H" key, CPU fan on the "F" key, etc. What do you think about those ideas? What else do you think would be a good idea? Do you already own a G910 or a BlackWidow Chroma, and you think you would be interested in using this feature? Thanks, Fiery

I'm afraid there's nothing new I could report about this feature request