Fiery

Thank you. I've sent you a private message about this.

Thank you! We will add the missing fan readings in the next AIDA64 beta update. I'll post a message into this topic once the new beta build is available for download.

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. Thanks, Fiery

Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://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.

I'm not sure what you mean by "true". The external IP address is polled by pinging our server, and that ping will provide the IP address of your computer. That is the true external IP address of your system.

Yes, it is.

I'd start by disabling the following options in AIDA64 / main menu / File / Preferences / Stability, and check whether it makes any difference. - Asetek LC sensor support - Corsair AXi sensor support - Corsair HXi/RMi sensor support - Corsair Link sensor support

We will add the CPU2 fan RPM reading in the next AIDA64 beta update. I'll post a message into this topic once the new beta build is available for download. As for HWMonitor, I think its eSIO temperature equals to "CPU" temperature (as it is labelled by AIDA64). While what HWMonitor reports as CPU temperature is the temperature reported as "Motherboard" by AIDA64. As far as I can tell, AIDA64 uses the right labels for thermal readings on your motherboard.

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. Finally, right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Do you have any water coolers or any special USB-connected devices that feature a monitoring solution? Like a smart PSU, smart UPS? Or maybe a USB hard drive?

I've sent you your AIDA64 product key in private message.

Thank you for checking this out. Meanwhile we've also got feedback on the correct temperature reading from a different source, and it almost matches your findings. Our corrected list would go like this: M.2 #1 --> (should be renamed to) ATX 6P M.2 #2 --> M.2 #1 DIMM --> M.2 #2 PCH --> DIMM ATX 6P --> PCH We'll alter AIDA64 accordingly in the next beta update.

That's an incomplete report that is unfortunately not useful to diagnose this issue. Please perform the report submit the way I've explained above.

Apparently not. I don't know tools that would show detailed EDID information. There must be some, but I never tried to find them.

It comes from the "Display Range Limits & Additional Timing Descriptor Definition (tag #FDh)", as dictated by the "VESA ENHANCED EXTENDED DISPLAY IDENTIFICATION DATA STANDARD (Defines EDID Structure Version 1, Revision 4)" document.

Thanks for the feedback

Thank you. Please submit a report from AIDA64 / main menu / Report / Submit Report To FinalWire. Enter "maverik1942 - Negative CPU Diode temperature reading" in the comments to let us identify your report submit and associate it with this forum topic. Thank you in advance.

We've tested the portable build of 4952, but still cannot reproduce the issue on our own Ryzen test systems. When the problem comes up, please submit a report from AIDA64 / main menu / Report / Submit Report To FinalWire. Enter "Deckard - Negative CPU Diode temperature reading" in the comments to let us identify your report submit and associate it with this forum topic. Thank you in advance.

The issue may be that the displays use a different DPI zoom setting. Do you know if that's the case? For example, the 2K display uses 150% font (DPI) scaling (zoom) while the other display uses 100% (standard setting).

Please try to launch AIDA64 while holding the left Shift key down, and try to catch the last status line displayed on the bottom of the AIDA64 splash screen. Let me know what the status line reads when the BSoD happens.

We never thought it would be useful, since it has nothing to do with the actual current drawn.

What version of AIDA64 are you using?

On the Computer / Sensor page you can modify labels by (single-)clicking on them. If you want to restore the default label, just clear the text and press Enter.

That's a rated value, not a measured value. It may or may not be accurate, and it usually should mean the maximum power the device could ever draw from the USB hub.

We've checked it on 3 different Ryzen systems, and AIDA64 Build 4952 provides the same (accurate) CPU Diode temperature readings than previous builds. Are you sure you don't have any incorrect offset configured for that reading, and also that you've restarted your system after upgrading to AIDA64 Build 4952?