ncclUnhandledCudaError: Cuda failure 999 'unknown error'
A generic CUDA 'unknown error' (999) surfaces during NCCL communicator initialization, usually pointing to a GPU in a bad state or a driver/runtime mismatch rather than an NCCL bug.
A generic CUDA 'unknown error' (999) surfaces during NCCL communicator initialization, usually pointing to a GPU in a bad state or a driver/runtime mismatch rather than an NCCL bug.
What this failure is
ncclUnhandledCudaError: Cuda failure 999 'unknown error' is a Communication failure seen during ML training runs. A generic CUDA 'unknown error' (999) surfaces during NCCL communicator initialization, usually pointing to a GPU in a bad state or a driver/runtime mismatch rather than an NCCL bug. Common tags: Nccl, Cuda, Error 999, Ddp.
Is this what broke your run? Paste your log.
You're reading about ncclUnhandledCudaError: Cuda failure 999 'unknown error'. 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 GPU is in an unrecoverable state (prior Xid, ECC, or hung context). CUDA driver / runtime / NCCL version mismatch across ranks. GPU memory pressure or a leaked context before init. 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
- DDP/NCCL init crashes on one or more ranks
- Error is generic with no specific cause
- Often during parameter-shape verification at DDP construction
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| ncclUnhandledCudaError: Call to CUDA function failed | A GPU is in an unrecoverable state (prior Xid, ECC, or hung context) |
| Last error: Cuda failure 999 'unknown error' | CUDA driver / runtime / NCCL version mismatch across ranks |
| Crash inside _verify_param_shape_across_processes | GPU memory pressure or a leaked context before init |
Which systems are affected
- Multi-GPU DDP/FSDP jobs
- Mismatched NCCL / PyTorch / CUDA driver stacks
- Nodes with a GPU under memory pressure or in a faulted state
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: ncclUnhandledCudaError: Call to CUDA function failed
- ✓Verified signal present: Last error: Cuda failure 999 'unknown error'
- ✓Verified signal present: Crash inside _verify_param_shape_across_processes
- ✓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 extensionNCCL errors in context
NCCL is where a distributed job reports failure, which is not the same as where it failed. The hub lists every common NCCL error next to what it actually indicates, and the environment variables that tell them apart.
Compare every nccl error side by sideRelated failures to investigate next
Root cause
- A GPU is in an unrecoverable state (prior Xid, ECC, or hung context)
- CUDA driver / runtime / NCCL version mismatch across ranks
- GPU memory pressure or a leaked context before init
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.