github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 00:22:43 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #6567] Improve error reporting with old or missing AMD driver on windows (unable to load amdhip64_6.dll) #29894

New Issue
Open
opened 2026-04-22 09:13:47 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-22 09:13:47 -05:00
Owner
Copy Link

Originally created by @Jiefei-Wang on GitHub (Aug 30, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/6567

Originally assigned to: @dhiltgen on GitHub.

I was trying to solve this issue that prevented me from using AMD GPU

time=2024-08-30T09:43:00.852-05:00 level=DEBUG source=amd_windows.go:33 msg="unable to load amdhip64_6.dll, 
please make sure to upgrade to the latest amd driver: The specified module could not be found."

Compared with the message for searching Nvidia, the AMD message is really minimal, here is the Nvidia output

time=2024-08-30T09:43:00.768-05:00 level=DEBUG source=gpu.go:469 msg="Searching for GPU library" name=cudart64_*.dll
time=2024-08-30T09:43:00.768-05:00 level=DEBUG source=gpu.go:488 msg="gpu library search" globs="[C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v12.2\\bin\\cudart64_*.dll* ..........]"

As you can see, ollama does not tell where it tries to find amdhip64_6. https://github.com/ROCm/ROCm/issues/3418#issuecomment-2253379050 said the DLL should be in C:\Windows\system32\amdhip64_6.dll, which is not the case as my dll is in C:\Program Files\AMD\ROCm\6.1\bin. It turns out that ollama uses the environment variable PATH to search for the DLL, which is not very clear just by reading the console debug output. To help future users, I'd like to suggest the following improvements:

  1. Print out the search path when searching for AMD GPU (like the Nvidia log above)
  2. Suppress Nvidia message when CUDA_VISIBLE_DEVICES=-1 and AMD message when HIP_VISIBLE_DEVICES=-1 to simplify the log (there is no need to print out the search path if one does not need Nvidia or AMD driver)
Originally created by @Jiefei-Wang on GitHub (Aug 30, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/6567 Originally assigned to: @dhiltgen on GitHub. I was trying to solve this issue that prevented me from using AMD GPU ``` time=2024-08-30T09:43:00.852-05:00 level=DEBUG source=amd_windows.go:33 msg="unable to load amdhip64_6.dll, please make sure to upgrade to the latest amd driver: The specified module could not be found." ``` Compared with the message for searching Nvidia, the AMD message is really minimal, here is the Nvidia output ``` time=2024-08-30T09:43:00.768-05:00 level=DEBUG source=gpu.go:469 msg="Searching for GPU library" name=cudart64_*.dll time=2024-08-30T09:43:00.768-05:00 level=DEBUG source=gpu.go:488 msg="gpu library search" globs="[C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v12.2\\bin\\cudart64_*.dll* ..........]" ``` As you can see, ollama does not tell where it tries to find `amdhip64_6`. https://github.com/ROCm/ROCm/issues/3418#issuecomment-2253379050 said the DLL should be in ` C:\Windows\system32\amdhip64_6.dll`, which is not the case as my dll is in `C:\Program Files\AMD\ROCm\6.1\bin`. It turns out that ollama uses the environment variable `PATH` to search for the DLL, which is not very clear just by reading the console debug output. To help future users, I'd like to suggest the following improvements: 1. Print out the search path when searching for AMD GPU (like the Nvidia log above) 2. Suppress Nvidia message when `CUDA_VISIBLE_DEVICES=-1` and AMD message when `HIP_VISIBLE_DEVICES=-1` to simplify the log (there is no need to print out the search path if one does not need Nvidia or AMD driver)
GiteaMirror added the feature requestamdwindows labels 2026-04-22 09:13:47 -05:00
GiteaMirror commented 2026-04-22 09:13:49 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Sep 3, 2024):

This DLL comes from the driver. It's not necessary to install ROCm on your system, but you will need to install the latest AMD driver. (e.g. 24.6.1)

<!-- gh-comment-id:2327463789 --> @dhiltgen commented on GitHub (Sep 3, 2024): This DLL comes from the driver. It's not necessary to install ROCm on your system, but you will need to install the latest AMD driver. (e.g. 24.6.1)
GiteaMirror commented 2026-04-22 09:13:50 -05:00
Author
Owner
Copy Link

@shoutsid commented on GitHub (Sep 15, 2024):

For those of us looking for where to download the 24.6.1 driver in question. As it wasn't obvious from googling around. https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-24-6-1.html#Contents

<!-- gh-comment-id:2351762246 --> @shoutsid commented on GitHub (Sep 15, 2024): For those of us looking for where to download the 24.6.1 driver in question. As it wasn't obvious from googling around. https://www.amd.com/en/resources/support-articles/release-notes/RN-RAD-WIN-24-6-1.html#Contents
GiteaMirror commented 2026-04-22 09:13:50 -05:00
Author
Owner
Copy Link

@fcstr commented on GitHub (Sep 21, 2024):

I am experiencing an issue with Ollama when using the latest AMD drivers (e.g., 24.6.1). Specifically, the application is looking for the file amdhip64_6.dll, but on my system (Windows 11 with the latest AMD drivers), the driver file in C:\Windows\System32 is named amdhip64.dll (without the "_6").

From the log:

time=2024-09-22T00:42:43.845+03:00 level=DEBUG source=amd_windows.go:33 msg="unable to load amdhip64_6.dll, please make sure to upgrade to the latest amd driver: The specified module could not be found."

Details:

OS: Windows 11
AMD Driver Version: 24.7.1
Path: C:\Windows\System32
Expected DLL: amdhip64_6.dll
Available DLL: amdhip64.dll

Could be that Ollama is expecting a different version or naming convention for the amdhip64.dll file. Could this discrepancy between the expected and available DLLs be the cause of the issue? If so, are there any workarounds or driver configuration settings that could resolve this?

<!-- gh-comment-id:2365331111 --> @fcstr commented on GitHub (Sep 21, 2024): I am experiencing an issue with Ollama when using the latest AMD drivers (e.g., 24.6.1). Specifically, the application is looking for the file amdhip64_6.dll, but on my system (Windows 11 with the latest AMD drivers), the driver file in C:\Windows\System32 is named amdhip64.dll (without the "_6"). From the log: time=2024-09-22T00:42:43.845+03:00 level=DEBUG source=amd_windows.go:33 msg="unable to load amdhip64_6.dll, please make sure to upgrade to the latest amd driver: The specified module could not be found." Details: OS: Windows 11 AMD Driver Version: 24.7.1 Path: C:\Windows\System32 Expected DLL: amdhip64_6.dll Available DLL: amdhip64.dll Could be that Ollama is expecting a different version or naming convention for the amdhip64.dll file. Could this discrepancy between the expected and available DLLs be the cause of the issue? If so, are there any workarounds or driver configuration settings that could resolve this?
GiteaMirror commented 2026-04-22 09:13:51 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Sep 24, 2024):

