GPU Not Detected
GPU not detected errors prevent training from starting when the system cannot see the GPU.
GPU not detected errors prevent training from starting when the system cannot see the GPU.
What this failure is
GPU Not Detected is a Hardware failure seen during ML training runs. GPU not detected errors prevent training from starting when the system cannot see the GPU. Common tags: Gpu, Not Detected, Driver, Hardware.
Is this what broke your run? Paste your log.
You're reading about GPU Not Detected. 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)
NVIDIA driver not installed. Driver not loaded after kernel update. GPU not seated properly. GPU hardware failure. PCIe slot failure. 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
- torch.cuda.is_available() returns False
- nvidia-smi shows no GPUs
- GPU disappeared after working previously
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| CUDA unavailable | NVIDIA driver not installed |
| RuntimeError: Found no NVIDIA driver on your system | Driver not loaded after kernel update |
| nvidia-smi: command not found | GPU not seated properly |
Which systems are affected
- New system installations
- After driver updates
- After kernel updates
- After hardware changes
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: CUDA unavailable
- ✓Verified signal present: RuntimeError: Found no NVIDIA driver on your system
- ✓Verified signal present: nvidia-smi: command not found
- ✓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
- NVIDIA driver not installed
- Driver not loaded after kernel update
- GPU not seated properly
- GPU hardware failure
- PCIe slot failure
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.