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.

Thank you. Do you mean both in terms of reliability of SPD readout and performance of SPD readout? Or you've just checked it once and it was all fine?

When does the crash happen? When you start AIDA64 and while it is showing its splash screen? Or when you click on the Computer / Sensor page? Thanks, Fiery

Which reading do you mean exactly? I can't find an association in the Task Manager between a process and a utilization value for a specific drive.

We've updated the RGB LED module with the following improvements: - new item type: All Keys - new item type: Mouse - support for Corsair Strafe RGB keyboard - support for Logitech G13, G19, G19s keyboards (has to be configured as All Keys) - support for Corsair M65 RGB, M65 Pro RGB, Sabre Optical RGB, Sabre Laser RGB, Scimitar RGB mice - support for Logitech mice (has to be configured as All Keys) - support for Razer Chroma mice - support for Razer Chroma SDK v1.1 It's available in the latest beta version of AIDA64 Extreme at: http://www.aida64.com/downloads/latesta64xebeta

No, it's definitely not artifical Are you using the 2 memory sticks in the same memory channel? Note that the more DIMMs you use in a memory channel, the less stable your memory controller will work at. Usually it's not a problem, but when you overclock your system or use agressive memory timing configuration, the system can get unstable if you use more than 1 memory module in a memory channel. Also, not all memory modules are designed to work stable when they are not the only memory module in a memory channel.

I suppose it is a temporary fan RPM readout issue of the motherboard sensor chip. On your system AIDA64 simply reads the fan RPM value out of the sensor chip, without converting it. So if it shows 19640 RPM, that's the value that the sensor chip provides.

Can you please check how CPU-Z and HWiNFO64 behave about SPD readout stability and performance?

Thank you for the feedback PCH Core temperature is not related to your CPU, but to the motherboard chipset, also known as PCH (Platform Controller Hub). PCH Core temperature is motherboard specific, and your current motherboard does not monitor such a temperature reading.

Thank you for the feedback. We can remove the 5 retries on the bank switch writes, although it would best if we could try finding out what causes the SMBus issues on your system

It could be due a number of issues. CPU cache malfunction, CPU hardware failure, RAM CRC error, motherboard failure, power supply unit failure, too excessive CPU overclocking, too strict memory timings configured, an overheating system component, etc. I'd try updating the motherboard BIOS first, then restoring all BIOS Setup settings to their default values. If it doesn't help, then check the temperatures and voltages both idle under load. If they show no issues, then you will need to try replacing parts one by one. It's not easy to diagnose such issues remotely though Regards, Fiery

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

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

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

As for the SPD detection anomaly, please upgrade to the latest AIDA64 Extreme beta update available at: http://www.aida64.com/downloads/latesta64xebeta Let me know if it helps. Please note that due to the nature of the issue, and since we've never seen similar issues on other systems, I still have to assume that it is caused by another software or service running in the background, polling the SMBus, without using synchronization mutex. It may be related to the UEFI BIOS or Windows 10, although even with such combination we've never got reports of similar issues from other users. So there must be some pecularity about your configuration...