Recent content by Martin

  1. Martin

    [Solved] Recent AM5 mobo shows weird VINx voltage readings

    OK, I will adjust the auto scaling in the next build.
  2. Martin

    [Solved] Recent AM5 mobo shows weird VINx voltage readings

    Ah, that's just scaling of the graph, not indication of 2.12V measurement. If the value is constant, the upper graph value is automatically increased.
  3. Martin

    [Solved] Recent AM5 mobo shows weird VINx voltage readings

    Is that 2.12V also recorded in Max column of sensors window? If yes, it might be due to running some other monitoring/fan/RGB control along with HWiNFO.
  4. Martin

    HWiNFO v8.25-5720 Beta released

    HWiNFO® v8.25-5720 Beta available. Changes: Fixed DIMM polling on AMD TRX50/WRX80/WRX90 systems. Fixed ACPI sensor synchronization. Enhanced workaround for Kingston Fury Beast RGB DIMMs. Added scaling of OSD x-axis based on width. Improved assigning of OSD position when adding items. Enhanced...
  5. Martin

    HWInfo Pro Auto Log

    Looks like the problem is in parsing of arguments supplied to command executed by "cmd". Try to store into a folder without space name, so e.g.: $command = '"C:\Program Files\HWiNFO64\HWiNFO64.exe" -lC:\Users\HWInfoLogs\' Or don't execute via cmd.
  6. Martin

    HWInfo Pro Auto Log

    Syntax should be same. Try to create a batch file (bat or cmd) and execute that one from PS.
  7. Martin

    Can't Monitor NPU Metrics (RAM, Utilization, Power) In Qualcomm(R) Hexagon NPUs.

    Unfortunately Qualcomm doesn't provide any information about NPU metrics. We have requested this (and several other information) long ago, but getting anything above standard public information is almost impossible (not even under NDA).
  8. Martin

    HWInfo Pro Auto Log

    The "Date/Time Format" in sensor settings refers to format inside the CSV log file (the date/time column), not the file name. The time-stamp used in log file name is just to make the name unique and it's using the "tick count" which is the number of milliseconds since the computer started...
  9. Martin

    HWiNFO64 crashes when closing

    Hmm, the attached Debug File doesn't indicate any abrupt termination of HWiNFO, so the problem must happen at application cleanup. I noticed that you have an Intel B-series GPUs. We have observed such problem during HWiNFO termination due to some issue in Intel graphics drivers. Please try to...
  10. Martin

    t_sensor not visible under Asus EC

    Try the latest Beta version v8.25, that should have this issue fixed.
  11. Martin

    Missing sensors

    Those sensors aren't missing, they are just not shown in UI because of a large column width. Try to shrink the window and then adjust column widths by moving the column header "|"
  12. Martin

    dGPU always on

    Then it must be a bug in drivers.
  13. Martin

    dGPU always on

    Are you using the latest HWiNFO version?
  14. Martin

    Wrong CPU power readings after sleep state

    Fast boot is a software feature, it should have no impact on hardware power monitoring. The "inaccuracy" of power reporting is due to transient changes to internal counters/timer.
  15. Martin

    Wrong CPU power readings after sleep state

    Power reading works using a differential method - there are 2 energy samples collected at different time points (polling cycles) and the difference between them divided by time delta is the power result. A system sleep or reboot turns off (or resets) several blocks in the CPU so if one sample...
Back
Top