Issue Station
Sign In
Tools hereToolbox

ollama - ✅(Solved) Fix windows11 ,ollama 0.19.0 meet trouble "loading..." [1 pull requests, 8 comments, 7 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
ollama/ollama#15253•Fetched 2026-04-08 02:33:37
View on GitHub
Comments
8
Participants
7
Timeline
10
Reactions
0
Author
palarking-huepalarking-hue
Participants
cheryeicheryeiCynaConsCynaConslbitoylbitoyliams000liams000palarking-huepalarking-huePolystation64Polystation64premmaddalipremmaddali
Timeline (top)
commented ×8cross-referenced ×1labeled ×1

Error Message

Exception 0xc0000005 0x8 0xffffffffffffffff 0xffffffffffffffff

PR fix notes

PR #15383: x/imagegen/mlx: this fix stops ollama from failing to initialise when running on non-mlx supported hardware, it can continue with CPU

Description (problem / solution / changelog)

Issue: #15253

My computer is a windows machine running on an AMD CPU and an AMD Radeon RX 6750 XT, I am blessed with not having CUDA and running into problems when running local LLMs. Recently I downloaded Ollama and ran into the issue that I couldn't even get the command to return anything without instantly getting the bellow error:

Exception 0xc0000005 0x8 0xffffffffffffffff 0xffffffffffffffff
PC=0xffffffffffffffff
signal arrived during external code execution

runtime.cgocall(0x7ff654cb1790, 0xc00004dda0)
        runtime/cgocall.go:167 +0x3e fp=0xc00004dd78 sp=0xc00004dd10 pc=0x7ff653b8243e
github.com/ollama/ollama/x/imagegen/mlx._Cfunc_mlx_random_key(0xc0000962e0, 0x19d6747566d)
        _cgo_gotypes.go:1978 +0x50 fp=0xc00004dda0 sp=0xc00004dd78 pc=0x7ff654210930
github.com/ollama/ollama/x/imagegen/mlx.RandomKey.func1(...)
        github.com/ollama/ollama/x/imagegen/mlx/mlx.go:1870
github.com/ollama/ollama/x/imagegen/mlx.RandomKey(0x19d6747566d)
        github.com/ollama/ollama/x/imagegen/mlx/mlx.go:1870 +0x5d fp=0xc00004ddd8 sp=0xc00004dda0 pc=0x7ff65421985d
github.com/ollama/ollama/x/imagegen/mlx.init.0()
        github.com/ollama/ollama/x/imagegen/mlx/mlx.go:1848 +0xa9 fp=0xc00004de28 sp=0xc00004ddd8 pc=0x7ff654219669
runtime.doInit1(0x7ff6560412c0)
        runtime/proc.go:7350 +0xdd fp=0xc00004df50 sp=0xc00004de28 pc=0x7ff653b6343d
runtime.doInit(...)
        runtime/proc.go:7317
runtime.main()
        runtime/proc.go:254 +0x325 fp=0xc00004dfe0 sp=0xc00004df50 pc=0x7ff653b54e85
runtime.goexit({})
        runtime/asm_amd64.s:1700 +0x1 fp=0xc00004dfe8 sp=0xc00004dfe0 pc=0x7ff653b8db21

The change I am proposing, protects the usage of the MLX lib in the event that it didn't happen to throw an error at time of init. Returning and continuing on should be ok as the application should fall back to using CPU in this scenario.

This fixes the issues some users have been recently experiencing.

Changed files

  • x/imagegen/mlx/mlx.go (modified, +5/-0)
RAW_BUFFERClick to expand / collapse

What is the issue?

When I use ollama 0.19.0,it can not load any models,just show "loading...",see this image: <img width="1108" height="863" alt="Image" src="https://github.com/user-attachments/assets/1839aebb-9fc3-4387-9463-eb4f902de5ba" /> when i exec "ollama --version" in cmd,ollama throw errors,msg like: PS C:\WINDOWS\system32> ollama --version Exception 0xc0000005 0x8 0xffffffffffffffff 0xffffffffffffffff PC=0xffffffffffffffff signal arrived during external code execution

runtime.cgocall(0x7ff6bf89c860, 0xc000045da0) runtime/cgocall.go:167 +0x3e fp=0xc000045d78 sp=0xc000045d10 pc=0x7ff6be79243e github.com/ollama/ollama/x/imagegen/mlx._Cfunc_mlx_random_key(0xc0000802e0, 0x19d4de7e62f) _cgo_gotypes.go:1978 +0x50 fp=0xc000045da0 sp=0xc000045d78 pc=0x7ff6bee0ea50 github.com/ollama/ollama/x/imagegen/mlx.RandomKey.func1(...) github.com/ollama/ollama/x/imagegen/mlx/mlx.go:1870 github.com/ollama/ollama/x/imagegen/mlx.RandomKey(0x19d4de7e62f) github.com/ollama/ollama/x/imagegen/mlx/mlx.go:1870 +0x5d fp=0xc000045dd8 sp=0xc000045da0 pc=0x7ff6bee1797d github.com/ollama/ollama/x/imagegen/mlx.init.0() github.com/ollama/ollama/x/imagegen/mlx/mlx.go:1848 +0xa9 fp=0xc000045e28 sp=0xc000045dd8 pc=0x7ff6bee17789 runtime.doInit1(0x7ff6c0c0f2c0) runtime/proc.go:7350 +0xdd fp=0xc000045f50 sp=0xc000045e28 pc=0x7ff6be77343d runtime.doInit(...) runtime/proc.go:7317 runtime.main() runtime/proc.go:254 +0x325 fp=0xc000045fe0 sp=0xc000045f50 pc=0x7ff6be764e85 runtime.goexit({}) runtime/asm_amd64.s:1700 +0x1 fp=0xc000045fe8 sp=0xc000045fe0 pc=0x7ff6be79db21

goroutine 2 gp=0xc0000028c0 m=nil [force gc (idle)]: runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?) runtime/proc.go:435 +0xce fp=0xc000079fa8 sp=0xc000079f88 pc=0x7ff6be79598e runtime.goparkunlock(...) runtime/proc.go:441 runtime.forcegchelper() runtime/proc.go:348 +0xb8 fp=0xc000079fe0 sp=0xc000079fa8 pc=0x7ff6be7650f8 runtime.goexit({}) runtime/asm_amd64.s:1700 +0x1 fp=0xc000079fe8 sp=0xc000079fe0 pc=0x7ff6be79db21 created by runtime.init.7 in goroutine 1 runtime/proc.go:336 +0x1a

