Crash: Accessing non-connected memory space around $2axx

## Summary
Crash observed accessing non-connected memory space around address $2axx.

## Details Needed
- Exact crash address(es) and context
- Stack trace (SP, A, X, Y registers at crash)
- What action/state was active when crash occurred
- Full crash trace if available
- Whether this is related to the stack underflow issue (#1217)

## Initial Assessment
Accessing memory around $2axx suggests:
- Stack pointer corruption (SP pointing to invalid RAM)
- Array/buffer overflow
- Uninitialized pointer dereference
- Stack underflow leading to execution of garbage return addresses

## Next Steps
1. Collect full crash trace information
2. Map crash address to routine/call site
3. Identify memory access patterns that could reach $2axx
4. Check for stack/buffer corruption in recent changes