@fcstr I just upgraded a windows system to 24.8.1 and here's what I see:

> ls C:\Windows\System32\amdhip64*.dll


    Directory: C:\Windows\System32


Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----         8/28/2024   5:37 PM       21762464 amdhip64.dll
-a----         8/28/2024   5:37 PM       20438408 amdhip64_6.dll

I believe the dll without the _6 is a v5 library which wont be compatible with our software. If you don't see a _6 file there, can you try running the following in an admin powershell and see if it appears someplace else?

> gci -path c:\windows -r -fi "amdhip64*.dll"
<!-- gh-comment-id:2371885740 --> @dhiltgen commented on GitHub (Sep 24, 2024): @fcstr I just upgraded a windows system to 24.8.1 and here's what I see: ``` > ls C:\Windows\System32\amdhip64*.dll Directory: C:\Windows\System32 Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 8/28/2024 5:37 PM 21762464 amdhip64.dll -a---- 8/28/2024 5:37 PM 20438408 amdhip64_6.dll ``` I believe the dll without the _6 is a v5 library which wont be compatible with our software. If you don't see a _6 file there, can you try running the following in an admin powershell and see if it appears someplace else? ```powershell > gci -path c:\windows -r -fi "amdhip64*.dll" ```
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 amd feature request windows
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#29894
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?