Site icon EfmSoft

What does HRESULT 0xC035000B (ERROR_HV_INSUFFICIENT_MEMORY) mean?

 
Could be also:
ConstantTypeOS
STATUS_HV_INSUFFICIENT_MEMORYNTSTATUSWindows
Previous Next
ERROR_HV_PROPERTY_VALUE_OUT_OF_RANGE ERROR_HV_PARTITION_TOO_DEEP

ERROR_HV_INSUFFICIENT_MEMORY

ERROR_HV_INSUFFICIENT_MEMORY is HRESULT 0xC035000B in the hypervisor pool capacity area of the Windows virtualization stack. It applies to memory owned or reserved by the hypervisor for partition, virtual-processor, mapping, or virtualization bookkeeping.

Why this HRESULT is specific

The host can have ordinary free memory while the specific hypervisor pool or allocation class needed by the operation cannot satisfy the request. Treat this as a host-capacity and fragmentation question at the exact operation boundary.

This result belongs to the hypervisor facility rather than the higher-level VM management UI. The TLFS and WHP documentation provide the surrounding partition, message, memory, and virtual-processor model, but the first low-level operation and any nested status remain the authoritative incident evidence.

Neighboring result: Unlike a caller output-buffer error, increasing a user-mode byte array does not address this result. Unlike ERROR_HV_NO_RESOURCES, this status identifies memory as the constrained class.

Records worth collecting

EvidenceWhy it changes the diagnosis
Host memory stateCapture committed bytes, available memory, Hyper-V dynamic-memory pressure, and the set of running partitions.
Requested operationRecord whether the failure occurred while creating a partition, mapping GPA, adding a VP, starting, restoring, or migrating.
Scale parametersKeep requested VM memory, vCPU count, mappings, and concurrent VM starts.
Fragmentation timelineNote host uptime, repeated create/delete cycles, checkpoints, and the last successful request of the same size.

A reproducible test plan

  1. Repeat on the same host after stopping one controlled VM, without changing the failing VM.
  2. Try a smaller supported memory or processor configuration to establish the capacity slope.
  3. Check host and Hyper-V event logs before restarting services or the host.
  4. Do not interpret guest free memory as evidence about the host hypervisor pool.

Use a controlled partition or disposable VM when a mapping, lock, or teardown test can be destructive. During the result run, keep page units, GPA boundaries, parent object, handle generation, and release order visible.

Comparison matrix

ControlInterpretationHold constant
Same request under lower host pressureIf it changes after controlled pressure is removed, quantify host/pool capacity; if not, focus on caller bookkeeping.Do not modify guest disks or unrelated VM devices during the result comparison.
Smaller exact rangeReduce only page count or mapped extent. If it moves, range arithmetic, object limits, or reserve capacity is involved.Keep the same block, GPA base, flags, and partition generation.
Balanced fresh lifecycleCreate, use, release, and destroy one object instance. If a different result appears after recreation, investigate leaked references, locks, handles, or mappings.Preserve sizes and operation order while changing only generation.

Misleading shortcuts

Restarting can release the exact lock, reference, mapping, or opaque handle behind it without fixing the lifecycle defect. Before recovering from it, preserve the object graph and acquire/release counts.

Keep the hexadecimal result value and any nested hypervisor status. Higher layers can map distinct resource, buffer, message, or state failures to the same generic start or migration message.

Verification after repair

The correction is proven when the original allocation succeeds repeatedly at the required scale and host pressure remains within an understood operating margin.

Technical references


Looking for a different code? Search another status or error code.

Exit mobile version