Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bambu Studio crashes when trying to slice project #3318

Closed
2 tasks done
GabrielQuintana opened this issue Jan 6, 2024 · 18 comments
Closed
2 tasks done

Bambu Studio crashes when trying to slice project #3318

GabrielQuintana opened this issue Jan 6, 2024 · 18 comments
Assignees
Labels
backend bug Something isn't working

Comments

@GabrielQuintana
Copy link

Bambu Studio Version

1.8.2.56

Where is the application from?

Bambu Lab Official website

OS version

Windows 11 Home

Additional system information

CPU: i9-14900k
Memory: 64 GB 6400mhz
GPU: Asus Nvidia GeForce RTX 4070 Ti

Printer

Bambu Lab X1C

How to reproduce

Open the provided 3mf file in bambu studios, and click "slice plate"

Actual results

Bambu Studio crashes

Expected results

The plate should be successful sliced

Project file & Debug log uploads

Log and Project.zip

Checklist of files to include

  • Log file
  • Project file
@GabrielQuintana GabrielQuintana added the bug Something isn't working label Jan 6, 2024
@QingZhangBambu QingZhangBambu self-assigned this Jan 8, 2024
@QingZhangBambu
Copy link
Collaborator

We found that some models cannot be sliced on Win 11. We'll try to fix this in next big version.

@QingZhangBambu
Copy link
Collaborator

image

@QingZhangBambu
Copy link
Collaborator

@GabrielQuintana is that still happend in the latest version on your PC?

@QingZhangBambu
Copy link
Collaborator

@GabrielQuintana holle, there is a method that some people said is helpful, may you try it and check if it is useful?.
For Win 11, here is how to set the affinity :
1- Open Task Manager (CTRL+SHIFT+ESCAPE)
2- Go to Details
3- find bambu-studio.exe and right click to chose "Affinity"
image
4- From the popup, it is possible to choose which thread(s) to use. For example, on my i9-13900K, I've got CPU0 to CPU31 (I've 8 performance cores with 2 threads, and 16 efficiency cores -> 32 "CPUs" listed)
image
And interestingly enough, when I slice without setting affinity (so, Bambu Studio uses all threads available) -> it crashes.
When I first set affinity to, for example, CPU0 to CPU3, or CPU0 to CPU7 -> slicing goes through successfully.

@GabrielQuintana
Copy link
Author

@QingZhangBambu Latest version (without modifying affinity) is still having the same issue where bambu studio crashes.

Though after setting the affinity to CPU0 to CPU7 (also tried CPU25-31) I got the exact same result, slicing does goes through successfully.

@QingZhangBambu
Copy link
Collaborator

@GabrielQuintana Then when the Studio crashed?

@GabrielQuintana
Copy link
Author

GabrielQuintana commented Jan 29, 2024

@QingZhangBambu Yes, it crashes when slicing on the new version too (When I don't do the affinity trick you mentioned). Should I provide logs again for the new version?

@QingZhangBambu
Copy link
Collaborator

yes, that would be helpful

@Blade-Strike
Copy link

I have the same exact issue. If I set infinity to 1-7 I'm good. Otherwise, it's a hard crash.
sys.txt

@QingZhangBambu
Copy link
Collaborator

@Blade-Strike maybe you can do some CPU tests. some users change the CPU and all problem be solved. https://community.intel.com/t5/Processors/i9-13900K-very-frequent-crashes-Windows-11-with-apps-games-and/m-p/1528789/highlight/true
#3354

@Arcaine10
Copy link

Good morning,
I may have found a solution without having to change the affinity each time. You have to download Intel extreme tuning utility, go to advanced tuning and set performance active-core tuning to 54. Since then I have had no more problems.
Capture d'écran 2024-03-12 072042

@GabrielQuintana
Copy link
Author

GabrielQuintana commented Mar 19, 2024

@QingZhangBambu Sorry forgot to update here, the issue was 100% the CPU being unstable because of some motherboards and intel software overclocking the CPU too much. which made any CPU intensive procedures like slicing crash every so often. So I'm good to close this issue if you are.

For other people experiencing the same issue as I was, here's the thread that helped me https://www.reddit.com/r/overclocking/comments/1axepvu/optimizing_stability_for_intel_13900k_and_14900k/

@QingZhangBambu
Copy link
Collaborator

ok ;)

@elyograg
Copy link

Good morning, I may have found a solution without having to change the affinity each time. You have to download Intel extreme tuning utility, go to advanced tuning and set performance active-core tuning to 54. Since then I have had no more problems.

This worked for me. Slicing is now stable. I was having a ton of problems with it. Mostly it would just crash Bambu Studio, but sometimes it would bluescreen or freeze the system so completely that the mouse pointer wouldn't even move.

@Pan-Chenliang
Copy link

Good morning, I may have found a solution without having to change the affinity each time. You have to download Intel extreme tuning utility, go to advanced tuning and set performance active-core tuning to 54. Since then I have had no more problems.

This worked for me. Slicing is now stable. I was having a ton of problems with it. Mostly it would just crash Bambu Studio, but sometimes it would bluescreen or freeze the system so completely that the mouse pointer wouldn't even move.

Same phenomenon on my 14900k, mouse pointer couldn't move, then bambu studio crashed or even blue screen.

@masystems
Copy link

Got the same issue here, had to set it use CPU0-7. Bambu, please fix your software.

@elyograg
Copy link

I did have this working with the changes to the Intel Extreme Tuning program, but it has started crashing again when slicing certain models. I didn't change anything.

Bambu Studio also crashes slicing the same model, but it causes a bluescreen instead of crashing the program.

@Skydev0h
Copy link

Skydev0h commented Jun 3, 2024

For me I had issue on an Intel i9-14900K, and it seems that the issue is in multithreading on both P-Cores and E-Cores.
Using a free CoreDirector utility I configured constraining bambu-studio.exe to P-Cores, and that not only fixed the crashes, but also sped up slicing by a significant margin.

image

Behind the scenes the application automatically configures process affinity to use only P-Cores and stay away from E-Cores. The possible issue is that P-Cores and E-Cores may be seen by the app or system as two different processors, and that may cause unexpected issues when accessing shared resources from multiple threads.

For me this is certainly not a stability issue, because I compiled some large Rust projects using all P and E cores (cpu load was about 100% for extensive amount of time) and that did not crash my system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend bug Something isn't working
Projects
None yet
Development

No branches or pull requests

9 participants