claude-code - 💡(How to fix) Fix Process crashes with exit code 3221225477 (0xC0000005 STATUS_ACCESS_VIOLATION) on Windows ARM [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#51898Fetched 2026-04-23 07:41:56
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×4commented ×2

Claude Code process repeatedly exits with code 3221225477 (0xC0000005 = STATUS_ACCESS_VIOLATION) on startup. This is a persistent issue observed across multiple Anthropic updates over the past two weeks.

The crash appears to occur during or shortly after session initialization — the same prompt is echoed 2–3 times in the UI before the process dies.

Error Message

Claude Code process exited with code 3221225477

Hex: 0xC0000005 = Windows STATUS_ACCESS_VIOLATION (equivalent to a segfault/memory access violation in the Node.js or native addon layer)

Root Cause

Claude Code process repeatedly exits with code 3221225477 (0xC0000005 = STATUS_ACCESS_VIOLATION) on startup. This is a persistent issue observed across multiple Anthropic updates over the past two weeks.

The crash appears to occur during or shortly after session initialization — the same prompt is echoed 2–3 times in the UI before the process dies.

Fix Action

Fix / Workaround

  • Persistent across multiple Claude Code updates (2+ weeks)
  • Blocks usage on Windows ARM entirely in some sessions
  • No workaround found — updating to latest version (2.1.114) does not resolve

Code Example

Claude Code process exited with code 3221225477
RAW_BUFFERClick to expand / collapse

Bug Report

Claude Code version: 2.1.114 Node version: v22.22.2 OS: Windows 11 Pro (ARM) — version 10.0.26200 Hardware: Samsung Windows ARM device Install method: npm global (@anthropic-ai/claude-code)

Description

Claude Code process repeatedly exits with code 3221225477 (0xC0000005 = STATUS_ACCESS_VIOLATION) on startup. This is a persistent issue observed across multiple Anthropic updates over the past two weeks.

The crash appears to occur during or shortly after session initialization — the same prompt is echoed 2–3 times in the UI before the process dies.

Reproduction

  • Launch Claude Code on Windows ARM
  • Send any message (or simply open a session with MCP servers configured)
  • Process exits with code 3221225477 before completing the response

Error

Claude Code process exited with code 3221225477

Hex: 0xC0000005 = Windows STATUS_ACCESS_VIOLATION (equivalent to a segfault/memory access violation in the Node.js or native addon layer)

Suspected trigger

Session startup with multiple MCP servers initializing simultaneously. The startup hook runs a large number of MCP tool initializations in parallel, which may be causing a memory pressure or race condition that triggers the access violation.

Impact

  • Persistent across multiple Claude Code updates (2+ weeks)
  • Blocks usage on Windows ARM entirely in some sessions
  • No workaround found — updating to latest version (2.1.114) does not resolve

Additional context

  • The error occurs on Windows ARM specifically — may be related to ARM-specific memory behavior in the Node.js runtime or native addons
  • Exit code appears in the Claude Code desktop app UI as a red error message at the bottom of the chat window
  • Session sometimes recovers after multiple retries, but the crash is frequent

extent analysis

TL;DR

The most likely fix involves addressing the suspected memory pressure or race condition caused by simultaneous MCP server initializations during session startup.

Guidance

  • Investigate the startup hook that runs multiple MCP tool initializations in parallel to identify potential memory leaks or synchronization issues.
  • Consider implementing a sequential initialization process for MCP servers to reduce memory pressure and avoid potential race conditions.
  • Review Node.js and native addon configurations to ensure they are optimized for Windows ARM architecture and can handle the memory requirements of the application.
  • Monitor system resources and memory usage during session startup to better understand the conditions leading to the access violation.

Example

No specific code snippet can be provided without more information on the startup hook and MCP server initialization code. However, a general approach to sequential initialization could involve using asynchronous programming techniques, such as Promise.all() or async/await, to ensure that each MCP server initialization completes before the next one begins.

Notes

The issue seems to be specific to Windows ARM devices, which might imply that the problem is related to how Node.js or native addons handle memory on this architecture. Further investigation into ARM-specific memory behavior and potential differences in how memory is allocated and deallocated compared to other architectures may be necessary.

Recommendation

Apply a workaround by modifying the startup hook to initialize MCP servers sequentially, as this approach directly addresses the suspected cause of the issue and may provide a temporary solution until a more comprehensive fix can be implemented.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING