Fixing 0X8007000E: Server Memory Error for New Channels

Quick Answer

Set PoolUsageMaximum and PagedPoolSize in registry to increase non-paged pool limit, then reboot. If that doesn't stick, find the driver leak with PoolMon.

I've seen this error pop up on Windows Server 2012 R2 and 2019 mostly, usually on machines running heavy print queues or terminal services. A client last month had their entire print spooler die because of this error—all printers went offline at 3 PM on a Friday. The error text says "The server does not have enough memory for the new channel," but it's not about RAM or page file. It's about the non-paged pool, a fixed-size kernel memory area that can get choked by a buggy driver or misbehaving application. Once it hits its cap, new connections or channels fail with 0X8007000E.

Fix Steps

1. Check your current non-paged pool usage
   Open Task Manager, go to Performance tab, select Memory, and look at "Non-paged pool" value. If it's above 500 MB on a server with 8 GB RAM or more, you have a leak. On clean servers, it's usually under 200 MB.
2. Increase the non-paged pool limit via registry
   This buys you time. Open regedit and go to:
   

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management

   
   Create a DWORD named PoolUsageMaximum (if missing) and set it to 60 (decimal). That tells Windows to cap pool usage at 60% of the maximum pool size instead of the default 40%. Also create or set PagedPoolSize to 0xFFFFFFFF (decimal -1) to let the system auto-grow paged pool. Reboot.
3. Restart the print spooler if printers are affected
   Run as admin:
   

   net stop spooler && net start spooler

   
   This clears queued jobs temporarily, but if the leak is from the spooler driver, it'll fill up again fast.
4. Identify the leaking driver with PoolMon
   Download PoolMon from Windows SDK or install via dism /online /add-capability /capabilityname:Tools.Graphics.DirectX~~~~0.0.1.0. Run poolmon.exe as admin. Press b to sort by bytes used, then p to sort by paged/non-paged. Look for the tag with the highest NonP value. Common leaky tags: MmSt (memory manager), File (file system), Fcb (file cache). Cross-reference the tag using findstr /m /l "" C:\Windows\System32\drivers\*.sys to find the driver file. Replace or update that driver.
5. If it's a third-party driver, disable it
   For example, if poolmon shows ACPI tags from your power management driver, disable it in Device Manager (unlikely). More common: a bad USB driver or network driver. Update the driver from the manufacturer's site, not Windows Update.

Alternative Fixes

• Reboot regularly — Set a weekly reboot in Task Scheduler to clear the pool. Not ideal but gets you running.
• Disable unnecessary services — If the leak is from Windows Search or Superfetch, stop them with sc stop WSearch and sc config WSearch start= disabled.
• Increase page file size — Set it to 1.5x RAM. Won't fix the pool limit directly, but gives the memory manager more room to breathe.
• Apply Windows updates — Some cumulative updates for Server 2019 and 2022 fix this exact pool exhaustion issue. KB5009557 and later include a fix for the print spooler memory leak.

Prevention Tips

• Monitor non-paged pool with Performance Monitor counter Memory\Pool Nonpaged Bytes. Set an alert at 400 MB on 8 GB servers.
• Don't install third-party antivirus that hooks kernel-level drivers—I've seen Trend Micro and McAfee cause this error.
• Keep all drivers, especially NIC and storage drivers, updated on the hardware vendor's page, not through Windows Update.
• If your server runs Hyper-V, check that dynamic memory isn't starving the host—set a minimum of 2 GB for the host.