What does BSOD 864 (XBOX_360_SYSTEM_CRASH) mean?

 
Previous Next
XBOX_CORRUPTED_IMAGE_BASE XBOX_360_SYSTEM_CRASH_RESERVED

XBOX_360_SYSTEM_CRASH

Xbox 360 compatibility crash bucket for XBOX_360_SYSTEM_CRASH

XBOX_360_SYSTEM_CRASH is bug check code 0x00000360. This value belongs to the Xbox/Xbox 360 crash range in bugcodes.h. It should be treated as a platform compatibility or emulator-style diagnostic bucket until the dump identifies the subsystem that raised it.

How to read it in a dump for XBOX_360_SYSTEM_CRASH

  • Check whether the environment is an Xbox platform, compatibility layer, or development kit scenario.
  • The title, compatibility layer, and platform service logs decide the meaning.
  • Do not apply normal desktop driver-remediation steps without platform evidence.

What to check for XBOX_360_SYSTEM_CRASH

  • Preserve title, platform, and deployment logs with the dump.
  • Check whether the crash follows a specific title, package, or system update.
  • Use platform-specific support tooling when available.

References for XBOX_360_SYSTEM_CRASH

Dump evidence for XBOX_360_SYSTEM_CRASH

For XBOX_360_SYSTEM_CRASH, 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_360_SYSTEM_CRASH”; 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_360_SYSTEM_CRASH

  • Run WinDbg !analyze -v, then inspect the documented meaning of each XBOX_360_SYSTEM_CRASH parameter instead of relying only on the probably-caused-by line.
  • For XBOX_360_SYSTEM_CRASH, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with xbox / 360 / system / crash.
  • For XBOX_360_SYSTEM_CRASH, 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_360_SYSTEM_CRASH before collecting the dump and event logs. For XBOX_360_SYSTEM_CRASH, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

Dump evidence for XBOX_360_SYSTEM_CRASH

For XBOX_360_SYSTEM_CRASH, 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_360_SYSTEM_CRASH”; 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_360_SYSTEM_CRASH

  • Run WinDbg !analyze -v, then inspect the documented meaning of each XBOX_360_SYSTEM_CRASH parameter instead of relying only on the probably-caused-by line.
  • For XBOX_360_SYSTEM_CRASH, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with xbox / 360 / system / crash.
  • For XBOX_360_SYSTEM_CRASH, 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_360_SYSTEM_CRASH before collecting the dump and event logs. For XBOX_360_SYSTEM_CRASH, 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.