Fiery

In your particular case IMHO it would be cheaper to buy the list of components for this display locally, and hire a local professional to build it for you. If he does everything by the book, AIDA64 will work with the display right away.

btmouse, beada: Please use this forum for English discussion only. Use private messaging to communicate in your native language. Thank you! btmouse: We're working together with beada to implement native support for their existing hardware in AIDA64. Till then RemoteSensor is the way to go:

Windows RT (which is the operating system running on Surface RT) doesn't support Win32 apps, but only Windows Store apps. AIDA64 is available in the Windows Store as a Windows Store app, Windows Phone 8.1 app as well as a Windows 10 UWP app. That's not the same as our main product (AIDA64 for Windows PCs), but only a light-weight free app that's designed to work well on phones and tablets. The successor to Windows RT, Windows 10 ARM is well supported by our main product because it has Win32 app execution capabilities through x86 emulation. It would be awesome if Microsoft backported Windows 10 ARM to Surface RT, since that would unlock running Win32 apps as well, but I wouldn't hold my breath on that due to the low amount of Windows RT based devices sold

AIDA64 supports all PSUs. If you mean such smart PSUs that can monitor their own voltages, temperatures and fan RPM, then all such PSU manufacturers offer products with or without such smart capabilities. So it's not possible to tell for example that "AIDA64 supports monitoring of all Corsair PSUs", since not all Corsair PSUs have such advanced features. AIDA64 basically has monitoring facilities for certain Corsair PSU, Enermax PSUs, Gigabyte PSUs, and Thermaltake PSUs. If you happen to buy a PSU with smart capabilities that is currently unsupported by AIDA64, we can look into it and most likely we can implement support for it if you can help a bit about test runs Edit: Also, why it's difficult for us to provide you with a full list of smart PSU models supported by AIDA64 is because AIDA64 supports PSU protocols, and not actual PSU models or SKUs. And even though I can say like "AIDA64 supports Corsair AXi, HXi and RMi Series of PSUs", the PSU protocols used by those PSUs may also be used in other PSU families of Corsair (or might be another manufacturer using the same protocol, although the chances are low).

I'd make sure to have the system running at stock settings (no overclock). If it still doesn't work, then try to borrow a PSU from a friend and check if it is the culprit or not. If that still doesn't solve it, try to borrow a set of RAM modules. If it still doesn't solve it, then it could well be the motherboard, which is the most difficult part to replace.

Yes, the pressure items are listed on the Computer / Sensor page, but currently they cannot be used (displayed) in other modules of AIDA64, like SensorPanel, OSD Panel, Sensor Icons, Desktop Gadget, etc.

Please send us an updated Corsair Link Dump and USB Dump, using AIDA64 v5.99.4900.

We've fixed the issue in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps when your nVIDIA GPU is sleeping or went to sleep after a few minutes of inactivity.

I think it's due to a difference between character-sets (character encoding) used on your PC and on your iPad/iPhone. We'll do some test runs and try to solve it by switching to UTF-8 or Unicode. I'll let you know in this topic once we have a fix for this issue.

I don't think it's related to any processes. After the SensorPanel freezes, please try to right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling 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

Yes, I'm afraid on some Asus systems that's the only solution when the stutter comes up. Strangely, it doesn't affect too many Asus systems, so it's not like it comes up on all Maximus XI Hero motherboards or such. There must be something unique in your system configuration that makes the EC work different to other systems based on the same motherboard.

Thanks a lot! We've added this display to AIDA64.

That looks like a very interesting project. IMHO it would be best if we could somehow work together to develop a custom, fast LCD protocol that works via USB connection. If you work for the manufacturer of the Beada hardware, please drop me a private message. If not, then please let me know what are your qualifications on the software developer's side, since only knowing a bit more about you (or what you can do on the side of your Beada hardware in terms of software/API matters) I can propose possible ways to implement a proper USB communications protocol for the Beada.

Thank you! Please repeat that process (no need to send us the report file again), then close the report window, keep looking at the GPU readings, and wait for a minute or two. It may switch back to detecting the card incorrectly as fake once the nVIDIA GPU goes back to sleep. Let me know if it happens that way or not.

So everything is working properly now?

Thank you for the files. We'll need to order a unit to help us investigate this issue. The new Platinum coolers apparently use a brand new protocol that we need to analyze and implement support for it. As soon as it becomes available in local stores, we'll order one and start working on it.

Great news, thank you for letting us know about the resolution.

What kind of water cooling system do you use?

We'll do some research on this. Please give us a few weeks, since things are winding down soon due to the holiday season

Do you already have a configuration file called AIDA64.INI in your AIDA64 installation folder?

That looks bad But, it's most likely because your nVIDIA GPU was sleeping. Please right-click on the GPU menu item in the left menu --> Quick Report --> Plain Text. Copy-paste the full results into this topic, or attach the TXT file to your post. Thanks, Fiery

1) It's impossible to detect whether a computer belongs to a certain department, unless that information is encoded in a software or hardware component. E.g. if all computers belonging to the sales department are part of a certain workgroup or Windows domain, then it's easy. If there's no such identifier encoded, then you may want to add that information to the systems of the sales department and then use AIDA64 to gather that information via the Audit Manager. 2) Load all reports into the AIDA64 Audit Manager, click on the Preferences toolbar button, select the Components tab, uncheck everything, expand HW Components, check the component called System Memory Size, press the OK button, click on Statistics 1 (Wide) in the left menu, and you can see the list of system memory sizes in your organization with their respective computer names. Now, if you want to have a more compact view, you can use Ctrl + left-click or Shift + left-click to select multiple items in the list of memory sizes -- for example all memory sizes that are less than 2 GB -- and then right-click --> Join Lines to collapse the list. In the Computers column you can still see the full list of computers belonging to the memory size category (group) that you've created via lines joining. 3) What software or hardware property do you have that reflects that property of the system? It's impossible to detect that based on a single time-stamp, but you may go with the OS Installation Date property (among SW Components in the AIDA64 Audit Manager). That property may not be all that useful for Windows 10 systems though. Otherwise, I'm not sure where can you find the age of the system encoded into a computer of yours...

Platform ID can be different for each CPU generation, so e.g. 03 could mean a different platform (socket/package) on Skylake than on Gemini Lake. What AIDA64 shows as platform ID is the same list of platforms for all generations, so 03 is translated to a specific platform and shown with its unique ID. That platform ID is unique to AIDA64. I'm not sure how useful would it be for AIDA64 users to know the ID that's assigned by Intel, since its meaning is not published anywhere actually. But, you can check Intel's platform ID in the CPUID & MSR Dump in AIDA64: just scan the output for "PlatID"

No, it's not possible. Unless you use a SQL database manipulating tool to temporarily remove 15 out of 20 of the computers from your database.

There must be something wrong about the OpenCL software stack. Try to uninstall and reinstall ForceWare.