I'm out of office until Aug-24. Will respond to all requests upon my return. Thanks, Martin

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Unidentified column at end of log
#1
Hello! I'm using the logging function to attempt to diagnose some issues with my GPU. There is something odd going on with my logs.

The last field of my sensors should be Total Errors, under Windows Hardware Errors.

   

On a fresh boot my log is just fine. It stops at Total Errors[], in the DZ column.

   

After the system has run a couple of hours something strange happens: A new value appears at the EA column. This column shouldn't exist. There is no identification for this value. No new sensor appears at the bottom of my sensors list as well.

   

Does anyone has any clue of what is this about?
Reply
#2
Such value appears at the end of the list (last column) if during runtime a new sensor value has appeared which was originally not present. Such situations can happen if a certain sensor doesn't provide valid (or any data) at the beginning of logging, but later it does. So such value will be then added to the end of the list, otherwise the order would be broken. And since the header was already written to the log a new one including the new value is appended at the end. Scroll down to the last row and you'll see the name of that value.
Reply
#3
(01-15-2017, 09:09 AM)Martin Wrote: Such value appears at the end of the list (last column) if during runtime a new sensor value has appeared which was originally not present. Such situations can happen if a certain sensor doesn't provide valid (or any data) at the beginning of logging, but later it does. So such value will be then added to the end of the list, otherwise the order would be broken. And since the header was already written to the log a new one including the new value is appended at the end. Scroll down to the last row and you'll see the name of that value.


I couldn't understand what you meant by "the end of the list" until I stopped the log manually. The issue I'm investigating makes crashes my system, so that last line containing the sensor names never gets written.

Thank you, I'll try to catch the moment the elusive sensor appears to stop the logging.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)