1. Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Logging problem with version 0.7.7

Discussion in 'GPU-Z' started by TomWoB, Feb 16, 2014.

  1. TomWoB New Member

    Joined:
    Jun 7, 2013
    Messages:
    12 (0.02/day)
    Thanks Received:
    13
    Location:
    Switzerland
    Hi all,

    new feature "Sensor refresh rate is adjustable now" of version 0.7.7 causes a problem in case of
    • "Log to file" is switched on and
    • "Sensor refresh rate" is defined < 1s
    Because time information in log-file doesn't contain any millisecond information, e.g.:

    Date , GPU Core Clock [MHz] , ...
    2014-02-16 14:32:05 , 378.9 , ...
    2014-02-16 14:32:05 , 378.9 , ...
    2014-02-16 14:32:05 , 378.9 , ...


    So, we have ambiguous time informatin within any second and tools which handle such log-files show strange diagrams with e.g. vertical lines (like my LogViewer, see http://www.techpowerup.com/forums/threads/logviewer-for-gpu-z-available.185299).

    Solution: please add milliseconds to log-time to solve this problem:

    Date , GPU Core Clock [MHz] , ...
    2014-02-16 14:32:05.123 , 378.9 , ...
    2014-02-16 14:32:05.456 , 378.9 , ...
    2014-02-16 14:32:05.678 , 378.9 , ...


    Hope you can include this in next version of GPU-Z !
     
  2. Vlada011

    Vlada011

    Joined:
    Sep 22, 2012
    Messages:
    335 (0.44/day)
    Thanks Received:
    34
    Location:
    Belgrade, Serbia
    GPU-Z 0.7.7 wrong read VRM temps on GTX780Ti Kingpin Classified(-111C and +400C) and can't save LN2 BIOS with message BIOS reading is not supported for this device...
    Previous version of GPU-Z save both BIOS normal as 0.7.2, 0.7.5,.... FIX THAT PLEASE IN NEXT VERSION OF SOFTWARES, HWINFO64 read VRM Max Temps normal.
     
  3. TomWoB New Member

    Joined:
    Jun 7, 2013
    Messages:
    12 (0.02/day)
    Thanks Received:
    13
    Location:
    Switzerland
    Hi Vlada011,

    I agree and I'm disappointed that GPU-Z doesn't have "a simple value check if a sensor value makes sense or not" !

    I also saw a lot of values < -100°C or > 150°C. The problem is, such values destroy somehow the "Show Lowest/Highest Reading" functionality. If you log some hours, for sure you have such useless values and the useful information about lowest/highest value is gone.

    Btw, it's simple to do a minimal check: e.g. my GenericLogViewer compares any value with it's previous value. In case of temperature values "it's not allowed to have a value change more then 20 to previous value". If this is the case (value change is > 20) GenericLogViewer ignores "actual value" and takes again "same value as previous value as actual value", because I assume that value change > 20 is an error in measurement (-> no unrealistic peaks in diagrams).

    And ... another simple check for temperatures could be: ignore all values < 0°C or > 150°C !
     
  4. TomWoB New Member

    Joined:
    Jun 7, 2013
    Messages:
    12 (0.02/day)
    Thanks Received:
    13
    Location:
    Switzerland
    Very disappointing: new GPU-Z version 0.7.8 still logs without millisecond information !
    Not good in case of logging interval < 1 second ... ambiguous time information !
     

Currently Active Users Viewing This Thread: 1 (0 members and 1 guest)

Share This Page