Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12389

  • Joined

  • Last visited

  • Days Won

    550

 Content Type 

Everything posted by Fiery

  1. Fiery
    Temperature #2 is odd, since you're supposed to have Temperature #1 (which is also called T_Sensor1) on your motherboard. PCH Diode is the internal temperature of the chipset (PCH), measured by the PCH's own thermal sensing logic.
  2. Fiery
    Thank you. I have no idea why it doesn't work, so we've ordered a Kraken X-3 device to check it out more thoroughly. Please give us 2 weeks to solve this, because most of our team is currently on vacation.
  3. Fiery
    Yes, that's how it works.
  4. Fiery
    It's odd, since AIDA64 doesn't write/alter BAR5, but only reads it. We're in contact with AMD about this issue, which seems to be due to a collision between AMD video drivers and the part of AIDA64 that detects unified shader count on AMD GCN and RDNA GPUs. I hope AMD can come up with a solution to this issue that was never a problem before. They must have changed something in one of the recent video driver updates that made the collision happen.
  5. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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
  6. Fiery
    What motherboard, CPU and video card(s) do you have in your system? Do you have Valorant Vanguard installed?
  7. Fiery
    Check what happens if you only enable the CPU subtest of the AIDA64 System Stability Test, and then what happens when you only enable the FPU subtest. The first one (CPU) will put less thermal stress on your system than the second one (FPU). Watch how the CPU temperature reacts to each of the tests. In case it crashes much quicker with the FPU subtest, then my conclusion would be that it is an overheating issue.
  8. Fiery
    Thank you for your feedback and kind words! Yes, we're already working on supporting the upcoming RTX 3000 Series "Ampere" GPUs As for the Statistics tab, the readings that you have on the Voltages tab should also appear on the Statistics tab. If that's not the case, then please send me a screenshot of both the Voltages and Statistics tab. Maximize the System Stability Test window before making the screenshots please.
  9. Fiery
    I'm certain the new CPU temperature reflects the right measurement for the CPU temperature. Here's a fix for the voltages: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works
  10. Fiery
    The above mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  11. Fiery
    Then the issue may be related to the AMD PMLog interface that AIDA64 uses to monitor Vega and Navi GPU based video cards. Please try to disable GPU sensor support in AIDA64 / main menu / File / Preferences / Stability and restart AIDA64 to apply the changes.
  12. Fiery
    Thank you, we'll implement those tricks in the next AIDA64 app update.
  13. Fiery
    Thank you! We'll make sure the next AIDA64 app update will detect Bluetooth version as 5.0 on your TV.
  14. Fiery
    Do you get proper results for the benchmarks that you can access from the left tree menu of AIDA64 main window, like CPU Queen or FPU Julia?
  15. Fiery
    Please post into this forum in English if possible.
  16. Fiery
    Thank you, those seem to be normal. Can you please post a screenshot of the Computer / Sensor page of AIDA64, showing all sensor readings ideally on a single picture? Or, you can use the right-click context menu on the Sensor page to copy the data to the Clipboard and paste it here, into the topic.
  17. Fiery
    Thank you! The issue may be related to your video card then. Do you have an nVIDIA video card in your computer?
  18. Fiery
    It's coming soon. Please don't mix support for that screen into this topic though.
  19. Fiery
    Try to ask Matrix Orbital about those issues. To me it seems to be a hardware failure or hardware configuration issue.
  20. Fiery
    These are respectful numbers indeed. Can they be better? I don't know, since we're not skilled in OC here at FinalWire Others may be able to chime in and give you more meaningful feedback on the OC achievements.
  21. Fiery
    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 --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  22. Fiery
    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. Thanks, Fiery
  23. Fiery
    There's no error log. You CPU made a glitch in its pipeline, but it's not possible to tell what caused the error, since it could be like 5 components of the CPU itself, and also buses on the motherboard, RAM modules, etc.
  24. Fiery
    We currently have no plans to support that display.
  25. Fiery

    dell

    Fiery replied to ququruvu's topic in Hardware monitoring

    Hard to tell, since Dell doesn't publish how it measures temperatures in its software. Most likely everyone's right, and your system has multiple thermal sensors.
×
×
  • Create New...