| Previous | Next |
| XBOX_360_SYSTEM_CRASH | BC_BLUETOOTH_VERIFIER_FAULT |
XBOX_360_SYSTEM_CRASH_RESERVED
Reserved Xbox 360 crash value for XBOX_360_SYSTEM_CRASH_RESERVED
XBOX_360_SYSTEM_CRASH_RESERVED is bug check code 0x00000420. This Xbox-range value is marked as reserved by its name. It can still appear in symbol tables, but a page should treat it as a reserved diagnostic bucket unless a dump provides a platform-specific interpretation.
How to read it in a dump
- Do not infer a detailed root cause from the reserved name.
- The code may be a placeholder or provider-defined bucket in platform diagnostics.
- Only dump context, title logs, and platform logs can identify the actual subsystem.
What to check
- Check whether the code was generated by test tooling, platform firmware, or compatibility infrastructure.
- Keep title and platform logs together with the dump.
- Avoid user-facing hardware conclusions from this reserved value alone.
References
- GDK console packaging overview
- Windows SDK bugcodes.h
- Microsoft Bug Check Code Reference
- Analyze a kernel-mode dump with WinDbg
Dump evidence
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 “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each parameter instead of relying only on the probably-caused-by line. - 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 / reserved.
- 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 this result before collecting the dump and event logs. 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.