Bambu Studio 2.1.1.52 crashing

Hello,
I just recently upgraded Studio to the latest version, 2.1.1.52, and I’ve been experiencing Studio crashing, just disappearing from the desk top, at any given time. This happens even when I’m not doing anything on it.
Has anyone experienced this?
The printer is connected via our company’s internal network, ethernet, not wi-fi.

1 Like

I haven’t seen that myself, and I almost always have it open as I’m checking on prints and slicing stuff pretty constantly.

It happens to me on LAN mode if the printer is turned off and fails to connect to it.

Really annoying.

Same. Got some configuration file errors everytime I started up Bambu lab. I uninstalled 2.1.1.52 and installed 2.0.3.54 and it works just fine.

Since you have B-labs open all the time, are you sure you’ve restarted it since the update? The update doesn’t take effect until you close out and restart the application. Just wondering. This new update seems to break connectivity with your printer and crashes because of it.

What OS version are you using?
What does the detailed OS Crash report show?

Yes.

I also run it on my Windows machine, I just happen to be at my laptop at the moment.

I’ve started seeing crashes more often. I’m not sure if I was just lucky before or what.

Mostly just when the software is idle, although I did have a crash the other day that was so bad I had to power cycle my computer. When I opened BS back up after that many of my previously saved settings were completely gone.

Now I can’t say for sure that it wasn’t an issue with my computer, but BS losing a lot of ‘saved’ settings makes me think it was the software.

Ugh.

Windows 11. I don’t know how to read the crash report, but this is what is shown:

On 20/06/2025:
Exceptions:
Exception Code :c0000005 ACCESS_VIOLATION
Exception Flag :0x0 NumberParameters :2
Param 0 :0x0
Param 1 :0x2a7f8
Context :000000B080733DC0
ContextFlag : 0x10005f, EFlags: 0x10246
Fault address: 0xE731055C 0x0:0x0

Show CallStack:

On 19/06/2025:
Exceptions:
Exception Code :c0000005 ACCESS_VIOLATION
Exception Flag :0x0 NumberParameters :2
Param 0 :0x0
Param 1 :0x5cf6c
Context :0000004C8E925C80
ContextFlag : 0x10005f, EFlags: 0x10246
Fault address: 0xF4D6A5E9 0x0:0x0

Show CallStack:
Call SymGetLineFromAddr64 ,Address f4d6a5e9 Error:000001e7
Call SymGetLineFromAddr64 ,Address f487cf2c Error:000001e7
Call SymGetLineFromAddr64 ,Address f487415d Error:000001e7
Call SymGetLineFromAddr64 ,Address f5d24712 Error:000001e7
Call SymGetLineFromAddr64 ,Address f5d1c2b4 Error:000001e7
Call SymGetLineFromAddr64 ,Address f5d1c67a Error:000001e7
Call SymGetLineFromAddr64 ,Address f5d1c943 Error:000001e7
Call SymGetLineFromAddr64 ,Address f5d1c1ca Error:000001e7
Call SymGetLineFromAddr64 ,Address f5d1c5ea Error:000001e7
Call SymGetLineFromAddr64 ,Address f5afe865 Error:000001e7
Call SymGetLineFromAddr64 ,Address f5afe890 Error:000001e7
Call SymGetLineFromAddr64 ,Address f5afe890 Error:000001e7
Call SymGetLineFromAddr64 ,Address f5afe890 Error:000001e7
Call SymGetLineFromAddr64 ,Address f5afe890 Error:000001e7
Call SymGetLineFromAddr64 ,Address f5afe890 Error:000001e7
Call SymGetLineFromAddr64 ,Address f5ba3af9 Error:000001e7
Call SymGetLineFromAddr64 ,Address f5d4b069 Error:000001e7
Call SymGetLineFromAddr64 ,Address f5d4ae75 Error:000001e7
Call SymGetLineFromAddr64 ,Address f5d4b0ea Error:000001e7
Call SymGetLineFromAddr64 ,Address f5d256b7 Error:000001e7
Call SymGetLineFromAddr64 ,Address f5d29217 Error:000001e7
Call SymGetLineFromAddr64 ,Address f5d94528 Error:000001e7
Call SymGetLineFromAddr64 ,Address f48d5ea4 Error:000001e7
Call SymGetLineFromAddr64 ,Address f3ebf3ef Error:000001e7
Call SymGetLineFromAddr64 ,Address f3f413c5 Error:000001e7
Call SymGetSymFromAddr64 ,Address d9da563a Error:000001e7
Call SymGetSymFromAddr64 ,Address d9da5b06 Error:000001e7
Call SymGetLineFromAddr64 ,Address e971259d Error:000001e7
Call SymGetLineFromAddr64 ,Address e9a6af78 Error:000001e7

On 18/06/2025:
Exceptions:
Exception Code :c0000005 ACCESS_VIOLATION
Exception Flag :0x0 NumberParameters :2
Param 0 :0x0
Param 1 :0xffffffff
Context :000000E11B0C6400
ContextFlag : 0x10005f, EFlags: 0x10246
Fault address: 0x1C9EC662 0x0:0x0

