RE: Prusa Slicer Crashing
@jason-m21
It may help us if you can collect a crash dump.
https://helgeklein.com/blog/2018/10/creating-an-application-crash-dump/
https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps
RE: Prusa Slicer Crashing
i haven't been able to reproduce this today. i have no idea what is different today, but its been fine so far.
as soon as the behavior returns, i will get the requested dump.
thanks for the assist.
jason
RE: Prusa Slicer Crashing
i haven't been able to reproduce this today. i have no idea what is different today, but its been fine so far.
as soon as the behavior returns, i will get the requested dump.
thanks for the assist.
jason
I've not seen it since recent Win10 updates and update to NVidia drivers.
RE: Prusa Slicer Crashing
If you are running an Asus laptop or a MSI mother board, you may find out that there is a magic Nahimic audio driver preinstalled on your system, which interferes with PrusaSlicer.
https://github.com/prusa3d/PrusaSlicer/issues/2522
Also there seems to be a report of some magical crashes in some magical InnoCielo Meridian application interfering with PrusaSlicer.
https://github.com/prusa3d/PrusaSlicer/issues/2939#issuecomment-577056071
I suppose there are some more similar rough applications that hook into PrusaSlicer and cause it troubles. MS Window is quite an open platform with rich API, which allows such things. If the 3rd party application screws, we cannot do much than to ask you to suppress the 3rd party application.
RE: Prusa Slicer Crashing
@bubnikv
Hello,
I'm not sure what the difference is between 2.0 and 2.1.1 but version 2.0 works without any issues. If anyone is interested, I'd be willing to show how the error occurs every time in version 2.1+ when I access a menu button from the toolbar or right-click menu via remote desktop.
My system is as follows:
Intel Core i7-8850 @ 2.6GHz, 32 GB Ram, 64 Bit Windows 10, Graphics: Citrix Indirect Display Adapter, Intel UHD Graphics 630, NVIDIA Quadro P1000
RE: Prusa Slicer Crashing
I figured out what my issue was, it doesn't like OctoPrint. On a fresh reboot slicer doesn't crash, the moment I start OctoPrint it instantly crashes. Even after I close OctoPrint something is still running in the background that slicer doesn't like. Then as soon as I reboot slicer runs fine again. I can repeat this fault over and over with the identical results. Slicer doesn't like OctoPrint on my laptop.
RE: Prusa Slicer Crashing
It may help us if you can collect a crash dump.
https://helgeklein.com/blog/2018/10/creating-an-application-crash-dump/
https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps
RE: Prusa Slicer Crashing
@bubnikv
Unfortunately slicer crashes like I've never seen an app crash before, as others have previously reported, it doesn't just "stop responding" it just makes a windows notification tone, the blue circle spins for a moment, and then slicer closes. It's not creating a .dmp file either in the CrashDumps folder.
System: Acer Predator 17 G9-793
RE: Prusa Slicer Crashing
@chad-m13
I can do that. I'm just waiting for IT with admin credentials. My user privileges on my work computer are unfortunately causing delays in getting this information.
RE: Prusa Slicer Crashing
@chad-m13
follow my instructions i did solve the problem and I had the same behavior in my machine. its farly new laptop. but in my desk computer that I have builded over the years I get no problem. so its something related to this new machines.
but I got it solved. if you have any questions whatsapp me. +56961572494 its faster
RE: Prusa Slicer Crashing
@dehtrim
> Has any progress been made on this? I still get this issue randomly. I can do 2 or 3 stls using the Nvidia RTX2060 before having to delete my profile information. I can use the sw renderer; however speed on bigger designs is a pita.
If you believe that the profile information is faulty, it would help us if you could open a github issue https://github.com/prusa3d/PrusaSlicer/issues
and attach your faulty profile to it before you delete it.
thank you
RE: Prusa Slicer Crashing
@fursphere
Thanks so much for the tip to run slicer as an administrator. It works! I'm new to the Prusa printers and to this forum. Just finished assembly of my new MK3S 2 days ago and got a little pissed when the slicer chrashed. You're an absolute life saver.
RE: Prusa Slicer Crashing
has there been any progress on this other than the switch to sw renderer ?
im still having the same issue, random crashes especially when trying to slice larger and more complex models.
if i stick to smaller models, it usually will work completely fine.
but if i load and try to slice a large bust, or other larger STL, it will crash. it will often crash when just looking at the larger models.
even before you hit slice. just going to a menu to select print settings can cause the crash.
prusaslicer leaves no crash log. just the windows ding, swirling blue cursor, then closes.
no error messages, and the slicer doesn't remember the print settings or anything.
the laptop is less than 6 months old. its an Acer swift 3 with 8 gb ram. 500G SSD, ATI RAEDON Vega 3 GFX chip set.
running windows 10 home.
the audio driver is an intel one, not the previously identified one that can cause issues.
im running the latest stable release version of prusaslicer also. so this issue has persisted over a few releases now.
there is clearly some issues with prusaslicer and non Nvidia cards.
i can't afford (and shouldn't have to) go buy a new laptop with an Nvidia chipset.
Prusaslicer is ALMOST the best slicer out there. but in my mind its not there just yet.
i have to in-fact warn people when i talk to them about it that it may randomly crash.
would be good to finally see a solution.
Jason
RE: Prusa Slicer Crashing
Started to get crashes now myself, And I have a fairly good computer, sliced several models and then all of a sudden I sliced 1 model and the computer locked up. Restarted the computer and tried again and this time Blue screen. No crash log.. no indication as to why it wont slice the file, the file shows no errors in it.
I sliced then with Cura and no issue at all, so its not the model..
My Mini has: A SuperPINDA + Bondtech Heatbreak + Bondtech Extruder installed
RE: Prusa Slicer Crashing
I should also add that the models will slice fine using canvas slicer. But not in prusa slicer. So I also agree it’s not the model.
infact I’ve been able to slice and print one of the busts previously when it was still slic3r PE. But now can’t with prusaslicer.
jason.
RE: Prusa Slicer Crashing
> Started to get crashes now myself, And I have a fairly good computer, sliced several models and then all of a sudden I sliced 1 model and the computer locked up. Restarted the computer and tried again and this time Blue screen.
PrusaSlicer cannot possibly be guilty of your Windows blue screens. Blue screens of death (BSOD) are the result of hardware or a operating system driver issue.
RE: Prusa Slicer Crashing
> @jason-m21
> the laptop is less than 6 months old. its an Acer swift 3 with 8 gb ram. 500G SSD, ATI RAEDON Vega 3 GFX chip set.
running windows 10 home.
8GB of RAM may be not enough for large objects (filling most of the print volume) if sliced with Gyroid infill and / or with very thin layer heights. PrusaSlicer may give you a low memory error, but if the stars are not aligned, it may crash instead.
RE: Prusa Slicer Crashing
@tim-m30
I work with a Dell E5420 laptop with internal Intel HD3000 and Open GL 3.1 and since PrusaSlicer 2.2.0 everything runs stable. Before that I had problems with the graphical representation of textures. Unfortunately Intel doesn't offer support for this graphics card anymore and doesn't answer support requests. Therefore I will take care in the future that no Intel graphics cards are installed when buying a laptop. I think Nvidia cards are a good solution.
Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.
RE: Prusa Slicer Crashing
> @jason-m21
> the laptop is less than 6 months old. its an Acer swift 3 with 8 gb ram. 500G SSD, ATI RAEDON Vega 3 GFX chip set.
running windows 10 home.8GB of RAM may be not enough for large objects (filling most of the print volume) if sliced with Gyroid infill and / or with very thin layer heights. PrusaSlicer may give you a low memory error, but if the stars are not aligned, it may crash instead.
I do have a habit of using gyroid infill. I’ll have to test what happens when I try cubic or grid.
the bust isn’t that big either. Around 150mm high and maybe 100mm wide.
I’ll try slicing it with the other infill and see what happens. I also usually print busts and figures at .1 or .15 layer heights too. I wouldn’t have expected that to cause an issue.
jason.