me too with windows 10 I can not start the program
Not that this is a fix but I've tried to upgrade from 4.6.2 to 4.8 but 4.8 always crashes upon opening an STL file (fatal error). If I revert back to 4.6.2, Cura works fine. I submitted a crash report. I'm running Windows 10, Nvidia GeForce MX350.
i'm use windows 10 and NvidiacGeForce540M
I resolve :
Set force_empty_shader_cache
under the [view]
heading to = True
in cura.cfg
resolve my problem
Thanks Andrea6. I just tried that, but unfortunately, it did not help.
- 2 months later...
Hi Damzil1991,
I'm sorry to be the bearer of bad news, but...
I experienced this fault with Cura some time ago and have given up on solving it with my 'Powerful' desk PC.
If I want to use Cura, I use my old laptop and it's fine.
The reason for the crash is the ASUS/Ryzen motherboard.
If your Ryzen system uses an 'MSI' motherboard, you seem to be OK with Cura
(So it's not the Ryzen processor at fault in itself)
I've had two systems crashing so severely, they had to be unplugged for 30 secs to get them to re-boot !
I'd 've thought this impossible before experiencing it first hand.
I've seen on other forums that people have changed their motherboards over to an MSI model and then been good to go...
If you have the cash and inclination to change you motherboard, then you can take this route, if not, then I'm afraid you'll never solve the problem.
- 2 weeks later...
Is there a known reason to why the ASUS/Ryzen combo is causing the crash? I have the combo but my doesn't crash. Cura will open a blank white screen and then close itself after a few seconds.
- 1 year later...
It seems to be an issue with AMD but it must be Cura that has the issue and needs to be fixed as no other slicer causes the crashes that Cura does.
- 6 months later...
I am having a similar issue with CUra. I even upgraded to 5.3. I either get a a Full, BSOD crash or Cura generates a "You should send a bug report" message on the screen. All I'm trying to do is slice a file. Bug report sent. I loaded PRUSA slicer and clioced the same file without issue. The minute I try it with CURA I get the bug message. After a reboot... like immediately after, when I slice the same file, I get a BSOD and the machine restarts.
This was amy gaming rig, and yes, it as a Asus ROG mainboard/ AMD CPU
Recommended Posts
damzil1991 2
Sorry I forgot to add that I have had the same issue with GTX 1080 GPU last year so don't think its related to the GPU
Link to post
Share on other sites