Fiery

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

2) Thank you for the data. Try to find the file called SiUSBXp.dll on your system, and let me know which path do you have it stored at. AIDA64 tries to load that file to activate Kraken sensor support from multiple paths, but maybe on your system it's at a non-standard location. Then, as a temporary solution, you can try copying the DLL into the installation folder of AIDA64. I suppose it will work that way too, please let me know how it goes. 3) No, AXi is not supported via USB connection either. It uses a special USB protocol that is tough to handle. HXi and RMi are way better about the USB protocol.

1) Unfortunately Sabertooth Z170 Series use a special EC muxing method that is very difficult and dangerous to handle by 3rd party software like AIDA64. Asus still refuses to implement the necessary industry standard mutexes to avoid collisions with other monitoring software. And when a collision occurs due to the EC mux, system could lock up. So we cannot risk implementing the EC mux in AIDA64. And without using the EC mux, it's not possible to access several fan header readings 2) Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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. 3) Corsair Link is not supported by AIDA64, and we do not plan to support it. Corsair HXi and RMi Series PSUs are supported, but only when they are directly connected to a USB header of the motherboard. 4) Are you sure the fan is spinning? AIDA64 will only pick up the GPU fan and show it on the Computer / Sensor page when it is spinning. It will not show 0 RPM there, but instead hide the relevant line about the GPU fan.

There's no need to define or maintain multiple pages. What you could do instead is set a larger layout size than what your phone/tablet display supports. E.g. on a iPhone 5S, the default layout size to use is 980 x 1648 pixels. If you define the layout size as 1960 x 3296, you can have basically 2x2 pages, and you use swipe navigation and pinch zoom to show a certain part of the layout on the screen.

Make sure to add items on Page 2..4, and then try to touch the LCD near the left and right edge to change page. It should work fine as long as the Strike7 SDK properly passes the touch events to AIDA64.

OpenCL.dll doesn't belong to AIDA64 at all. It belongs to the video driver and/or your CPU driver. Try to reinstall your video driver, and see if it helps. If not, then just disable (untick) the GPU subtest in the AIDA64 System Stability Test window to prevent it from using OpenCL.

Thank you for the feedback

Your proposed setup will work fine, since multiple panels of different kind is fully supported. What is only partly supported is having multiple devices of the same kind, like two Samsung SPF devices. Some of the device kinds are supported that way too, but some others aren't, so it's a case by case basis.

We've looked into it, and it seems the only way to detect a custom TJMax configuration (initiated by a BIOS Setup option) is by using a non-documented interface of Intel processors. And using that interface is quite dangerous, since it is linked to the FIVR (integrated VRM) of the CPU, so if anything slips, your CPU may just get a voltage spike that causes irreversible damages. And we don't want to go down that path But if you know the right TJMax temperature value, then you can specify it in AIDA64 / main menu / File / Preferences / Hardware Monitoring.

We will implement the requested new feature in the next AIDA64 beta update (due next week). You will be able to define up to 10 environment variables (A64IMP1..A64IMP10) that AIDA64 will pick up and let you display on the OSD Panel, Sensor Panel, LCD, etc.

We've checked, and NIC1 and NIC2 are not mixed by AIDA64. So please make sure to check your configuration, to make sure you really have configured the 2 sets of graphs for different NIC indexes.

Thank you for the feedback. The missing temperatures of CPU Package, CPU IA Cores and CPU GT Cores will be added in the next AIDA64 beta update due next week. The other missing values are platform specific, so they are only available on such motherboards that support those readouts. The mentioned 3 temperatures are CPU specific, since they are measured by the CPU itself, so they can be measured independent from the underlying motherboard.

Can you please let us know the command-line you use to launch AIDA64 from your logon script? Thanks, Fiery

Thank you for the feedback

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 me know if it helps. Thanks, Fiery

You can find the mentioned new AIDA64 Extreme beta update at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Thank you for the data. 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 me know if it helps. Thanks, Fiery

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 me know if it helps. Thanks, Fiery

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 me know if it helps. Thanks, Fiery

BTW, we've checked it out, by installing the tool called "Desktop Gadgets Revived 2.0". And it works fine with the AIDA64 Desktop Gadget on our Windows 10 64-bit TH2 test system. You just need to right-click on the Windows Desktop --> Gadgets to enable the AIDA64 gadget. On Windows Vista and Windows 7 AIDA64 can automatically activate the gadget, but with this tweak (I mean Desktop Gadgets Revived) you have to place it on your Desktop manually.

Thank you, we'll check it out. I'm not sure what does the Samsung frame has to do with the Desktop Gadgets or SensorPanel though. I hope you know that you can use the SensorPanel and the LCD module in the same time Just because you have a Samsung frame, it doesn't mean you cannot use the SensorPanel along with it If you only need a few items on it, you can configure the SensorPanel easily to suit your needs.

Thank you for the data. We will fix the issue in the next AIDA64 beta update due in a few days from now. Regards, Fiery

Which 3rd party layer do you mean? Where can we download and try it? BTW, AIDA64 SensorPanel is a lot more flexible than the Desktop Gadget module: http://forums.aida64.com/topic/667-share-your-sensorpanel/

Make sure to restart Windows after the upgrade. If it doesn't help, then 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. Thanks, Fiery