Conceptio › Archive › arXiv CS
arXiv CS open access

TrainSDC: Characterizing and Mitigating Silent Data Corruption in Large Language Model Training

2026 · arxiv_cs
arXiv CS · Papers · 2026
Open Source ↗Direct PDF ↓
neural-networks
Conceptio Open Archive

Analyze & explore related research in Conceptio

Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.

TrainSDC: Characterizing and Mitigating Silent Data Corruption in Large Language Model Training Zhipeng Xia1 , Haotian Xu1 , Siyu Yun1 , Liqi Lin1 , Hu Liu2 , Yu Li1,∗ , Cheng Zhuo1 1

arXiv:2608.30769v1 [cs.LG] 31 Aug 2026

∗

Zhejiang University

Huawei

Corresponding author: yu.li.sallylee@gmail.com

Abstract

and leave persistent damage. A useful characterization must therefore consider both where a fault enters the training computation and how its effect evolves over time. Studies using faulty production hardware analyze SDC at the levels of submodule computation, a single optimizer step, and an extended training period [Ma et al., 2025]. Large injection campaigns characterize the outcomes of transient faults in LLM training [Yu et al., 2025]. Instruction- and RTL-level studies vary injection sites, fault patterns, and numerical formats [Altenbernd et al., 2026, Tyagi et al., 2026]. However, these studies do not jointly compare the major Transformer components in the forward and backward passes or distinguish short-lived effects from damage that remains at the end of training. This incomplete understanding also limits protection design. Existing defenses infer corruption from aggregate training signals [Altenbernd et al., 2026, Yu et al., 2025], check selected computations [Liang et al., 2025], identify faulty devices [Lei et al., 2026], or duplicate execution [Park et al., 2026]. These methods either operate at coarse granularity, cover only selected computations, or incur the cost of redundant execution. Without a detailed characterization of error propagation, it remains unclear where direct verification is needed and where lightweight monitoring is sufficient. We therefore conduct a systematic fault-injection study of pre-norm LLMs. We inject faults at the outputs of the major components in a Transformer block during both forward and backward passes. We measure the largest loss change and the remaining change at the end of training to distinguish faults that fade from those that cause lasting damage. Based on the different ways faults propagate in the forward and backward passes, we design TrainSDC with a separate protection method for each pass. Our contributions are threefold:

LLM training is increasingly vulnerable to silent data corruption (SDC), yet existing protection methods largely treat Transformer computations uniformly because their vulnerability remains poorly understood. We present the first systematic characterization of SDC vulnerability across major computation interfaces in both the forward and backward passes of Transformer training. Our analysis reveals two distinct error propagation mechanisms: forward-pass vulnerability is highly location dependent, with faults on the Q/K path producing persistent training deviations, whereas backward-pass vulnerability is largely governed by gradient exponent distributions rather than computation locations. Motivated by these observations, we propose TrainSDC, a characterization-guided protection framework consisting of Q/K-path recomputation, residual-gain monitoring, and exponent-aware gradient scaling. Experiments on Llama 3.2-1B and Qwen3-0.6B show that TrainSDC maintains training behavior close to fault-free execution under both sparse and dense fault injection while introducing only 1.65%–6.76% runtime overhead.

1

2

Introduction

In LLM training, silent data corruption (SDC) occurs when a hardware fault produces an incorrect result without triggering an exception or error signal. Because the corrupted value is consumed as valid, it can flow through activations and gradients into parameter updates even when the loss and other global signals show no obvious anomaly. The damage may become visible only later as a loss spike or failed convergence, or remain hidden while degrading final model quality [Dixit et al., 2021, Ma et al., 2025]. Training larger models typically requires more accelerators and longer runs, increasing the chance that SDC affects training. At the scale of Gemini, the team estimated that SDC events could affect training every one to two weeks [Team et al., 2023]. Without a direct alarm, assessing SDC risk requires understanding how a corrupted value propagates and whether its effect disappears or persists in later updates. A large immediate deviation is not necessarily the most harmful: some errors fade as training proceeds, whereas others bias later updates

• To our knowledge, we present the first systematic characterization of SDC vulnerability across all major modules in a Transformer block during both forward and backward passes. • We find that faults in Q/K path outputs cause more persistent forward-pass damage, whereas faults in value, attention-output, and MLP computations cause larger but shorter-lived loss changes. Backward-pass vulnerability 1

varies less across components, and fault amplification depends on the exponent distribution of gradients.

gradient aggregation, faulty devices, or job recovery rather than local Transformer computations. In contrast, we compares SDC vulnerability across the major computations in a Transformer block and separately analyzes the forward and backward passes. TrainSDC uses this characterization to protect the two passes differently without continuously duplicating the full training computation.

• We develop TrainSDC, which checks Q/K operations through recomputation, monitors residual connections, and re-executes flagged steps in the forward pass. For the backward pass, it selects a power-of-two loss scale from clean gradient statistics.

3

On Llama 3.2-1B and Qwen3-0.6B, TrainSDC mitigates both sparse and dense faults with limited overhead. It maintains results close to fault-free training under sparse faults and preserves convergence under dense faults causing unprotected training to diverge. Overall, TrainSDC restores training outcomes to a level close to fault-free training.

2

Fault Characterization

This section characterizes how transient computation errors affect large language model training. We examine how their effects vary across module outputs and between forward and backward stage, and trace whether the errors are amplified, attenuated, or retained. These results provide the basis for the protection design presented in the next section.

Related Work

3.1