Show CallStack:
Call SymGetLineFromAddr64 ,Address 1c9ec662 Error:000001e7
Call SymGetLineFromAddr64 ,Address 1c9ec943 Error:000001e7
Call SymGetLineFromAddr64 ,Address 1c9ec1ca Error:000001e7
Call SymGetLineFromAddr64 ,Address 1c9f5c93 Error:000001e7
Call SymGetLineFromAddr64 ,Address 1c873a8c Error:000001e7
Call SymGetLineFromAddr64 ,Address 1ca1b069 Error:000001e7
Call SymGetLineFromAddr64 ,Address 1ca1ae75 Error:000001e7
Call SymGetLineFromAddr64 ,Address 1ca1b0ea Error:000001e7
Call SymGetLineFromAddr64 ,Address 1c9f56b7 Error:000001e7
Call SymGetLineFromAddr64 ,Address 1c9f9217 Error:000001e7
Call SymGetLineFromAddr64 ,Address 1ca64528 Error:000001e7
Call SymGetLineFromAddr64 ,Address 1b5a5ea4 Error:000001e7
Call SymGetLineFromAddr64 ,Address 1ab8f3ef Error:000001e7
Call SymGetLineFromAddr64 ,Address 1ac113c5 Error:000001e7
Call SymGetSymFromAddr64 ,Address 9ee9563a Error:000001e7
Call SymGetSymFromAddr64 ,Address 9ee95b06 Error:000001e7
Call SymGetLineFromAddr64 ,Address 1737259d Error:000001e7
Call SymGetLineFromAddr64 ,Address 17d4af78 Error:000001e7

Windows 10, Network plugin not installed, Changing printes or filaments available in vendor selection several times (< 6) BS will “disapear” on clicking confirm without saving changes. BS has been restarted several times (not including crashes). Don’t have access to event log at the moment.

Here it also crashes every time. I start printing and leave. When I wake up the MacBook Bambulab Studio isn‘t responding and need to be restarted.

Very annoying…

Looks like an error in the application code, not a DLL. But this should give the Bambu Labs developers some clues to narrow down the cause of the crash.

NOTE - MacOS gives a more user readable report, Windows requires that the developer connect the report to their app to find the full stack trace, and Linux is still stuck in the 1990s, unless you use third party crash report libraries.

1 Like

Yep, been getting crashing happening with 2.1.1.52 without any error messages or notification - just disappearing from the desktop. Sometimes it happens while slicing, sometimes after slicing is done, sometimes while it’s just sitting doing nothing.

I’ve uninstalled and reinstalled 2.0.3.54 (the previous version I was using) and things are working fine. Hoping the folks at Bambu get one this and issue an update soon

2 Likes

I’ve been using our x1e at work pretty much on a daily basis this past week and so far I’ve not experienced any crashes. It’s like the software decided to behave itself.
Our network at work is heavily secured and may have features that might interfere with how Studio operates. I’m not a software engineer so have no idea if this is the case.
As of this morning, 02-07-2025, I’ve been experiencing crash after crash. I removed a print started the evening before. Started my PC and after logging in started Studio to send another print. Loaded the part to print, sliced it then Studio disappeared. Studio crashed several times there after, before slicing, after slicing, before sending, doing nothing, etc. Eventually I was able to send the print before it crashed. When this happened I restarted Studio right away and checked to see if the printer received the file. It did and it looked like the print was starting as normal. Then my colleague came up to me and asked me to check the printer, it appeared to him (he was doing a task near the printer) like it was printing with PLA Wood, not the material I assigned, PLA Matt (black). I killed the print and started again. This time it’s printing with the correct material. How could this happen? I did check to see what material was selected in Studio and it looked correct, yet PLA Wood was being used. Strange.
At this moment, as I type this, I have Studio open and I can see the printer printing away. Studio has not crashed. Strange.

Add me to the list this crashes many times a day while printing.

How do you downgrade?

I’ve not had any crashes for a while. Last week on one particular day I had continuous crashes. Every few minutes it would crash for no reason. Eventually it stopped and I was finally able to get a print started. Ever since that day I’ve not had a single crash. It seems like it fixed itself, again.

recently i update the SW , and i loose the posibility to edit the profiles, im not sure if the options are hiden in a different place or what happen :confused:

Same happening bere I’m dead

It’s August, still CTDs, any updates in the pipeline

Description
Faulting Application Path: C:\Program Files\Bambu Studio\bambu-studio.exe

Problem signature
Problem Event Name: BEX64
Application Name: bambu-studio.exe
Application Version: 2.1.1.52
Application Timestamp: 684fd5c0
Fault Module Name: StackHash_e24c
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: PCH_4B_FROM_ntdll+0x00000000000A17A4
Exception Code: c0000005
Exception Data: 0000000000000008
OS Version: 10.0.22631.2.0.0.256.48
Locale ID: 1033
Additional Information 1: e24c
Additional Information 2: e24c17adb673b5e014795ba9d0f904bd
Additional Information 3: f2ac
Additional Information 4: f2acf1870a22227b103c9d7b2bc9aabe

Extra information about the problem
Bucket ID: 419b7283610e8fd369718de1136a561a (1833402521149396506)

1 Like