Repository navigation
Description
Name and Version
C:\LLM\vLLM>llamacpp\llama-server --version
version: 0.1.0-dev (build 10437, commit 16d222f)
built with Clang 20.1.8 for Windows x86_64
Operating systems
Windows
GGML backends
Vulkan
Hardware
AMD Ryzen AI MAX+ 395 @ 128GB shared memory
Models
https://huggingface.co/ggml-org/Qwen3.8-27B-GGUF:Q8_0 with vision enabled
Problem description & steps to reproduce
When providing an image via the webui and simply asking what it sees in the image, the server silently crashes even with verbose logging.
First Bad Commit
No response
Relevant log output
C:\LLM\vLLM>llamacpp\llama-server -hf ggml-org/Qwen3.8-27B-GGUF:Q8_0 --hf-token <token_deleted> --jinja -ngl 99 -c 65536
0.00.476.362 I cmn common_param: common_params_print_info: verbosity = 3 (adjust with the -lv N CLI arg)
0.00.477.937 W srv llama_server: -----------------
0.00.477.943 W srv llama_server: CORS is set to allow all origins ('*') and no API key is set
0.00.477.944 W srv llama_server: this can be a security risk (cross-origin attacks)
0.00.477.944 W srv llama_server: more info: #25655
0.00.477.945 W srv llama_server: -----------------
Downloading mmproj-Qwen3.8-27B-Q8_0.gguf ─────────────────────────── 100%
Downloading Qwen3.8-27B-Q8_0.gguf ────────────────────────────────── 100%
68.09.817.504 W finalize_file: failed to create symlink: A required privilege is not held by the client.
68.09.817.510 W finalize_file: switching to degraded mode
68.09.833.809 I srv load_model: loading model 'ggml-org/Qwen3.8-27B-GGUF:Q8_0'
68.18.031.614 I cmn init: llama threadpool init, n_threads = 16
68.18.284.342 W load_hparams: Qwen-VL models require at minimum 1024 image tokens to function correctly on grounding tasks
68.18.284.348 W load_hparams: if you encounter problems with accuracy, try adding --image-min-tokens 1024
68.18.284.348 W load_hparams: more info: #16842
68.18.730.138 I srv load_model: loaded multimodal model, 'C:\Users<username_deleted>.cache\huggingface\hub\models--ggml-org--Qwen3.8-27B-GGUF\snapshots\0669b98607d47046c7c2b3f801011d54a08cfccf\mmproj-Qwen3.8-27B-Q8_0.gguf'
68.19.172.410 I srv load_model: initializing, n_slots = 4, n_ctx_slot = 65536, kv_unified = 'true'
68.19.181.947 I srv init: chat template supports preserving reasoning, consider enabling it via --reasoning-preserve
68.19.181.972 I srv llama_server: model loaded
68.19.181.977 I srv llama_server: listening on http://127.0.0.1:8080
68.19.181.977 W srv llama_server: NOTICE: server default port will be changed to :9931 in a future release
68.19.181.978 W srv llama_server: ref: #26508
68.54.927.911 I slot get_availabl: id 3 | task -1 | selected slot by LRU, t_last = -1
68.54.929.055 I slot launch_slot_: id 3 | task 0 | processing task, is_child = 0
68.59.734.505 I slot print_timing: id 3 | task 0 | prompt processing, n_tokens = 46, progress = 0.02, t = 4.81 s / 9.57 tokens per second
C:\LLM\vLLM>
Activity
AriatneAI commentedon Aug 15, 2026
To clarify, this is not a new bug. It also happened with Qwen3.6 from unsloth and Qwen3.8 from unsloth as well.
AriatneAI commentedon Aug 15, 2026
Text alone with MTP works
[-]Eval bug:[/-][+]Eval bug: Vision not working with Qwen 27B 3.6/3.8 on AMD AI Max[/+]cobra91 commentedon Aug 15, 2026
Log say 68.18.284.342 W load_hparams: Qwen-VL models require at minimum 1024 image tokens to function correctly on grounding tasks
68.18.284.348 W load_hparams: if you encounter problems with accuracy, try adding --image-min-tokens 1024
Did u test to add it ? Because on many model without this args vision not working ;)
AriatneAI commentedon Aug 15, 2026
Yes,
Result:
And also without MTP
Here's the snip of the chat
same silent crash :(
AriatneAI commentedon Aug 15, 2026
Also worth mentioning: same setup works on an NVIDIA 4080
AriatneAI commentedon Aug 15, 2026
On the same AMD AI Max machine using the ROCm version the test runs as well, but at very slow speeds because its not using the GPU
So it seems to be related to the Vulcan backend
AriatneAI commentedon Aug 15, 2026
On a related note: disabling flash attention, even at minimal context length of 8K and no vision, also leads to a crash
AriatneAI commentedon Aug 15, 2026
--no-mmproj-offload fixes it, then the server uses the CPU instead
satoyon commentedon Aug 16, 2026
On my AMD Ryzen AI MAX+ 395, I am able to input images and the model correctly describes their content.
Command-line arguments:
Logs during execution:
However, when processing an image, several warnings appear such as:
W find_slot: non-consecutive token position 46 after 45 for sequence 0 with N new tokens
These do not seem to cause any actual issues in the output.
AriatneAI commentedon Aug 16, 2026
If I may ask, Linux or MS Host? Terminal looks like Linux
satoyon commentedon Aug 16, 2026
It's actually Windows 11 Pro 25H2.
AriatneAI commentedon Aug 16, 2026
Is this the ROCm version?
Did you install any ROCm drivers? because when I use the ROCm version --list_devices does not report any
AriatneAI commentedon Aug 16, 2026
I tried your command and it still crashes on me :/
satoyon commentedon Aug 16, 2026
Yes, I am using the ROCm version (Release build b10410). Please refer to this issue for instructions on how to use it:
#26996
AriatneAI commentedon Aug 16, 2026
You, Sir, are my hero! It works! 💃
bitlamas commentedon Sep 2, 2026
same symptom on a different model: qwen3.8-flash-next. but with one caveat:
llama-mtmd-clihandles the image.llama-serverdoes not. same model, same mmproj, same build, same gpu.that rules out the weights, the projector and the vulkan backend, and leaves the server path.
environment:
36b101543), vulkan, msvc x6432.0.31007.5012, windows 11qwen4exp), UD-Q4_K_XL, mmproj F16the model differs from the one in the report, so the shared factor is not the architecture.
the failing invocation:
the server's last lines before the exit:
the process ends there. the http request returns a connection reset.
the same model and projector under
llama-mtmd-clicomplete, and the answer describes the image correctly:what the failure is not:
find_slotwarnings. they appear in the successfulllama-mtmd-clirun as well.image decodedis logged for every batch before the exit.negative checks, with what each could have seen:
GGML_ASSERTin 420 lines of-lv 4output. that log does carry asserts. one appears in the same file for an unrelated failure on the same build.%LOCALAPPDATA%\CrashDumpsholds dumps for this binary from earlier unrelated faults, so collection works.on this build the exit is not an unhandled exception.
one extra observation. after a failed image request, the next plain text request to the same server also ends the process. text requests issued before any image are stable across many turns.
if you need i'm willing to test a patch build on this hardware, or let me know if you need further logs or a higher verbosity capture.
update:
--no-mmproj-offloadfixes this on vulkan, confirmed on a second architecture.the workaround posted earlier in this thread also works for qwen3.8-flash-next (
qwen4exp), build 10737, vulkan, Radeon 8060S. the projector runs on cpu, the server describes the image correctly, and a plain text request sent immediately afterwards also succeeds. the process stays alive.so the failure is in the gpu path for the projector, not in the weights, the projector file, or the model architecture.
llama-mtmd-cliwas already working with the same model and mmproj before this change, which points the same way.cost of the workaround, measured on this hardware:
--image-min-tokens 1024raises even a 64x64 image to 1024 tokens, so any image costs about a minute.resizing images before sending is the practical mitigation. dropping
--image-min-tokensis the other lever where grounding accuracy is not needed.one note for anyone arriving here from a search: this issue is closed, but the vulkan path is not fixed. the close followed a move to a rocm build. on vulkan the crash still reproduces on current master unless
--no-mmproj-offloadis passed.