Characterizing SDC in LLM training. Prior work studies SDC through production-system measurements and controlled fault injection. Fleet-scale measurements document the prevalence and diversity of SDC in production hardware [Dixit et al., 2021]. Experiments on unhealthy training nodes analyze real-world SDC at three scales: attention and FFN outputs, a single optimizer step, and an extended training period [Ma et al., 2025]. These experiments preserve realistic hardware behavior, but do not control fault location and timing or separate the individual computations within attention and FFN. Controlled studies inject faults at GPU matrix-multiply instructions [Altenbernd et al., 2026], run large transient-fault campaigns [Yu et al., 2025], or combine RTL-level simulation with training-level injection to study permanent faults [Tyagi et al., 2026]. Our work differs in granularity and comparison scope: under the same fault settings, we inject faults separately at the outputs of individual Transformer computations and into their corresponding backward gradients. This allows us to compare vulnerability across locations and passes and distinguish short-lived from lasting effects. Training-time SDC protection. Some methods use traininglevel statistics to detect faults. Altenbernd et al. identify harmful updates from changes in the magnitude of AdamW parameter updates and the global gradient norm [Altenbernd et al., 2026]. LLMFT instead uses heuristic training features as input to a learned fault detector [Yu et al., 2025]. These methods do not check individual Transformer computations. ATTNChecker applies algorithm-based fault tolerance (ABFT) to detect and correct extreme errors in attention [Huang and Abraham, 1984, Liang et al., 2025]. SpareTrain reduces the overhead of complete dual modular redundancy by reusing activation checkpointing and idle GPU time [Park et al., 2026]. ATTNChecker protects attention, whereas SpareTrain duplicates the full computation. Other methods focus on distributed training. PAFT handles gradient-aggregation errors [Tang et al., 2025]; AEGIS detects SDC online and identifies faulty GPUs [Lei et al., 2026]; and ByteRobust diagnoses failures and accelerates recovery [Wan et al., 2025]. These methods address

Fault Model and Metrics

Fault type. Persistent failures in storage are generally easier to detect because storage systems commonly use errorcorrecting codes and related integrity checks. In contrast, transient errors in computation can produce an incorrect result without leaving a persistent state and are therefore harder to detect. A transient error affects only the current tensor computation, and neither the corrupted value nor its bit state is retained by the next execution. We focus on transient errors in arithmetic computation and do not model persistent storage failures. Injection location. We inject errors into module activation outputs during the forward pass and their corresponding output gradients during the backward pass. For an activation x, the backward target is gx = ∂L/∂x. In each target module, we randomly select m elements and flip four randomly selected bits in each element. All module outputs use the same random seeds, and injection is performed in the original data type. Parameters, optimizer states, and stored training data are not modified. Loss-deviation metrics. The loss-deviation metrics separate the largest deviation during training from the deviation at the final step. Let tf denote the first faulty step and T the final step: DMaximum ≜ max (Lfault (t) − Lclean (t)) ,

(1)

Dfinal ≜ Lfault (T ) − Lclean (T ).

(2)

tf ≤t≤T

Repeated clean trajectories estimate nondeterministic training variation. Efinal is the largest pairwise final-loss difference among clean runs, while EMaximum is the largest pairwise loss difference at any aligned step. Figures report Dfinal /Efinal and DMaximum /EMaximum . A value above one exceeds every observed clean-to-clean difference under the corresponding metric. 2

Figure 1: Characterization results for SmolLM2-135M and NanoChat-GPT-124M. Panels (a) and (b) report the normalized final loss deviation, panels (c) and (d) report the normalized maximum loss deviation, and panels (e) and (f) report fault propagation using relative L2 error.

3.2

Experimental Design

exceeds the clean tensor magnitude. A larger value therefore indicates a more pronounced effect of the fault.

Experiment 1: training vulnerability. Experiment 1 measures training vulnerability at forward and backward stage separately. We select SmolLM2-135M and NanoChat-GPT-124M as the experimental models because their modern Transformer architectures are representative of compact language models. In the injection experiment, SmolLM2 targets layer 20 and runs from steps 1222 to 2035, whereas NanoChat-GPT targets layer 5 and runs from steps 955 to 1907. Each run modifies rank 0, corrupts 100,000 elements at 1% of training steps, and uses the shared random selection described above. Repeated no-fault runs establish (Efinal , EMaximum ) as (0.000456, 0.009299) for SmolLM2 and (0.000389, 0.003153) for NanoChat-GPT.

3.3

Observation O1: Forward sensitivity is path-dependent, whereas backward sensitivity is broad. Across both models, the final loss is most sensitive to faults in the Q/K path outputs, namely the Q and K tensors consumed by the attention operator, together with the input and post-attention normalization outputs. This ranking is architecture-invariant: although NanoChat-GPT applies Q/K RMSNorm after the projections and thus absorbs projection-stage errors, the Q/K path outputs remain the most vulnerable interface in both architectures. Figure 1 further shows that peak and final loss deviations follow different rankings. Faults in the V, normalization, MLP, and block outputs produce the largest immediate loss perturbations, but these disturbances are gradually attenuated by normalization and subsequent clean updates. In contrast, faults in the Q/K path outputs produce only modest immediate loss perturbations while leading to the largest final loss deviations, indicating that they silently alter the optimization trajectory rather than causing conspicuous short-term failures. Backward injection exhibits much weaker module differentiation. Most monitored gradients lead to similarly large training deviations, suggesting that backward vulnerability is not dominated by individual Transformer modules but instead requires protection with broad coverage. Design implication. Forward protection should distinguish computations according to their propagation characteristics.

Experiment 2: propagation diagnostic. Experiment 2 traces the propagation of the injected fault through downstream modules. The experiment uses the same target layers, element selection, and bit selection as Experiment 1. Each run injects one module output and records the resulting changes at downstream attention, residual, multilayer-perceptron, normalization, and language-model output. For a monitored module output tensor x, the propagation metric is Rx =

∥xfault − xclean ∥2 . ∥xclean ∥2

Characterization Results

(3)

The numerator measures the difference between the faulty and clean tensors, while the denominator normalizes this difference by the magnitude of the clean tensor. Figures 1(e) and (f) report log10 Rx , where a positive value indicates that the difference 3

Q/K-path faults are difficult to detect from downstream signals despite their lasting impact, whereas backward protection should employ a unified mechanism rather than modulespecific protection.

