github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-07-16 05:05:37 -05:00
Code Issues 16.9k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #16029] Windows 10 Ollama v0.22.1 and NVIDIA GeForce GTX 1060 Driver version 582.28 (01.28.2026) Pairing Ignores GPU and Workaround #87892

New Issue
Open
opened 2026-05-10 06:33:09 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-10 06:33:09 -05:00
Owner
Copy Link

Originally created by @mindtd on GitHub (May 6, 2026).
Original GitHub issue: https://github.com/ollama/ollama/issues/16029

What is the issue?

Update to Ollama to v0.22.1 and NVIDIA Driver: version 582.28 (01.28.2026), ollama ignores GPU and runs 100% on CPU.

Observation - 04.27.2026 ollama runs BUT "ollama ps" shows 100% CPU.

Spent hours and tried Set Environment Variables / different combinations (from Google sources) to no avail -
CUDA_VISIBLE_DEVICES = 0
OLLAMA_VULKAN = 1
ROCR_VISIBLE_DEVICES = 0

Resolution -workarond reinstall

  1. Ollama v0.21.3 https://github.com/ollama/ollama/releases/tag/v0.21.3-rc0
  2. NVIDIA Driver: version 581.80 (10.20.2025)

Fact - ollama ps confirms 100% GPU running tinydolphin and mixed of CPU/GPU runnign gemma3.
Task Manager GPU also shows GPU activity throughout ollama run.

Relevant log output

OS

Windows

GPU

Nvidia

CPU

AMD

Ollama version

v0.22.1

Originally created by @mindtd on GitHub (May 6, 2026). Original GitHub issue: https://github.com/ollama/ollama/issues/16029 ### What is the issue? Update to Ollama to v0.22.1 and NVIDIA Driver: version 582.28 (01.28.2026), ollama ignores GPU and runs 100% on CPU. _Observation_ - 04.27.2026 ollama runs BUT "ollama ps" shows 100% CPU. Spent hours and tried Set Environment Variables / different combinations (from Google sources) to no avail - CUDA_VISIBLE_DEVICES = 0 OLLAMA_VULKAN = 1 ROCR_VISIBLE_DEVICES = 0 **Resolution** -workarond reinstall 1. **Ollama v0.21.3** https://github.com/ollama/ollama/releases/tag/v0.21.3-rc0 2. **NVIDIA** Driver: version **581.80** (10.20.2025) Fact - ollama ps confirms 100% GPU running tinydolphin and mixed of CPU/GPU runnign gemma3. Task Manager GPU also shows GPU activity throughout ollama run. ### Relevant log output ```shell ``` ### OS Windows ### GPU Nvidia ### CPU AMD ### Ollama version v0.22.1
GiteaMirror added the bug label 2026-05-10 06:33:09 -05:00
GiteaMirror commented 2026-05-10 06:33:10 -05:00
Author
Owner
Copy Link

@novovictus commented on GitHub (May 9, 2026):

I built a small Windows/NVIDIA telemetry tool called WTG for this kind of debugging: figuring out whether a workload is really using the NVIDIA GPU, or whether Windows Task Manager is just not showing the relevant activity clearly.

Project page:
https://ninja-neer.net/

GitHub:
https://github.com/novovictus/WTG

Basic test:

.\wtg.exe --watch 250

Run that side-by-side with the workload and compare Task Manager, VRAM movement, GPU utilization, and power draw.

If Task Manager is flat but WTG shows VRAM/power/utilization movement, the GPU may be active and Task Manager may be misleading. If WTG is also flat, the workload probably is not reaching the NVIDIA GPU.

Happy to help interpret output if anyone posts a sample or emails wtg@ninja-neer.net.

<!-- gh-comment-id:4413488519 --> @novovictus commented on GitHub (May 9, 2026): I built a small Windows/NVIDIA telemetry tool called **WTG** for this kind of debugging: figuring out whether a workload is really using the NVIDIA GPU, or whether Windows Task Manager is just not showing the relevant activity clearly. **Project page:** https://ninja-neer.net/ **GitHub:** https://github.com/novovictus/WTG **Basic test:** ```powershell .\wtg.exe --watch 250 ``` Run that side-by-side with the workload and compare Task Manager, VRAM movement, GPU utilization, and power draw. If Task Manager is flat but WTG shows VRAM/power/utilization movement, the GPU may be active and Task Manager may be misleading. If WTG is also flat, the workload probably is not reaching the NVIDIA GPU. Happy to help interpret output if anyone posts a sample or emails [wtg@ninja-neer.net](mailto:wtg@ninja-neer.net).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#87892
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?