Fiery

No, there's no issue about updating the values in the hardware monitoring module of AIDA64. If you check the Config / Environment Variables page, you can see that the changes are not committed in a way that AIDA64 could realize them. Probably using environment variables for such purposes isn't a good idea afterall. We could however pick another method. How about going for Registry? Like using the following path to import values from? HKEY_CURRENT_USER\SOFTWARE\FinalWire\AIDA64\ImportValues

Press Windows key + R (to Run a program), enter: sysdm.cpl On the top row of tabs, select Advanced. Then, near the bottom of the window, push the Environment Variables button.

Thank you. The issue will be fixed in the next AIDA64 beta update due later this month. It will also add more voltages, like DIMM, DDR VPP, PCH +1.0V, VCCIO, and VCCSA.

Thank you, the issue will be fixed in the next AIDA64 beta update due later this month.

What motherboard do you have? I suppose it's not the one in your signature, which shows a Sandy Bridge system

No, apparently not true For test runs we've had to use System Properties / Environment Variables to set the new AIDA64 specific environment variables.

I suppose something got revamped with a recent eScan software update that rendered the current anti-virus detection module of AIDA64 not working anymore about eScan. We'll fix it up and also add support for Zemana later this month.

Are you sure the same user has that variable set than who is running AIDA64? You can verify the list of environment variables in AIDA64 / Config / Environment.

Thank you for the info. Please try to edit the AIDA64.INI configuration file (which you can find in the AIDA64 installation folder), using a text editor like Notepad. Find the following line in there: LowLevelDellSMI=1 And change it to: LowLevelDellSMI=0 Let me know if it helps.

Don't worry, the 5 retries will be removed in the next AIDA64 beta update

You have to set a value for a particular item to make it appear among the other sensor items. It's not possible, since the name of the variable has to be fixed. And no, we do not want to add all possible values You can set an AIDA64-specific variables (A64IMP1..A64IMP10) to the value of another environment variable you would like to see there.

Does it work as you've expected?

What we usually do is put the laptop under heavy stress (like by using the FPU subtest of the AIDA64 Stability Test), watch -- well, hear -- the fans as they spin up (or as the single fan spins up), and then check if the exhaust ports really let hot air get out of the laptop chassis. In many cases, especially when the laptop is over 1 or 2 years old, dust can gather up inside the exhaust ports and that would prevent hot air from escaping the laptop chassis. And when that happens, all components of the laptop get overheated, and usually the system acts weird like throws BSoD or powers off.

Try to update the BIOS to the latest stable one, and then restore all settings to the factory default. Maybe you've used excessive overclock for either the CPU or the RAM, and that made your system unstable. Regards, Fiery

Also, I've just sent you a private message about this issue

Thank you. Your system seems to be equipped with a proprietary sensor chip or Embedded Controller chip that is currently not supported by AIDA64. Quite frankly, we don't even know the name of the chip, since it doesn't appear at any of the place where try to find such a chip Do you have any software that can show you the readings you miss from AIDA64?

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, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Yes, but please note that AIDA64 has a built-in help file as well. Just press F1 in AIDA64, or go to main menu / Help / AIDA64 Help. The built-in help may be a bit more up-to-date Regards, Fiery

Please note that most laptops can control fan speed, but cannot monitor the actual fan RPM. Regards, Fiery

Okay, just wanted to check There may still be a compatibility issue between your motherboard and the memory modules. For example, we've got a pair of HyperX DDR4-2133 modules that an ASRock Z170 chipset based motherboard cannot work stable with, but the same modules work with a similar motherboard with the same chipset (Z170) made by Gigabyte.

Make sure to check if the memory modules are running at the desired frequency, and are supplied with the right voltage for the requested frequency. FX processors can drive DDR3 modules at up to 1866 MHz, while Sandy Bridge was only DDR3-1333 capable (without overclocking, of course). Maybe your RAM was running at 1333 MHz in your old system, but now it's running at 1600 or 1866 MHz, and that makes a difference. Especially if it doesn't get the necessary level of voltage from the memory controller. How long: we generally recommend 12 to 24 hours. No, it won't stop automatically. If you don't stop it, and there's no error detected, then it will run forever

On behalf of the team, I'll take that as a compliment

Thank you for your reply. Can you please check what is the last message displayed on the bottom of the AIDA64 splash screen before the crash happens? Also, when you say crash, what exactly does that entail? Does the mouse cursor stops? Does Windows report that AIDA64.EXE crashed? Is there a BSoD thrown?

Thank you. Are you sure all your network users have write privileges (permissions) to the \\server\NETLOGON\Updater\aida64reports folder?

Thank you. Then the issue may well be in our SMBus register write code. We'll try to find out how can we improve it. I'll let you know in this topic when we have an update on this matter.