Fiery

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?

The CPU Diode thermal reading is measured using the on-die thermal diode of your CPU. If it shows an invalid reading, it can mean either that a certain offset has to be applied on the readings; or the CPU provides an invalid thermal reading for some reason. Please verify the CPU Diode reading using HWMonitor, and let me know if it shows a similarly incorrect value or not.

Do you have any labels that you previously have renamed on the Computer / Sensor page? The two PCH values should be correct, since one of them ("PCH") comes from the EVGA Z390 Dark MCU, but the other ("PCH Diode") comes directly from the chipset of your motherboard. The thermal reading labelled as "DIMM" should indicate the one that's labelled as "VDIMM VRM" in the UEFI Setup. There's a glitch about showing ATX 6P thermal reading. We will fix it in the next AIDA64 beta update. As for the two M.2 temperatures, they come from the EVGA Z390 Dark MCU, while the two bottom thermal readings showing your SSD temperatures come directly from your SSDs. They have no direct relation to each other, and they are all meaningful readings.

That's what the monitor reports as its capabilities via the standard VESA EDID block. You can verify that information by checking the EDID details using other diagnostics software.

We've found 4 additional thermal rails on your motherboard that provide seemingly valid readings. We'll add them in the next AIDA64 beta build. I'll post a message into this topic once the new beta update is available for download.