We consequently recompute the complete Q/K path, covering the projections, normalization, and rotary position encoding. At the same time, under the transient fault model, a fault is not expected to affect both executions identically, so a mismatch between them indicates an incorrect Q/K result. The complete Q/K path is executed twice with the same input and network parameters. At worker rank r, layer ℓ, and training step t, denote the original tensors entering attention by b r,ℓ,t and Qr,ℓ,t and Kr,ℓ,t . The second execution produces Q b Kr,ℓ,t as their recomputed counterparts. Compact fingerprints avoid retaining and directly comparing the full Q/K tensors. Each Q or K tensor is reduced to two 64-bit XOR fingerprints, producing a 128-bit representation. For a flattened tensor Z = (z0 , . . . , zn−1 ), let bi = bits(zi ) denote the raw binary encoding of zi , let w denote its bit width, and let L denote the number of elements packed into one fingerprint word. The fingerprints are

Observation O2: Q/K-path faults are weakly observable, whereas most other forward faults remain detectable after propagation. Figures 1(e) and (f) show that faults in the Q/K path outputs are strongly attenuated by the softmax operation and subsequent residual addition. Consequently, even substantial corruption often results in only modest downstream loss perturbations and can escape both loss-based and activationmagnitude monitoring, although the altered attention allocation continues to influence subsequent parameter updates. In contrast, faults originating from the V path, normalization, attention output, and MLP remain visible as abnormal magnitude changes at the following residual writeback. These faults therefore preserve observable signatures after propagation, making them amenable to lightweight runtime monitoring. Design implication. Protection should directly verify computations whose faults become weakly observable after propagation, while computations that preserve detectable propagation signatures can instead be protected through lightweight monitoring.

4

ϕraw (Z) =

(bi ≪ w(i mod L)) ,

(4)

mix(i, bi ),

(5)

i=0

ϕindexed (Z) =

n−1 M i=0

⊤

Φ(Z) = [ϕraw (Z), ϕindexed (Z)] .

(6)

