I'm not sure what I'm seeing. It looks like a given process id sometimes reports different image file names at different times, without getting a "process termination" notification for that process id.
I've written an IRP logger that tracks activity on my dev machine so I can better determine how our driver is functioning, and how it handles different situations. In logging an IRP, we record the requestor process id, along with other information, and queue it for the logger. The logger then uses PsLookupProcessByProcessId() to get a PEPROCESS, then ObOpenObjectByPointer() to get a handle, finally ZwQueryInformationProcess(ProcessImageFileName) to get the image name.
This logger also hooks process creation/termination notifications (PsSetCreateProcessNotifyRoutineEx()) and logs those.
Most of the time the IRP logger reports a consistent process image name from IRP to IRP, and the process creation and termination events agree with what is occurring. Some process ids, however, tend to give different process image names at different times, without intervening process termination and creation notifications. Usually, if not exclusively, the processes doing this are OS utilities such as backgroundTaskHost.exe changing to Windows Defender or vice versa.
It looks like you're new here. If you want to get involved, click one of these buttons!
|Upcoming OSR Seminars|
|Developing Minifilters||29 July 2019||OSR Seminar Space|
|Writing WDF Drivers||23 Sept 2019||OSR Seminar Space|
|Kernel Debugging||21 Oct 2019||OSR Seminar Space|
|Internals & Software Drivers||18 Nov 2019||Dulles, VA|