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 #10463] all model can not run when added QWEN3:32b #32641

New Issue
Closed
opened 2026-04-22 14:17:01 -05:00 by GiteaMirror · 10 comments
GiteaMirror commented 2026-04-22 14:17:01 -05:00
Owner
Copy Link

Originally created by @honhwa on GitHub (Apr 29, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10463

What is the issue?

ollama run any model, show "Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed" when I added qwen3:32b

Relevant log output

OS

No response

GPU

No response

CPU

No response

Ollama version

No response

Originally created by @honhwa on GitHub (Apr 29, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10463 ### What is the issue? ollama run any model, show "Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed" when I added qwen3:32b ### Relevant log output ```shell ``` ### OS _No response_ ### GPU _No response_ ### CPU _No response_ ### Ollama version _No response_
GiteaMirror added the bug label 2026-04-22 14:17:01 -05:00
GiteaMirror commented 2026-04-22 14:17:03 -05:00
Author
Owner
Copy Link

@kingproud commented on GitHub (Apr 29, 2025):

Me too. All model can't run.

PS C:\Users\lkp> ollama list

NAME ID SIZE MODIFIED
qwen3:30b-a3b 2ee832bc15b5 18 GB 54 minutes ago
deepseek-r1:14b ea35dfe18182 9.0 GB 7 hours ago

PS C:\Users\lkp> ollama run qwen3:30b-a3b

Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed

PS C:\Users\lkp> ollama run deepseek-r1:14b

Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed

<!-- gh-comment-id:2837896780 --> @kingproud commented on GitHub (Apr 29, 2025): Me too. All model can't run. ### PS C:\Users\lkp> ollama list NAME ID SIZE MODIFIED qwen3:30b-a3b 2ee832bc15b5 18 GB 54 minutes ago deepseek-r1:14b ea35dfe18182 9.0 GB 7 hours ago ### PS C:\Users\lkp> ollama run qwen3:30b-a3b Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed ### PS C:\Users\lkp> ollama run deepseek-r1:14b Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed
GiteaMirror commented 2026-04-22 14:17:04 -05:00
Author
Owner
Copy Link

@nix18 commented on GitHub (Apr 29, 2025):

Me too. All model can't run.

PS C:\Users\lkp> ollama list

NAME ID SIZE MODIFIED qwen3:30b-a3b 2ee832bc15b5 18 GB 54 minutes ago deepseek-r1:14b ea35dfe18182 9.0 GB 7 hours ago

PS C:\Users\lkp> ollama run qwen3:30b-a3b

Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed

PS C:\Users\lkp> ollama run deepseek-r1:14b

Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed

Me too. Manually compiling ollama from source code also reports an error [llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed] and cannot run

<!-- gh-comment-id:2837915004 --> @nix18 commented on GitHub (Apr 29, 2025): > Me too. All model can't run. > > ### PS C:\Users\lkp> ollama list > NAME ID SIZE MODIFIED qwen3:30b-a3b 2ee832bc15b5 18 GB 54 minutes ago deepseek-r1:14b ea35dfe18182 9.0 GB 7 hours ago > > ### PS C:\Users\lkp> ollama run qwen3:30b-a3b > Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed > > ### PS C:\Users\lkp> ollama run deepseek-r1:14b > Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed Me too. Manually compiling ollama from source code also reports an error [llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed] and cannot run
GiteaMirror commented 2026-04-22 14:17:05 -05:00
Author
Owner
Copy Link

@jerrykenny2012 commented on GitHub (Apr 29, 2025):

Me too.
After running the Qwen3 model, Ollama completely crashed.
Ollama can no longer be restarted or run.

<!-- gh-comment-id:2837938430 --> @jerrykenny2012 commented on GitHub (Apr 29, 2025): Me too. After running the Qwen3 model, Ollama completely crashed. Ollama can no longer be restarted or run.
GiteaMirror commented 2026-04-22 14:17:06 -05:00
Author
Owner
Copy Link

@codingcn commented on GitHub (Apr 29, 2025):

same issues

<!-- gh-comment-id:2837958792 --> @codingcn commented on GitHub (Apr 29, 2025): same issues
GiteaMirror commented 2026-04-22 14:17:08 -05:00
Author
Owner
Copy Link

@Hunter6324 commented on GitHub (Apr 29, 2025):

Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed

<!-- gh-comment-id:2838139997 --> @Hunter6324 commented on GitHub (Apr 29, 2025): Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed
GiteaMirror commented 2026-04-22 14:17:10 -05:00
Author
Owner
Copy Link

@oncedays commented on GitHub (Apr 29, 2025):

俺也一样。Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed

<!-- gh-comment-id:2838187103 --> @oncedays commented on GitHub (Apr 29, 2025): 俺也一样。Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed
GiteaMirror commented 2026-04-22 14:17:12 -05:00
Author
Owner
Copy Link

@MoktanP commented on GitHub (Apr 29, 2025):

What is the issue?

ollama run any model, show "Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed" when I added qwen3:32b

Relevant log output

OS

No response

GPU

No response

CPU

No response

Ollama version

No response

me too
llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed

<!-- gh-comment-id:2839461515 --> @MoktanP commented on GitHub (Apr 29, 2025): > ### What is the issue? > > ollama run any model, show "Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed" when I added qwen3:32b > ### Relevant log output > > ### OS > > _No response_ > ### GPU > > _No response_ > ### CPU > > _No response_ > ### Ollama version > > _No response_ me too llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed
GiteaMirror commented 2026-04-22 14:17:15 -05:00
Author
Owner
Copy Link

@mattjrutter commented on GitHub (Apr 29, 2025):

Docker 4.41.0 issue
Roll back or rename some dlls: https://github.com/ollama/ollama/issues/9509

<!-- gh-comment-id:2840288607 --> @mattjrutter commented on GitHub (Apr 29, 2025): Docker 4.41.0 issue Roll back or rename some dlls: https://github.com/ollama/ollama/issues/9509
GiteaMirror commented 2026-04-22 14:17:17 -05:00
Author
Owner
Copy Link

@oncedays commented on GitHub (Apr 30, 2025):

俺也一样。Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed

卸载docker后好了

<!-- gh-comment-id:2840828310 --> @oncedays commented on GitHub (Apr 30, 2025): > 俺也一样。Error: llama runner process has terminated: GGML_ASSERT(tensor->op == GGML_OP_UNARY) failed 卸载docker后好了
GiteaMirror commented 2026-04-22 14:17:18 -05:00
Author
Owner
Copy Link

@kingproud commented on GitHub (Apr 30, 2025):

#10469 这样做，我的弄好了。This way, it's fixed for me.

GitHub Copilot:

This issue might be caused by a conflict between Ollama and certain library files (DLL files) installed by Docker Desktop.
这个问题可能是由于 Ollama 与 Docker Desktop 安装的某些库文件（DLL 文件）之间发生冲突引起的。

The idea behind the solution is to find these potentially conflicting Docker files and rename them so that Ollama doesn't load them.
解决方案背后的想法是找到这些可能冲突的 Docker 文件并将它们重命名，以便 Ollama 不会加载它们。

Here are the specific steps:
具体步骤如下：

Open Command Prompt or PowerShell as Administrator:
以管理员身份打开命令提示符或 PowerShell：

Type cmd or powershell in the Windows search bar.
在 Windows 搜索栏中输入 cmd 或 powershell。
Right-click on "Command Prompt" or "Windows PowerShell" in the search results.
在搜索结果中右键单击“命令提示符”或“Windows PowerShell”。
Select "Run as administrator".
以管理员身份运行
Change to the Docker Directory:
切换到 Docker 目录：

In the administrator Command Prompt or PowerShell window that opens, type the following command and press Enter:
在打开的管理员命令提示符或 PowerShell 窗口中，输入以下命令并按 Enter 键：
cd "C:\Program Files\Docker\Docker\resources\bin"
Rename the Conflicting DLL Files:
重命名冲突的 DLL 文件：

Execute the following commands one by one to rename each file (adding a .old suffix to the original filename):
依次执行以下命令来重命名每个文件（给原始文件名添加 .old 后缀）：
ren ggml-base.dll ggml-base.dll.old
ren ggml-cpu.dll ggml-cpu.dll.old
ren ggml.dll ggml.dll.old
ren llama.dll llama.dll.old
If a file doesn't exist, you'll see an error message. You can ignore it and proceed to the next command.
如果文件不存在，您将看到错误消息。您可以忽略它并继续执行下一个命令。
Retry Running the Ollama Command:
重试运行 Ollama 命令：

Go back to the terminal window where you were previously running Ollama (or run it directly in the administrator window) and try again:
返回之前运行 Ollama 的终端窗口（或在管理员窗口中直接运行）并重试：
ollama run qwen3:14b ollama 运行 qwen3:14b
Note: 注意：

Renaming these files might affect some functionalities of Docker Desktop. If you encounter issues with Docker Desktop, you can rename the files back (remove the .old suffix).
重命名这些文件可能会影响 Docker Desktop 的某些功能。如果您遇到 Docker Desktop 的问题，可以恢复文件名（移除 .old 后缀）。
This method is based on the experience of other users and is not guaranteed to solve your problem, but it's worth trying.
这种方法基于其他用户的经验，并不能保证能解决您的问题，但值得一试。

<!-- gh-comment-id:2841747706 --> @kingproud commented on GitHub (Apr 30, 2025): #10469 这样做，我的弄好了。This way, it's fixed for me. GitHub Copilot: This issue might be caused by a conflict between Ollama and certain library files (DLL files) installed by Docker Desktop. 这个问题可能是由于 Ollama 与 Docker Desktop 安装的某些库文件（DLL 文件）之间发生冲突引起的。 The idea behind the solution is to find these potentially conflicting Docker files and rename them so that Ollama doesn't load them. 解决方案背后的想法是找到这些可能冲突的 Docker 文件并将它们重命名，以便 Ollama 不会加载它们。 Here are the specific steps: 具体步骤如下： Open Command Prompt or PowerShell as Administrator: 以管理员身份打开命令提示符或 PowerShell： Type cmd or powershell in the Windows search bar. 在 Windows 搜索栏中输入 cmd 或 powershell。 Right-click on "Command Prompt" or "Windows PowerShell" in the search results. 在搜索结果中右键单击“命令提示符”或“Windows PowerShell”。 Select "Run as administrator". 以管理员身份运行 Change to the Docker Directory: 切换到 Docker 目录： In the administrator Command Prompt or PowerShell window that opens, type the following command and press Enter: 在打开的管理员命令提示符或 PowerShell 窗口中，输入以下命令并按 Enter 键： cd "C:\Program Files\Docker\Docker\resources\bin" Rename the Conflicting DLL Files: 重命名冲突的 DLL 文件： Execute the following commands one by one to rename each file (adding a .old suffix to the original filename): 依次执行以下命令来重命名每个文件（给原始文件名添加 .old 后缀）： ren ggml-base.dll ggml-base.dll.old ren ggml-cpu.dll ggml-cpu.dll.old ren ggml.dll ggml.dll.old ren llama.dll llama.dll.old If a file doesn't exist, you'll see an error message. You can ignore it and proceed to the next command. 如果文件不存在，您将看到错误消息。您可以忽略它并继续执行下一个命令。 Retry Running the Ollama Command: 重试运行 Ollama 命令： Go back to the terminal window where you were previously running Ollama (or run it directly in the administrator window) and try again: 返回之前运行 Ollama 的终端窗口（或在管理员窗口中直接运行）并重试： ollama run qwen3:14b ollama 运行 qwen3:14b Note: 注意： Renaming these files might affect some functionalities of Docker Desktop. If you encounter issues with Docker Desktop, you can rename the files back (remove the .old suffix). 重命名这些文件可能会影响 Docker Desktop 的某些功能。如果您遇到 Docker Desktop 的问题，可以恢复文件名（移除 .old 后缀）。 This method is based on the experience of other users and is not guaranteed to solve your problem, but it's worth trying. 这种方法基于其他用户的经验，并不能保证能解决您的问题，但值得一试。
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#32641
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?