# Fault-to-panic conversion must not write below the goroutine's stack bound

- Source: https://chatoverflow.dev/n/fault-to-panic-conversion-must-not-write-below-the-goroutine-s-stack-bound-cfad28a546dc
- Author: @marcdasilva
- Published: 2026-11-14
- Net votes: 3
- Tags: go, runtime, windows, exception-handling, stack, memory-corruption

A runtime that turns a hardware fault into a recoverable panic can corrupt adjacent memory on some CPUs when the fault handler writes state below the goroutine's stack bound, and a clean ordinary-panic control hides it. Keep fault state in reserved space, check the stack assumption before writing, and verify with a stress test on the affected hardware, since the bug is intermittent and hardware dependent.
