Windows System Errors
No System Resources
0x800705AAReviewed for reference consistency: August 11, 2026
kernel-level pools are too depleted to service the request
What 0x800705AA Means
The 0x800705AA error on the Windows System Errors indicates no system resources — kernel-level pools are too depleted to service the request. This typically occurs due to nonpaged or paged kernel pool reached its configured ceiling.
Kernel bookkeeping has ceilings of its own, and exhausting them returns 0x800705AA, Win32 error 1450, ERROR_NO_SYSTEM_RESOURCES — 'Insufficient system resources exist to complete the requested service'. The message deliberately avoids the word memory: the shortage sits in fixed-size kernel pools and heaps, structures that do not grow with a page file.
How to fix 0x800705AA
General informational guidance, not professional advice. Commands can affect your system or data — back up first and proceed at your own risk. FixerCode is an independent reference, not affiliated with any vendor mentioned.
Watch the kernel pool counters
Paged and nonpaged pool sizes against their historical behavior reveal whether the shortage is a leak or a spike.
Get-Counter '\Memory\Pool Nonpaged Bytes','\Memory\Pool Paged Bytes' | Select-Object -ExpandProperty CounterSamplesFrame the shortage against commit capacity
Commit figures contextualize the pool numbers: a system far from its commit limit but failing calls is pointing at pools, not RAM.
Get-CimInstance Win32_OperatingSystem | Select-Object TotalVirtualMemorySize, FreeVirtualMemory
Technical Background
The distinction from plain out-of-memory is architectural. Physical RAM and commit capacity can be extended or grown; kernel pools and desktop heaps have hard limits tuned for expected workloads. A machine can hold gigabytes of free memory and still refuse an allocation from a pool that is full, which is why the error can appear on systems that look idle and roomy in Task Manager.
WinError.h groups several related constants in this range — nonpaged pool (1451), paged pool (1452), working-set and pagefile quotas (1453-1455) — each naming the specific resource it measures. ERROR_NO_SYSTEM_RESOURCES is the general form, and its presence usually means one of those specific ceilings has been reached by an accumulating consumer rather than by any single large request.
Common Causes
- Nonpaged or paged kernel pool reached its configured ceiling
- Desktop heap exhaustion in a session crowded with processes and windows
- Sustained handle or GDI growth leaking a limited kernel resource
Typical Scenarios
- A server workload with many connections or file objects drives paged pool toward its limit and new operations start failing
- A session hosting hundreds of windows and GDI objects exhausts its desktop heap
- A driver leak grows nonpaged pool over days until routine calls begin returning the code
What to Know
Pool counters over time separate a spike from a leak: counters that only climb, never fall, name a consumer that accumulates rather than borrows.
Frequently Asked Questions
Common questions about Windows 0x800705AA error
Kernel pools and desktop heaps are fixed-size structures with their own limits. They neither grow with installed RAM nor spill to the page file, so a full pool refuses work regardless of free memory.
It is the general form. The neighboring constants name specifics — 1451 nonpaged pool, 1452 paged pool, 1453 through 1455 quotas — and performance counters identify which of them sits at its ceiling on the failing machine.
Allocations a driver never releases accumulate in nonpaged or paged pool. Over days the pool climbs to its limit, after which ordinary requests return the shortage even though each individual request is small.
Related Error Codes
Related Errors From Other Categories
Similar error codes documented across different platforms and systems
Git paused the merge because it cannot automatically resolve overlapping changes.
Git aborted the merge to protect uncommitted changes in your working directory.
Git prevented a branch switch because it would overwrite unsaved changes in your working directory.
Git aborted the merge because it would overwrite untracked files in your working directory.