Zero Gradient / Dead Neurons
Zero gradients stall training when ReLU neurons die or gradient flow is broken in the network.
Zero gradients stall training when ReLU neurons die or gradient flow is broken in the network.
What this failure is
Zero Gradient / Dead Neurons is a Training Stability failure seen during ML training runs. Zero gradients stall training when ReLU neurons die or gradient flow is broken in the network. Common tags: Dead Relu, Zero Gradient, Training Stability, Activation.
Is this what broke your run? Paste your log.
You're reading about Zero Gradient / Dead Neurons. 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)
ReLU neurons output 0 for all inputs (dead ReLU). Gradient flow blocked by saturated activations. Learning rate too high causing parameter divergence. Incorrect gradient checkpointing. 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
- Loss stops improving despite non-zero loss
- Gradient norms for some layers are exactly zero
- Certain layers don't update
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| gradient_norm for layer X is 0.0 | ReLU neurons output 0 for all inputs (dead ReLU) |
| Param norm for layer X unchanged across steps | Gradient flow blocked by saturated activations |
| Specific layers never update | Learning rate too high causing parameter divergence |
Which systems are affected
- Deep networks with ReLU activations
- Networks with high learning rates
- Networks with batch normalization
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: gradient_norm for layer X is 0.0
- ✓Verified signal present: Param norm for layer X unchanged across steps
- ✓Verified signal present: Specific layers never update
- ✓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
- ReLU neurons output 0 for all inputs (dead ReLU)
- Gradient flow blocked by saturated activations
- Learning rate too high causing parameter divergence
- Incorrect gradient checkpointing
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.