Here, ⊕ denotes bitwise XOR, ≪ denotes a bit shift, and mix(i, bi ) combines each element encoding with its flattened index. The indexed fingerprint reduces cancellation between changes at different tensor positions. A Q/K mismatch is reported when either fingerprint pair differs between the two executions:  b  1, if Φ(Qr,ℓ,t ) ̸= Φ(Qr,ℓ,t ), QK b r,ℓ,t ), ar,ℓ,t = 1, if Φ(Kr,ℓ,t ) ̸= Φ(K (7)   0, otherwise.

Protection Design

Figure 2 illustrates the overall architecture of TrainSDC. TrainSDC follows the characterization in Section 3 and adopts heterogeneous protection for different stages of Transformer training. For the forward pass, protection is determined by fault propagation behavior. Computations whose faults become difficult to observe after propagation are protected through direct verification, whereas computations whose faults remain observable are protected through lightweight runtime monitoring. For the backward pass, vulnerability exhibits much weaker dependence on computation location. TrainSDC therefore employs a unified numerical protection mechanism based on exponent-aware gradient scaling.

4.1

n−1 M

Residual Gain Guard. The residual gain guard covers transient faults outside the Q/K path. These faults reach the residual writebacks without passing through any intermediate normalization, and therefore arrive as unattenuated amplitude errors. The residual output is then passed directly to subsequent computation, so the amplitude error propagates through the network and can be detected from the input-to-output residual gain. The first step computes the amplitude change across each residual writeback. For worker rank r, layer ℓ, training step t, and p ∈ {attention, multilayer perceptron}, let xp,in r,ℓ,t and p,out xr,ℓ,t denote the residual input and output. The root mean square and residual gain are v u |x| u 1 X t x2 , (8) R(x) = |x| i=1 i     p p,in gr,ℓ,t = log R(xp,out ) + ϵ − log R(x ) + ϵ . (9) r,ℓ,t r,ℓ,t

Forward Pass Protection

The characterization identifies two categories of forward computations with distinct protection requirements. Faults in the Q/K path become weakly observable after propagation while causing the most persistent training deviation. These computations therefore require direct verification. In contrast, faults in the remaining forward computations preserve detectable propagation signatures, allowing them to be protected through lightweight runtime monitoring instead of redundant execution. Q/K Path Recomputation. The preceding observations show that a transient fault at any stage before the Q/K tensors enter attention can affect training. Protecting only the Q/K projections is therefore insufficient because faults can also arise during Q/K normalization or rotary position encoding.

Here, |x| is the number of elements, R(x) represents the endp point amplitude, and gr,ℓ,t represents its relative change across 4

Figure 2: Overview of the protection design. Q/K path recomputation verifies the Q/K tensors before attention, while the residual gain guard monitors the residual writebacks after attention and the multilayer perceptron. Exponent scaling protects gradient computation in the backward pass. the residual writeback. The logarithm places amplification and attenuation around zero. The residual gain guard reuses the token-wise mean square computed by root mean square normalization instead of scanning the residual tensor again.

p µpℓ,t = median(Hℓ,t ),

spℓ,t = max 1.4826 median |h − µpℓ,t |, smin p

j̸=r p p er,ℓ,t = gr,ℓ,t − cp−r,ℓ,t .

,

(13)

h∈Hℓ,t

The second step compares each worker rank with the remaining worker ranks. In distributed data-parallel training, all worker ranks use the same network parameters at the same training step, so the remaining worker ranks provide a current reference. The reference and rank-specific deviation are

p cp−r,ℓ,t = median gj,ℓ,t ,

(12) !

p zr,ℓ,t =

|epr,ℓ,t − µpℓ,t | spℓ,t

.

(14)

Here, µpℓ,t is the typical historical deviation, spℓ,t is its medianp absolute-deviation scale, and zr,ℓ,t measures the current deviation relative to normal historical variation. p After computing zr,ℓ,t for all worker ranks, the residual gain guard selects the largest score z(1) . A transient fault is detected when z(1) exceeds the effective threshold. The worker rank producing z(1) is identified as the faulty candidate.

(10) (11)

4.2

Here, j indexes the remaining worker ranks, cp−r,ℓ,t is their median residual gain, and epr,ℓ,t measures how far worker rank r deviates from that reference. Excluding worker rank r prevents it from changing its own reference.

Backward Pass Protection

Unlike the forward pass, backward vulnerability exhibits little dependence on Transformer modules. This suggests that protecting individual computations separately would incur additional overhead without addressing the primary source of vulnerability. To identify this common source, we analyze the numerical behavior of gradient representations under bit flips. We find that the numerical magnitude of a gradient tensor directly determines its vulnerability to bit flips. For a bfloat16 value g, let ej denote exponent-field bit j. When the original and flipped values are both finite, flipping ej changes the magnitude

The detection thresholds are calibrated separately for the monitored layers and residual writebacks. Because normal cross-rank deviations can change with input data and training progress, a fixed reference may become inaccurate. A sliding p window Hℓ,t therefore stores recent finite deviations, with the largest absolute deviation excluded before each update. The normalized score is 5

by [Kalamkar et al., 2019] | flipej (g)| |g|

( j 22 , ej = 0, = −2j 2 , ej = 1.

(15)

The effect of a flip therefore depends on the current bit value. Small gradients occupy low exponent codes, where the selected exponent bits are zero more often, so a flip amplifies the value. Increasing the magnitude shifts the exponent-code distribution upward; once the selected bits become one, the same flip turns one into zero and attenuates the value instead, as illustrated in Figure 2. The two directions cause very different damage. An amplified corrupted gradient propagates into the global parameter update, whereas an attenuated corrupted gradient suppresses its own contribution and causes little deviation. Thus, exponent scaling protects the backward pass by moving gradients from the amplifying region into the attenuating region. Exponent scaling changes exponent codes while preserving the parameter update. We use k to specify the scaling factor 2k . Before the backward pass, the loss is multiplied by 2k , which multiplies every generated gradient by the same factor and adds k to its exponent code. Immediately before gradient clipping and the parameter update, the gradient is divided by 2k , so the update is unchanged: k

gs =

4.3

∂(2 L) = 2k g, ∂θ

2−k gs = g.

Figure 3: Choosing the scaling factor k. The measured Final dev. is compared with Ramp across candidate values of k. strong under a random ranking. The correlation is ρ = 0.650 with pperm = 0.067 for Llama-3.2-1B and ρ = 0.867 with pperm = 0.005 for Qwen3-0.6B (n = 9 per network). Based on these results, all subsequent experiments fix the scaling exponent at the selected optimum k = 15.

(16)

The scaling exponent k is selected by minimizing the predicted vulnerability within the numerical range of the backward pass. The choice is a trade-off. A small k leaves many gradients in exponent codes for which a bit flip amplifies the value, whereas a large k pushes the upper tail of the distribution toward non-finite values. We therefore collect a histogram H of gradient exponent codes from clean training steps and evaluate each candidate by shifting the codes by k:  j 2 X Ramp (k; H) = PH,k (ej = 0) 22 − 1 , (17)

5.1

Experimental Setup

Data. The evaluation uses the same document-disjoint SmolLM2-derived split for both networks [Allal et al., 2025]. The split contains 1,193,639 training and 12,056 evaluation documents sampled proportionally from DCLM-Edu, FineWeb-Edu, Stack-Edu, InfiMM-WebMath, FineMath, and Cosmopedia-v2, then tokenized separately for each network. The available training and evaluation corpora contain 1.102B/10.959M Llama tokens and 1.126B/11.181M Qwen tokens. Each run consumes about 100M training tokens, including 40M in the aligned continuation. Final evaluation covers 614,400 held-out token positions, and no evaluation document occurs in training.

j∈J k∈Ksafe

Evaluation

Models and training. The evaluation uses Llama 3.2-1B (16 layers) [Grattafiori et al., 2024] and Qwen3-0.6B (28 layers) [Yang et al., 2025], instantiated from their configurations with random weights (seed 8) and without pretrained weights. Every fault-free, faulty, protected, and ablation run resumes from a common step-1221 checkpoint and ends at step 2035. Training uses data parallelism on six NVIDIA A100 80-GB graphics processing units, one 1024-token sequence per rank, and eight accumulated microbatches, for 49,152 tokens per network update. Computation uses bfloat16 automatic mixed precision and float32 parameters. AdamW uses (β1 , β2 ) = (0.9, 0.95), ϵ = 10−8 , weight decay 0.1, and global gradient clipping at 1.0. The learning rate warms up for 100 steps to 5 × 10−5 and cosine-decays to 10% of that value.

Selecting the Scaling Exponent

k ∗ = arg min Ramp (k; H).

5

(18)

Here, J contains the exponent positions included by the fault model, PH,k (ej = 0) is the fraction of shifted codes for which bit ej is zero, and Ksafe contains the candidates that keep the shifted codes within the finite range. Each term weights the probability of an amplifying flip by its squared relative magnitude change, so Ramp measures the expected amplification risk of a candidate. The common bit-selection probability is omitted because it is constant across the candidates and does not change k ∗ . Figure 3 compares the measured final deviation with the predicted Ramp (k; H) across the evaluated values of k. Spearman’s ρ measures whether the two quantities give a consistent ranking of k, while pperm is the exact two-sided permutation probability of observing an association at least this

Fault injection. We instantiate the fault model of Section 3.1 as follows. To additionally evaluate detection capability under sparse faults, we introduce a 10-element injection setting. For each spatial intensity, the protocol triggers 813 injection events; all remaining settings are identical. 6

Network

Method

Overhead ↓ (%)

Dfinal ↓

DMaximum ↓

∆PPL ↓

Top-1 ↑ (%)

W L2 ↓ (%)

Fault 0.00 / 0.00 +1.72e-2 / nonfinite 1.23e-1 / nonfinite 4.04 / – 94.20 / – 0.69 / – Loss spike ≈ 0 / ≈ 0 +1.72e-2 / +1.15e-1 1.24e-1 / 2.84e-1 4.03 / 27.60 94.40 / 82.60 0.692 / 2.10 Inf/NaN ≈ 0 / ≈ 0 +1.72e-2 / +1.18e-1 1.23e-1 / 4.28e-1 4.04 / 28.60 94.20 / 82.20 0.69 / 2.15 Llama 3.2 ATTNChecker 7.65 / 7.65 +1.75e-2 / +1.07e-1 3.73e-2 / 3.86e-1 4.07 / 25.40 94.30 / 83.40 0.692 / 2.00 1B Harmful-update 12.10 / 12.10 +1.08e-2 / +5.37e-3 1.15e-1 / 1.57e-1 2.49 / 1.25 95.00 / 96.90 0.510 / 0.480 LLMFT 13.50 / 13.50 +1.68e-2 / +9.43e-2 9.37e-2 / 2.42e-1 3.86 / 22.20 94.50 / 84.60 0.679 / 1.84 Ours 1.65 / 1.65 -3.86e-5 / +6.32e-4 2.86e-4 / 9.14e-3 -3.37e-3 / 0.173 99.10 / 98.60 2.83e-2 / 0.149

Qwen3 0.6B

Fault 0.00 / 0.00 +2.30e-2 / nonfinite 9.65e-2 / nonfinite 5.43 / – 93.10 / – 0.69 / – Loss spike ≈ 0 / ≈ 0 +2.17e-2 / +1.25e-1 9.59e-2 / 2.82e-1 5.24 / 36.30 93.60 / 81.80 0.677 / 2.60 Inf/NaN ≈ 0 / ≈ 0 +2.30e-2 / +1.27e-1 9.65e-2 / 3.21e-1 5.43 / 36.90 93.10 / 81.70 0.690 / 2.67 ATTNChecker 36.70 / 36.70 +2.10e-2 / +1.26e-1 2.67e-2 / 2.93e-1 5.06 / 37.10 93.70 / 81.70 0.656 / 2.69 Harmful-update 11.20 / 11.20 +1.39e-2 / +3.82e-3 8.85e-2 / 1.56e-1 3.24 / 1.14 94.50 / 97.90 0.471 / 0.361 LLMFT 5.62 / 5.62 +2.17e-2 / +1.05e-1 7.06e-2 / 2.48e-1 5.33 / 29.50 93.60 / 84.20 0.676 / 2.25 Ours 6.76 / 6.76 +3.87e-6 / +6.15e-4 2.22e-4 / 1.48e-2 -1.25e-3 / 0.175 99.10 / 98.80 2.16e-2 / 0.109

Table 1: Evaluation under the transient-fault injection protocol. Each slash-separated metric reports results for 10 corrupted activation elements (left) and 100,000 corrupted activation elements (right) per injection event.

Network Variant

Dfinal ↓

5.2

∆PPL ↓

Llama

Q/K path Only +1.69e-2 / +9.03e-2 4.00 / 21.70 Residual Only +1.44e-2 / +9.02e-2 3.37 / 21.40 Exponent scaling Only +3.03e-4 / Inf 7.28e-2 / – Complete -3.86e-5 / +6.32e-4 -3.37e-3 / 0.173

Qwen

Q/K path Only +2.15e-2 / +1.02e-1 5.22 / 28.50 Residual Only +1.98e-2 / +1.04e-1 4.59 / 29.10 Exponent scaling Only +1.12e-3 / Inf 0.250 / – Complete +3.87e-6 / +6.15e-4 -1.25e-3 / 0.175

Main Results

All methods use the same checkpoints, data order, and injection schedules. Harmful-update follow prior training studies [Altenbernd et al., 2026], and ATTNChecker follows its attentionprotection setting [Liang et al., 2025]. LLMFT uses its learned detector through our zero-shot oracle-route adapter [Yu et al., 2025]. Slash-separated values denote 10 / 100,000 corrupted elements. At 10 elements, the complete method achieves near-zero Dfinal , DMaximum below 2.9 × 10−4 , and negligible ∆PPL on both models, with 1.65% overhead on Llama and 6.76% on Qwen. At 100,000 elements, unprotected training diverges, whereas the complete method preserves convergence consistent with fault-free training. Its Dfinal is 6.32 × 10−4 / 6.15 × 10−4 , DMaximum is 9.14 × 10−3 / 1.48 × 10−2 , and ∆PPL is 0.173 / 0.175. It achieves the best reported outcome metrics on both models and at both fault intensities.

Table 2: Component ablation under the unified injection protocol. Each slash-separated metric reports results for 10 corrupted activation elements (left) and 100,000 corrupted activation elements (right) per injection event.

Protection configuration. The protection configuration applies fused recomputation to the Q/K path, the residual gain guard to residual writebacks, and exponent scaling to the backward pass. Fused recomputation covers the Q/K path in every layer, while the residual gain guard samples layers {0, 5, 10, 15} in Llama and {0, 9, 18, 27} in Qwen. An alarm discards the accumulated gradients and replays all accumulated microbatches without a transient fault before the network update. Exponent scaling uses k = 15, and automatic scale adjustment is disabled.

5.3

Ablation Study

The ablation evaluates the Q/K-path check, residual gain guard, and exponent scaling individually, with the complete method included as a reference. All variants use the same injection protocol as Table 1. At 10 elements, exponent scaling is the strongest individual component, reducing Dfinal to 3.03 × 10−4 / 1.12 × 10−3 and ∆PPL to 0.0728 / 0.250 for Llama/Qwen. At 100,000 elements, K15-only encounters found_inf, so its Dfinal and PPL are not reported. Q/K-only and residual-only produce Dfinal near 10−1 and ∆PPL between 21.4 and 29.1, whereas the complete method reduces Dfinal to 6.32 × 10−4 / 6.15 × 10−4 and ∆PPL to 0.173 / 0.175. The three components therefore provide complementary protection under strong faults.

Metrics. The evaluation reports Overhead, Dfinal , DMaximum , ∆PPL, Top-1 and W L2. Dfinal and DMaximum follow Section 3, and ∆PPL is the held-out perplexity difference from the aligned fault-free run. Top-1 measures token agreement, W L2 measures relative parameter drift. Overhead is the change in mean fault-free step time over 100 measured optimizer steps. 7

6

Conclusion

of the 30th ACM SIGPLAN Annual Symposium on Principles and Practice of Parallel Programming, PPoPP ’25, pages 252–266, New York, NY, USA, 2025. Association for Computing Machinery. doi: 10.1145/3710848.3710870.

This work shows that query/key path faults cause more persistent damage, whereas value, attention-output, and multilayerperceptron faults cause larger but shorter-lived loss changes. Backward vulnerability varies less across components and depends on the gradient exponent distribution. Based on these findings, TrainSDC combines query/key path recomputation, the Residual Gain Guard, and exponent scaling. On Llama 3.21B and Qwen3-0.6B, TrainSDC mitigates both sparse and dense faults with limited overhead and restores training outcomes to a level close to fault-free training.

Jeffrey Jian Ma, Hengzhi Pei, Leonard Lausen, and George Karypis. Understanding silent data corruption in llm training. In Proceedings of the 63rd Annual Meeting of the Association for Computational Linguistics (Volume 1: Long Papers), pages 20372–20394, 2025. Rihae Park, Yeonjae Kim, Seung Yul Lee, Yeonhong Park, and Jae W. Lee. SpareTrain: Fault-tolerant LLM training via low-cost dual modular redundancy. In International Conference on Learning Representations, 2026. URL https: //openreview.net/forum?id=kDeS8jpeiZ.

References Loubna Ben Allal, Anton Lozhkov, Elie Bakouch, Gabriel Martín Blázquez, Guilherme Penedo, Lewis Tunstall, Andrés Marafioti, Hynek Kydlíček, Agustín Piqueres Lajarín, Vaibhav Srivastav, et al. Smollm2: When smol goes big–data-centric training of a small language model. arXiv preprint arXiv:2502.02737, 2025.

Zhenheng Tang, Junlin Huang, Zichen TANG, Xueze Kang, Yuxin Wang, Peijie Dong, Shaohuai Shi, Xiaowen Chu, and Bo Li. Identifying and mitigating errors in gradient aggregation of distributed data parallel training, 2025. URL https://openreview.net/forum?id=zOgUQM6uLZ.

Anton Altenbernd, Philipp Wiesner, and Odej Kao. Exploring silent data corruption as a reliability challenge in llm training. arXiv preprint arXiv:2604.00726, 2026.

Gemini Team, Rohan Anil, Sebastian Borgeaud, Jean-Baptiste Alayrac, Jiahui Yu, Radu Soricut, Johan Schalkwyk, Andrew M Dai, Anja Hauth, Katie Millican, et al. Gemini: a family of highly capable multimodal models. arXiv preprint arXiv:2312.11805, 2023.

Harish Dattatraya Dixit, Sneha Pendharkar, Matt Beadon, Chris Mason, Tejasvi Chakravarthy, Bharath Muthiah, and Sriram Sankar. Silent data corruptions at scale. arXiv preprint arXiv:2102.11245, 2021.

Abhishek Tyagi, Saurabh Hukerikar, Nirmal Saxena, Yanxiang Huang, Philip Shirvani, Chung-Hsuan Tung, and Yuhao Zhu. LLM-PRISM: Characterizing silent data corruption from permanent GPU faults in LLM training, 2026.

Aaron Grattafiori, Abhimanyu Dubey, Abhinav Jauhri, Abhinav Pandey, Abhishek Kadian, Ahmad Al-Dahle, Aiesha Letman, Akhil Mathur, Alan Schelten, Alex Vaughan, et al. The llama 3 herd of models. arXiv preprint arXiv:2407.21783, 2024.

Borui Wan, Gaohong Liu, Zuquan Song, Jun Wang, Yun Zhang, Guangming Sheng, Shuguang Wang, Houmin Wei, Chenyuan Wang, Weiqiang Lou, et al. Robust llm training infrastructure at bytedance. In Proceedings of the ACM SIGOPS 31st Symposium on Operating Systems Principles, pages 186–203, 2025.

Kuang-Hua Huang and Jacob A. Abraham. Algorithm-based fault tolerance for matrix operations. IEEE Transactions on Computers, C-33(6):518–528, 1984.

An Yang, Anfeng Li, Baosong Yang, Beichen Zhang, Binyuan Hui, Bo Zheng, Bowen Yu, Chang Gao, Chengen Huang, Chenxu Lv, et al. Qwen3 technical report. arXiv preprint arXiv:2505.09388, 2025.

Dhiraj Kalamkar, Dheevatsa Mudigere, Naveen Mellempudi, Dipankar Das, Kunal Banerjee, Sasikanth Avancha, Dharma Teja Vooturi, Nataraj Jammalamadaka, Jianyu Huang, Hector Yuen, et al. A study of bfloat16 for deep learning training. arXiv preprint arXiv:1905.12322, 2019.

Pengfei Yu, Jingjing Gu, Hao Han, Dazhong Shen, Bao Wen, and Yang Liu. Exploring and mitigating failure behavior of large language model training workloads in hpc systems. In Proceedings of the International Conference for High Performance Computing, Networking, Storage and Analysis, pages 1165–1179, 2025.

Kinman Lei, Liyan Zheng, Xiang Li, Hongmin Chen, Yun Zhang, Gaohong Liu, Zuquan Song, Zixuan Ma, Zhiyu Xue, Minghui Yu, et al. Safeguarding {LLM} training at scale: Online {SDC} detection and insights from 35 million {GPU} hours. In 20th USENIX Symposium on Operating Systems Design and Implementation (OSDI 26), pages 1369–1384, 2026. Yuhang Liang, Xinyi Li, Jie Ren, Ang Li, Bo Fang, and Jieyang Chen. ATTNChecker: Highly-optimized fault tolerant attention for large language model training. In Proceedings 8

A

Appendix

A.1

Robustness across Fault Rate, Layer, and Injection Budget

Motivation. The main characterization of SmolLM2 uses Layer 20, injects faults in 1% of training steps, and corrupts 100,000 elements in each selected tensor. We test whether its forward-pass observations remain visible when varying the fault-step rate, target layer, and injection budget separately. Experimental variants. Figure 4 reports three controlled variants on SmolLM2-135M. Rate robustness uses Layer 20, a 0.1% fault-step rate, and 100,000 corrupted elements. Layer robustness uses Layer 10, a 1% fault-step rate, and 100,000 corrupted elements. Budget robustness uses Layer 20, a 1% fault-step rate, and corrupts exactly 1% of each target tensor. For a target tensor xi containing Ni elements, the last variant uses mi = round(0.01Ni )

(19)

corrupted elements. All remaining settings, including the training continuation, temporal injection schedule, random seeds, bit-flip policy, optimizer, and fault-free reference trajectory, follow the main characterization. Results. Across all three variants, forward sensitivity remains path-dependent. Q/K-path faults consistently leave final deviations above the fault-free envelope, while normalization outputs are also vulnerable. In contrast, V, multilayer perceptron, and block-output faults mainly produce large peak deviations that are attenuated during subsequent training. These results agree with Observation O1 and show that the forward-pass pattern remains under changes in fault-step rate, target layer, and injection budget.

Figure 4: Additional forward-pass characterization of SmolLM2-135M. Panels (a) and (b) evaluate rate robustness at Layer 20 with a 0.1% fault-step rate and 100,000 corrupted elements. Panels (c) and (d) evaluate layer robustness at Layer 10 with a 1% fault-step rate and 100,000 corrupted elements. Panels (e) and (f) evaluate budget robustness at Layer 20 with a 1% fault-step rate and exactly 1% of each target tensor corrupted.

A.2

Operating Characteristics of Forward Protection

Threshold calibration and online state. Calibration starts from the common step-1221 checkpoint and runs 100 fault-free optimizer steps (steps 1222–1321). The sliding-window length is W = 64 accepted detector observations, normally one per optimizer step. For each monitored layer and residual path, one clean observation contributes the R − 1 rank deviations with the 9

smallest absolute values; the largest rank deviation is omitted. With R = 6, the stored window therefore contains 64 × 5 = 320 scalar deviations per layer and path. The first 64 calibration steps seed this window, while all 100 calibration steps are used to determine the calibrated threshold floors. Consequently, the evaluation run begins with a full window and has no additional deployment warm-up. The robust scale follows the definition in the main text. The detector uses threshold coefficient α. Let cprel,ℓ,cal and cpz,ℓ,cal denote the largest eligible relative-deviation and robust-z scores observed in the 100 clean calibration steps before any safety scaling. With smin = 10−6 and adaptive quantile q = 1, the effective thresholds at step t are ! p τrel,ℓ,t = α max cprel,ℓ,cal , max (exp(|h|) − 1) , p

(20)

h∈Hℓ,t

p τz,ℓ,t = α max

cpz,ℓ,cal ,

p |h − median(Hℓ,t )|

max p max(1.4826 MAD(Hℓ,t ), 10−6 ) h∈Hp ℓ,t

! .

(21)

Thus, the same coefficient jointly scales the fixed calibration floor and the adaptive history term. The floor prevents an unusually quiet recent window from making the detector over-sensitive, while the history term follows legitimate training drift. Selection of α. We sweep α ∈ {1, 1.5, 2, 2.5, 3} using the same four monitored layers, checkpoint, detector history, fault locations, and random seed. For each candidate, clean false positives are measured on 200 held-out fault-free optimizer steps. Detection is measured on 96 residual-path snapshot-replay events per network: 48 events with 10 corrupted elements and 48 events with 100,000 corrupted elements. Table 3 reports the result. Network

α

Clean step FPR

10-element recall

100,000-element recall

Llama 3.2-1B

1.0 1.5 2.0 2.5 3.0

33/200 (16.5%) 3/200 (1.5%) 1/200 (0.5%) 0/200 (0%) 0/200 (0%)

48/48 (100.00%) 17/48 (35.42%) 17/48 (35.42%) 17/48 (35.42%) 17/48 (35.42%)

48/48 (100.00%) 41/48 (85.42%) 41/48 (85.42%) 41/48 (85.42%) 41/48 (85.42%)

Qwen3-0.6B

1.0 1.5 2.0 2.5 3.0

17/200 (8.5%) 0/200 (0%) 0/200 (0%) 0/200 (0%) 0/200 (0%)

7/48 (14.58%) 7/48 (14.58%) 7/48 (14.58%) 7/48 (14.58%) 7/48 (14.58%)

32/48 (66.67%) 32/48 (66.67%) 32/48 (66.67%) 32/48 (66.67%) 32/48 (66.67%)

Table 3: Selection of the single effective Residual Gain Guard coefficient α. Clean FPR is the optimizer-step false-positive rate on 200 held-out fault-free steps. The two recall columns report detected events out of 48. The setting α = 1 is over-sensitive on both networks. From α = 1.5 onward, recall is unchanged on this sweep, while the clean FPR continues to decrease. We select α = 2.5 because it is the smallest candidate with zero held-out clean alarms on both networks and shows no recall reduction relative to α = 1.5 or 2. The resulting per-layer, per-path calibration floors are listed in Table 4. Attn. τrel

τzAttn.

Llama 3.2-1B 0 5 10 15

0.340077 0.008262 0.008631 0.007139

10.926 11.462 16.026 14.899

0.322114 11.736 0.017856 25.025 0.019817 13.107 0.033000 9.942

Qwen3-0.6B

0.282147 0.008335 0.006522 0.010103

11.798 15.364 15.650 13.767

0.206769 0.011517 0.009818 0.018967

Network

Layer

0 9 18 27

MLP τrel

τzMLP

13.587 19.679 16.609 12.445

Table 4: Per-layer, per-path calibrated threshold floors after applying the selected α = 2.5. “Attn.” and “MLP” denote the attention and multilayer-perceptron residual writebacks. 10

Alarm aggregation and history admission. For each layer and path, the implementation considers the largest and second-largest rank scores. The robust-z branch alarms when the largest score reaches τz and is at least 1.5 times the second-largest score; a companion relative-deviation branch applies the same dominance rule using τrel . A nonfinite or negative reused mean-square value bypasses both thresholds and causes an immediate alarm. Nonfinite values are never written to the history. All rank, path, and monitored-layer decisions are OR-reduced into one optimizer-step alarm. Multiple simultaneous alarms retain their individual diagnostics but trigger only one replay of the accumulated microbatches, with fault injection disabled, before a single optimizer update. An attempt rejected by the Residual Gain Guard is not written to its window. The online window persists within an uninterrupted training process but is not stored in the ordinary model/optimizer checkpoint. On restart, the reported implementation reloads the same 64-step seed from the separate calibration file rather than carrying recent deployment history across the checkpoint. All reported main runs were uninterrupted, so this restart behavior does not alter their measurements. Results. Table 3 reports the held-out clean behavior used to select α. At the selected α = 2.5, neither network raises an alarm in the 200-step clean holdout. We then run an independent 814-step fault-free deployment trace and three complete 813-event fault traces per network. The complete clean traces produce zero alarms for Qwen and one alarm for Llama, corresponding to a combined step-level FPR of 1/1628 = 0.061%. This longer measurement is the clean FPR reported below; it does not change the held-out sweep used to select α. Network

Clean alarms

10 elements

1,000 elements

100,000 elements

All fault runs

Llama 3.2-1B Qwen3-0.6B

1/814 (0.12%) 0/814 (0%)

175/403 (43.42%) 165/403 (40.94%)

338/403 (83.87%) 279/403 (69.23%)

348/403 (86.35%) 316/403 (78.41%)

861/1209 (71.22%) 760/1209 (62.86%)

Table 5: Complete-run clean FPR and forward-alarm recall with α = 2.5. Each fault run contains 403 valid forward injection events. An event is detected when Q/K Path Recomputation or the Residual Gain Guard requests a pre-update replay.

Injection module or node

10 elements

1,000 elements

100,000 elements

Total

Share (%)

Attention weights Attention logits Down projection Attention residual Pre-o attention output Output projection Input RMSNorm SiLU output Up projection Gate projection Post-attention RMSNorm Gated MLP product Value projection Block output

45 32 39 28 42 25 48 37 35 32 33 27 25 18

45 32 28 28 17 21 0 7 1 3 0 3 3 1

45 32 20 27 8 10 0 0 0 0 0 0 0 0

135 96 87 83 67 56 48 44 36 35 33 30 28 19

16.94 12.05 10.92 10.41 8.41 7.03 6.02 5.52 4.52 4.39 4.14 3.76 3.51 2.38

All protected Q/K-path targets

0

0

0

0

0.00

Table 6: Post-hoc composition of missed forward alarms with α = 2.5, aggregated over both networks. Share is relative to all 797 missed forward events across the three spatial intensities. Across all three intensities, Q/K Path Recomputation detects every direct corruption of the protected Q/K-path targets. The remaining misses are concentrated in attention weights, attention logits, and residual or projection outputs outside that exact-recomputation boundary. Increasing the number of corrupted elements primarily improves Residual Gain Guard recall: the combined recall rises from 43.42% to 86.35% for Llama and from 40.94% to 78.41% for Qwen.

A.3

Temporal Stability of the Exponent-Scaling Parameter

Motivation. Exponent scaling selects k from the exponent-code histogram of clean backward gradients. This selection is practical only if the same value can be held for a substantial training interval. We therefore measure how the selected value 11

evolves over the complete public checkpoint trajectory of Pythia-1B. Checkpoint sweep. We evaluate all 154 released checkpoints from step 0 through step 143,000. At each checkpoint, we run 12 fixed WikiText-103 validation sequences with batch size 1 and sequence length 1,024. We collect the BF16 exponent histogram Ht of dL/dY at all 64 Transformer linear projections, using 8,192 deterministic samples per projection and sequence, or 6,291,456 samples per checkpoint. No fault is injected during profiling. We evaluate the same candidate set as in the main method and compute the pointwise selection k ∗ (t) = arg min Ramp (k; Ht ).

(22)

k∈Ksafe

For phase-wise deployment, a held value kheld remains admissible while its predicted risk is at most 25% above the pointwise minimum. A new profile is required only when this condition no longer holds. The reported values of k use the same training-equivalent convention as the main experiments. Within 25\% of pointwise minimum

Pointwise k *

74K steps at fixed k = 15

one later reassessment

16 Training-equivalent k

Held k

14

12 warmup

Relative excess risk (\%)

10

25\% limit 20

10

0 0

20K

40K

60K 80K Pythia pretraining step

100K

120K

140K

Figure 5: Temporal stability of exponent scaling across all 154 public Pythia-1B checkpoints. The upper panel shows the pointwise optimum k ∗ , the values within 25% of its predicted risk, and the value held for each phase. The lower panel shows the relative excess risk of the held value. The shaded region marks warm-up, and the vertical dashed line marks the only later reassessment after the initial post-warm-up value is established at step 4,000. Results. Figure 5 shows frequent movement during warm-up and the immediate post-warm-up transition. Once k = 15 is selected at step 4,000, it remains admissible through step 78,000, a span of 74,000 training steps. One later reassessment at step 79,000 selects k = 13, which remains admissible through the final checkpoint at step 143,000. The relative excess risk remains below the 25% limit throughout both intervals. Thus, after the initial post-warm-up operating point is established, the remaining trajectory of more than 100,000 steps requires only one additional reassessment. Practical implication. The scaling exponent k is evaluated more frequently during warm-up, when the histogram changes rapidly, and is then held fixed over long training intervals. For this trajectory, the initial post-warm-up value requires only one reassessment in the latter half of training.

12

Related documents

Record · ID 622547 · SHA-256 63a5e6ff9e4fbac0
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive