High non-paged pool memory usage on S2D failover clusters - refs.sys?

Peter Camps 20 Reputation points
2026-10-02T11:39:36.0833333+00:00

After several updates in August 2026 (Windows updates (KB5101372), secure boot certificates and HPE SPP P95170_001_gen10spp-2026.05.00.00-SPP2026050000.2026_0527.9 we are experiencing what looks like a memory leak on all Windows 2025 Core Hyper-V servers in S2D failover clusters. The non-paged pool is steadily increasing and eventually leads to a non-responsive host. After a reboot the non-paged pool starts at about 5 GB and eventually grows to several hundreds GB.

Poolmon shows after reboot about 1 week ago:

User's image

Refs.sys shows high usage. The version of refs.sys was 10.0.26100.33158. After discovering the problems we started installing KB5122871 and got refs.sys version 10.0.26100.33438. But the problem is still unresolved. At this moment we need to reboot the Hyper-V servers every few weeks to bring the non-paged pool usage back down.

We are using HPE Proliant DL380 Gen10 Plus servers with NVMe drives, Intel(R) Ethernet Network Adapter E810-XXVDA4 NIC's.

All storage is configured as 3-way mirror with CSVFS_ReFS

Windows Server Core 2025

But even in my small (virtual) test cluster i can see that the non-paged pool is steadily increasing. This is a nested Hyper-V cluster with no third party drivers.

Anybody experiencing the same issue? Or have a resolution for this problem?

Peter Camps

Windows for business | Windows Server | Storage high availability | Clustering and high availability

7 answers

Sort by: Newest
  1. Peter Camps 20 Reputation points
    2026-11-19T09:50:05.84+00:00

    Has anybody already installed KB5131080 (OS Build 26100.33822) - November 10 update? ReFS.sys version 10.0.26100.33822.

    I installed this yesterday on our 2-node S2D cluster and to my surprise it looks like the the MSPi growth is a lot less than it used to be. My virtual testcluster is also showing the same symptoms. Maybe it is a bit early to celebrate (a little bit), it has only been 20 hours since I updated 1 cluster, but maybe somebody else can confirm this.

    I will keep you posted, let's see how it performs after next weekend.

    Peter.

    Was this answer helpful?


  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Fedor Travinsky 10 Reputation points
    2026-10-21T10:01:44.59+00:00

    We see the same MSPi non-paged pool leak on a Windows Server 2025 S2D cluster (4 × Dell R640, CSVFS_ReFS, two CSVs: 9 TB NVMe mirror + 18 TB hybrid). Build 26100.33438 (KB5122871), refs.sys 10.0.26100.33438, so the September CU does not fix it for us either.

    One node reached 40,066,531 MSPi allocations = 152.8 GiB non-paged pool after 24.8 days uptime (384 GB RAM); MSPi was 99% of all NP pool.

    1. Growth is tied to CSV ownership

    • Owning one CSV: ~6 GB/day. Owning both: ~17 GB/day (~18,000 allocs vs ~3,000 frees per minute).
    • Nodes owning no CSV: MSPi stays near zero (0.01 GB on a node running 12 VMs).
    • After moving the CSVs off a node, growth stops immediately (0 allocs/frees per minute), but the memory is never released. Only a reboot frees it.

    2. Live kernel dump (LiveKD -ml) of the affected node

    • !poolused 2 MSPi: 40,066,531 allocs, 164,108,436,752 bytes, Minstore generic/untagged allocation, refs.sys
    • Every allocation is a large page allocation of exactly 0x1000 bytes.
    • 24 blocks sampled across ~1.48M hits from !poolfind MSPi -nonpaged -large are byte-for-byte identical: 512 bytes of data, the rest zero, no pointers to code or kernel objects.
    • Those 512 bytes are a GPT protective MBR (LBA 0):
    Offset Bytes Meaning
    0x000 33 C0 8E D0 BC 00 7C … Windows MBR boot code
    0x1B8 00 00 00 00 Disk signature 0 (GPT)
    0x1C2 EE Partition type: GPT protective
    0x1C6 01 00 00 00 Starting LBA 1
    0x1CA FF FF FF FF Size: disk > 2 TiB
    0x1FE 55 AA Boot signature

    So it looks like refs.sys (Minstore) repeatedly reads sector 0 of a large GPT disk, most likely the CSV virtual disk, into a 4 KB non-paged buffer that is never freed. At ~6 GB/day that is roughly 17 reads/sec per CSV on the coordinator.

    How to check your own nodes

    poolmon -b                                        # MSPi Nonp bytes per node
    Get-ClusterSharedVolume | ft Name, OwnerNode      # compare with CSV owners
    !poolused 2 MSPi                                  # in a dump
    !poolfind MSPi -nonpaged -large                   # then db <addr> on a few hits
    

    Interim mitigation: watch MSPi per node, move CSVs away and reboot before NP pool gets critical. A live dump is available if Microsoft wants it.

    Was this answer helpful?


  4. Andy Taylor 0 Reputation points
    2026-10-20T08:52:05.58+00:00

    Hi @Peter Camps Did you get anywhere with this? We're having exactly the same issue with a 2 node 2025 Datacenter Hyper-V cluster. CSV Ownership seems to trigger this increasing MSPi allocation. We're seeing approx 1GB an hour until the host becomes unresponsive.

    Was this answer helpful?


  5. Peter Camps 20 Reputation points
    2026-10-15T08:40:30.1466667+00:00

    Yesterday i upgraded the firmware and drivers of the Intel(R) Ethernet Network Adapter E810-XXVDA4 to 5.00 (firmware) and 1.21.114.0 (drivers) on a 2-node cluster. But looking at the graphs today it is still slowly growing.

    At this moment I am growing out of options. There is a new update (KB5126646) which again introduces a new refs.sys but I installed this on 1 cluster and it changed de refs.sys version but not the issues we are having.

    Peter

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.