goroutine 3 gp=0xc000002c40 m=nil [GC sweep wait]: runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?) runtime/proc.go:435 +0xce fp=0xc00007bf80 sp=0xc00007bf60 pc=0x7ff6be79598e runtime.goparkunlock(...) runtime/proc.go:441 runtime.bgsweep(0xc000088000) runtime/mgcsweep.go:276 +0x94 fp=0xc00007bfc8 sp=0xc00007bf80 pc=0x7ff6be74de74 runtime.gcenable.gowrap1() runtime/mgc.go:204 +0x25 fp=0xc00007bfe0 sp=0xc00007bfc8 pc=0x7ff6be742285 runtime.goexit({}) runtime/asm_amd64.s:1700 +0x1 fp=0xc00007bfe8 sp=0xc00007bfe0 pc=0x7ff6be79db21 created by runtime.gcenable in goroutine 1 runtime/mgc.go:204 +0x66

goroutine 4 gp=0xc000002e00 m=nil [GC scavenge wait]: runtime.gopark(0xc000088000?, 0x7ff6c016a760?, 0x1?, 0x0?, 0xc000002e00?) runtime/proc.go:435 +0xce fp=0xc00008ff78 sp=0xc00008ff58 pc=0x7ff6be79598e runtime.goparkunlock(...) runtime/proc.go:441 runtime.(*scavengerState).park(0x7ff6c0d29ba0) runtime/mgcscavenge.go:425 +0x49 fp=0xc00008ffa8 sp=0xc00008ff78 pc=0x7ff6be74b909 runtime.bgscavenge(0xc000088000) runtime/mgcscavenge.go:653 +0x3c fp=0xc00008ffc8 sp=0xc00008ffa8 pc=0x7ff6be74be7c runtime.gcenable.gowrap2() runtime/mgc.go:205 +0x25 fp=0xc00008ffe0 sp=0xc00008ffc8 pc=0x7ff6be742225 runtime.goexit({}) runtime/asm_amd64.s:1700 +0x1 fp=0xc00008ffe8 sp=0xc00008ffe0 pc=0x7ff6be79db21 created by runtime.gcenable in goroutine 1 runtime/mgc.go:205 +0xa5

goroutine 5 gp=0xc000003340 m=nil [finalizer wait]: runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?) runtime/proc.go:435 +0xce fp=0xc000091e30 sp=0xc000091e10 pc=0x7ff6be79598e runtime.runfinq() runtime/mfinal.go:196 +0x107 fp=0xc000091fe0 sp=0xc000091e30 pc=0x7ff6be741207 runtime.goexit({}) runtime/asm_amd64.s:1700 +0x1 fp=0xc000091fe8 sp=0xc000091fe0 pc=0x7ff6be79db21 created by runtime.createfing in goroutine 1 runtime/mfinal.go:166 +0x3d rax 0xffffffffffffffff rbx 0x7ffbcc47e5b0 rcx 0x7ffbcc47e598 rdx 0x7ffbcc016300 rdi 0x0 rsi 0x4c5953f890 rbp 0x7ffc9f950380 rsp 0x4c5953f7d8 r8 0x32c8 r9 0x0 r10 0x1c71cb90000 r11 0xc000000d r12 0xffffffffffffffff r13 0x5d r14 0x1 r15 0x0 rip 0xffffffffffffffff rflags 0x10286 cs 0x33 fs 0x53 gs 0x2b PS C:\WINDOWS\system32>

My computer is

<img width="1108" height="842" alt="Image" src="https://github.com/user-attachments/assets/0e478e33-52a1-4f22-8ed0-45e8ef27dece" />

Relevant log output

OS

windows 11

GPU

intel ark 130T

CPU

intel ultra 5

Ollama version

0.19.0

extent analysis

TL;DR

The issue with ollama 0.19.0 failing to load models and throwing errors may be related to compatibility or dependency issues, and a potential workaround could be to check for updates or try a different version.

Guidance

  • Check the ollama documentation and GitHub page for any known issues or compatibility problems with Windows 11 or the specified hardware configuration.
  • Verify that all dependencies required by ollama are properly installed and up-to-date.
  • Consider trying a different version of ollama to see if the issue persists, as this could help identify if the problem is version-specific.
  • Review the stacktrace for any clues about the specific cause of the error, such as issues with memory allocation or external code execution.

Example

No specific code example is applicable in this case, as the issue appears to be related to the ollama application itself rather than user-written code.

Notes

The provided information does not include specific details about the models being loaded or the exact steps taken before the error occurs, which could be helpful in diagnosing the issue. Additionally, the error message suggests a low-level system error, which may require specific technical expertise to resolve.

Recommendation

Apply workaround: Try a different version of ollama or check for updates to see if the issue is resolved, as this is a non-invasive and relatively simple step that could potentially resolve the problem.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#prompt issue#agent setup#task chaining#parallel task#integration issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING