Fiery

That sounds odd. Try to download the beta ZIP package, and extract it into a new, empty folder, and see if it runs from there. Also try to right-click on AIDA64.EXE in the File Explorer --> Properties --> Unblock --> OK. BTW, what Windows version do you have installed?

Have you performed the upgrade properly? Did you copy all files from the ZIP beta package into the existing installation folder of AIDA64, and overwrote any existing files? Somehow AIDA64 (the new beta version) cannot load its kernel driver on your system, which could be due to a few issues, like: 1) Lack of kernel driver files in the folder where AIDA64.EXE resides in. 2) Lack of necessary (administrator) privileges at the user who starts AIDA64.EXE

Try to restart your computer, and it should fix it up. Regards, Fiery

Are you sure you're not mixing Mbps (Megabit per second) and MB/s (MegaByte per second) ? 1 MB/s = 8 Mbps.

Please let me know what motherboard do you have, what Windows version do you have installed, and what drives do you have connected to which SATA/RAID controller. And also, in what mode do you use that controller? Thanks, Fiery

We currently have no plans to extend the list of sensors where we provide information on fan duty cycle. It's actually not that useful a value, and could be very misleading if someone relies on it. Because even if duty cycle is e.g. 75% or 100%, the fan could be stopped or clogged.

Those readings should also be available for all nVIDIA GPUs in the system. But, they may be unavailable for the secondary GPU because it is sleeping at the time AIDA64 tries to collect sensor information for it. It's not something that's easy to get around: you can try configuring your sensor items while putting a constant load on the secondary GPU, to make sure ForceWare drivers prevent it from going to sleep. Or, you can temporary disable the sleep mode for the secondary GPU -- I'm not sure if it's possible though.

Duty cycle is not available for most sensor readings, that's just normal. One of the USB sensor or PSU sensor modules of AIDA64 could cause that. You can try disabling the sensor devices that you know don't have connected to your system in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. If that doesn't help, then please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB Dump, and copy-paste the results into this topic. Also, make sure to use the latest beta version of AIDA64 available at: http://www.aida64.com/downloads/latesta64xebeta

Thank you for the feedback

I will drop a message into this topic once the new beta is available for download.

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 us know if it helps. If not, then please let us know more about your hardware and operating system.

I know what popup you meant. I was talking about a different window, the one that is the Properties box of the AIDA64.EXE file that you can access in File Explorer after right-clicking on AIDA64.EXE. You don't have to start AIDA64 to access that window.

Support for K7 anti-virus and firewall products will be implemented in the next AIDA64 beta update due in a few days from now.

Thank you for the feedback, I'm glad it works fine now. You can avoid that by right-clicking on the AIDA64.EXE file in File Explorer --> Properties --> Unblock (put the tick in the checkbox) --> OK. Example:

We haven't changed anything about the OpenGL module, so it should work similarly across the two AIDA64 versions you've tried. Try to reinstall AIDA64 v5.50, restart Windows, and it may just help.

The mentioned new AIDA64 beta -- including the GPU fan issue fix -- is available for download at: http://www.aida64.com/downloads/latesta64xebeta I'm glad you could resolve the Device Manager issue

The mentioned new AIDA64 beta is available for download at: http://www.aida64.com/downloads/latesta64xebeta

I see. Make sure to report that issue to Samsung. Sadly the built-in (default) Windows NVMe driver is very limited, so it's not possible to provide SMART information using that driver.

PStates Monitor is not an official feature of any AIDA64 edition. We will only decide about which edition to implement it in when we introduce it as an official feature. Regards, Fiery

What's wrong with using Samsung NVMe drivers for Samsung NVMe SSDs?

No, I'm sorry, but we wouldn't want to go down that path.

Thank you for the dumps. As I've suspected, it is a GPU pecularity. Your GPU reports a valid, non-zero fan RPM measurement even when the fan is driven at 0% duty cycle, so when it's basically instructed to stop. We'll implement a workaround to show 0 RPM when the duty cycle is 0%. It will be included in the next AIDA64 beta update due in a few days from now.

Intel Haswell processors tend to overheat and throttle under heavy load, so it's normal what you can see on the throttling graph. The rest, including the high temperatures are also normal for a Haswell based mobile system. Regards, Fiery

I don't think it's possible to detect the actual maximum network speed in any ways. And without knowing the cap, we cannot implement an automatic range for the gauges.

A couple of Celsius below TJMax. How much is "couple of"? Only Intel knows. AIDA64 provides information on the TJMax value on the Motherboard / CPUID page. AFAIK it's not possible to detect at which point the CPU will actually start to throttle. But, you can use the FPU subtest of the AIDA64 System Stability Test to find that out. It means 10% of the time the CPU is throttling. So e.g. if you run the test for 1 second, the CPU will actually do work (processing, computing) for only 0.9 seconds. The remaining time is in the stalled state, so given that example, the CPU is not doing any work for 0.1 seconds out of 1 second. Yes, it is a bit, it is a state of the CPU. What AIDA64 does is: it checks that bit very frequently (100 times per second), and makes an average of those readings. So it will basically have 100 readings of the throttling state bit, and if 10 times out of 100 the throttling bit is 1 (meaning: throtting is active), it will calculate a 10% throttling value.