BS is randomly crashing

I am not seeing the pattern to give a better description.
Because I am not seeing a pattern. I can’t give you a list of instructions that force it to happen.

It seams to be happening during or after slicing and previewing.
does not seam to be dependent on the complexity of the model.
does not seam to happen all the time.

I can do the same thing and sometime it works and sometime it crashes (BS closes and does not save the file). Most of the time it gives me the option to reload.

Sometimes it happens when sending to the printer.

I am currently using 2.2.00.85 on win 11.
the problem has happened for the past couple months. Spanning a couple BS upgrades.

thank you for suggesting any suggestions.

BS for Bambu Studio might not be the best abbreviation :laughing::laughing:

I see the humor of Bull S. is the standard abbreviation of BS. But the people should recognize the real abbreviation meaning.
LOL

More seriously. A uninstall and reinstall fixed this when it happened to me.

Have you checked the Windows 11 Event Viewer for the crash log? In there you’ll find a report you can copy and paste into any AI with the prompt: “View this report, explain it in layman’s terms, and help me find a remedy.”

Here’s what that looks like:

Open Event Viewer and go to Windows Logs → Application. If you’ve never used this utility before, it may take a few minutes for the logs to load. Event Viewer displays data from five core Windows logs, and over time they can grow large - so be patient.

Filter to the time period when your application crashed if you want to reduce clutter.

Then filter for Critical and Error events, which will narrow it further.

This will leave you with a list you can scroll through. You’ll need to click on each entry to find the crash report for your program.

Copy and paste that report into the AI along with the prompt I supplied at the beginning of this post. A screenshot can be read by the AI so no need to copy and paste text. In fact, I’ve found that screenshots can reduce AI hallucinations.:

___________________________________

From my experience, unless you’re lucky enough to find a clear cause (like a failed network module or a crash tied directly to a driver), the logs almost always trace back to a generic software bug. The most common I’ve seen is “Application tried to access memory it did not own.” Unless you have the skills and energy for deep software diagnostics, that information is usually only useful to the developers. The way I use it - when I’m suitably motivated (and truth be told, BL is the last company I’d go out of my way to help) - is to package up the report and send it to tech support. Since I’ve already done some of the heavy lifting, and as long as I can reproduce the error (which it sounds like you can’t), they tend to be more responsive with concrete suggestions. But this is BL we’re talking about - so odds are they’ll just ask for your logs, skim them, and regurgitate the Wiki. That’s about as far as their “support” goes.

1 Like

I actually thought bambu suite since it seems less mature than bambu studio.

the problem was the video card. Thread optimization. For BS it needs to be OFF. I have yet to try using the video driver to create program specific settings.
It is frustrating that my initial search of the wiky didn’t find that. Then the forum post was unsuccessful also. Tech support took a week to address. But it is solved. Much less annoying now.
the link to the instructions is:
https://wiki.bambulab.com/en/bambu-studio/troubleshoot/win-crash-when-slicing