Fiery

I'm afraid we don't have any information on that Renesas chip, and it doesn't seem to be compatible with older PWM chips. We'll need to get the datasheet of that chip to implement support for it.

We've fixed the Intel ARK link to work properly. As for https, it should work automatically as http websites should be automatically redirected to their https counterpart. Yes, I'm aware of the fact that not all website admins are attentive enough to make it happen, but they all should.

Awesome!

We've tried to replicate the issue using our own 800P device. Apparently it works properly under Windows XP, but under Win7 and Win10 the device fails to accept the "switch to mini-monitor mode" command when AIDA64 issues it. Even more strange is that it fails to accept the command when Samsung's own Frame Manager software issues it. So the device seems to be unable to work at all in mini-monitor mode with Windows 7 and Windows 10 We've tried to come up with a workaround, but no luck so far. We will try to figure out a special way to talk to the device, in a hope that we can get it somehow to switch to mini-monitor mode using alternative methods.

Try to uninstall AIDA64, and install the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know if it makes a difference.

No, because there're hundreds of places in our code where such an issue could happen if we're not 100% careful So it's tough to find the place without knowing more about the event that triggers the issue.

Less than a month from now

Try to remove all AIDA64-related entries from the Registry. Start REGEDIT.EXE, navigate to: HKEY_CURRENT_USER\Software\FinalWire Right-click on AIDA64 (inside FinalWire in the left tree) --> Delete --> Yes

Please note that it's not possible to diagnose such issues remotely. You may want to take your phone to a local specialist and have it checked out.

It is detected using various detection methods and built-in hardware databases. It's not possible to edit that string.

It's odd that they are not listed among the other sensor items. Can you see the Radeon VII thermal readings on the Computer / Sensor page?

Awesome, thank you for your help and feedback!

Thank you for your feedback!

Awesome, thank you!

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.

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