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 #10219] System crashes when attempting to load a model that exceeds RAM capacity #32466

New Issue
Closed
opened 2026-04-22 13:45:42 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-22 13:45:42 -05:00
Owner
Copy Link

Originally created by @yukkuriTV on GitHub (Apr 10, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/10219

What is the issue?

This happened with gemma3:12b-it-q8_0. The installed memory is 16GB, but most of it is actually occupied by Windows. Therefore, a small amount of swap should be used during loading, but this does not work properly and the whole system crashes. Since it crashes, you cannot check the log. It's the worst.

Relevant log output

OS

Windows

GPU

Nvidia

CPU

Intel

Ollama version

0.6.5

Originally created by @yukkuriTV on GitHub (Apr 10, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/10219 ### What is the issue? This happened with gemma3:12b-it-q8_0. The installed memory is 16GB, but most of it is actually occupied by Windows. Therefore, a small amount of swap should be used during loading, but this does not work properly and the whole system crashes. Since it crashes, you cannot check the log. It's the worst. ### Relevant log output ```shell ``` ### OS Windows ### GPU Nvidia ### CPU Intel ### Ollama version 0.6.5
GiteaMirror added the needs more infobug labels 2026-04-22 13:45:42 -05:00
GiteaMirror commented 2026-04-22 13:45:46 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Apr 10, 2025):

The server log will have been written before the runner crashed, see here on how to locate it.. As there is no log provided but you think RAM has been exceeded, I would guess an OOM issue, in which case see here for mitigation techniques..

<!-- gh-comment-id:2794164731 --> @rick-github commented on GitHub (Apr 10, 2025): The server log will have been written before the runner crashed, see [here](https://github.com/ollama/ollama/blob/main/docs/troubleshooting.md#how-to-troubleshoot-issues) on how to locate it.. As there is no log provided but you think RAM has been exceeded, I would guess an OOM issue, in which case see [here](https://github.com/ollama/ollama/issues/8597#issuecomment-2614533288) for mitigation techniques..
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 needs more info
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#32466
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?