Fiery

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.

In theory, yes. That's why there's a CPU register that stores the TJMax value for the actual CPU part. While in previous (pre-Core i3/i5/i7) Intel CPUs there was a common value for every CPU generation. Yes, that could happen, especially if they're not the same stepping. The concept behind all this comes from the manufacturing properties of a certain batch of processors. Intel (and other CPU manufacturers as well) release a CPU using a certain stepping, a certain physical layout first, when the CPU debuts on the market. And then through the life of the CPU generation (in your case it's Haswell-E) Intel keeps improving the manufacturing process and develops new steppings. And in many cases those improvements effectively improve the thermal capabilities and/or the clock tolerancies of processors, and may enable using higher or lower TJMax values in the same time. It is especially important for mobile CPUs, but Intel also improves high-end desktop and server CPUs through their manufacturing lifetime as well.

TJMax temperature depends on the actual CPU part. It is programmed into each CPU by Intel, and so it's not possible to tell what temperature a particular 5820K or any other modern Intel CPU would throttle at. Regards, Fiery

I'm afraid it could be due to a number of issues, including: faulty memory module(s), incorrect memory timing/voltage settings, compatibility issues between your memory modules and your motherboard, Windows driver or configuration issue (low chances IMHO), power supply failure, motherboard failure, CPU failure. Since you seem to have a brand new CPU, motherboard and PSU, it's unlikely that they cause the issues. We've seen similar problems with an ASRock Z170 motherboard and HyperX DDR4 modules, where no matter what we tried, the motherboard kept being unstable with those memory modules -- but the same motherboard worked great with Crucial DDR4 modules, and the HyperX modules worked flawlessly in a Gigabyte Z170 motherboard. In your case I'd try contacting Asus to find out whether your memory modules are 100% compatible with your motherboard. If Asus said yes, then I suppose a RAM RMA or replacement to different brand modules may be necessary to resolve this. Although it's not really possible to diagnose such issues remotely, so please take everything I said as pure guesses, and not definitive guidelines or diagnosis. Regards, Fiery

Device Manager: You can try re-installing Intel chipset software package, it may help. But, if the device is still there, you don't have to worry about it. It doesn't bring any useful functions to Windows, but it also doesn't require a driver to be installed. Chassis fans: Thank you for the data. Please note that the 3rd chassis fan is already there on the Computer / Sensor page of AIDA64, it's just called Power Supply fan. We will fix the labelling issue in the next AIDA64 beta update. Video card fan: Thank you for the data, but we need 2 different dumps, one for the fan spinning state, and another for the fan stopped state. So we could compare the registers output to see where the catch is. Thank you for your time.

That was a special limited-period promotion that is now over. I've sent you a private message about this.

Thank you for the feedback

Fortunately there's no alert method for computer self-destruction

You don't have to. You can renew an old, expired license anytime. We currently have no plans to introduce a lifetime license.

1) The device is most likely the Thermal Controller of the Z97 PCH. On some systems the BIOS hides that device, but AIDA64 will re-enable it in order to provide PCH Diode temperature readout. 2) Several ASRock motherboards use a poorly implemented fan muxing mechanism that is unsupported by AIDA64. On your particular motherboard that effectively means that only one of the CPU fan headers can be monitored by AIDA64. However, the rest of the fan headers should be available on the Sensor page of AIDA64, albeit they may be labelled differently, like System fan or Aux fan. If they're not there, then 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. 3) The video card fan issue is most likely because even after the fan is stopped, your GPU still reports the last fan RPM for whatever reason. It could be a VBIOS issue or a GPU pecularity. We can check what's going on, but in order to do that, we would need to see how the GPU registers look like when the fan is not spinning, and also when it is spinning. So if it's possible, please issue an ATI GPU Registers dump for both states, by right-clicking on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. Copy-paste the full results into this topic. Thank you for your help. Regards, Fiery