If you’re only interested in files that contribute to MmSt usage you can dump control area objects instead:
lkd> !ca 0 8
Scanning large pool allocation table for Tag: MmCa (fffffa800c600000 : fffffa800c900000)
fffffa8009d2b9c0 0000000000000000 0 File: \Windows\ServiceProfiles\LocalService\AppData\Local\FontCache-FontFace.dat
fffffa8009d2bdd0 0000000000000000 0 File: \Windows\setupact.log
fffffa800714df20 0000000000000000 0 File: \Windows\System32\winevt\Logs\Microsoft-Windows-Winlogon%4Operational.evtx
…
You can use different flags for more details, or to filter by section type (file/pagefile/image).
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Mark Cariddi
Sent: Monday, December 12, 2011 8:41 AM
To: Windows File Systems Devs Interest List
Subject: RE: [ntfsd] FileObjects in system Dump
I believe that there is a gflags setting that will cause the object manager to keep an internal list of all file objects. I can’t remember the command you use to then get a list of them, but as Don mentions you can use the !handles…
–Mark Cariddi
OSR Open Systems Resources, Inc.
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Monday, December 12, 2011 11:16 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] FileObjects in system Dump
I don’t know of a way to list all objects, you can list all handles with !handle which will get you a lot of the objects.
Hi,
I have a scenario where kernel PageMemory is being depleted. On doing
!poolused on System dump indicates that MmSt tag is main consumer
indicationg high File IO. Also, “File” tag is also consuming more memory.
From the user mode, there is no handle leak. However, I doubt that our
mini-filter might be holding reference to FileObject opened by user
mode application.Our driver is mini-filter.
Is there a way we can list all FileObject in the dump.