Thirded, because at some point, ProcessExplorer started recording the resource usage history of a process (CPU usage, memory, I/O) only the moment you explicitly opened that particular process's properties window for the first time.
Because the last version of ProcessExplorer that didn't exhibit that behaviour no longer works on current Windows versions (certainly not 10, and I'm no longer sure whether 7 wasn't already problematic, too), ProcessHacker instead it is then.
Because the last version of ProcessExplorer that didn't exhibit that behaviour no longer works on current Windows versions (certainly not 10, and I'm no longer sure whether 7 wasn't already problematic, too), ProcessHacker instead it is then.