What does BSOD 855 (XBOX_CORRUPTED_IMAGE) mean?

 
Previous Next
XBOX_ERACTRL_CS_TIMEOUT XBOX_INVERTED_FUNCTION_TABLE_OVERFLOW

XBOX_CORRUPTED_IMAGE

Xbox image corruption bucket for XBOX_CORRUPTED_IMAGE

XBOX_CORRUPTED_IMAGE is bug check code 0x00000357. This bug check value belongs to the Xbox-related range in bugcodes.h. It indicates that an image used by the Xbox platform path was considered corrupted during loading or validation.

How to read it in a dump for XBOX_CORRUPTED_IMAGE

  • Identify the exact image, package, or executable being loaded.
  • Image signature, format, base address, and unwind metadata can be relevant.
  • Do not generalize it to ordinary desktop DLL loading without Xbox-platform context.

What to check for XBOX_CORRUPTED_IMAGE

  • Verify the package or image from a trusted build source.
  • Check signing, packaging, and deployment logs.
  • Use the dump to determine whether corruption is in storage, package layout, or loader metadata.

References for XBOX_CORRUPTED_IMAGE

Dump evidence for XBOX_CORRUPTED_IMAGE

For XBOX_CORRUPTED_IMAGE, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “XBOX_CORRUPTED_IMAGE”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for XBOX_CORRUPTED_IMAGE

  • Run WinDbg !analyze -v, then inspect the documented meaning of each XBOX_CORRUPTED_IMAGE parameter instead of relying only on the probably-caused-by line.
  • For XBOX_CORRUPTED_IMAGE, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with xbox / corrupted / image.
  • For XBOX_CORRUPTED_IMAGE, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Do not repeatedly reboot a machine affected by XBOX_CORRUPTED_IMAGE before collecting the dump and event logs. For XBOX_CORRUPTED_IMAGE, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

Dump evidence for XBOX_CORRUPTED_IMAGE

For XBOX_CORRUPTED_IMAGE, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “XBOX_CORRUPTED_IMAGE”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for XBOX_CORRUPTED_IMAGE

  • Run WinDbg !analyze -v, then inspect the documented meaning of each XBOX_CORRUPTED_IMAGE parameter instead of relying only on the probably-caused-by line.
  • For XBOX_CORRUPTED_IMAGE, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with xbox / corrupted / image.
  • For XBOX_CORRUPTED_IMAGE, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Do not repeatedly reboot a machine affected by XBOX_CORRUPTED_IMAGE before collecting the dump and event logs. For XBOX_CORRUPTED_IMAGE, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

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