Fiery

AIDA64 is not linked to that DLL, and it never tries to load it. What could happen on your system is that when AIDA64 tries to detect a certain system setting or property, a background process or service gets activated, and that process/service cannot load the mentioned DLL file.

It will not detect the GPU on the Display / GPU page, and it will not display any readings on the Computer / Sensor page for the video card.

Yes, but it's not because we want you to pay again, but because we cannot implement support for all future hardware. And implementing support for new technologies, newly released hardware is a constant work on our part. That's why we have to release beta updates every week (sometimes twice a week), and stable updates every 2-3 months. AIDA64 not like most software: it's not enough to update it once a year to keep it fresh and bug-free. It's not easy to keep AIDA64 up-to-date, and if you are a sort of hard-core user who keeps his hardware always up-to-date, then it's necessary for you to keep AIDA64 up-to-date as well by using the latest version. Of course it's not mandatory, so e.g. if you buy a new video card and your old AIDA64 version doesn't support it, but you can live without monitoring your new video card, then you can still keep using the old AIDA64 version. Yes, AIDA64 is a bit like an anti-virus, but only if you keep changing your hardware. If you keep your hardware for years, then you can keep your old AIDA64 for years, you don't have to always have the latest version installed. Unless of course you want to use a new feature that is not related to hardware, like the RemoteSensor and Logitech Arx modules that we've rolled out last December. An example of a case when you don't need to renew AIDA64 for years: the last computer I've assembled for myself was back in 2011. It was based on a Z68 chipset, Core i7-2600 "Sandy Bridge" CPU, and Windows 7 64-bit. I've kept the system almost intact for 4 years, and only a few days ago I've retired it an switched to a completely new PC. If I purchased AIDA64 back in 2011, just because of new technology rolling out I wouldn't have had to renew my license until today. Now that my new computer is based on the latest hardware (Z170 + Skylake) and has the latest OS (Windows 10) installed, I would have to renew my license. But between today and 2011 the old license would have worked perfectly.

It depends on the type of hardware in question. Future GPUs cannot be supported, because their IDs usually do not leak before their launch. CPUs and chipsets are different beasts, usually they are supported months (in some cases 6+ months) before their market launch. Motherboards, and especially special sensor tweakings cannot be implemented before the market launch of the actual motherboard model in question. New, hot technology advancements like NVMe can sometimes be supported before an actual product hits the market. Regards, Fiery

We will add the missing fan item to the AIDA64 hardware monitoring module in the next AIDA64 beta update due in a few days from now. Thanks, Fiery

I suppose Win10 has got a revamped memory management subsystem that is more sensitive to applications "eating up" system memory You can simply ignore that warning message of Win10.

We will add the missing fan item to the AIDA64 hardware monitoring module in the next AIDA64 beta update due in a few days from now. Thanks, Fiery

Does the fan appear properly on the Computer / Sensor page in AIDA64? Thanks, Fiery

It could be normal, actually. AIDA64 System Stability Test allocates all available physical RAM in its memory subtest. If you keep using your computer while the test is running, and you have no swap file defined, it is very likely that Windows will run out of system memory. In which case it's best to avoid using the computer while the AIDA64 stress test is running.

No, we haven't got any reports of such an issue, and we also haven't seen it on our own test systems yet. Which subtests do you have enabled? (CPU, FPU, etc) Do you have any common hardware components in your systems? Like, all of them has a nVIDIA GPU or such?

Thank you. The issue will be fixed in the next AIDA64 beta update.

Have you tried restarting your computer after the update?

We currently have no plans to implement such a feature.

Thank you for your help about this issue. Here's the official beta update that implements the fix for Dell SMI sensors: http://www.aida64.com/downloads/latesta64xebeta

Quite frankly, we have zero information on how to monitor that PSU. But we can try finding it out if you could help us a little bit First of all, please upgrade to the latest AIDA64 Extreme beta update available at: http://www.aida64.com/downloads/latesta64xebeta Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump. Copy-paste the full results into this topic. Thanks, Fiery

1) AIDA64 System Stability Test includes a GPU subtest that stresses video adapters via OpenCL. It's a generic stress test, so it doesn't focus on the VRAM specifically, but perform compute tasks to stress both the GPU and the VRAM. There is no dedicated VRAM stress test in AIDA64, and quite frankly, I don't know any software that would do that. It would be possible to develop such a software, so maybe one day someone will come up with it. 2) It's not possible to specifically stress or diagnose the PSU, since it's not a smart component. It cannot run tests or any other tasks, it just provides power for the other system components. It is possible however to run such a stress test with AIDA64 that draws the most power from the PSU, so it effectively stresses the PSU as much as possible. Just open the AIDA64 System Stability Test, only enable (tick) the FPU subtest there, and press the Start button. In some cases it is best to enable GPU subtest as well, to stress both the CPU and GPU. Regards, Fiery

Just focus on the CPU Package value.

CPU Package is the temperature that is measured by the CPU itself, and it represents the overall temperature of the CPU package -- as opposed to the core temperatures which correspond to an individual CPU core.

Such issue can happen with Corsair RGB keyboards where each international layout would require us to add a separate layout table. The lack of standard SDK/API makes our lives a lot tougher than with Logitech and Razer RGB keyboards And as I've stated above, currently AIDA64 supports only the US layout for Corsair RGB keyboards, but it will work with other layouts as long as you keep in mind that some keys may be mixed up. What keyboard model do you have? Do you also use RemoteSensor or Logitech Arx? When you use those modules, AIDA64 will try to keep the Preferences window as large as possible, to let the LCD layout editor/preview fit without too much shrinking (zoom-out).

We've just checked our GLCD2USB device under Windows 10 RTM 64-bit, using the default HID driver, and it works flawlessly. Init failed means the device doesn't return RID_GET_INFO packet via HidD_GetFeature. Are you sure your device has got the right firmware and the firmware is properly flashed? Can you communicate with the device using your own application or another Windows or Linux software?

HWiNFO64 should use the same access method. But AIDA64 does a few tricks when e.g. CPU temperature cannot be measured via Dell SMI -- and that may just make a difference. Also, AIDA64 supports 2 different interfaces to issue Dell SMI calls, so it would be necessary to understand the exact method used on your system. Please create the following outputs and send them in email to me (I'll send you my email address in private message in a minute): 1) A screen shot of the Computer / Sensor page of AIDA64. If possible, please adjust the window size to show all readings on a single shot. If not possible, then please create 2 screen shots to make sure we can see all information. 2) A screen shot that shows HWiNFO64 Dell SMI readings. I think it's called Dell EC in HWiNFO64. 3) Right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Save it to a TXT file and attach it to your email. 4) Right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Save it to a TXT file and attach it to your email. Thank you in advance.

1) Do you have any external storage devices connected to your PC? 2) Do you have any special water cooling systems in your PC? 3) Do you have any external LCD or VFD devices connected? (not counting your monitor(s), of course) 4) What motherboard, CPU and video card do you have in your PC? Thanks, Fiery

Yes, in such case your phone is the router. But I don't think such ports have to be configured on the phone in any ways. Just specify port 8080 in the AIDA64 Preferences, and use the IP address with ":8080" in the web browser. However, your have to make sure your internet provider (the one that gave you the SIM card for your cell phone) doesn't limit or block traffic on non-standard TCP/IP ports.

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

Please upgrade to the latest beta version of AIDA64 Extreme available at: http://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.