I have recently built a new PC, using Intel Core Ultra 7 + 48GB DDR5 on a Gigabyte motherboard. Everything installed so far works perfect and is fast. However, today I installed Bambu Studio ver 2.3.0.70. I logged in etc, it seems fine. I can open a model for printing, it opens. I can rotate, add support etc. So far so good. But as soon as I click on Slice the system crashes all the way back to where I see my BIOS (as if I hit Enter to open the BIOS at startup). I can exit the BIOS and windows 11 pro starts normally. I have just tried removing Bambu Studio wiping it completely and starting with a second clean install. The results are exactly the same.
Next I started my old PC running Bambu Ver 2.2.2.56 and this works great.
I am at a bit of a loss on how to trouble shoot the new PC. I am running other complex programs and they all work fine,I have stressed the new PC with test programs and it passes without problems.
Thanks, this sounds promising. Indeed, I am using a NVIDIA graphics adapter. Microseconds after clicking on “Slice” it crashes and goes straight to the BIOS menu. Tomorrow I will fire the new PC up again and find those NVIDIA settings. I will post the result, hopefully - solved!
Thanks so much for the guidence and link. I made the changes to NVIDIA and voila Bambulab Studio now works faultlessly. Slightly odd is that I had moved the NVIDIA graphics card from the old PC, and there it worked fine. Anyway, now I’m a happy camper. The loading time of Bambulab Studio is greatly reduced. The old machine took 8 - 10 seconds to launch Bambulab, the new PC takes 1.1 - 1.3 seconds to launch.
One other thing to keep in mind and where I was leaning when you said it crashed to BIOS (which is pretty odd these days) - memory. Especially with a new PC.
There is a free routine that some motherboards even have built in is Memtest86. If it’s built into the BIOS you access it from the BIOS but there is also a version you can run from a USB drive.
It tests memory all sorts of ways. It runs various patterns designed to trip up adjacent bits, stress memory cells, and it tries to starve them of refresh cycles IIRC. Anyway, it tests memory in ways designed to catch issues.
Memory can be good, marginal, or bad. It can have little traps waiting for various programs to access it in just the wrong way. And it can go bad over time. Work around enough computers and replacing memory can get to take up a fair amount of time.
This wasn’t that but anyone having computer memory weirdness might want to keep it in mind. In my time with PCs at home I’ve only had one stick go bad on me but Memtest found it and made troubleshooting easy. It’s a good test just in general since many may not stress their memory enough in normal use to expose lurking issues. When building a system I always verify the memory is good using it. It can save much trouble troubleshooting things that aren’t the issue.
Hi, thank you. As this is all new hardware I decided to take your advice and to run Memtest86. I ran it overnight as I could see testing would take quite a while. Anyway it completed the tests with zero errors. I am running the Intel Core Ultra 7 256K with the Intel 200S Boost BIOS, and the DDR5 memory at 8000 MT/s. Also a 4GB NVME at its limit. But everything seems solid and this setup will do me for a few years. Thanks again
Very glad you tried it out and that it ran clean! It gives confidence in the hardware and lets you focus on other things. And glad you found the actual issue.
