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?

Along with the Logitech Arx integration, we've also come up with a new LCD module that basically acts as a web server. You can use your main computer to run AIDA64 on it and maintain its built-in web server, and you can use your other computers or mobile devices to monitor your main computer's status remotely, using nothing but a web browser. You can activate it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / RemoteSensor. Once you activated it, you can enter the IP address in virtually any web browsers to connect to the RemoteSensor. You can check the primary IP address of your computer on the Computer / Summary page in AIDA64. If it is e.g. 192.168.1.123, then enter the following in the address bar of your web browser: http://192.168.1.123 Or, in case you use a different TCP/IP port than the default http port of 80, then enter the address like this: http://192.168.1.123:8080 (if you use a TCP/IP port of 8080) Or, in case you try to use a web browser on the same computer where AIDA64 is running, you can simply use "localhost" instead of the IP address, like this: http://localhost Once you did that, you should see the AIDA64 splash screen in your web browser. It will provide you with information on the resolution that you need to use to get the most out of the LCD layout designer. On iOS devices the default setting should be close to the actual value to use, while on Android and other devices it may not match at all, so you need to change both the width and height. Please note that the Preview Resolution usually will not match the native screen resolution of your device. It's not a problem at all, and that discrepancy is due to the way web browsers manage the pixels of your screen, so don't be surprised that e.g. an iPhone 5 would report a Preview Resolution of 980 x 1360 pixels After the Preview Resolution is updated on the AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD page, you can use the same LCD layout designer that you would use for other LCD devices or the SensorPanel. Known issues and limitations: 1) Graphs and gauges are not implemented yet. We're planning to add them in the next few weeks. 2) RemoteSensor uses HTML5 SSE (Server-Sent Events) to refresh the web page, without having to reload it all the time. SSE is supported by almost all major web browsers, including Android Browser, BlackBerry 10 Browser, Chrome, FireFox, Opera, and Safari. However, it is sadly not yet supported by Internet Explorer. AIDA64 implements a trick to get around that limitation, but it sometimes will result in a mixup of the browser. If you notice that after changing the LCD layout in the AIDA64 Preferences, a strange log replaces the LCD layout in your browser, just refresh the web page. Hopefully Microsoft will finally implement SSE support in Internet Explorer 12 3) In order to prevent your mobile device from going to sleep while having the web browser open, you may need to install special apps on your mobile device. RemoteSensor has absolutely no control over the power management behavior of your mobile device. In case this is a deal breaker for you, and you've got a Logitech Gaming hardware, consider using Logitech Arx instead of the RemoteSensor. You can try the RemoteSensor in the following new AIDA64 beta update: http://www.aida64.com/downloads/latesta64xebeta Please let us know how it works on your mobile devices Thanks, Fiery

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.

I don't think it's possible to measure that.

It's most likely because AIDA64 is polling your GPU(s) and that activity prevents your video driver from putting your video card(s) to sleep.

Thank you for your feedback!

Thank you for your feedback

Please upgrade to the latest beta version of AIDA64 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 makes a difference.

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.

Thank you! Please 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 how it works.

Now https://www.aida64.com/downloads/latesta64xebeta

Best option is #2 since it wouldn't collide with Asus' own solutions. We've fixed the missing sensors in the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta I'm not sure what's happening about SensorPanel. Please check this beta and let me know if that issue persists.