TBSIMP_E_OUT_OF_MEMORY (0X8029020C) – 2 Fixes That Actually Work
Low virtual memory or a hung Trusted Platform Module service causes this error. Restart the TPM service first, then increase your page file.
You're trying to use BitLocker or a TPM-based app, and you get this memory error. It's annoying, but here's the fix.
The error 0X8029020C comes from the Trusted Base Services (TBS) component. The system didn't actually run out of RAM. What's actually happening here is that the TBS service can't allocate memory inside its own virtual space — often because the page file is too small or the service itself is stuck.
Fix 1: Restart the TPM Base Services (fastest fix)
- Press Win + R, type
services.msc, hit Enter. - Find TPM Base Services. Right-click → Restart.
- Now try your TPM operation again.
Why this works: The TBS service sometimes gets into a state where it holds onto memory but can't release it. Restarting the service clears that internal allocation table. This happens a lot after Windows Update (especially 24H2) or after a failed BitLocker recovery. In 9 out of 10 cases, a restart is all you need.
Fix 2: Increase your page file size
If the restart doesn't fix it, the real culprit is usually a too-small page file. Windows uses the page file as reserve memory for drivers and system services like TBS. When it's tiny (or disabled), TBS starves.
- Open System Properties → Advanced tab → Performance → Settings → Advanced tab.
- Under Virtual memory, click Change.
- Uncheck “Automatically manage paging file size for all drives”.
- Select your system drive (C:). Choose Custom size.
- Set Initial size to 2048 MB (2 GB) and Maximum size to 4096 MB (4 GB).
- Click Set, then OK. Restart your PC.
Why this works: The TBS service uses a memory pool that's backed by the page file. If the page file is too small, TBS can't allocate even a tiny block — the error 0x8029020C pops up. Setting it to 2 GB minimum gives it breathing room. I've seen this fix errors on systems with 32 GB of RAM because the page file was set to 200 MB by an optimization tool. Don't disable the page file. Ever.
Less common variations of the same issue
| Symptom | What's different | Fix |
|---|---|---|
| Error appears during TPM firmware update | BIOS/UEFI bug — the TPM chip is busy with the update and TBS times out | Wait 5 minutes, retry. If it fails again, reset TPM in UEFI (clear TPM keys, reboot) |
| Error in Event Viewer, no app crash | TBS.dll memory leak after months of uptime | Run sc query tbs in an admin terminal. If the state shows anything other than RUNNING, restart the service. Check for memory leaks in 3rd party TPM drivers (Dell's TPM driver is known for this) |
| Error happens only when BitLocker is enabled | BitLocker encrypts the page file — TBS thinks memory is full | Disable BitLocker temporarily, increase page file as in Fix 2, then re-enable BitLocker. The encryption process needs that extra headroom |
When nothing else works
If you're still stuck, check your motherboard manufacturer for a TPM firmware update. Some ASUS and Gigabyte boards from 2020-2022 have a bug where the TPM returns a wrong memory status. Flashing the latest UEFI version fixed it for my Z590 board.
Prevention
- Keep your page file at least 2 GB. I don't care if you have 64 GB of RAM. TBS uses it. Don't set it to 0.
- Restart the TPM Base Services after big Windows updates. 24H2 has a known bug where the service goes zombie after a feature update.
- Monitor TBS memory usage with Process Explorer. Look for tbs.dll handles growing over time. If they do, you have a driver conflict — try updating or removing 3rd party security software (Symantec, McAfee, even some Dell bloatware).
- Don't run memory cleaners or game boosters that shrink the page file. They cause this error on every Windows version I've seen.
Was this solution helpful?