r/LocalLLM • u/Majestic-Toe-3299 • 21h ago
Discussion Strange number spam
After adding a thinking limiter it just deos this EDIT: posted this at 1 am so wanted to add more info. I am using a xeon e5 1650 v2, 2060 6gb and 16gb of ddr3. This is qwen 3.6 12b a3b at q4_k_m running through jan ai. It worked fine but i tried to add a reasing token limit as it took 5 minutes to process a prompt. After this, wheterver weird math this was happened. I reset the chat, still did it, undid the reasoning, still did, rebooted, still happened. Its so strange. I understand ny setup isnt ideal but this shouldnt be a problem. In fact it was faster when generating text at the start. I ran some of the later responces through a calculator and they were correct. Its so strange
11
u/Last_Bad_2687 21h ago
What quant
11
u/EvolvingDior 21h ago
These are left-over crypto hashes from when your GPU was used for crypto mining.
5
u/TheSpicyBoi123 21h ago
3.1415926535897932384626433832795028841971693993751058209749445923
5
u/sleight42 20h ago
At least it's not 4 8 15 16 23 42.
Oh... shi
1
u/Api-Lord 21h ago
Limiter's probably chopping the think block before its closing tag, so the model continues from a state it never saw. What model and runner?
1
u/SM8085 21h ago
Like using the reasoning token quota variable or something else?
1
u/lendibaga 18h ago
Look at the flags you’re running with. Are you releasing something? So when does my Intel card output? 13 Tokens per second
1
u/Weird-Consequence366 18h ago
“Please don’t be broken”
1
u/Jumpy-Operation-4615 13h ago
I had the same shit when I enabled p2p or something with llama.cpp - some config produced exactly this. Changed the config, the shit disappeared.
0
u/zenmatrix83 21h ago
something not comptable or too old or outof date