CUDA wheel installs, but GPU is never used on Windows 11 (Python 3.11, CUDA 12.1, torch finds GPU)

Open
#2,079 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
ai, backend

Research direction

The issue is a silent fallback to CPU on Windows with CUDA 12.1. Start by examining the llama_cpp Python bindings, particularly the GPU layer assignment logic and Windows-specific DLL loading. Check the build configuration for the cu121 wheel and look for any environment variable or runtime checks that might disable GPU usage. Verify the model loading logs to see if GPU layers are being requested but ignored.

Written by the indexing model from the issue text.

Description

On Windows 11, with Python 3.11 and a CUDA 12.1-compatible NVIDIA GPU, I can successfully install llama-cpp-python via pip from the cu121 wheel, but no matter what, all model layers are always assigned to CPU only.

torch works and finds the GPU (torch.cuda.is_available() == True).

All paths and DLLs appear correct.

No errors, just silent fallback to CPU for every layer, even with n_gpu_layers set. Tried -1 and 32

I have confirmed this across multiple clean venvs and installs.

System Info

OS: Windows 11 Pro

GPU: NVIDIA RTX 4060 Ti, 16 GB VRAM

NVIDIA Driver Version: NVIDIA-SMI, 581.57

CUDA Toolkit Version: 12.1 (from PATH and NVIDIA tools)

Python Version: 3.11.x

llama-cpp-python Version: 0.3.16 (from pip show llama-cpp-python)

Installation Command:

pip install llama-cpp-python --extra-index-url https://abetlen.github.io/llama-cpp-python/whl/cu121

Model Used: Mistral 7B Q5_K GGUF (4.7GB)

What I Tried

Fresh venv (python -m venv envgpu311)

Confirmed correct Python version: where python → E:\envgpu311\Scripts\python.exe

pip list shows torch 2.5.1+cu121, llama-cpp-python 0.3.16

System PATH contains correct CUDA 12.1 bin directory

cudart64_121.dll is present in CUDA bin

Test script:

from llama_cpp import Llama
llm = Llama(model_path="E:/Python/Models/Mistral/lucian_model.gguf", n_ctx=512, n_gpu_layers=32, verbose=True)
print(llm("Hello, world!"))

Logs never mention CUDA or GPU, only assigned to device CPU for every layer.

torch tests pass:

import torch
print(torch.version) # 2.5.1+cu121
print(torch.cuda.is_available()) # True

Tried uninstalling all other venvs, cleaning PATH, and purging pip cache.

Also tried n_gpu_layers=-1 and 32 as stated above

What Happens

Model loads, runs, and produces output—but all layers go to CPU, no GPU assignment or CUDA logs, and performance matches CPU.

What I Expected

Layers assigned to GPU, CUDA logs in output, and at least some portion of the model running on GPU

Other Details

No error messages, just silent fallback to CPU.

Issue persists across all wheels and source builds tested.

pip show llama-cpp-python:

Name: llama_cpp_python
Version: 0.3.16
Location: E:\envgpu311\Lib\site-packages
Requires: diskcache, jinja2, numpy, typing-extensions

torch and other CUDA tools/apps detect GPU fine.

Latest NVIDIA driver installed 10/15/2025

Dominant language
Python
Stars
10.7k
Forks
1.5k
Avg merge
1h 40m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from abetlen/llama-cpp-python

All issues in abetlen/llama-cpp-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.