0Pricing
CUDA Academy · Lesson

Driver, Runtime, and Toolkit Versions

Which pieces must agree for CUDA to run.

Driver, Runtime, and Toolkit Versions is a free CUDA Academy lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the CUDA Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Three Moving Parts

Running CUDA needs three pieces to cooperate: the GPU driver, the CUDA runtime, and the CUDA toolkit. When they line up, your code just works. 🧩

The Driver

The driver is the low-level software that lets your operating system actually talk to the physical GPU. It ships with NVIDIA's GPU drivers, separate from the toolkit.

The Runtime

The CUDA runtime is the friendly library your program links against. It offers the cudaMalloc and cudaMemcpy calls you will write every day.

The Toolkit

The CUDA toolkit bundles the compiler, the runtime libraries, and headers. Installing it is how you get nvcc and everything needed to build GPU code.

The Golden Rule

Here is the rule that saves you hours: your driver must be at least as new as the toolkit. A newer driver runs older toolkits, but never the reverse.

Check the Driver Version

To see your driver and the maximum CUDA it supports, run nvidia-smi in a terminal and read the top header line.

nvidia-smi

Check the Toolkit Version

To confirm which CUDA toolkit compiler you have installed, ask nvcc directly. The version it prints is what your builds will target.

nvcc --version

Two Versions, One System

It is normal for nvidia-smi and nvcc to show different numbers. The first reports the driver's max CUDA; the second reports the installed toolkit. That gap is fine.

Forward Compatibility

Programs you build are tied to a runtime version. A newer driver stays backward compatible, so older CUDA binaries keep running after you upgrade your driver.

When Things Break

Seeing an error like driver version is insufficient almost always means your driver is too old for the toolkit. Update the driver, not the toolkit.

Query Versions in Code

Your program can read both numbers at runtime. The runtime API exposes them so you can log versions or fail early with a clear message.

int rt, drv;
cudaRuntimeGetVersion(&rt);
cudaDriverGetVersion(&drv);

Quick Check

Time to test the version relationship.

Recap

You met the driver, runtime, and toolkit, and learned the golden rule: keep the driver as new or newer than the toolkit. Now you can diagnose version errors fast. 🚀

Frequently asked questions

Is the “Driver, Runtime, and Toolkit Versions” lesson free?

Yes — the full text of “Driver, Runtime, and Toolkit Versions” is free to read here on the web, and the CUDA Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the CUDA Academy course, upgrade to CoddyKit PRO.

What will I learn in “Driver, Runtime, and Toolkit Versions”?

Which pieces must agree for CUDA to run. You practise CUDA Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start CUDA Academy?

No prior experience is required. CUDA Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Driver, Runtime, and Toolkit Versions” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this CUDA Academy lesson?

Yes. Every CUDA Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

  1. Driver, Runtime, and Toolkit Versions
  2. Reading nvidia-smi Like a Pro
  3. Compiling with nvcc
  4. Hello GPU: Your First .cu File
← Back to CUDA Academy