GPU Memory Row Remapping Event
The GPU remaps a failing memory row after ECC errors. A recovery mechanism, but a rising remap count signals degrading memory that may need RMA.
The GPU remaps a failing memory row after ECC errors. A recovery mechanism, but a rising remap count signals degrading memory that may need RMA.
What this failure is
GPU Memory Row Remapping Event is a Hardware failure seen during ML training runs. The GPU remaps a failing memory row after ECC errors. A recovery mechanism, but a rising remap count signals degrading memory that may need RMA. Common tags: Row Remap, Ecc, Memory, Dcgm.
Is this what broke your run? Paste your log.
You're reading about GPU Memory Row Remapping Event. Paste your own crash log or traceback below and get the real root cause for YOUR run, not this generic entry. No account, no card. Logs are masked at ingress and never saved to account history.
Want 14 days on the Scale plan?
Request an evaluation code. A verified workplace organization activates up to 50 diagnoses a day, alerts, history, and follow-up questions. No credit card or automatic subscription.
Why it happens (the mechanism)
A memory row developed uncorrectable/excessive errors. The GPU remaps it to a spare row (finite supply). Underlying memory degradation. Taken together, these mechanisms explain why the failure is reproducible, why it tends to surface on specific workloads or scales, and why generic mitigation attempts often fall short without addressing the underlying cause.
What you'll observe
- ECC errors followed by a memory remap
- Remap count increasing over time
- Concern about GPU memory health
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| DCGM row remap count > 0 (or increasing) | A memory row developed uncorrectable/excessive errors |
| Xid messages referencing row remapping / ECC | The GPU remaps it to a spare row (finite supply) |
| Pending remap requires a GPU reset to take effect | Underlying memory degradation |
Which systems are affected
- A100/H100 and other GPUs with row-remapping
- Long-running nodes accumulating ECC events
- Clusters monitoring DCGM remap fields
How to confirm this is the problem
Use this checklist to test the hypothesis against a small reproduction. No single line proves the root cause, so preserve the preceding events and compare one variable at a time.
- ✓Reproduce the failure from a clean checkpoint/seed: the symptom must appear without warm-up state from a previous run.
- ✓Verified signal present: DCGM row remap count > 0 (or increasing)
- ✓Verified signal present: Xid messages referencing row remapping / ECC
- ✓Verified signal present: Pending remap requires a GPU reset to take effect
- ✓A targeted fix from the "How to fix it" section eliminates or substantially reduces the symptom within one validation pass.
The fix and the prevention pattern
The root cause is on this page and stays free. A free account adds the exact remediation steps, saved history, and the fix on every entry in the encyclopedia.
Sign up free. Unlock the full analysisNo credit card. Daily allowance follows verified trust tier. Instant access.
Diagnose this failure in VS Code
Select the traceback or open the failed terminal, then run Denpex locally to see the initiating rank, collateral failures, exact fix, and verification command without uploading the log.
Install the free VS Code extensionRelated failures to investigate next
Root cause
- A memory row developed uncorrectable/excessive errors
- The GPU remaps it to a spare row (finite supply)
- Underlying memory degradation
The fix and how to prevent it
Evaluate Denpex on your own logs
Request a Scale evaluation code. A verified workplace organization activates 14 days with up to 50 diagnoses a day. Every account keeps its current diagnosis allowance and gets a verification path. No card or automatic subscription.
Don't just read the fix, diagnose your run
The encyclopedia tells you what went wrong. Denpex tells you what went wrong in YOUR training run. With your logs, your config, and your stack.