Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12004

  • Joined

  • Last visited

  • Days Won

    525

 Content Type 

Everything posted by Fiery

  1. Fiery
    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.
  2. Fiery
    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).
  3. Fiery
    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.
  4. Fiery
    We never thought it would be useful, since it has nothing to do with the actual current drawn.
  5. Fiery
    What version of AIDA64 are you using?
  6. 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.
  7. Fiery
    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.
  8. Fiery
    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?
  9. Fiery
    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.
  10. Fiery
    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.
  11. Fiery
    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.
  12. Fiery
    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.
  13. Fiery
    I don't think it's possible to measure that.
  14. Fiery
    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.
  15. Fiery
    Thank you for your feedback!
  16. Fiery
    Thank you for your feedback
  17. Fiery
    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.
  18. 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.
  19. Fiery
    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.
  20. Fiery
    Now https://www.aida64.com/downloads/latesta64xebeta
  21. Fiery
    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.
  22. Fiery
    The above mentioned new beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  23. Fiery
    For your motherboard you can either: 1) Use AIDA64 v5.99.4900 and disable Asus WMI sensor support or 2) Use AIDA64 v5.99.4944 and enable Asus WMI sensor support Option #1 will however collide with Asus AI Suite or the BIOS interface of the sensor solution on your motherboard. So it's best to go for option #2.
  24. Fiery
    It's quite possible that Storage Executive uses a fixed thermal offset of +5 Celsius on the measured Enclosure Temperature values. If it's possible, please try to put a bit of a pressure on the drive to make it heat up over 30 Celsius, and check if the difference between what AIDA64 reports and what Storage Executive reports stays the same 5 Celsius. If yes, then we will implement the temperature offset for MX500 in the next AIDA64 beta build.
  25. Fiery
    Thank you for the data! We will fix the issue in the next AIDA64 beta update. I will post a message into this topic once the new beta becomes available for download.
×
×
  • Create New...