Drivers
Known-bad ranges, the clean-install ritual, and why Studio drivers exist.
Driver bugs present as device-lost crashes mid-session or as denoiser artifacts — not as load failures. If the operator loads and then the GPU resets under load, start here.
Short version: run the latest Studio driver. Game Ready drivers ship first and regress compute paths more often; Studio is the same driver on a slower, better-tested cadence.
Known ranges (placeholder)
| Driver range | Symptom | Verdict |
|---|---|---|
| 572.00 – 572.42 | DLSS-RR denoiser NaN flashes | Skip |
| 566.xx | Stable everywhere we test | Floor for Photon |
| < 560.00 | Load refused (Driver too old) | Hard floor |
The clean-install ritual
When a machine misbehaves on a driver that's fine elsewhere:
Download the current Studio driver directly from NVIDIA — not Windows Update, not GeForce Experience.
Run the installer with Custom → Perform a clean installation checked. This clears cached shader blobs and stale settings profiles, which is the actual fix more often than the driver version.
Reboot, then delete TouchDesigner's own shader cache folder so nothing stale is replayed against the new driver.
Enterprise/vPro fleets that pin drivers via SCCM: the pinned driver is usually months behind the floor. The plugins print the minimum version in the status string — hand that line to IT, it is the whole conversation.