| Previous | Next |
| OSS_INDEFINITE_NOT_SUPPORTED | OSS_BAD_TABLE |
OSS_MEM_ERROR
OSS_MEM_ERROR (0x8009300E) is an OSS ASN.1 runtime result for memory access violation in codec execution. The runtime detected or trapped an invalid access, often caused by a bad pointer, corrupt value object, wrong ABI, or earlier overwrite. Because crash or exception address and call stack is central to this condition, Microsoft’s HRESULT range and the OSS Nokalva return-code documentation should be read together. Start the investigation by recording module architecture, calling convention, and compiler settings, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
What the return code narrows down
At the memory access violation in codec execution boundary, capture the first OSS function returning the value and note whether the operation was encode, decode, copy, compare, constraint validation, or trace setup. Preserve the selected PDU, encoding rules, and lifetime of every caller-owned buffer; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Test one variable at a time
- Reproduce with page heap and full symbols
- Test a freshly constructed minimal PDU
- disable custom allocators only as an isolation step
Build a useful capture
- crash or exception address and call stack
- module architecture, calling convention, and compiler settings
- lifetime of every caller-owned buffer
Neighboring statuses: the result
OUT_MEMORY is a refused allocation; MEM_ERROR indicates that an address was not safe to access.
Instrumentation
Where crash or exception address and call stack can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use module architecture, calling convention, and compiler settings together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Verify the repair: the result
Find the first corruption or ABI mismatch and verify under memory instrumentation, not by catching and ignoring the status.
Technical references
Looking for a different code? Search another status or error code.