What does HRESULT 0xC037001C (ERROR_VID_STOP_PENDING) mean?

 
Could be also:
ConstantTypeOS
STATUS_VID_STOP_PENDINGNTSTATUSWindows
Previous Next
ERROR_VID_VIRTUAL_PROCESSOR_LIMIT_EXCEEDED ERROR_VID_INVALID_PROCESSOR_STATE

ERROR_VID_STOP_PENDING

ERROR_VID_STOP_PENDING is HRESULT 0xC037001C in the VID virtual-processor stop transition area of the Windows virtualization stack. It applies to a request to stop a virtual processor while an intercept or exit transition is still pending.

Object lifecycle behind the result

The VP cannot reach the requested stopped state immediately because the virtualization stack must finish handling a pending intercept. Preserve the exit reason and cancellation sequence rather than issuing repeated stops.

Neighboring result: INVALID_PROCESSOR_STATE means the requested operation does not fit the VP state generally. STOP_PENDING identifies a transitional condition with outstanding intercept work.

Diagnostic evidence matrix

EvidenceWhy it changes the diagnosis
VP identityRecord partition, VP index, thread, and generation.
Pending interceptCapture exit reason, message, or emulation work not yet completed.
Stop requestKeep initiator, timestamp, and desired VM transition.
Cancellation pathRecord whether run cancellation, device completion, or acknowledgement was issued.

Test one variable at a time

  1. Request cancellation/exit through the supported VP run path.
  2. Complete or abort intercept handling before final teardown.
  3. Serialize stop with device-emulation callbacks.
  4. Test stop during each major exit reason under instrumentation.

Reduce the reproducer to one partition and as few VPs as possible. In the diagnostic trace, instrument each run, exit, cancel, stop, reset, and delete transition so an asynchronous completion is not mistaken for an immediate state change.

How to read the controls

ControlInterpretationHold constant
One VP versus target countIf it appears only as processors are added, record the first failing index and capability/configuration limit.Keep partition properties and host topology fixed.
Clean partition generationA fresh partition changing it points to stale VP state, pending exits, or incomplete deletion rather than guest code.Use identical VP indexes, registers, and run sequence in the result comparison.
Instrumented run/stop raceControl run, cancel, intercept completion, stop, reset, and delete order. The first illegal transition explains it.Keep one VP and one deterministic exit reason until ordering is proven.

Scope of this status

Repeated start/stop commands can obscure the first illegal VP transition behind it. Preserve run-thread, exit reason, pending intercept, cancellation, and state-completion order.

Regression proof

The VP reaches stopped state after pending work drains, without repeated stop storms or lost intercept completion.

Technical references


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