Fiery

We've checked it, and both EXS_FAN_1 and EXS_FAN_2 should already be measured as long as they are spinning (provide a non-zero RPM readout). However, their label in AIDA64 will be Chassis #5 and Chassis #6 respectively. Fan #21 is the fan connected to your Kraken device.

Thank you! Please upgrade to the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.

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

We've fixed that bug in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Please let me know how it works.

Thank you, that was a big help. We've fixed the sensor readings on your motherboard in the following new AIDA64 Engineer beta update: https://www.aida64.com/downloads/latesta64eebeta Let me know how it works.

I've already stated above that it's not possible to do that with AIDA64 right now.

Please let me know which temperatures are still missing. The following temperatures should already be measured on Radeon VII: - Edge (as "GPU" temperature) - Mem (as "GPU Memory" temperature) - VR VDDC (as "GPU VRM" temperature) - VR MVDD (as "GPU VRM1" temperature) - VR SoC (as "GPU VRM2" temperature) - HotSpot (as "GPU Hotspot" temperature)

You need to use either Fraps or RTSS (Rivatuner Statistics Server) to measure FPS during gaming. Once you have one of those software set up, you can use AIDA64 to communicate with that software and get the readings from them and display them in AIDA64 in some way (like SensorPanel, OSD Panel, etc).

A straight green line and a constant 0% throttling is actually the best thing It means your CPU is not overheating and not slowing (throttling) itself down because of it.

After that 20 seconds delay you need to install the custom driver. And only after the driver is installed AIDA64 will be able to pick the device up as a USB device.

We've added support for Samsung SPF Digital Photo Frames. It works with the following models: SPF-72H SPF-75H SPF-76H SPF-83H SPF-85H SPF-85P SPF-86H SPF-86P SPF-87H SPF-105P SPF-107H 700T 800P 800W 1000P 1000W The following models are not supported at this time: SPF-72V SPF-83V SPV-105V The following models do not support Mini Monitor Mode, and so AIDA64 cannot use them as an external LCD: SPF-71E SPF-71ES You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Samsung. For the most stable operation it is recommended to uninstall Samsung Frame Manager and Mini Monitor drivers, and install our own Samsung SPF LibUsb driver instead: http://download.aida64.com/resources/lcd/samsung_spf_lcd_driver.zip Our driver can directly communicate with the device, without interfering with Samsung's drivers or the Frame Manager software. Alternative solution is having the appropriate Samsung SPF Windows drivers installed (part of Samsung Frame Manager software), but that usage scenario is not guaranteed to work properly. Notes: - If the device disconnects after a few seconds, enable the option Send keep-alive packet in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Samsung - AIDA64 will switch the device from Mass Storage Mode to Mini Monitor Mode if necessary. That transition could take up to 10 seconds. When the switch takes place, and there's Samsung Frame Manager software installed, Windows Aero may get disabled by Samsung Frame Manager's Mini Monitor feature - AIDA64 has a built-in facility to prevent collisions with Samsung Frame Manager. In case it fails to work, and AIDA64 frames collide with Samsung Frame Manager frames, then terminate the process called "sam_controller.exe" via Windows Task Manager, or uninstall Samsung Frame Manager - If Samsung Frame Manager is installed, but its Mini Monitor feature is not used, it's recommended to disable the Samsung Monitor device in Device Manager / Display Adapters. You can find the new AIDA64 beta update at: http://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD device that is currently unsupported by AIDA64. BTW, Futaba MDM166A VFDs and Yoctopuce OLEDs are also supported now by the latest AIDA64 beta. Regards, Fiery

Does the whole computer (Windows) freeze or only the keyboard becomes unusable?

Thank you! How does the latest beta work about your fans?

Please post a pair of nVIDIA GPU Registers dump and nVIDIA SMBus Dump, along with a similar shot of EVGA Precision+AIDA64 side-by-side that you've shown for at least 2 states. One state is where fans are spinning at a low speed (e.g. idle), and one where you've manually set the fans to spin at 100% (maximum RPM). That way we can put the pieces of the puzzle about iCX2 together hopefully It's really not easy, because Precision seems to combine RPM values coming from not only iCX2, but ForceWare as well.

Thanks for the feedback. The new items should be available for the SensorPanel automatically -- but they're not added to the SensorPanel layout automatically. You need to right-click on your SensorPanel --> New, and pick the item you're looking for.

We will implement the requested changes in the next AIDA64 beta update. I will let you know in this topic once the new build becomes available for download.

Thanks for your feedback!

What we've just rolled out with AIDA64 v4.60 is only the first wave of new LCD and VFD devices. If you consider interface, protocol, controller and all other variables, there are literally hundreds of different LCD/VFD devices out there. We're already working on a number of new devices (Acer Idea 500, AX206-based firmware-hacked DPF, ct-Mausekino, Cwlinux, Futaba MDM166A, picoLCD, SoundGraph iMon UltraBay LCD, Sure Electronics, Trefon, Yoctopuce, etc) that will be added during the next few weeks, and then a lot more is coming. We're collecting ideas on which displays to support next, so feel free to let us know what display you've got, or what display you want to see being supported by AIDA64. Make sure to state display manufacturer, display model, interface (USB, serial, parallel, I2C, etc), and if possible, show us the device you've got by posting a link to the product page or a hardware review. If your unsupported LCD/VFD uses USB connection, please post a USB dump of it: right-click on the bottom status bar of AIDA64 v4.60 --> System Debug --> USB Dump. Copy-paste the full results into this topic. Regards, Fiery

Maybe the values become too low When the DL/UL rate is for example 3 KB/s, the MB/s value would be 0.0029 MB/s. With 2 decimals it is displayed as 0.00 MB/s.

Thanks for the feedback!

Yes, and already added support for it in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta You can activate the Rival 710 OLED module in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / SteelSeries. Let me know how it works.

Thank you. We've improved on Radeon VII support in the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta On the Display / GPU page the new update should measure GPU clock and memory clock properly now, and should display a whole bunch of sensor readings on the Computer / Sensor page as well. Please let us know how it works on your Radeon VII cards.

The above mentioned new AIDA64 beta build is available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works

We've implemented a trick in the latest AIDA64 beta build (available at: https://www.aida64.com/downloads/latesta64xebeta ) where if you specify the measurement unit as GHz for clock frequency items, the value will be divided down by 1000 to display the frequency in GHz. I hope you will find it useful for your purposes BTW, a similar trick was already available for network download/upload rate items where you can specify the unit as Mbps or MB/s to convert measurements to a more meaningful value. Same for total network download/upload items where you can specify GB as the unit.

This is really puzzling... The issue must be related to the kind of card you've got (that it's a mining adapter and not a video adapter). We've ordered an Asus Mining-P106-6G board to try and replicate the issue here and dig down deeper. I apologize for the delays in fixing this issue. I'll update you in this topic once we've got the mining card.