| Previous | Next |
| TBSIMP_E_COMMAND_CANCELED | TBSIMP_E_LIST_NO_MORE_ITEMS |
TBSIMP_E_OUT_OF_MEMORY
What failed and what did not
TBSIMP_E_OUT_OF_MEMORY (0x8029020C) belongs to the public and internal TPM Base Services path. The base What Is page already shows the short Windows message; the additional diagnostic value is that this result marks the TBS implementation cannot allocate memory for command scheduling, virtualization or response handling.
Collect a useful trace
| Question | Evidence for this HRESULT |
|---|---|
| What exact state was rejected? | the TBS implementation cannot allocate memory for command scheduling, virtualization or response handling |
| Which layer owns the result? | The TBS client library, local RPC service and command scheduler before or around device execution. |
| What must be correlated? | command and response sizes, number of contexts and virtual resources, process and system memory pressure, service events, and leak trend |
| What is the controlled comparison? | reduce the workload to one context and one small command and observe whether memory use returns after cleanup |
Separate caller data from platform state. The result caller data includes the command, structures, lengths, handles and flags; platform state includes TPM generation, provisioning, locality, lockout, resource inventory, firmware and the TBS service lifecycle. This result is actionable only after the rejected side is identified.
Narrow experiment
Use the following verification sequence:
- Capture the unmodified failing input and
0x8029020C. - Reduce the workload to one context and one small command and observe whether memory use returns after cleanup.
- Compare the first result divergent field or state transition.
- Repeat this result only after restoring the same baseline, with a bounded retry policy where the specification permits retry.
Similar-looking outcomes
| Other code | Why a different remedy follows |
|---|---|
TBSIMP_E_COMMAND_FAILED | The TPM command failed — a separate checkpoint when compared with this result. |
TBSIMP_E_COMMAND_CANCELED | The command was canceled — a separate checkpoint when compared with it. |
TBSIMP_E_UNKNOWN_ORDINAL | The TBS does not recognize the specified ordinal — a separate checkpoint when compared with it. |
TBSIMP_E_NOT_ENOUGH_SPACE concerns TPM resource capacity, not host memory. The result difference determines whether to change serialization, authorization, resource lifetime, firmware/PPI state, command policy or only retry timing.
Operational response
Correct the original boundary by choosing this direction: release leaked contexts/resources and update the affected Windows component if memory growth is internal and reproducible. Do not restart or disable TBS before capturing its service and event data. Most caller-contract errors are reproducible without touching TPM ownership, firmware state or stored keys.
A successful it outcome preserves the intended hardware trust boundary, passes the original request, and produces verifiable output. Masking it, swallowing this HRESULT or switching silently to a software provider is not remediation.
References used for this checkpoint
- Microsoft: About TPM Base Services — source for the checkpoint.
- Microsoft: TBS return codes — source for the checkpoint.
- Microsoft: Tbsi_Context_Create — source for the checkpoint.
- Microsoft: Tbsip_Submit_Command — source for the checkpoint.
Looking for a different code? Search another status or error code.