Capture a short WPR trace with Pool usage, File I/O activity, and First Level Triage while the growth is occurring, then use WPA’s Pool → FMfn → Stack view to identify the allocation path and correlate it with file activity.
1. Capture allocation stacks during a controlled reproduction
WPR/WPA is the best first discriminator because PoolMon identifies the growing tag but not the call path responsible for creating or retaining the allocations. The Pool Usage profile records the pool tag and allocation stack; Microsoft’s documented pool-leak analysis pivots on Type, Paged, Pool Tag, Stack, Count, and Impacting Size.^1^
- Install the Windows Performance Toolkit from the Windows ADK if WPR/WPA is not already installed.
- Open Windows Performance Recorder as administrator.
- Select:
- Pool usage
- File I/O activity
- First Level Triage
- File logging mode
- Start recording immediately after a reboot, or just before the known rapid-growth interval.
- Reproduce for only as long as necessary—your 36-minute reproduction may produce a very large ETL. Stop after
FMfnhas increased materially. - Save the ETL, open it in WPA, then select Trace → Load Symbols.
- Add Memory → Pool and arrange the table as:
- Pool Tag
- Paged
- Impacting type
- Pool Tag Module
- Stack
- Count
- Impacting Size
- Size
- Filter to
FMfn,Paged, and preferably Impacting allocations. Expand Stack and sort by Impacting Size.
Microsoft documents that the Pool table’s stack shows the code path leading to an allocation and that Impacting allocations contribute to steady-state usage.^2^
Run comparable traces for:
- OneDrive stopped.
- OneDrive synchronizing.
- Each removable third-party minifilter absent, using the vendor-supported disable/uninstall procedure.
Because growth begins before OneDrive, do not treat OneDrive.exe or CldFlt as established causes. Compare the dominant FMfn allocation stacks and rates between runs.
2. Interpret FMfn ownership correctly
An FMfn mapping to fltmgr.sys identifies the component performing the allocation, not necessarily the minifilter whose operation caused Filter Manager to allocate it. A minifilter can request file-name information through FltGetFileNameInformation; depending on the query mode, Filter Manager checks or populates its name cache, and the returned structure is allocated from paged pool.^3^
Therefore, yes: a third-party minifilter can plausibly drive Filter Manager name-cache allocations even when PoolMon displays a Filter Manager tag. PoolMon’s tag-to-driver mapping is based on pooltag.txt, and that mapping is not complete or a causal call-stack analysis.^4^
The decisive evidence is whether WPA shows a third-party module in the allocation stack or whether controlled removal changes the allocation slope—not the mapped tag alone.
3. Use targeted Filter Verifier only after identifying suspects
Driver Verifier can deliberately crash or destabilize the machine. Create recoverable backups and use it on a test system if possible; do not select every driver or ntoskrnl.
For one suspect third-party minifilter at a time:
verifier.exe /standard /driver VendorFilter.sys
For the minimal Windows 11 Filter Verifier checks:
verifier.exe /ruleclasses 5 37 /driver VendorFilter.sys
Filter Verifier tracks Filter Manager objects including name-information structures, contexts, callback data, file objects, filters, instances, and volumes. It can report leaked reference-counted objects when the filter unloads.^5^
To disable verification:
verifier /reset
Restart afterward. Verification is most effective when restricted to named suspect drivers.^6^
4. Preserve a kernel dump at high pool usage
Configure System Properties → Advanced → Startup and Recovery → Settings → Write debugging information → Kernel memory dump. A kernel dump contains kernel and kernel-driver memory and is normally the most useful dump type for this investigation.^7^
In WinDbg:
.reload
!poolused 4
!poolfind FMfn 1
!fltkd.filters
!fltkd.frames
!fltkd.volumes
!poolused 4 sorts by paged-pool consumption; !poolfind FMfn 1 searches paged pool for that tag.^8^ ^9^ The !fltkd commands enumerate attached filters, frames, instances, and volumes.^10^
Known-issue status
The current Windows 11 25H2/26H2 Release Health information does not list this specific FMfn/Filter Manager/OneDrive pool-growth pattern.^11^ A closely matching public 25H2 report exists, but it has no accepted or recommended resolution and therefore does not establish a confirmed product defect.^12^
For Microsoft escalation, provide the WPR ETL with symbols/load instructions, high-usage kernel dump, fltmc filters/instances/volumes output, exact OS build, PoolMon time series, and matched OneDrive-on/off traces.
References
- Troubleshoot processes and threads by using WPR and WPA
- Exercise 3 - Track Driver Footprint and Dynamic Allocations During Boot
- FltGetFileNameInformation function (fltkernel.h)
- PoolMon Examples
- File System Filter Verification
- Driver Verifier
- Overview of memory dump file options for Windows
- Using the Kernel Debugger to Find a Kernel-Mode Memory Leak
- !poolfind
- Tools for minifilter development and testing
- Windows 11, version 25H2 known issues and notifications
- Windows 11 25H2 kernel pool leak: FMfn and File allocations retained ...