Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #1322] [BUG]: Hard lockup of Windows 11 computer when using native embeddings option in AnythingLLM v1.5.3 & v1.5.5 #830

New Issue
Closed
opened 2026-02-22 18:21:38 -05:00 by yindo · 3 comments
yindo commented 2026-02-22 18:21:38 -05:00
Owner
Copy Link
Copy Source

Originally created by @LindsayRex on GitHub (May 9, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1322

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

Issue: Hard lockup of Windows 11 computer when using native embeddings option in AnythingLLM v1.5.3 to encode PDFs for a Milvus DB

Description:
Whenever I attempt to utilize the native embeddings option in AnythingLLM v1.5.3 to encode PDFs for a Milvus DB, my Windows 11 computer experiences a hard lockup. There are no blue screens or debug messages; instead, the entire system abruptly reboots after approximately one minute of running the embedding process. This issue does not occur with previous versions of the software. It seems like the CPU is being overloaded during the process.

Alternative Solutions Attempted:
I also tried using LM Studio Nomic 1.5 embeddings with local services, but encountered errors. Despite witnessing GPU activity, indicating processing of PDF files, there is no interaction with the Milvus server, as evidenced by the absence of network traffic, unlike when utilizing the native embeddings option.

System Information:

Operating System: Windows 11 (latest edition)
CPU: Intel Core i7 12900k
GPU: Nvidia RTX 4070 Super
Request:
I'm seeking guidance on how to capture relevant logs or troubleshoot this issue, as the current version of the software appears to be unusable on Window

Are there known steps to reproduce?

No response

Originally created by @LindsayRex on GitHub (May 9, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/1322 ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? Issue: Hard lockup of Windows 11 computer when using native embeddings option in AnythingLLM v1.5.3 to encode PDFs for a Milvus DB Description: Whenever I attempt to utilize the native embeddings option in AnythingLLM v1.5.3 to encode PDFs for a Milvus DB, my Windows 11 computer experiences a hard lockup. There are no blue screens or debug messages; instead, the entire system abruptly reboots after approximately one minute of running the embedding process. This issue does not occur with previous versions of the software. It seems like the CPU is being overloaded during the process. Alternative Solutions Attempted: I also tried using LM Studio Nomic 1.5 embeddings with local services, but encountered errors. Despite witnessing GPU activity, indicating processing of PDF files, there is no interaction with the Milvus server, as evidenced by the absence of network traffic, unlike when utilizing the native embeddings option. System Information: Operating System: Windows 11 (latest edition) CPU: Intel Core i7 12900k GPU: Nvidia RTX 4070 Super Request: I'm seeking guidance on how to capture relevant logs or troubleshoot this issue, as the current version of the software appears to be unusable on Window ### Are there known steps to reproduce? _No response_
yindo added the possible bugDesktop labels 2026-02-22 18:21:38 -05:00
yindo closed this issue 2026-02-22 18:21:38 -05:00
yindo commented 2026-02-22 18:21:38 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (May 9, 2024):

I specifically think this is related to the Milvus integration as no other vectorstores cause this issue. The native works fine with 20K files embedded and no issue. To run the program in an observable manner you can run it via powershell
C:\Users\user\AppData\Programs\anythingllm-desktop\AnythingLLMDesktop.exe and it will print all logs to the terminal window and should show something when attempting to upsert the vectors.

@timothycarambat commented on GitHub (May 9, 2024): I specifically think this is related to the Milvus integration as no other vectorstores cause this issue. The native works fine with 20K files embedded and no issue. To run the program in an observable manner you can run it via powershell `C:\Users\user\AppData\Programs\anythingllm-desktop\AnythingLLMDesktop.exe` and it will print all logs to the terminal window and should show _something_ when attempting to upsert the vectors.
yindo commented 2026-02-22 18:21:38 -05:00
Author
Owner
Copy Link
Copy Source

@LindsayRex commented on GitHub (Jun 6, 2024):

Hi Gents, I tried just using the native lance vector db. Same problem. i.e i removed the milvus db.. its also doing it on version 1.5.5 .

I wasn't sure how to get any verbose login out of the app.

"C:\Users\user\AppData\Programs\anythingllm-desktop\AnythingLLMDesktop.exe and it will print all logs to the terminal window and should show something when attempting to upsert the vectors."

this idea didnt work either.

I wil be clearer. My computer hard resets the power. What is even more astonishing is its win 11 VM running on linux proxmox host which also resets. I have never ever seen anything like this.

I need to stream verbose logs to files that write somehow, maybe using transaction logs ? as the a log file will get corrupted, when the power resets.

Cheers,

Lindsay

@LindsayRex commented on GitHub (Jun 6, 2024): Hi Gents, I tried just using the native lance vector db. Same problem. i.e i removed the milvus db.. its also doing it on version 1.5.5 . I wasn't sure how to get any verbose login out of the app. "C:\Users\user\AppData\Programs\anythingllm-desktop\AnythingLLMDesktop.exe and it will print all logs to the terminal window and should show something when attempting to upsert the vectors." this idea didnt work either. I wil be clearer. My computer hard resets the power. What is even more astonishing is its win 11 VM running on linux proxmox host which also resets. I have never ever seen anything like this. I need to stream verbose logs to files that write somehow, maybe using transaction logs ? as the a log file will get corrupted, when the power resets. Cheers, Lindsay
yindo commented 2026-02-22 18:21:38 -05:00
Author
Owner
Copy Link
Copy Source

@LindsayRex commented on GitHub (Jun 6, 2024):

Ok, so the fix after googling for 'embedding files in ollama into lancedb crashing windows 11' seems to be for some people to turn off cpu overclocking.. so I tried turning on off intel turbo frequency in my bios. Bingo, no more hard power resets when i embed lots of files in bulk.

@LindsayRex commented on GitHub (Jun 6, 2024): Ok, so the fix after googling for 'embedding files in ollama into lancedb crashing windows 11' seems to be for some people to turn off cpu overclocking.. so I tried turning on off intel turbo frequency in my bios. Bingo, no more hard power resets when i embed lots of files in bulk.
yindo changed title from [BUG]: Hard lockup of Windows 11 computer when using native embeddings option in AnythingLLM v1.5.3 & v1.5.5 to [GH-ISSUE #1322] [BUG]: Hard lockup of Windows 11 computer when using native embeddings option in AnythingLLM v1.5.3 & v1.5.5 2026-06-05 14:37:26 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label Desktop possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#830
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?