What does HRESULT 0xC00D117B (NS_E_MEMSTORAGE_BAD_DATA) mean?

 
Previous Next
NS_E_PDA_UNSPECIFIED_ERROR NS_E_PDA_FAIL_SELECT_DEVICE

NS_E_MEMSTORAGE_BAD_DATA

Practical scope of NS_E_MEMSTORAGE_BAD_DATA

This HRESULT is produced at reading the in-memory burn description or staged item data. This result belongs to cd/dvd recording and imapi state, not to an undifferentiated “Windows Media problem.”

Pipeline position

At the checkpoint, windows Media Player builds a burn playlist, refreshes its calculated status and delegates physical recording or erase work to the optical-disc stack; The recorder, inserted medium, burn format, staging files and write engine each have a separate lifecycle. The page-specific boundary is reading the in-memory burn description or staged item data.

A recorder that enumerates can still be busy, incompatible with the inserted medium or unable to sustain the selected write operation. In a typical failing run, stale or damaged in-memory staging metadata is reused after a failed session.

Reproduction record

EvidenceWhy it matters for memstorage bad data
Producing object and operationrecorder unique ID and exclusive-access owner, inserted media profile/state, burn format, playlist item, source locality, duration/byte estimate, staging directory free space, write speed, current IMAPI action and underlying HRESULT
Decisive observationburn object generation, serialized playlist/staging data size, checksum/parse result and producer
Generation identityRecord the same disc, device, job or Player operation generation that returned this result; a reconnect or media change creates a different test.
Underlying resultKeep the first device, filesystem, COM, codec, DirectShow, IMAPI or BITS result seen before the Player mapped it to this result.
Controlled comparisonRepeat the producing call after changing only this condition: rebuild the burn playlist and staging data from known-good source items.

Reading the evidence

ObservationInterpretation
The recorded values match the boundaryThe result is consistent with reading the in-memory burn description or staged item data; correct that state before changing unrelated codecs, drivers or playlists.
A lower layer failed before this resultPreserve that earlier HRESULT or device result because it may be only the Player-level mapping.
The same call passes after one isolated changeThe comparison supports the memstorage bad data diagnosis rather than a broad installation failure.
The code changes after retesting itThe boundary was passed; diagnose the new HRESULT as the next independent stage.

It scopes the failure to reading the in-memory burn description or staged item data.

Verification procedure

  1. Capture 0xC00D117B, it, the exact Player/API operation and the first timestamp at which it appears.
  2. Save burn object generation, serialized playlist/staging data size, checksum/parse result and producer; do this before ejecting media, reconnecting a device, canceling a job or rebuilding the Player object.
  3. correlate the result with recorder unique ID and exclusive-access owner, inserted media profile/state, burn format, playlist item, source locality, duration/byte estimate, staging directory free space, write speed, current IMAPI action and underlying HRESULT.
  4. Reproduce once with the original source and destination, then apply only this change: rebuild the burn playlist and staging data from known-good source items.
  5. Create a fresh operation generation and verify that the original call advances beyond the memstorage bad data boundary.

Results that may look similar

Related resultDifferent diagnostic boundary
NS_E_IMAPI_LOSSOFSTREAMINGsustaining the IMAPI recorder data stream throughout the write operation
NS_E_FAIL_LAUNCH_ROXIO_PLUGINactivating the legacy third-party recording plug-in selected by the Player
NS_E_NO_CD_BURNERenumerating an optical drive that reports burn capability to the Player

Change the smallest responsible condition

The targeted action is to rebuild the burn playlist and staging data from known-good source items. While retesting it, keep unrelated media, device, playlist and network values unchanged.

When verifying it, do not repeatedly start a new burn against a drive that still owns or finalizes the previous session; Capture the media state and recorder owner before ejecting or replacing the disc.

References


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