Meta traced 6 of 419 Llama 3 405B training interruptions to silent data corruption — here's how to detect it

AWS ML Blog · rss · 2026-11-12

AWS ML Blog details detecting and recovering from silent data corruption (SDC): GPUs return wrong-but-plausible numbers with no error, which flow into every replica's gradients and weights while loss looks normal for hours. Meta attributed 6 of 419 unexpected interruptions in Llama 3 405B pretraining (up to 16K H100s, 54 days) to SDC — and those were only the caught ones.

Why existing checks miss it: ECC guards memory, not the ECC-less tensor-core math path; Xid errors require the GPU to self-report; deep health checks run on idle nodes; transport and checkpoint checksums verify delivery, not computation.

Three in-loop checks (the only layers that catch truly silent SDC):

Localization and recovery: map suspect rank to a Kubernetes node, cordon it, corroborate with DCGM metrics and a deep health check, replace the node, resume from a pre-window checkpoint. Validated with fault injection on 4 ml.p5.48xlarge instances (32 H100s); code is open source.

Original post →

More from Infra

Infra channel →