nvlddmkm TDR (Timeout Detection and Recovery)
The display driver crashes and recovers (or fails to recover) due to a long-running CUDA kernel triggering the OS watchdog.
The display driver crashes and recovers (or fails to recover) due to a long-running CUDA kernel triggering the OS watchdog.
What this failure is
nvlddmkm TDR (Timeout Detection and Recovery) is a Hardware failure seen during ML training runs. The display driver crashes and recovers (or fails to recover) due to a long-running CUDA kernel triggering the OS watchdog. Common tags: Tdr, Windows, Nvlddmkm, Timeout.
Is this what broke your run? Paste your log.
You're reading about nvlddmkm TDR (Timeout Detection and Recovery). 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 CUDA kernel executed for longer than the OS TDR delay (default 2 seconds), causing the OS to reset the GPU driver. Thermal throttling or unstable GPU clocks leading to a hard driver crash. 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
- Display driver crashes
- CUDA kernel timeout
Common symptoms and what they mean
| Symptom | Why it happens |
|---|---|
| nvlddmkm stopped responding and has successfully recovered | A CUDA kernel executed for longer than the OS TDR delay (default 2 seconds), causing the OS to reset the GPU driver. |
| TDR detected | Thermal throttling or unstable GPU clocks leading to a hard driver crash. |
| Display driver nvlddmkm stopped responding | A CUDA kernel executed for longer than the OS TDR delay (default 2 seconds), causing the OS to reset the GPU driver. |
Which systems are affected
- Windows Workstations
- WSL2
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: nvlddmkm stopped responding and has successfully recovered
- ✓Verified signal present: TDR detected
- ✓Verified signal present: Display driver nvlddmkm stopped responding
- ✓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 CUDA kernel executed for longer than the OS TDR delay (default 2 seconds), causing the OS to reset the GPU driver.
- Thermal throttling or unstable GPU clocks leading to a hard driver crash.
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.