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...

AFAIK Commander Mini uses the Corsair Link framework which we do not support in AIDA64.

AFAIK it's not possible to detect that under Windows

BTW, we've checked, and haven't found any ways to programmatically control the backlighting of Deathstalker Ultimate keyboard. Do you have any software that can do that, besides Razer Synapse? Or maybe you know of an API or SDK that can be used for that purpose? The SwitchBlade UI SDK that is used to control the integrated LCD screen and dynamic keys do not seem to implement a method to control the keyboard backlighting

No, I'm sorry, but AIDA64 doesn't support Corsair Link. It does support certain PSUs like Corsair RMi and HXi, but only when they are connected to the motherboard directly via USB. Regards, Fiery

The requested feature will be implemented in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new beta is available for download.

Thank you. Somehow enumerating SPD memory modules takes a very long time on your system. Are you sure you don't have any other software running in the background that may read (poll) memory modules or other SMBus devices like sensor chips? Asus AI Suite, HWiNFO, HWMonitor, CPU-Z, SIV come to mind...

With UEFI boot the classic BIOS regions do not exist anymore, but they can be emulated. However, in case your motherboard fails to emulate those regions properly, it is only a cosmetic issue that doesn't cause any actual problems. Thank you for the data. It seems your memory modules sometimes fail to change the DDR4 SPD bank. Current DDR4 platforms use a proprietary method to switch between the 2 SPD banks, and even though we use the switch "by the book", it doesn't seem to work reliably on your system. It works fine on other systems though. We'll have to do more test runs on our own DDR4 test systems to find out what can we do about this. I suppose by trying to perform the bank switch 5 times (instead of just once, like now) it could work on your system too, but maybe there's a better solution than that. I'll keep you posted in this topic about this issue. I suppose one of the hardware monitor modules run longer than before. It can be caused by a hardware component or driver behaving differently now than before. Please create and post a Sensor Debug --> Sensor Profiling Dump. That provides vital information on the init and poll performance of the AIDA64 hardware monitor modules.

Thank you, we've forwarded your message to our friend who's responsible for the Portugese (Portugal) localization of AIDA64.

SM_SLOWMACHINE Nonzero if the computer has a low-end (slow) processor; otherwise, 0. You can find more info on those entries (around "Slow Processor") at: https://msdn.microsoft.com/en-us/library/windows/desktop/ms724385(v=vs.85).aspx Regards, Fiery

No, it's not possible to customize the Statistics columns. It may be possible to save the last column widths, but even if we do that, it wouldn't be helpful in your case. Because the basic rule about saving column sizes is that when you set one column to zero width (to effectively hide the column), the next time the column will be restored to its original size. This is to avoid users not being able to restore a previously hidden column. We do have plans about localizing the System Stability Test, but first we have to completely redesign it. It's a bit of a challenge, because it's not easy to come up with a layout that is both suitable for hardcore users and average Joes...

Those are indeed intruiging ideas We'll work on them Do you own an RGB mouse?

The motherboard ID and video BIOS date problem are both caused by UEFI boot. Some motheboards fail to emulate the classic system BIOS (F0000) and video BIOS (C0000) segments. Motherboard ID is not that useful information these days anyway, and you maye able to see the video BIOS date on the Display / GPU page where it is read from the GPU directly. As for the SSD temperature, that is read directly from the SSD, without any offset or otherwise influencing the value the drive provides. You can verify the measured value by checking it with HWMonitor and HD Sentinel. As for the SPD issue, please 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. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

That's quite odd Maybe an anti-virus software moved it there? Please note that it could cause issues with other software like NZXT CAM as well. You may want to copy the file into CAM's installation folder as well, just in case