Cura: [CURA 4.0.0 BETA] Black screen after 2 minutes with Ryzen CPU and ASUS motherboard

[fanfan7110]

Hello,
At each launch without exception of Cura 4.0.0 beta, the software runs for about 1 to 2 minutes then the screen goes black, all the USB systems are disconnected and the PC is permanently blocked in this black screen. Even the Reset does not work anymore. The power must be turned off and then reactivated to restart.
There is no precise point that triggers this problem, as it can happen without a model, with a model, during a calculation or even empty.
To check, I reformatted the computer and reinstalled everything and the problem returned to the identical.
On my second PC (less powerful but Intel processor) the problem does not appear.
By taking the same configuration of the intel but copied in the Ryzen, the bug is still there. This is not an installation problem or defective files. I would rather look at an incompatibility with the processor.

Application Version
CUra 4.0

Platform
Windows 10

Printer
Alphawise U20

Steps to Reproduce
Just install in a ryzen5

Actual Results
Black screen

[fieldOfView]

Can you check if the memory use of Cura increases in those 1 to 2 minutes (using the windows Task Manager)? If that does not result in something that explains the lockup, checking temperatures may also be interesting (but you'll have to find a tool for that yourself).

[Ghostkeeper]

Google says to look at power settings, such as this in Windows: https://youtu.be/bheUmk2qEp4?t=82
Or this in the BIOS: http://forum.asrock.com/forum_posts.asp?TID=7890

Edit: Reported below, this has no effect apparently.

[fanfan7110]

So, there is no memory increase except when it slice.. No excessive temperature.
For windows setting and bios i'll see that.

[Ghostkeeper]

We have a similar report on Ultimaker's forum now: https://community.ultimaker.com/topic/26654-cura-crashes-my-entire-computer/

[fanfan7110]

yes, it's exactly the same problem. and with two ryzen.... it's not a coincidence

[fieldOfView]

Since none of the developers have a Ryzen system, we really need your feedback to know if the proposed power settings/bios changes fix the issue.

[fanfan7110]

Absolutly not. This setting have no effect.
I have tested with the parameters you had advised and the bug is still there. I also tried many other bios settings without results

[janrg]

Unfortunately, my MB's UEFI (ASUS STRIX X-470-F, UEFI Revision 4018) doesn't seem to have an option for disabling C-states. I've changed the power plan now and will try to provoke the issue into occurring. Will report back.

[janrg]

Sadly, that did not do the trick. I left Cura open and while I was using the Computer it worked fine, but when I stepped away for 10 minutes, it locked up again.

[janrg]

Oh, I should point out I'm actually running 3.6, not 4...

[Ghostkeeper]

It's very hard to say something about this issue :disappointed: We don't know what's causing it or why it only happens with Ryzen. We also don't have any computers here with Ryzen to reproduce the issue.

Cura's only binary code under our source control is in CuraEngine/libArcus but since this happens during idle that's not running. The rest of Cura's binary code is in our dependencies such as Qt, CPython, etc. so then you would expect this to happen with other applications as well that depend on the same dependencies.

Maybe this also happens with other Qt-based applications, such as FileZilla or OpenSCAD?

[fanfan7110]

in fact no, i use Fillezilla all days and there is no problem with it.
To be precise, no software installed in my machine reproduces the problem found on cura.
I use daily software like filezilla, fusion360, meshmixer, Zbrush without any worries.
Still yesterday, I made the settings of cura 4.0 and during keyboard editing parameter entry the screen became black and it was finished.
Note that often, after reboot, Cura forces reset the settings to zero to return to its basic installation state (if that can help). So you have to tell again what is the printer etc.

[Ghostkeeper]

That means that the configuration files got corrupt. It may have happened during saving of profiles.

[robnivis]

Hello I am also having this problem

CPU: Ryzen 5 2600
GPU: Nvidia GTX 1070

I think there must be an issue with cura vs AMD CPUs

[Tibdarko]

Same with :
CPU: Ryzen 7 2700X
GPU: Nvidia GTX 1080
RAM : 16 Go (2 x 8 Go), 3000 MHz, CAS 15
Win 10

Both Cura 3.6 and 4.0

[fanfan7110]

See the list of users that extends, it is no longer a simple bug strictly local, but a problem operating Cura with a Ryzen processor .. The list of blocked users may well lengthen a little every day :)

[Ghostkeeper]

On this thread they seem to arrive at it being a problem of the CPU not getting enough power. They also indicate that it often happens during idle time just after a CPU-intensive task, which is very typical for Cura's usage pattern.

[fanfan7110]

It can not be that, because the bug appears even if we did not even start loading a model.
For example, launch Cura and just wait a few minutes for the screen to turn black.
Or just access the cura's settings for cut and block the pc. So unless you consider that access to cura parameters is an overload of the processor (in this case you have to redo all programming software, lol) it is impossible that it comes from what you said.

[Ghostkeeper]

Launching Cura is a pretty CPU-intensive task :P

[fieldOfView]

Do you have the "Aura" or "AI Suite" mentioned in the thread above installed?
There are more reports of black screen issues connected with these packages:
https://forums.tomshardware.com/threads/ryzen-27700x-black-screen-issue.3393849/
https://community.amd.com/thread/231672

[robnivis]

just out of interest, I noticed my GPU temperature (GTX 1070) was idling REALLY high

might be worth checking if your fans are spinning and if your fan curves are correct

it feels somewhat like the GPU maxing out on temperature and shutting down which causes a cascading issue through the rest of the system.

I just ensured my fans are both running quietly at idle now (15% until 45C), so I will see if the issue persists

[robnivis]

update: issue still persists.

Although I think it's prudent for everyone to check their GPU is working as intended.

just uninstalled AURA as per fieldOfView's suggestion, already had AI suite uninstalled

[adamheinmiller]

Ryzen 2700 X
ASUS Strix X470-F
Nvidia GTX 1060
Windows 10
Cura 3.6

I'm also experiencing this issue. My system is otherwise completely stable. I have the same symptoms as everyone else - system goes dead without warning, have to physically cut power to get it to start back up.

It occurs whether I'm actively using Cura or have it in the background. It usually happens 5-8 minutes after starting Cura. Confirmed it's not CPU/GPU thermals - they are near idle temps if I open Cura and let it sit until a crash. I do have Ryzen Master installed but nothing is customized. I've also tried using Process Lasso to restrict Cura to a single core, but it has no effect.

[fieldOfView]

It would be very helpful if anyone with a spare partition could do a clean installation of Windows 10 without installing AURA and AI Suite, and see if it reproduces there. From what I have read in the linked articles, uninstalling does not fix it (leaves something behind?).

[fanfan7110]

It would be very helpful if anyone with a spare partition could do a clean installation of Windows 10 without installing AURA and AI Suite, and see if it reproduces there. From what I have read in the linked articles, uninstalling does not fix it (leaves something behind?).

Already done and explained in the first post. Even after full formatting and a clean reinstallation without anything else, as soon as Cura is reinstalled and started up the problem is present. In fact, when I reformatted my PC, the crash even appeared about 10 seconds after the first start of Cura 4. The hardware was a Ryzen 5 1600 with Asus Prime X370 Pro card and 16 GB of RAM.
I changed yesterday for a Ryzen 7 2700X with motherboard
Gigabyte GA-B450M-DS3H. For now no blocking, but as it worked sometimes .. I will see with time

[robnivis]

Uninstalling AURA and having already uninstalled AI seems to have worked for me. Have used CURA 3.6,0 extensively in recent days and no random blackouts.

ROG STRIX B450-F
Ryzen 5 2600
EVGA GTX 1070 SC2

NZXT CAM and EVGA Precision X1 installed

[janrg]

I have neither AURA nor AI installed...

[robnivis]

List your build specs?

Mobo
Cpu
Gpu
psu

[janrg]

Oh sorry, I thought I had already listed that here, but I only did in the Cura forum.
ASUS STRIX X470-F
R7 2700X
EVGA RTX 2080 XC
Seasonic 660 Platinum XP2

[adamheinmiller]

It would be very helpful if anyone with a spare partition could do a clean installation of Windows 10 without installing AURA and AI Suite, and see if it reproduces there. From what I have read in the linked articles, uninstalling does not fix it (leaves something behind?).

I've never had either utility installed on my system.

I didn't list my motherboard in my prior post. I have the ASUS Strix X470-F.

[robnivis]

So the issue appears to have returned when I just left CURA idle for about 30minutes...

Very very odd

[janrg]

It does appear though that aside from the Ryzen CPU, the common factor between all of us is that we have ASUS motherboards...

[robnivis]

I am potentially swapping mine to an MSI soon as the ASUS AM4 boards aparently have poor VRM so this could be a contributing factor

I read the same issue (minus the cura part) on an amazon review also, so CURA may be coincidental rather than causational

[adamheinmiller]

It does appear though that aside from the Ryzen CPU, the common factor between all of us is that we have ASUS motherboards...

I am potentially swapping mine to an MSI soon as the ASUS AM4 boards aparently have poor VRM so this could be a contributing factor

I read the same issue (minus the cura part) on an amazon review also, so CURA may be coincidental rather than causational

We can't rule it out certainly, but I think another element here is we all have otherwise stable systems, and ASUS is a very popular board manufacturer - it was the only one available when I purchased my Ryzen, so a small sample size might make this a coincidence.

I've left my system running 24+ hours, pedal to the metal, doing stress tests on OC's. I've also had it running multi-day video encoding jobs (maxed CPU/GPU, high memory + disk IO) and it has been eminently stable. I think any fundamental stability issues with the board would be exposed in those extreme workloads. Cura, or something it does, seems unique in its ability to brown-note my system.

I've switched to using Cura on my Macbook so I'm not experiencing this any longer - but I'm happy to assist with any troubleshooting regarding this issue.

[janrg]

Just wondering do you ever put your Ryzen PC on standby? Thinking back to when I first set mine up, I used to get similar problems sometimes when I set it to standby, which is why I haven't done that in a long time. I think perhaps cura is triggering some underlying issue in the ASUS motherboards...

[rxdpunk]

Let me add my system to this list.
Ryzen 7 1700 4ghz
16gb ddr 4 3000mhz
Gtx 1070
Asus x370 pro motherboard

I get the same exact crash as reported by other users. In fact I didn't realize what was causing my crash for awhile. I ended up removing all over clocking from my system. Tinkered with power states. Removed all system standby. Even bought a new monitor because I thought it was failing lol.

[fanfan7110]

For information, as I said above, I switched to a Ryzen 7 2700X with Gigabyte GA-B450M-DS3H motherboard. this is now several days (see weeks) and with this new equipment I did not have any blocking or bug .. Would it be fair with version 1 of ryzen?

[rxdpunk]

I did drive format and fresh install of windows 10 home yesterday. So far cura 4 runs without crashing the system anymore.

Update: Cura 4.0 still crashes sometimes just a minute open, sometimes longer but always results in a black screen and have to reset pc by toggling switch on power supply

[TheFluffyWalrus]

I am also having the same issue also all the others having the same issue also seem to be running Nvidia GPUs...

Ryzen 7 2700x
Asus Prime x470 Pro
32gb Corsair 3000mhz
Nvidia 2080RTX

[AstraelOrannis]

Also having this problem.

Cura 4.0.0
Ryzen 2700X
Nvidia RTX 2080

32GB RAM
ASUS Strix X470-F motherboard

CPU, VRM and GPU are liquid cooled, temps are 50C or less.

I pulled my OC off the CPU and GPU still am getting blackscreened after about 30 minutes in CURA.

BIOS are updated and I have checked CPU voltage and made sure there isn't a power problem.

[Ghostkeeper]

So far we've seen it with all sorts of Ryzen chips:

• 7-2700X (most common)
• 5-2600
• 5-1600
• 7-1700

Maybe it only happens when the PSU is not strong enough?

[rxdpunk]

I have 850w power supply happens under idle

[AstraelOrannis]

750w 80+ gold PSU
Also happens under idle

[TheFluffyWalrus]

Thermaltake Smart 750w here... def does it on idle doesn't matter when it is.. Sometimes it crashes a few minutes in, sometimes 30+, one time it actually stayed running overnight after I went to bed and forgot to shut the machine down then crashed shortly after I woke the machine

[fanfan7110]

Hummm ... Have you see that all your motherboard are ASUS ???

[fanfan7110]

i tell that because since i have change my asus motherboard with a gigabyte, i don't have bug anymore

[rxdpunk]

If that is the the case I dont understand. What is happening between this one piece of software and a motherboard? I can push this PC to play destiny 2 maxed out for 8hrs straight.

[fanfan7110]

i know, i know (i'm a destiny 2 player's too) but it's a fact .. i don't have bug anymore

[robnivis]

It isn't a matter of how high you can push your PC or PSU's being undersized

to me the common issue here is ASUS motherboards with Ryzen chipsets. Could it be down to ASUS typically not having very good VRMs on their boards?

Also I find it bizarre that I ONLY experience this issue with CURA, no other program does it

[fanfan7110]

It's right and I think that's the case for everyone here. .Only Cura 4 create this problem and no other software...
In fact, I don't understand why the Cura developers team doesn't rent or borrow just a PC under Asus / Ryzen to see the logs of the development software.

[robnivis]

I had the problem with cura 3.6.0 and cura 4

For the amount of money ultimaker make, it feels like the €500 it would take to build a decent ASUS Ryzen PC to test this is trivial. Especially considering how widespread Ryzen is becoming

[Ghostkeeper]

For Ultimaker it's always been a matter of not having enough people to do the work rather than enough money or tools.

Not all Ryzen computers reproduce this though. One of our colleagues just got a Ryzen as well with ASUS motherboard, but doesn't see it happen (so far).

I would also have no idea where to look for a fix :confused: It's not like Python has an instruction that says "please freeze the CPU and make the screen go black" that accidentally gets triggered in our code due to a typo or something. It'll be either a bug in CPython, Qt or in GCC together with these Ryzen chips, and I suspect it's some bug in the power control of that motherboard which triggers on the type of power behaviour that Cura has, i.e. bursts of high CPU usage with breaks in between (like the internet says).

[TheFluffyWalrus]

So since I can reproduce this what can I do to help you fix the problems for other people?

[Ghostkeeper]

Maybe you could try putting Cura and CuraEngine's process on a lower priority?

Or maybe try running a different process at the same time that always takes 100% CPU, so that there are no breaks in the CPU usage any more (as far as the motherboard is concerned).

[TheFluffyWalrus]

Cura and the slicing engine both on low priority with prime95 eating everything so far so good... it is 12:31AM EST will leave this running while I sleep.... @Ghostkeeper Another thing I noticed about everyone crashing is we all have NVIDIA cards as well. I don't think its effecting people with ATI cards.... Could it also be GPU related?

EDIT:
SPOKE TOO SOON..... As I was shutting off the light to leave the room computer shut off dead as a door nail... So whats next brother?

[Ghostkeeper]

Do you have ASUS AI Suite installed? According to this thread and this post it can crash the GPU. It's been mentioned before here.

This guy with a similar issue mentions that he had installed MSI command centre and it pops up a message saying that his voltages are wrong: thread

I also see a lot of threads online where they ask the user to upgrade the BIOS on the motherboard or the BIOS on the GPU. And a lot of people complaining that ASUS quality control is terrible...

[TheFluffyWalrus]

I dont have ASUS AI suite installed... I will update my BIOS and and see if there is a BIOS update for my Founders Edition RTX then do the test again and report back.

Edit 1:
My Motherboard bios was already up to date

Edit 2:
No bios for the GPU

[rxdpunk]

I clean installed no AI suite current bios on everything still happens

[Ghostkeeper]

Maybe something else you could try is to install a very old version of Cura: http://dulek.net/work/Cura-2.1.2-win64.exe See if it happens there.
Installing this should not influence your modern Cura installation unless you install it over the same folder (but by default they are installed to different folders).

[TheFluffyWalrus]

Ok will do that it looks like Nvidia release some new drivers that fixed a bug in old drivers that caused CPU issues going to test with those and see what happens first.

https://www.tomshardware.com/news/nvidia-430-39-driver-cpu-usage-issues,39195.html

[TheFluffyWalrus]

still crashed after drivers update trying old cura now

[TheFluffyWalrus]

@Ghostkeeper 2.1.2 does not seem to be causing the same issues as the newer versions of cura

[Ghostkeeper]

Aha, so it must be either something we added in the past 4 years, or a nondeterministic issue... Doesn't narrow it down much, but it's something.

It'll still be very hard to debug this if we can't reproduce the issue ourselves though.

[TheFluffyWalrus]

Any way to add a logger to the current version? That just constantly logs
everything your application is doing until the computer crashes? I'm more
than happy to run such an application.

On Fri, May 3, 2019, 5:03 AM Ghostkeeper [e-mail] wrote:

Aha, so it must be either something we added in the past 4 years, or a
nondeterministic issue... Doesn't narrow it down much, but it's something.

It'll still be very hard to debug this if we can't reproduce the issue
ourselves though.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Ultimaker/Cura/issues/5265#issuecomment-489019762,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB6PHDDQ4K6GFAFBWFOS36DPTP5UXANCNFSM4GT63QFQ
.

[Ghostkeeper]

Thanks for your enthusiastic effort, by the way. It's nice to have a community willing to help.

@LipuFei you had a library that you added to Cura to output all the memory modifications in Python, right? What was it? If it's a pure Python library we can copy that into the source directory on a branch and create a build with it.

I don't think we'll see much though. If the processor freezes, it won't be able to write anything to file any more after the freeze, so it will have the last few seconds in the output buffer and won't be able to store it on disk before the freeze if we log it.

[TheFluffyWalrus]

You are offering a fantastic piece of software for free as well as sharing the source why would I not want to help. This is exactly what open source is about.

[adamheinmiller]

How many legacy versions are available/can be built? Since you've established an upper and lower boundary on the problem, we should be able to b-tree this and narrow it down to a few months with only a few more tests.

Can a working Cura version be built from the Github repo? I work in software development, albeit not Python, but if I could get it built and running locally I could help narrow it down to an offending commit.

On May 3, 2019, at 5:03 AM, Ghostkeeper [e-mail] wrote:

Aha, so it must be either something we added in the past 4 years, or a nondeterministic issue... Doesn't narrow it down much, but it's something.

It'll still be very hard to debug this if we can't reproduce the issue ourselves though.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[fieldOfView]

It would be my guess that the "thing" happens in PyQt or Qt that ship with Cura, not actually the (Python) Cura code itself. Since Cura 2.1, the version of PyQt has been upped a couple of times. I also don't think 2.1 is the last version that does not crash. Cura 2.7 is still available here:
https://ultimaker.com/en/products/ultimaker-cura-software/list

[TheFluffyWalrus]

I'll go install cura 2.7 now

[TheFluffyWalrus]

no crashes in 2.7
trying 3.2.1

[TheFluffyWalrus]

@Ghostkeeper it seems its 3.6 and 4 that are the only ones that seem to crash
I am currently testing 3.5.1 and no issues so far 5 hours in

[Ghostkeeper]

That narrows it down a bit. It seems we split off the branches for 3.5 on the 19th of September (Talk Like a Pirate Day), and for 3.6 on the 30th of October, so it must be some commit between that. When looking through the commits on cura-build-environment I see a bunch of changes to Python libraries as well as this change to the VC build environment and this change adding xz (and some commits for only MacOS).

[Lexiv]

I had the same issue with 4.0.
It seems to be fixed in 4.1 beta for me

[Ghostkeeper]

Huh, that's weird. We didn't change anything to fix this. Leastways, not on purpose. How about the 4.1 stable?

[Lexiv]

Is there a 4.1 stable?

[fieldOfView]

Yes, see https://ultimaker.com/en/products/ultimaker-cura-software

[Lexiv]

Oh sorry, got a bit confused because it wasn't available on sunday 😅

4.1 stable hasn't crashed my pc either (yet?). I've only sliced once with it though.
Maybe someone else who had this problem before can test 4.1.

My PC specs:

Ryzen 2600
Asus X470 Prime
Windows 10 (1809)

[adamheinmiller]

I updated my Ryzen PC to Cura 4.1 last night (specs further up the thread) and I haven't had any issues yet. I had Cura open last night for ~90 minutes while intermittently using it, and then left it open to idle overnight. My PC put itself to sleep after an hour or so, but woke right up this morning with no issues.

With Cura 3.6 my PC would hard crash in just a few minutes of even having it open and idle.

I'll keep using it and see if any issues come up, but there definitely seems to be a positive improvement here with this version.

On May 28, 2019, at 11:43 PM, Lexiv [e-mail] wrote:

Oh sorry, got a bit confused because it wasn't available on sunday 😅

4.1 stable hasn't crashed my pc either (yet?). I've only sliced once with it though.
Maybe someone else who had this problem before can test 4.1.

My PC specs:

Ryzen 2600
Asus X470 Prime
Windows 10 (1809)

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[Ghostkeeper]

On the Ultimaker forum someone reported that he still has this problem in Cura 4.1: https://community.ultimaker.com/topic/26654-cura-crashes-my-entire-computer/?tab=comments#comment-240611

[Lexiv]

My PC crashed again too while having Cura 4.1 open in the background.. so yeah, the problem is still there 😕

[adamheinmiller]

I also experienced a few crashes over the weekend. They were different though - my PC crashed and restarted on its own in a more traditional manner. They occurred while Cura was open in the background, and seemed to take more time to occur.

On Jun 3, 2019, at 8:34 AM, Lexiv [e-mail] wrote:

My PC crashed again too while having Cura 4.1 open in the background.. so yeah, the problem is still there 😕

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[Asbra34]

I also have this problem with 4.1, but in some rare cases the computer can reboot rather than become unresponsive. I first thought this had something to do with my overclock so i reset my OC setting but it made no difference. The computer usually becomes unresponsive within 20 minutes of opening Cura.

System:
Ryzen 7 2700X
Asus X470 Prime
GTX 1070

[Skybeat]

I have the same issue and reported it in this case https://github.com/Ultimaker/Cura/issues/5988

But i have this issue also with Cura 3.5.
My System
Windows 10 v.1903
AMD Ryzen 7 2700X
Nvidia Geforce 1060GTX 6GB

For me the crash comes some times after 1 minute some thimes after 10 minutes etc. It is different eachtime i use Cura. My Log attached in the Case #5988

[lenne0815]

Same Issue here, pc reboots with 4.1. Nvid / Ryzen

[lenne0815]

Still same issue on 4.2. if i remember correctly i can confirm it started with 3.6.

[Ghostkeeper]

But i have this issue also with Cura 3.5

Ah so maybe it did occur then but maybe less often? Cura 3.5 had fairly different power usage patterns than Cura 3.6 due to the changes to gap filling lines merging back then.

[lenne0815]

Only happens when cura idles in the backgroud, ive never had it happening while in ise.

And its easy to reproduce because it happens 100% of the time.

[disneytoy]

SAME PROBLEM:

Ryzen 3700x
32gb RAM
Asus Prime x470.
GTX 460 (old)
Win 10 Ultimate x64.
Cura 4.1.

3 times in a row my computer shut down after less than 5 minutes, while I was printing. I thought it might be USB or the printers main board?

Then I ran my computer 73 hours no issues. (no Cura)

Then today, NO USB plugged in, I was trying to set-up a new Cura profile, and my computer shut down. Everything on Idle. Ryzen temps in the mid 30c. 3-5% load (not printing).

As a new build I was concerned it may be CPU, Motherboard, Power supply, but now at least I know it is Cura. That is sad, because that is the only slicer I have any experience with.

Be great for a fix. With all the new Rizens I can only imagine many more problems. the 3700x is quite amazing for 8 cores and 65 watt TCP.

[Skybeat]

Since so many people have this issue, will a developer of CURA may give us some information or even a tool to debug get some more information for the developers? It is a bad situation to know that cura will frezz the pc but you want and need to slice a object. So please developer team of cura, give us some status info about the very bad BUG and what are the next steeps from your side to go on and fix this major BUG. Thank you!

[LipuFei]

@LipuFei you had a library that you added to Cura to output all the memory modifications in Python, right? What was it? If it's a pure Python library we can copy that into the source directory on a branch and create a build with it.

That library meliae is not pure Python and it's outdated for a long time. The release, if I remember it right, only works for Python 2. I partially ported it to Python 3 around 18 months ago, but I don't know if it's usable now. In short, that library is not available at the moment.

[LipuFei]

@Skybeat We have discussed this, if this is hardware issue that it cannot cope with a certain busty workload pattern, unfortunately we don't think that we can do much about it. We also don't have any Ryzen hardware to debug this issue, which makes it more difficult. But if you have more information or ideas on what could have caused the problem, we are happy to try them out.

That being said, one thing I can think of is that, in Cura, we have a thread pool for running jobs. This thread pool will create an equal amount of threads as the number of your CPU cores. With Ryzen there are more CPU cores, so more threads. So, this can be special in the case of Ryzen, although those threads are mostly idle.

I will create a Cura build with 2 threads max in the thread pool and upload the link here. You can try it see if it makes any difference. Thanks!

[lenne0815]

Sounds great, right now its atleast for usb printing unusable for amd users. Another annoyance is that it just survices that many hard crashes before parts break, right now the octoprint plugin stopped working for me.

[Ghostkeeper]

Handling 20 threads should be no problem for the operating system though. Right now Firefox is running 255 processes on my computer (wtf...) let alone the number of threads in each of those.

[LipuFei]

@Skybeat @lenne0815 Hi all, the link below is a Cura 4.2.1 build with at most 2 threads in the job queue.

https://we.tl/t-VubRI3UrF5

[disneytoy]

Commenting on your thought of creating too many threads. I have the 3700x 8 core 16. My last shutdown was on a fresh restart/Cura launch, No model loaded, I was just setting up a printer profile.

I'm thinking it is filling something up, that is why it takes a couple minutes to get to the crash.

Thanks for you work.

With these new Ryzen CPUs you will see a lot more users. AMD is killing it across the board on CPU vale from low end to server level.

I will try your new build and report back.

Cura is my favorite slicer:-)

[Asbra34]

@LipuFei I tested your build and it still crashed the computer, i sliced a part and then let it idle and within 10 minutes the screen was black and unresponsive.

[LipuFei]

@Asbra34 I'm now curious, if you launch Cura, don't slice anything and let it idle, will it also go black? This may help us to isolate the issue to Cura or CuraEngine.

[janrg]

@LipuFei Perhaps another avenue of investigation would be to create a bunch of binaries for the commits mentioned in https://github.com/Ultimaker/Cura/issues/5265#issuecomment-489535920 to nail down the exact commit that caused this issue?

[LipuFei]

@janrg @Skybeat mentioned that 3.5 also causes the problem for him. :(

Good idea though, it's still a bit tricky to figure out where to start the split. I think starting from figuring out if running Cura alone will cause a crash can already help a lot.

• If running Cura alone without doing any slice already causes a crash, we can start narrowing it down to a plugin, or Uranium, or Cura, or maybe some Python package we use.
• If it only crashes after we do a slice, we can check if running CuraEngine alone causes the problem, and investigate further, etc.

Splitting with Cura release versions still gives a way too broad scope because it includes all the parts that were just mentioned.

[Asbra34]

@LipuFei I started cura almost immediately after your comment and it just now crashed, so around 20 minutes. I just started it and did not load any models or anything.

[LipuFei]

@Asbra34 Thanks! We will discuss this and hopeful get some new ideas.

[disneytoy]

Crashes 3700x with no model loaded or slicing, about 3 minutes Idle. No other apps open.

[LipuFei]

Hi all, for us to make sure that CuraEngine has nothing to do with this issue, could you try one more thing? Thanks in advance.

• Open your Cura installation directory and rename the file CuraEngine.exe to for example CuraEngine.exe.bak. (See screenshot below)
• Start Cura.exe
• Open TaskManager, go to the Details tab, sort by name, and make sure that there's no CuraEngine.exe running.
• Keep Cura idle and wait see if the problem still occurs.

[Asbra34]

@LipuFei I tested cura without CuraEngine (checked task manager and there was no slice button in cura) and it crashed after around 30 minutes idle. I did not load any models or even rotate the view. And i used your debug_ryzen build.

[GibsAndBits]

@LipuFei I have experienced this issue as well and I believe it may be an issue specifically with Ryzen CPUs and ASUS motherboards. There is an issue with the monitoring sensors in the ASUS motherboards that cause a similar issue if multiple monitoring programs access the same sensor. This results in a "frozen" PC state where the PC is still on, but no inputs function, including the PC power button.

Rather lengthy post for more info:
ASUS x470F forum post

Hope this at least sheds some light on the cause of the issue.

[lenne0815]

Does cura poll sensors ?

[Ghostkeeper]

No, it doesn't. It does poll USB ports though. Complete list (as far as I can think of) that Cura ever uses from your OS:

• File system
• USB ports
• Internet connection, incl. zeroconf listening
• CPU and memory
• Detecting operating system
• Creating windows and interactive GUI elements (incl. mouse and keyboard)
• Rendering with OpenGL
• Creating file dialogues
• Drag-and-drop on the window
• Environment variables such as %APPDATA%.

@GibsAndBits that matches with the findings previously in this thread from fanfan7110.

[lenne0815]

Interesting, maybe @fanfan7110 can report again if he ever encountered the issue on the gigabyte board later on. Im also on a asus board fwiw.

Would it be possible to get a build for testing with the whole usb component cut out ?

Edit: after further inspection the linked thread from @gibsandbits doesnt really reflect my problem, its a fan issue with the x470, my fans work fine until the pc blackscreens / lock up.

[GibsAndBits]

The issue I linked was related to a black screen crash on Asus+Ryzen where the PC becomes unresponsive with a black screen, but remains powered on indefinitely. This is the same type of crash I have experienced with Cura. The only way to restart computer is to manually cut power to the motherboard, as even the power button is unresponsive. A lot of information about the problem is vague, as there isn't a crash or error event. However, the majority of people in that thread have avoided it by not installing monitoring suites, such as AISuite, Asus Aura, etc.

[Skybeat]

@LipuFei I tested cura without CuraEngine (checked task manager and there was no slice button in cura) and it crashed after around 30 minutes idle. I did not load any models or even rotate the view. And i used your debug_ryzen build.

Exactly the same for me.

[Skybeat]

The issue I linked was related to a black screen crash on Asus+Ryzen where the PC becomes unresponsive with a black screen, but remains powered on indefinitely. This is the same typemof crash I have experienced with Cura. The only way to restart computer is to manually cut power to the motherboard, as even the power button is unresponsive. A lot of information about the problem is vague, as there isn't a crash or error event. However, the majority of people in that thread have avoided it by not installing monitoring suites, such as AISuite, Asus Aura, etc.

Well, i have installed the AISuite. I will uninstall it and try it again. I will post the result

[lenne0815]

I dont have ai suite or any other monitoring software installed, nor does my pc blackscreen in any other situation than running cura in the background. But, i think we can establish that everyone reporting crashes runs an asus mobo ?

[GibsAndBits]

I have been able to use PrusaSlic3r successfully on my Ryzen PC without any crashes. I believe PruseSlic3r has USB/serial interfacing disabled by default (if it's even an option, I use a Raspberry pi). Could the serial interaction be a potential cause? I believe the serial interface goes through the same Super I/O chip as temp monitoring.

[disneytoy]

I do use an Asus Prime x470 with 3700x. But I don't get a black screen. It just restarts. I have a fast M.2 SSD as start up, so when Cura "crashes" I'm back to the login windows 10 ultimate screen in a couple seconds.

Interesting if we can take a poll of those with Asus x470 motherboards here?

[LipuFei]

@GibsAndBits Thanks for the information. I only found an Asus Prime X470-PRO on Asus website. Is that the one you are using? I also saw a BIOS update on July 31. Does that help?

@disneytoy Below is a poll for this issue. I've never used this polls app before so not sure if it works..

EDIT: Changed to focus on ASUS motherboards.

[lenne0815]

Thats way to focused on the 470x i think we should focus on asus ryzen mobos in general, im on a asus x370 prime and have the problems. I do have a ryzen non asus setup aswell though, ill install cura there, load my profiles and see if that crashes also later today.

[LipuFei]

Thats way to focused on the 470x i think we should focus on asus ryzen mobos in general, im on a asus x370 prime and have the problems. I do have a ryzen non asus setup aswell though, ill install cura there, load my profiles and see if that crashes also later today.

I've updated the polls to focus on Asus motherboard in general.

[lenne0815]

Perfect ! Im really looking forward to testing it later today.

[LipuFei]

@GibsAndBits The USB/serial connection code hasn't seen many changes For those of you how suspect the USB/serial connection. If you suspect the USB connection, you can remove the "USBPrinting" plugin in the plugins folder where your Cura is installed. The screenshot below also shows a number of plugins that you can remove without crashing Cura, but of course, some functionalities will not function correctly or not be available at all.

EDIT: forgot the screenshot...

[Skybeat]

So I have uninstalled all Monitoring software as well as AI Suite but the crash is still there.
Next i will remove plugins as @LipuFei recommended.

[Ghostkeeper]

Easier way to disable plug-ins is from the interface: Go to Marketplace, then "Installed" tab. Then uncheck the plug-ins you wish to disable and restart Cura.

[Ghostkeeper]

Well, i have installed the AISuite. I will uninstall it and try it again. I will post the result

Note that previously in this thread people have said that removing the AISuite only solved the problem by removing all traces of it, by completely reinstalling the computer without that AISuite thing.

[GibsAndBits]

@LipuFei my hardware is an Asus ROG Strix x470-f Gaming with a Ryzen 2600X CPU. I have never had AISuite installed on my current OS install.

[disneytoy]

Yes I am using a 3700x with Asus Prime X470-PRO Latest bios Version 5204 2019/07/31. I have AI Suite but never used it?

[TheFluffyWalrus]

@LipuFei

Another thing we have in common is we all seem to have "NVIDIA GPUS"....

I personally don't think it's directly related to RYZEN and ASUS but I think NVIDIA is part of the issue too

[janrg]

@TheFluffyWalrus Given the marketshare of NVIDIA it's not surprising, you'd expect perhaps 1 person out of a group of our size to not have one (perhaps 2 if you factor in that people with AMD CPUs may be more likely to buy AMD GPUs)

[disneytoy]

My GPU is an old GTX 460 9 years old

[robnivis]

Well, i have installed the AISuite. I will uninstall it and try it again. I will post the result

Note that previously in this thread people have said that removing the AISuite only solved the problem by removing all traces of it, by completely reinstalling the computer without that AISuite thing.

when I did this previously it didn't solve the problem, only gave a very brief respite

[lenne0815]

So i ran it on my ryzen msi board with amd gpu - no crash.
But just to make matters even more confusing, a guy reported with the same as my crash mobo that it doesnt crash for him...

[robnivis]

So to summarise a little here:

13 reports from ASUS boards crashing, 2 reports from Gigabyte and MSI not crashing

Of the ASUS boards, B-450 (1 report), X-450 (1 report), X-470 (8 reports), X-370 (2 reports)

So it can be narrowed down to ASUS boards I think. Could it be the ASUS VRM issue we mentioned a couple of months ago?

[TheFluffyWalrus]

@janrg I am suggesting to those who have an AMD CPU that has GRAPHICS remove their dedicated NVIDIA card and see if they still crash?

[disneytoy]

I'm taking a poll on the Facebook CR10 user group and so far those with Cura+Ryzen+MSI no issues.

[disneytoy]

WORKAROUND: I'm still testing. I tried Ideamaker but could not figure it out. I know Cura settings very well. I downloaded SANDBOXIE which is a windows sandbox. I right clicked Cura and chose RUN IN SANDBOXIE. It puts a yellow outline around the window. So far no crashes after 30 min. I'll let it run and report back if it crashes.

UPDATE: It crashed after an hour. Came back to the boot screen:-(

[Ghostkeeper]

Could you guys try using compatibility mode for layer view? It's in Preferences -> Configure Cura... -> Force Layer View Compatibility Mode.

This causes Cura to be rendered with OpenGL 2.1 instead of OpenGL 4.0.

[disneytoy]

"Preferences -> Configure Cura... -> Force Layer View Compatibility Mode."

Tried it. I crashed in 1 hour. (3700x Aus Prime x470)

So Developers,

What processes are you running that don't start for 60 minutes?

[Ghostkeeper]

Nothing afaik. The longest timer in Cura is 8 minutes to refresh an authentication token, and that only happens while you're logged into an Ultimaker account. After that, the longest timer I know of is the 30 second timeout of messages on the bottom of your screen.

Maybe something could be happening with the internet connectivity? Cura doesn't make a connection to the internet aside from user interaction (like opening the Marketplace), EXCEPT if you're connected to your printer via OctoPrint or connected to an Ultimaker printer via LAN. It then requests a status update every 2 seconds. Maybe if the internet connection is interrupted something could happen?

From all the things I've seen though, something is going wrong in the power management of the motherboard or access to RAM. I'm 99% sure that Cura just happens to hit some usage pattern that triggers it. The online forums about this topic report that it happens while gaming or when a VM is open.

[disneytoy]

I don't know if the log would tell us anything after a crash:

How do I view Windows logs?

Click Windows Start button > Type event in Search programs and files field.
Select Event Viewer.

Navigate to Windows Logs > Application, and then find the latest event with “Error” in the Level column and “Application Error” in the Source column.

Copy the text on the General tab.

[rxdpunk]

Been using 4.3. I am no longer getting a crash that completely shutdown pc and requires a hard power cycle. However after random amounts of time it will cause my pc to reboot. I haven't timed it but maybe around 20 min or so before a reboot occurs.

[LipuFei]

I dont know... We didn't do anything specifically for this problem because we still don't know the root cause.

[Ghostkeeper]

We still haven't been able to do anything to fix this, no. Our programming language of choice is powerless with this sort of thing.

Maybe you downloaded new drivers for your CPU or new graphics drivers and that fixed it? Or changed the result?

[nallath]

[disneytoy]

lenno0815, Which Asus motherboard are you using, and have you updated bios at all?

[disneytoy]

Thanks. I will try the new 4.3 on my Asus Prime x470 (3700x).

UPDATE: Crashed at 17 minutes Idle with a stl loaded and sliced:-(

[disneytoy]

Can I confirm from the developers, there is no crashing issue on MSI boards? I may get a new Motherboard.

[Ghostkeeper]

We only know of the issue from this thread (and the accompanying forum topic that linked to it).

In this thread it was determined that the issue was only happening with the combination of ASUS motherboards together with Ryzen CPUs. As far as we've seen anyway.

[lenne0815]

Aaaaaaaand It Crashed AGAIN Hooooray !!!

[VanillaWaferX]

Going to throw another report of crashing in the mix.
Asus ROG Strix x470-f Ryzen 2700 4x8gb Corsair ram and a XFX vega 64. I am also running windows and Cura 4.1 off an NVME Ssd in case that matters.

I want to note that my crashes are random. Not Right away and Cura does not have to be open during the crash. If I open it at some point I might get a hard crash later after I close it.

Also I'm going to grab 4.3 when I get home and start testing.

Update: 4.3 Crashed sitting in the background with a sliced model. About an hour and a half open and black screens pc.

[barthelby]

just found this topic after 3 weeks of random crashes

my config:

• Ryzen 7 2700
• Asus Prime X470-Pro
• GTX 1080
• 16Go DDR
• Windows 10
• Cura 4.3.0

i've done a fresh install two days ago (thought it was a driver problem...)

[FluffyTheWalrus]

So I can confirm my issue went away when I swapped my NVIDIA GPU for an ATI GPU...

3 days running idle no crashes, 1 day printing from USB no crash.

[larsleukert]

Since uninstalling Asus AI Suite and Aura Sync Software i have never had reboots again.
Before i had reboots after several minutes - only with Cura running/idle.
(Asus Prime X470-PRO, Ryzan 7 2700x, RadeonRadeon RX 590, not OCed)

[barthelby]

Nope it doesnt Come from there, all Asus addons were Nevers installed on my computer

[smartavionics]

BTW, has anyone tried running Cura on Linux on the same hardware? i.e. boot off a USB or another partition and then run the Linux version of Cura. If so, does it still crash?

[FluffyTheWalrus]

I have a spare SSD I could install Ubuntu, Mint, Debian... What do you folks want to see?

[janrg]

What I have tried is running Cura in a Linux virtual machine. It's a rather ugly workaround but it works.

[FluffyTheWalrus]

I wouldn't say that's an ugly work around in fact it's quite smart

[smartavionics]

Any distro would be OK, I think. I have to admit that I don't have a good reason to suggest running Cura on Linux other than it would at least provide some evidence that the hardware is not inherently unreliable.

Python, Qt and PyQt on Linux are compiled using gcc. On Windows, Cura uses a pre-built version of PyQt (which include Python and Qt). I don't know how that is built, what compiler is used, etc.

[FluffyTheWalrus]

Okay when I get home I will install that OS and we will test

[FluffyTheWalrus]

Will use Ubuntu

[smartavionics]

FYI see https://community.ultimaker.com/topic/29797-experimental-windows-cura-build-based-on-pyqt-513/ maybe it's worth trying?

[FluffyTheWalrus]

No crashes on Linux same hardware

[sipos84]

been getting crashes for weeks. I suspected cura early on but now its confirmed as all the crashing has actually caused some issues with my psu with all the hard resets (shouldnt but its currently being RMA).

anyway, here are my specs,

asus prime 470
ryzen 2700
raedeon rx580
was using a seasonic 650 (currently on its way to RMA), replaced with an evga 650 g+
win 10
32gb corsair ram
samsung ssds

crashes after about 2-5 mins now. before it would crash randomly 5mins to 60 mins. oddly enough my pc works fine if after a boot i never run it. but after i run it, even close it, i will get a random crash anyway within 5-60mins. but if i never run it, never crashes.

i will also try a virtual pc to run it and see

[AlwaysMe009]

Has anyone had any luck finding a fix or work around on this yet? Been getting crashes that kills the entire computer.
Windows 10
Cura 4.3.0
Ryzen 5 1600x
ASUS Prime X370-Pro
GTX 1060
16gb ddr4
Samsung Evo ssd

[gdavey]

I am also getting the same issues Cura works fine until I send to one of my printers and then my pc crashes.

OS: Windows 10 64bit
Cura: Ultimaker Cura 4.3
CPU: Ryzen 7 2700x
Mobo: Rog Strix X470-F Gaming
GPU: 2 x ZOTAC GeForce GTX 1080 Ti Mini
Memory: Corsair RGB Vengence Pro 3000mhz
HDDS: 2 x 970 PRO NVMe M.2
4x SanDisk SSD PLUS 480 GB
1 x Seagate 4 TB BarraCuda

[AlwaysMe009]

I have done what others above have said and installed Cura 4.3.0 on Ubuntu 19.10 that is running in Virtual Machine 6.0.14. So far so good. Haven't had a crash yet.

[Rodriges-MkII]

I have same problem with my computer

PC
OS:Windows10 64bit
CPU:Ryzen2700x
GPU:GTX1050Ti
RAM:DDR4 32GB
MOTHER:ROG STRIX X470-F GAMING
STRAGE0:NVME SSD 512GB
STRAGE1:5TB HDD

Cura:ver 4.3.0

[AlwaysMe009]

Just an update after about a week. I haven't had a single crash since running Cura in Virtual Machine. It's definitely not the best option (slow/laggy), but I feel it is better than nothing.

[FluffyTheWalrus]

I would like to point out I have allowed Cura to run for 24 hours... No virtual machine, Ubuntu Linux and I have had absolutely no crashes.

[disneytoy]

I miss Cura. My settings were great. Having lots of issues with Prusa Slicer 2.1 and Simplify3d:-(

[Ghostkeeper]

It seems that towards the end of September, ASUS has provided new BIOS for all (or many?) of its modern motherboards. If you haven't tried that one yet, perhaps you can update.

[FluffyTheWalrus]

@Ghostkeeper I have personally updated my bios it did not resolve the issue... What did work is running Linux natively and had absolutely no crashes... Is there a difference between the Windows version and the Linux version of Cura? If so that could be the solution..

[fieldOfView]

The biggest difference I can think of is that the Windows version runs on Windows, while the Linux version runs on Linux. They operate in fairly different contexts, with very different drivers and supporting applications.

I still suspect an interplay of Cura with "Aura" or "AI Suite" or something that gets installed with either of these tools as I suggested here:
https://github.com/Ultimaker/Cura/issues/5265#issuecomment-468178699
The solution indicated there is to never install those tools; uninstalling apparently leaves something behind. I have no Ryzen system, so I don't know what that something might be.

[lenne0815]

Its clear by now that it wont be resolved so i switched to prusa slicer which suits my usecase better anyway ( i need adjustable layer heights for most of my prints and the ui is much faster ) For anyone looking for a great alternative i can only recommend it. Im just wondering about ultimaker customers, do they get prusa slicer profiles with their machines now ?

[disneytoy]

I miss using Cura, I've gone Simplify3D and Prusa Slicer now. I just know all the tweaking in Cura advanced settings much better.

[TwoHeadedBoy]

This is also happening to me:
OS: Windows 10 x64
CPU: AMD Ryzen 5 2600x
MOBO: ASUS Prime X470-Pro
GPU: GeForce RTX 2070
RAM: Corsair Vengeance DDR4 32 GB

I’m concerned that this will happen again without even starting Cura after a fresh restart. Is there any likelihood of that?

[SpaceAge12]

Still happening in CURA 4.4
OS: Windows 10 x64
CPU: AMD Ryzen 5 2600x
GPU: GeForce RTX 2070
RAM: HyperX Fury DDR4 16GB

[Ghostkeeper]

I’m concerned that this will happen again without even starting Cura after a fresh restart. Is there any likelihood of that?

Yeah, there is.

As far as we've seen, this blackout occurs when the CPU needs to alternate often between high power usage and low power usage. Something goes wrong between the motherboard and CPU. This happens to match the power usage profile of Cura, which is why people attribute this to Cura. But when doing other stuff that alternates between high and low power usage, such as restarting your computer, it could also blackout then.

[lenne0815]

I doubt that, firstly i never had an unaccounted reboot when cura wasnt running and secondly i never had an unnacounted reboot with any other type of software. While i can imagine it has something to do with power states and the boards, its only ever been cura + windows triggering the bug for me.

[Ghostkeeper]

Maybe you haven't experienced this in other ways, but other people have. They are coming to the same conclusions there: Don't install AURA suite, power regulation problems, ASUS boards only, etc.

[Rodriges-MkII]

I changed my BIOS to ver.5406 and still have same issue , so I change my slicer to Prusa slicer

[Ninnog43]

@Ghostkeeper I can confirm that the problem is with Asus MB's combined with Amd CPU's... I have tried to run Cura on 3 different pcs now PC (A) (https://pcpartpicker.com/list/pv6Wcq) PC (B) (https://pcpartpicker.com/list/ZmGZcq) PC (C) is a old HP beatsaudio laptop. So from my experience PC B and C run Cura without a hitch other than being slow but PC (A) will crash at a random time to black screen of death after Cura is launched. PC (A) Does Not have AURA or AI Suite installed and has never done this with any other software or game i have run on it including some of the most graphically and CPU-intentive games/software of 2019 with no problems but some how Cura just seems to kill it even if its in the background so im stumped.

[disneytoy]

My workaround: AMD 3700/Asus Prime x470.

I design in Fusion 360. Export an STL. Then I launch Cura 4.4. (so slow 30+ seconds on an NVME) I import the model, rotate etc. Slice and save to my card. (I miss USB printing though).

Then I quit. So the small window of time I need to slice does not crash my computer. I use to leave Cura running 24/7 in the background.

But at least I can use it. I do have S3D, and was trying Prusa. But I understand the advanced setting in Cura much better. I'm more lost in the other slicers.

[Ghostkeeper]

Some more internet discussions about this combination of motherboard and CPU:

• https://forums.unraid.net/topic/61767-amd-ryzen-update/
• https://linustechtips.com/main/topic/1117451-rtx-2070-super-black-screen-or-freeze/
• https://www.nvidia.com/en-us/geforce/forums/geforce-graphics-cards/5/283981/black-screen-with-rtx-2080-ti-after-restarting-pc/ (some users are reporting different issues in this thread)

It seems that the problem is that the CPU finds that no processing power will be needed for a while and instructs the PSU to go to power saving mode C6, which should go to 0.4V of potential, but the PSU is not able to handle that since it usually never goes below 0.8V, yet Asus claims that the PSU is able to handle that.

ASRock had this problem as well but it was fixed in their BIOS version 4.4. That thread has some interesting analysis about the issue.

I also found several articles that AMD tried to fix it with certain other Haswell instructions and claimed that it was fixed but then had to crawl back on those claims.

[disneytoy]

That is an interesting theory _" It seems that the problem is that the CPU finds that no processing power will be needed for a while and instructs the PSU to go to power saving mode C6"_

But my system always has a ton of other apps running, Browsers etc. I can't imagine it is ever completely Idle, even if I am away.

Though I wish it gets fixed. I can use Cura, just launch, load slice and quit.

[Ghostkeeper]

As long as your CPU isn't always on 100%, there are times that your CPU, or at least one core of it, will be completely idle, however short. Whether those short waits are enough for the CPU to decide to send a message to the PSU I can't say.

You might be able to test that theory by getting another process to keep all cores occupied 100% of the time but give that process a low priority. It will interfere with Cura's performance (especially since the slicing process also gets a low priority) but at least it can test the theory that those guys came up with.

[Elisedlund]

Cura powercycles my computer at random(like every couple of hours)
I felt a that i got lower crash frequency when I lowered my CPU overclock and Ram frequency

I have a ryzen 1800x + 1080ti and use cura 4.0.0

Closing down cura as soon i have have sliced fixes my crash issues. (I have had this problems for months until now i figured out that it only happen when cura was up)

[tpmeredith]

Having the same issue.. Ryzen 3900x. Before seeing this thread i tried:
Swapped boards from asrock x570 Taichi to asus x570 rog strix-f with up to date bios on both
4-5 ram kits some b-die 3200mhz-3600mhz (tried setting timings manually not just with xmp, etc) Also tried downclocking to 2600-3000mhz, i always adjust fabric to 50% too (up to 1600ish) as recommended
multiple power supplies (850w platinum right now)
Using EVGA 1070
Swapped 3900x to a different brand new one, since we ordered multiple for work.
I can run prime95 for 10+ minutes no problem. Ran furmark no problem.

Gonna try disabling c states/etc.

Similar to other user reported often when it happens it corrupts profile too.

Have tried cura 4.0 to current 4.4.ish

[Derrin616]

My Cura also crashes in like 5 min! Most times i just start Cura and in 1 sec i import my stl en spam on Slice and export it and close Cura.

That crash is very annoying because it fucks my pc and it also reset sometimes the cura profiles so i get that welcome popup and everything is lost.

PC:
Asus ROG STRIX B-450-F Gaming
Ryzen 5 2600
Asus GTX 1050 Dual
Corsair 3200Mhz 2x8GB RAM
Coolermaster 650w PSU
Samsung 970 evo 500GB

[Skybeat]

My Cura also crashes in like 5 min! Most times i just start Cura and in 1 sec i import my stl en spam on Slice and export it and close Cura.

That crash is very annoying because it fucks my pc and it also reset sometimes the cura profiles so i get that welcome popup and everything is lost.

PC:
Asus ROG STRIX B-450-F Gaming
Ryzen 5 2600
Asus GTX 1050 Dual
Corsair 3200Mhz 2x8GB RAM
Coolermaster 650w PSU
Samsung 970 evo 500GB

Welcome in the "club".
The most annoying thing is that Cura is the only software what makes this issue and problems with my PC, no other software is crashing my pc.
I am a developer myself and I cannot understand why the developers of CURA do not provide us with a debug version in order to collect more clues and data on where the BUG can be found in Cura. Yes it is 100% a bug in CURA that no other software and no other slicer makes my PC crash so badly.

I have been thinking that the CURA with such hard crashes also damaged my hardware.
SO please development team of cure, don't stay silent anymore.
Let your fingers fly and provide us a debug version where you log as much as posible.
Log each thread you have in your code, each array hashtable and so on to find your bug and giv you tha chance to fix it..

This issue is now open since over 1 year and it is time to do some thing on your side.

[smartavionics]

It's probably not a bug in the Cura source that's at fault here. AFAIK, the same source running on the same PC hardware doesn't lock up if the OS is Linux and not Windows. I believe that people have even run a Linux VM on WIndows on the same HW and it doesn't lock up.

[smartavionics]

Hi @LipuFei , have you tried building Qt/PyQt on Windows recently instead of using the ready made releases? Maybe it's worth a shot?

[Skybeat]

It's probably not a bug in the Cura source that's at fault here. AFAIK, the same source running on the same PC hardware doesn't lock up if the OS is Linux and not Windows. I believe that people have even run a Linux VM on WIndows on the same HW and it doesn't lock up.

No no, you are wrong. Yes we are not using Linux, we use Windows but CURA is available for Windows.
Next point is, no one in all this comments have a issue with any other software on Windows, except with CURA.
As a developer of CURA, you can not say it is not a BUG in CURA because this kind of hard crashes are not normal and ONLY happen with CURA on Windows.
It is easy is to say it is not a bug in Cura, but as a good developer you want have a 100% stable software providet or I'm wrong?

[Derrin616]

It's probably not a bug in the Cura source that's at fault here. AFAIK, the same source running on the same PC hardware doesn't lock up if the OS is Linux and not Windows. I believe that people have even run a Linux VM on WIndows on the same HW and it doesn't lock up.

No no, you are wrong. Yes we are not using Linux, we use Windows but CURA is available for Windows.
Next point is, no one in all this comments have a issue with any other software on Windows, except with CURA.
As a developer of CURA, you can not say it is not a BUG in CURA because this kind of hard crashes are not normal and ONLY happen with CURA on Windows.
It is easy is to say it is not a bug in Cura, but as a good developer you want have a 100% stable software providet or I'm wrong?

Yes you are right! This is not a normal bug! My whole pc is just spacing i litterly need to kill it with power even the reset button does not work. Im a Dev self and im asking how the heck can u get it it crash it so hard that nothing works

[smartavionics]

Well, firstly, I am not a UM Cura developer, I'm just a Cura user that has made some contributions to the Cura code base.

Secondly, I personally don't give a flying fuck about whether Cura runs on Windows or not as I never use Windows[*] and can't imagine how anyone could want to use it.

Anyway, as I just mentioned above, I wonder if there is some mileage in building the Windows Cura release differently as perhaps the problem is due to a compiler bug or library bug that is in the pre-built software (Python, Qt, PyQt, etc.) that Cura uses.

On the Linux builds, all of that stuff is compiled from scratch.

Im a Dev self and im asking how the heck can u get it it crash it so hard that nothing works

You would have thought that a robust OS would not allow a user program to lock up the hardware.

• actually, I do use Windows but only to build my Cura releases.

[Derrin616]

But who makes Software without a log folder?

[fieldOfView]

I don't know who makes software without logging. Not "us". At least not in this project.

cura.log can be found here:
https://github.com/Ultimaker/Cura/wiki/Cura-Preferences-and-Settings-Locations

[Skybeat]

I don't know who makes software without logging. Not "us". At least not in this project.

cura.log can be found here:
https://github.com/Ultimaker/Cura/wiki/Cura-Preferences-and-Settings-Locations

You are right, CURA hase some logging but in my oppinion not as much as it have to be.
Can you expand the logging so that we can provide you whi more detailed log data for this extrem hard crashes.
And again, that you know how hard this crashes are, if CURA crashes my PC, I have to turn off my PC via the power supply switch and remove the power cable from it for 10 seconds. After that I'm abail to start my PC again. So trust me if i say it is a extrem hard crash.

Since I'm also a developer, here is what I do if I have a bug and cannot find it right away:
I create a debug version and give it to the user with the instructions on how to use it.
I also expand the logging extremely, in every thread, in every loop and so on, there are log entries.
So you can also find a bug.
I know this is a lot more work for you but you have to do some thing if you want provide a 100% working software.
I mean, we know that this crashes most of the time are with AMD CPUs and Asus mainbords, so have you think about the point how many AMD CPUs and Asus mainboards are out in this world? so this problem will be come bigger and bigger if you dont do anything.

If you provide us a debug version I'm happy to test it for you and provide you the data after the next crash.

[fieldOfView]

For the record, like @smartavionics I am a community contributor to the Cura project. I don't have to do anything.

I'm sorry you can't currently run the software on your computer, and I know there are others like you. I have contributed fixes for specific configurations before, but the problem here is that the crash happens outside of the code that I contribute to; the crash does not happen in the Cura code but it seems to be in the code of the frameworks or 3rd party code that we use in combination with platform specific drivers. If the problem were directly caused by the Cura code, it would show up in the current logs. We can't add logs "in every thread, in every loop and so on" in your drivers, or in all the 3rd party frameworks or modules we use.

[smartavionics]

Trawling the internet, I see that one cause of Ryzen lockups is due to the use of FMA3 instructions. It is possible to disable the use of those instructions in the C runtime and so I have built a Windows release that does that. I don't have a Ryzen so i can't test it but if anyone here is willing to give it a go, please do and report whether it behaves any differently.

You can find my releases at https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0.

Please read the README.md file there for more info.

[smartavionics]

Actually, I don't think my release is going to be any good because some of the pre-built DLLs used also contain FMA3 instructions and they will not be disabled. If the crashes really are being caused by the Ryzen FMA3 bug, then this is going to be hard to fix. However, I understand that problem was addressed by AMD some time back with new BIOS and microcode so maybe the Cura crash is something else.

[nallath]

It is easy is to say it is not a bug in Cura, but as a good developer you want have a 100% stable software providet or I'm wrong?

I want to have a 100% stable release, but I also know that I won't ever achieve that. I also don't want a stable release at all costs. As much as it pains me, we also have to do something called "triage", where depending on the severity and difficulty of fixing it, it gets a priority.

[Ghostkeeper]

Hi @LipuFei , have you tried building Qt/PyQt on Windows recently instead of using the ready made releases? Maybe it's worth a shot?

LipuFei stopped working for Ultimaker recently. It's something we can try, but it might just be easier to upgrade to a new Qt version and just as effective in re-randomising the instructions. Then again, this issue also occurs with Cura 3.2 when we were still on Qt 5.8, so maybe not.

Next point is, no one in all this comments have a issue with any other software on Windows, except with CURA.

We've pointed out numerous software packages with the same problem in previous responses.

About the logging expansion, we're really not sure where to start here. The problem seems to occur in idle, which expands the search radius to about 2.5 million lines of code that we'd have to log. And most likely it's still not within those lines but in one of our dependencies. Other similar threads of investigating this bug on the AMD forums have pointed out that it's a processor instruction that makes it go into low-power mode because there is no code to execute.

I'm currently most hopeful for this comment:

Gonna try disabling c states/etc.

@tpmeredith did you try disabling C states in your BIOS yet?

[Skybeat]

The problem seems to occur in idle, which expands the search radius to about 2.5 million lines of code that we'd have to log.

Well not for me because i have crashes also after slicing whene I'm in the preview mode and for example turn the model in CURA.
SO i think it is not only in idle.

[Skybeat]

Trawling the internet, I see that one cause of Ryzen lockups is due to the use of FMA3 instructions. It is possible to disable the use of those instructions in the C runtime and so I have built a Windows release that does that. I don't have a Ryzen so i can't test it but if anyone here is willing to give it a go, please do and report whether it behaves any differently.

You can find my releases at https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0.

Please read the README.md file there for more info.

Thank you for the test release, i will try it later today whene I'm back at home and will give you feedback after the test.

[smartavionics]

Well not for me because i have crashes also after slicing whene I'm in the preview mode and for example turn the model in CURA.

Hmm, that does make me think the crashes are due to the FMA3 Ryzen bug because turning the model does a bunch of math that is quite likely to use the FMA3 instructions.

If you try my latest release and it doesn't crash when idle but still crashes when the model is turned I think that would confirm my theory.

[Rodriges-MkII]

@smartavionics
I installed your latest version app and left for about an hour and my pc is still running
I will try other operations now

[smartavionics]

With the UM releases, would it have crashed in an hour of running idle?

[Rodriges-MkII]

Yes, Cura4.4 and 4.3 crashed on my PC in minutes with no 3D model loaded as far as I know

[Ghostkeeper]

The FMA3 issue was fixed 3 years ago in a BIOS update. It wouldn't explain why it only occurs with ASUS motherboards either. Maybe we're trying to battle multiple issues here with the same symptoms.

[Skybeat]

Trawling the internet, I see that one cause of Ryzen lockups is due to the use of FMA3 instructions. It is possible to disable the use of those instructions in the C runtime and so I have built a Windows release that does that. I don't have a Ryzen so i can't test it but if anyone here is willing to give it a go, please do and report whether it behaves any differently.

You can find my releases at https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0.

Please read the README.md file there for more info.

I have tested your test-release, but I have hat the crash abou 1,5 min after start.
Now comes the interesting thing:
Second time I have start my Visual Studio and open the Cura.exe as a project. Than i startet debug the project (F5) in VS and since than it is running without a crash till now (currently runtime with the debuger is 25 min).
It is fully useable.

The Output of the debuger since the start are the follow lines:

QObject::connect: Cannot queue arguments of type 'QList'
(Make sure 'QList' is registered using qRegisterMetaType().)
Model size of -30 is less than 0
qml: TableViewSelection: index out of range
qml: TableViewSelection: index out of range
Model size of -31 is less than 0

Now the question is why cura crashes the system, when it runs without the debuger but not if it is running with the VS debugger?!

[smartavionics]

That's interesting info, so it doesn't look like the problem is the old FMA3 Ryzen bug.

[Skybeat]

Now the crash was there again (with debugger running) after nearly a hour. :-(

[nallath]

This is usually the case for race conditions. Attaching a debugger will make things slower and thus change the behavior.

[smartavionics]

I really don't have any idea of what's causing this crash but I had this mad idea that it would be worth seeing if a 32 bit version behaves the same so could some people please try it out. You can find it at the normal place, https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0. Obviously, it won't run as quick as a 64 bit release but if it doesn't lock up the machine at least it would be better than nothing.

[Skybeat]

I really don't have any idea of what's causing this crash but I had this mad idea that it would be worth seeing if a 32 bit version behaves the same so could some people please try it out. You can find it at the normal place, https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0. Obviously, it won't run as quick as a 64 bit release but if it doesn't lock up the machine at least it would be better than nothing.

Thank you,
I will give it a try and come back with a feedback ;-)

[Derrin616]

My pc also randomly crasht this evening its the same crash i get with Cura i needed to turn off power supply. But i didn’t used Cura so what caused it to crash that hard

[Skybeat]

I really don't have any idea of what's causing this crash but I had this mad idea that it would be worth seeing if a 32 bit version behaves the same so could some people please try it out. You can find it at the normal place, https://www.dropbox.com/sh/s43vqzmi4d2bqe2/AAADdYdSu9iwcKa0Knqgurm4a?dl=0. Obviously, it won't run as quick as a 64 bit release but if it doesn't lock up the machine at least it would be better than nothing.

Sorry bad i have bad news, with the 32bit version the crash happens also

[smartavionics]

Sorry bad i have bad news, with the 32bit version the crash happens also

Thanks for taking the time to try it out. Well, that's me out of ideas for the moment.

[Ghostkeeper]

@Skybeat could you try disabling C States in your motherboard's BIOS?

[Skybeat]

@Skybeat could you try disabling C States in your motherboard's BIOS?

Oh I forgot to do that. I will do this today and then I will inform you about the result

[Derrin616]

Hey,

Again my pc randomly crashed again with the hard way like it happends with Cura!

I used like 2 hrs before the crash Cura for like 3 min and closed it.

I filmed the crash this time
https://youtu.be/asogQRVeSFk

[CWempe]

fyi:

I had the same issue a few times the last two days.

Screen goes black and I had to restart the system or it restarted itself.

I am new to 3d printing and don't have much experience with Cura, yet.
I used 4.4.x for a few month and after updating to 4.5.0 this issue happened.
Maybe I am using Cura different now, because I put more effort in in the last days.

I would also like to pint out my system is a Intel Core i5-6500 with onboard graphics only.

I will report, if I get more usefull information in the next days.

[Demadig]

Hey,

I have the same issue there in the lastest Cura.
Also with a Ryzen and an Asus MB.
It's pretty hard to get the gcode files and the settings done in that short period of time,
before the PC shuts down. It's really a race against time there^^

Btw. thank you for the Support here, and hopefully there is a Solution for this problem in the near future.

[Derrin616]

i have an idea its fixed for me. Im using Cura alot and i don't have those crashes anymore for over a month now

If i use Cura most times i use it a couple of minutes not just slice and quit

[saul095]

@Derrin616 you have a solution to this problem? what is it

[Derrin616]

@saul095 I didn't said i got a solution but i mentioned that i use Cura alot now and it dind't crash anymore so thats weird. Im using Cura like everyday and it didn't crashed in a month /1,5 months

[saul095]

My GPU still crashes, crashes more often when I have 2 monitors set up.
AMD Ryzen 5 2600 CPU
Radeon RX 570 series GPU

[Saegusae]

This issue persists on my installation of Cura 4.6.1,

AMD Ryzen 3900x (Upgraded from 2600, still had the same issue)
ASUS x470 Prime Pro Motherboard
RTX2080 Graphics card
64GB 3200MHz ram

The entire computer crashes and hard reboots (no blue screen, no error message) only when Cura has been running for a few minutes. 100% reproduction rate

[KuroCanidae]

The problem is still occuring for me with Cura ver. 4.6.1, and a clean install.

AMD Ryzen 2700x
Asus Rog Strix X470-F motherboard
SAPPHIRE Radeon RX Vega 64 graphics card
Corsair Vengeance LPX 16GB ram

My computer hard crashes, with no warning, or error message after Cura has been running for a while. It stays black with the components running, but responds to no inputs from the mouse and or keyboard. I must physically unplug the power supply in order to reboot the computer. Does this only when Cura is running, and I am able to consistently reproduce the problem.

[CWempe]

For the record.
I had no issues since I last posted here. (1,5 months ago)

[Demadig]

Me too.
Since I use Cura 4.5.0 I had no issues what so ever.
Used the program for 15 min. without any crashes.

[fieldOfView]

@CWempe, @Demadig, since not much was changed to fix this on the Cura side (because none of the developers has access to hardware that reproduces the issue) it would be interesting to know what other changes you made to your system (driver updates etc).

[CWempe]

I only had the issue for two days.
I don't know what changed. If anything changed at all.

[Ghostkeeper]

I would still like to know if disabling C states in the motherboard resolves the issue. Is there anyone that can try?

[goddamnmaddog]

I have ASUS Prime X470 with Ryzen 2700X and encountered the problem very often.
I have this problem since Cura 4.0 something (But thinking about it, I switched to a Ryzen back then)

Now I was using 4.6.1 and it crashed.

I got in by BIOS now and disabled C Stats for CPU. Hopefully this works.

What kind of output do you need? What can I do?

EDIT: Now it crashed again. (about 1h of program running with stl loaded)

[Ghostkeeper]

Aww. They say here and here that disabling global C states, or at least C6, works to prevent the issue.

Here are some newer discussions on the AMD forums about this issue:

• https://community.amd.com/thread/239990 (seems to point out RAM clock speed as the problem)
• https://community.amd.com/thread/244440 (again the link with the AI Suite software, but also lots of discussions about RAM).

[JTensai]

I'm also running into this problem. I'm on a Ryzen 3 3900x. Crashes in the middle of use as well as in the background. No logs whatsoever, just black screen reboot. No high RAM issues or temperature issues. Would love to get this fixed as I have gotten quite fond of Cura.

[mahtDFR]

@JTensai are you able to try 4.6.1? Some Ryzen issues around this have been resolved since version 4.0.0 beta.

[JTensai]

@mahtDFR yes, this is occurring on 4.6.1

[mahtDFR]

We'll need a log from you to be able to try to debug things.
https://github.com/Ultimaker/Cura#logging-issues

[TheMaskedDeveloper]

I'm also running into this problem. I'm on a Ryzen 3 3900x. Crashes in the middle of use as well as in the background. No logs whatsoever, just black screen reboot. No high RAM issues or temperature issues. Would love to get this fixed as I have gotten quite fond of Cura.

On an Asus mainboard? (Luckily it disappeared on my system after uninstalling Ai-Suite,
although it was not the solution for everyone.)

[mahtDFR]

@JTensai, are all your drivers up to date? This was a thing.

[KuroCanidae]

@mahtDFR All my drivers are up to date, and it's occurring even more often now. Yesterday, I had it up for a mere 15 minutes, before it crashed my computer, _while_ I was using it. Really frustrating since Cura is really awesome.

[JTensai]

@TheMaskedDeveloper yes, it is on an Asus ROG Strix X470-F Gaming motherboard.

@mahtDFR All my drivers are up to date in windows update, and graphics card (GTX 2070 Super) is always up to date. I'll look at logging

[KuroCanidae]

Also here is the requested info:

cura.log
DxDiag.txt

[Ghostkeeper]

We'll need a log from you to be able to try to debug things.

There are no logs for this crash because the CPU locks up rather than Cura. The CPU is not able to compute anything any more, including the processing of logs.

The only possible avenue I know now for this issue is to adjust your RAM clock speed to something that is supported by the motherboard and the CPU. But again we can only go by what we find online.

[XDGFX]

I'm having an identical issue

• 3700X
• Asus B450-F
• Cura 4.6

I was logging my system before one of the crashes using HWINFO, I've attached the file. I looked through all the sensors but didn't notice anything abnormal (I know someone mentioned RAM usage before). Not sure if it's helpful but maybe it can reveal something.

HWINFO.zip

[disneytoy]

REPORT:

3700x Asus Prime x470. Cura 4.6.1 Win 10. By accident I left Cura on after I sliced. Its a day later and no crash. I haven't updated bios. Nothing really changed accept 4.6.1.

My usual work around was to quickly slice and quit. But it is Idle in the BG fine.

[Hookedon3D]

I am in the same boat! After reading the comments on here I did a clean install of windows 10 pro x64 and disabled C state in the bios and still the same thing. However, my issue is I can't open cura it just freezes up on my second monitor. I am using cura 4.6.1 and here is my specs

Ryzen 9 3900x

32gb memory

XFX RX 580

MSI Prestige X570 Creator Mobo

If I open cura on my main display it works but if I moved to my second display it just freezes. I've had the same issue with amd ryzen master. So, at this point I am not sure what more I can do as I have replaced most of my components. Thanks in advance!

[fieldOfView]

@Hookedon3D: that's not the issue we're discussing here, so any fixes proposed here will likely not work for you.

[Razorlights]

Hi all, know this is a relatively old forum and maybe this has been resolved already, but I have found something that works for me!

Ryzen 2600X
ASUS X470 Prime-Pro
GTX 1660 Super
16GB DDR4 3000Mhz
Windows 10 Home
Cura 15.04.3 (Win 8 compatibility)

So I was reading about people's thoughts on the CPU load and disabling C state, this doesn't seem an option in my Asus BIOS.
However there is something similar that works for me, I enabled all 4 cores in the BIOS and not crashed so far over 48 hours of use over a few weeks, when usually I had the same problem every hour or so, however I am using an older stable version (in my opinion) of Cura and using windows 8 compatibility, so maybe all these factors together are a win for my system. Hope this helps someone!

[Razorlights]

This issue persists on my installation of Cura 4.6.1,

AMD Ryzen 3900x (Upgraded from 2600, still had the same issue)
ASUS x470 Prime Pro Motherboard
RTX2080 Graphics card
64GB 3200MHz ram

The entire computer crashes and hard reboots (no blue screen, no error message) only when Cura has been running for a few minutes. 100% reproduction rate

Have a look at my comment above and see if this help you!

[Hookedon3D]

I'll try windows 8 compatibility and see if thats going to resolve the issue.

[disneytoy]

Cura 4.6.1 Win 10 Asus prime x470. 32gb ram, x3700. For what ever reason no more crashes. I haven't even updated bios.

It is sometimes open in the background for days, no more issues.

[Ghostkeeper]

@Hookedon3D see https://github.com/Ultimaker/Cura/issues/4427. You have different symptoms and a different cause than the rest here.

@disneytoy Could it have been a CPU driver update, maybe?

[zachcheatham]

This started happening more frequently than usual. I'm not able to have Cura 4.6.1 open for more than 10 minutes before my entire PC resets. Asus ROG x470-F and a Ryzen 3800X. Windows 10 recently updated to the 2004 release.

Prior, the issue had seemed to have gone away for months.

[jaydenrussell]

I'm having the same issues, pc is on all time and 0 crashes unless I leave Cura 4.6.1 open or using it. Windows Event Viewer shows nothing since this doesn't even BSOD, just resets but doesn't actually reset. Usually power cycle will fix.

Ryzen 5 2600
Asus Prime X470-PRO
32GB XMP profile
Win 10 2004 release

Run with latest AMD chipset drivers and no Asus/Amd utilities.

[spiritedfang]

Same issues with 4.6.1...

Ryzen 5 3600X, not overclocked with turbo turned off
Asus Prime X470-PRO
32GB RAM, not overclocked with base profile
NVIDIA RTX 2070 Super, again, not overclocked
Win 10 2004 release

Nothing but the most up-to-date drivers. Fresh Windows install.

[Thisismydigitalself]

Cura keeps crashing the whole PC without BSOD. usually when i zoom in on my models. happens regardless of model's complexity. Win10/64, NV Geforce 750TI, Cura 4.4.1 (Had to revert from 4.6 which kept changing nozzle size from 1.75 to 2.85) - All latest drivers and updates.

[ppatches24]

Its still happening
Asus mb, 2080 ti, win 10, ryzen 9 3900X. Everything is up to date.

[Ghostkeeper]

Here's another thing you can try: https://community.amd.com/thread/230269#comment-2933613

The general theme on that thread and this one lately seems to be that any software that monitors CPU temperatures or fan speeds needs to be disabled, such as Corsair iCue, F-Stream Tuning, Aura, AI Suite, etc.
Cura doesn't monitor any computer resources like that. Unless maybe the USB ports count? This can be tested by disabling the USB printing plug-in.

[disneytoy]

Just curious,

Anyone else with my same hardware:

Ryzen 3700X
ASUS Prime x470
32GB RAM
Nvidia GTX 1650 Super
Win 10

Because I had this problem, but it fixed itself. I can leave 4.6.1 running in the background for days, no more crashes. Maybe it was an auto driver update for my video card?

[pjrt]

Same here. This bug seems to be pretty old, still no solution?

AMD Ryzen 7 2700x 8 Cores
16GB RAM
NVidia GTX 1070
Win 10 Pro

[Razorlights]

Success (almost), less crashes when I installed without support for Adruino!
Ryzen 2600x, ASUS mobo, GTX 1660 Super.

[Ghostkeeper]

This bug seems to be pretty old, still no solution?

Bug reports are still coming in on the AMD support forums so I think they don't have a solution yet.

[spiritedfang]

Success (almost), less crashes when I installed without support for Adruino!
Ryzen 2600x, ASUS mobo, GTX 1660 Super.

Less crashes or no crashes? I'm also still looking for a way around this. I just haven't been using Cura since as a precaution.

[spiritedfang]

I noticed a pattern here... we're all using NVIDIA graphics cards (unless anyone can confirm a case using an RX card). I created a new thread in NVIDIA's support forums: https://www.nvidia.com/en-us/geforce/forums/geforce-graphics-cards/5/391498/consistent-crashes-from-using-ultimaker-cura/. Hopefully they can get back to us regarding if this is a driver issue or not. /shrug

Edit: This also happens on RX cards (see below)

[ppatches24]

I noticed a pattern here... we're all using NVIDIA graphics cards (unless anyone can confirm a case using an RX card). I created a new thread in NVIDIA's support forums: https://www.nvidia.com/en-us/geforce/forums/geforce-graphics-cards/5/391498/consistent-crashes-from-using-ultimaker-cura/. Hopefully they can get back to us regarding if this is a driver issue or not. /shrug

I was about to open a ticket with Asus because I thought we all had Asus boards. This is clearly not just a cura issue there is some other deeper problem going on here.

And cura 4.6.1 is still crashing on my system. I hop on my other i7 PC 0 problems. Opening up tickets with some of these hardware manufacturers are I think the next step.

[spiritedfang]

I noticed a pattern here... we're all using NVIDIA graphics cards (unless anyone can confirm a case using an RX card). I created a new thread in NVIDIA's support forums: https://www.nvidia.com/en-us/geforce/forums/geforce-graphics-cards/5/391498/consistent-crashes-from-using-ultimaker-cura/. Hopefully they can get back to us regarding if this is a driver issue or not. /shrug

I was about to open a ticket with Asus because I thought we all had Asus boards. This is clearly not just a cura issue there is some other deeper problem going on here.

And cura 4.6.1 is still crashing on my system. I hop on my other i7 PC 0 problems. Opening up tickets with some of these hardware manufacturers are I think the next step.

I tried with ASUS and their support basically told me it could be anything. They asked me to rule out the graphics, memory, and CPU first before contacting them... which was a fat load of good. From what I know about the AMD microcode though, it should be relatively the same across boards. It's possible that ASUS delivered a bad microcode version, though I really don't know. Try making a support thread with AMD. Their support rocks, and they'll actually try to reproduce the problem on their side if you give them all the hardware details. Loop us in if you make progress on that front.

[RagabashLOE]

I noticed a pattern here... we're all using NVIDIA graphics cards (unless anyone can confirm a case using an RX card). I created a new thread in NVIDIA's support forums: https://www.nvidia.com/en-us/geforce/forums/geforce-graphics-cards/5/391498/consistent-crashes-from-using-ultimaker-cura/. Hopefully they can get back to us regarding if this is a driver issue or not. /shrug

I can confirm it's not restricted to NVIDIA cards. I have the same issue on Radeon RX 580, Ryzen 5 2600, Asus Prime B450-Plus.

[TheMaskedDeveloper]

As I remember nearly everyone with this kind of issue is using an ASUS board.
As mentioned before, my issues disappeared after uninstalling the AI suite. Others had no luck with this solution (or have never installed / used the AI Suite).
May be there are some circumstances that are affected either by the AI Suite or some BIOS settings as they both can tweak the same parameters. (Try using BIOS defaults or disable any kind of OCs /CPU optimization related stuff in the BIOS)
Sure enough there are a couple of users with similar issues - but i think they have nothing in common with "our" issue here.

[KuroCanidae]

I noticed a pattern here... we're all using NVIDIA graphics cards (unless anyone can confirm a case using an RX card). I created a new thread in NVIDIA's support forums: https://www.nvidia.com/en-us/geforce/forums/geforce-graphics-cards/5/391498/consistent-crashes-from-using-ultimaker-cura/. Hopefully they can get back to us regarding if this is a driver issue or not. /shrug

I'm using a RX Vega 64, as well as a ROG Strix X470-F board (pretty much a full AMD system), and to this day am still having the issue. Also I can confirm it only happens with Cura as any other slicer software works with zero issue, even if left open all day.

[spiritedfang]

Ah, thanks for the confirmations. So that leaves the processor / chipset and motherboard. I don't have AI Suite installed on my computer, and I tried disabling all of the AI stuff in the BIOS and that didn't help. Still wondering what could be causing this.

[lillalysmasken3]

I seem to have the same issue. Thaught i had solved it by disabling one drive and google drive on my computer but sadly no.
Have run previous versions of cura (currently running 4.6.1) without issue.

Running a ryzen 5 2xxx. Not overclocked.
Nvidea 1070ti. not overclocked.
Asus b450 mothervoard with Corsair 3GHz ddr4 ram.
Samsung 950 M.2 ssd.

The time it takes to crash seems pseudorandom, from 1-15 minutes (haven't actually timed it).

[rayjd1650]

Ryzen 7 3700X
Sapphire RX 5700XT
Asus Prime X370 Pro

I am using 4.6.1 and get the crash probably once a week.

I do not have any of the AI Suite software installed

Edit: I _do_ have iCUE, so I'm guessing that's the issue

[goddamnmaddog]

Funny, I don't know if this helps, I can't explain it and for me it is confusing:

I Installed Virtualbox and created a linux image, booted it, installed cura, sliced something, and BAM!

The same blackscreen as I had on windows.

I thought a virtual machine is to protect my computer from this happening.

[spiritedfang]

Funny, I don't know if this helps, I can't explain it and for me it is confusing:

I Installed Virtualbox and created a linux image, booted it, installed cura, sliced something, and BAM!

The same blackscreen as I had on windows.

I thought a virtual machine is to protect my computer from this happening.

Did you have AMD-V enabled?

[goddamnmaddog]

Funny, I don't know if this helps, I can't explain it and for me it is confusing:
I Installed Virtualbox and created a linux image, booted it, installed cura, sliced something, and BAM!
The same blackscreen as I had on windows.
I thought a virtual machine is to protect my computer from this happening.

Did you have AMD-V enabled?

I don't know the exact name, I turned on hardware virtualization in the UEFI, because otherwise, I couldn't install the Linux image. Is this what AMD-V could be, or is it something I have to setup in Virtualbox?

Since I deleted the VM, I could retry with new VM? Would this help?

[danym21]

Hello,
looks like I have the same issue,
AMD Ryzen 7 2700X
16GB Ram
Win10 2004
Asus Prime X470-Pro
Asus ROG-STRIX-RTX2080-S-O8G-GAMING
hard rebooting/black screen no errors in the logs only Event (41) that the system was unexpected shutdown.
is there a option in cura to get a debug log so that we can see what cura is starting to do when it happens?

edit: also in Cura 4.7.1

[aahhhlan]

Same issue
Ryzen 5 2600X
32GB ram
win 10
ASUS ROG STRIX B450-F GAMING

[Ghostkeeper]

is there a option in cura to get a debug log so that we can see what cura is starting to do when it happens?

Cura by default logs the maximum available log level in its resource folder in %APPDATA%\cura\cura.log.
However in this case the problem is that the CPU stops working. In that case the computer won't be able to process any log entries any more either.
From what we've seen earlier in this thread, the problem seems to occur most often when ramping down power usage from the CPU after having completed a slice.

[merpsquirrel]

Might have figured this one out. I was getting a black screen and crashing in Ryzen 3800 and gtx1080. I actually got the same failures in cura, slic3r, creality. I wanted to try to run it in VMware to test but couldn’t start vm due to amd Cpu virtualization being off in the Bios, then remembered that Amd-v is often used for graphic intensive workloads. So turned it on and skipped VMware and just tried cura again bam no problems. All the others worked now too. If you have a Ryzen turn on Amd-v or cpu virtualization in the bios. Often times intel has theirs on by default or many cpus just don’t have it. I think the software sees it has it and try’s to use it but amd defaults to off.

[JTensai]

On my board (ROG Strix x470-F Gaming) AMD-V is called "SVM (Secure Virtual Machine) mode" and it has always been enabled and I still run into the issue. It does seem to only occur after slicing.

[spiritedfang]

Might have figured this one out. I was getting a black screen and crashing in Ryzen 3800 and gtx1080. I actually got the same failures in cura, slic3r, creality. I wanted to try to run it in VMware to test but couldn’t start vm due to amd Cpu virtualization being off in the Bios, then remembered that Amd-v is often used for graphic intensive workloads. So turned it on and skipped VMware and just tried cura again bam no problems. All the others worked now too. If you have a Ryzen turn on Amd-v or cpu virtualization in the bios. Often times intel has theirs on by default or many cpus just don’t have it. I think the software sees it has it and try’s to use it but amd defaults to off.

Yep, I can debunk this as well. I've had virtualization on since the beginning. Good that you're thinking about the problem though.

[Firetop]

Happy to report that my issues have now been solved.

I had similar issues on my setup, would completely crash and reboot my workstation automatically after a few minutes with any of the CURA versions 4.0+ software started. (Did not need to cut power for it to restart my station, but I do have it set to restore last state when it dies in the bios.)

Also did not matter if I was printing or had a model loaded.

Uninstalling BOTH the Asus AURA and Corsair ICUE Software resolved the issues for me here.

F.Y.I; Using an ASUS motherboard and Ryzen 3800x

[belviranli]

Happy to report that my issues have now been solved.

I had similar issues on my setup, would completely crash and reboot my workstation automatically after a few minutes with any of the CURA versions 4.0+ software started. (Did not need to cut power for it to restart my station, but I do have it set to restore last state when it dies in the bios.)

Also did not matter if I was printing or had a model loaded.

Uninstalling BOTH the Asus AURA and Corsair ICUE Software resolved the issues for me here.

F.Y.I; Using an ASUS motherboard and Ryzen 3800x

Is it still OK, over the last 2 days?

[Firetop]

Happy to report that my issues have now been solved.
I had similar issues on my setup, would completely crash and reboot my workstation automatically after a few minutes with any of the CURA versions 4.0+ software started. (Did not need to cut power for it to restart my station, but I do have it set to restore last state when it dies in the bios.)
Also did not matter if I was printing or had a model loaded.
Uninstalling BOTH the Asus AURA and Corsair ICUE Software resolved the issues for me here.
F.Y.I; Using an ASUS motherboard and Ryzen 3800x

Is it still OK, over the last 2 days?

Yep! Since removing Corsair ICUE and Asus AURA, my system is completely stable using Windows 10 over the last 2 days. No reboots. No black screens or crashes.

I was able to upgrade from CURA 4.1 to 4.7.1 without issues and I'm now running the latest version of CURA and running prints over USB as long as 12 hours a time since with no issues.

Obviously, I now lost control of any of my system lights and LEDs with ICUE and Aura uninstalled. But I rather have a working 3D printer than strobing motherboard and cooling lights.

[belviranli]

Happy to report that my issues have now been solved.
I had similar issues on my setup, would completely crash and reboot my workstation automatically after a few minutes with any of the CURA versions 4.0+ software started. (Did not need to cut power for it to restart my station, but I do have it set to restore last state when it dies in the bios.)
Also did not matter if I was printing or had a model loaded.
Uninstalling BOTH the Asus AURA and Corsair ICUE Software resolved the issues for me here.
F.Y.I; Using an ASUS motherboard and Ryzen 3800x

Is it still OK, over the last 2 days?

Yep! Since removing Corsair ICUE and Asus AURA, my system is completely stable using Windows 10 over the last 2 days. No reboots. No black screens or crashes.

I was able to upgrade from CURA 4.1 to 4.7.1 without issues and I'm now running the latest version of CURA and running prints over US as long as 12 hours a time since with no issues.

Obviously, I now lost control of any of my system lights and LEDs with ICUE and Aura uninstalled. But I rather have a working 3D printer than strobing motherboard and cooling lights.

I had Aura installed but was not using it, because it was somehow not working anyways with my board.

Will report back in a day or two.

Thanks for the help.

[spiritedfang]

Happy to report that my issues have now been solved.
I had similar issues on my setup, would completely crash and reboot my workstation automatically after a few minutes with any of the CURA versions 4.0+ software started. (Did not need to cut power for it to restart my station, but I do have it set to restore last state when it dies in the bios.)
Also did not matter if I was printing or had a model loaded.
Uninstalling BOTH the Asus AURA and Corsair ICUE Software resolved the issues for me here.
F.Y.I; Using an ASUS motherboard and Ryzen 3800x

Is it still OK, over the last 2 days?

Yep! Since removing Corsair ICUE and Asus AURA, my system is completely stable using Windows 10 over the last 2 days. No reboots. No black screens or crashes.
I was able to upgrade from CURA 4.1 to 4.7.1 without issues and I'm now running the latest version of CURA and running prints over US as long as 12 hours a time since with no issues.
Obviously, I now lost control of any of my system lights and LEDs with ICUE and Aura uninstalled. But I rather have a working 3D printer than strobing motherboard and cooling lights.

I had Aura installed but was not using it, because it was somehow not working anyways with my board.

Will report back in a day or two.

Thanks for the help.

We already confirmed this doesn't solve the problem... but I uninstalled both again and tried with 4.7.1 to reconfirm.

It still crashes within a few minutes of keeping it loaded on a fresh install of Windows 10.

[belviranli]

Mine didn't crash for a day or 2, and again I needed to unplug to reset.

---

From: Spirited [e-mail]
Sent: Sunday, October 25, 2020 6:35:47 PM
To: Ultimaker/Cura [e-mail]
Cc: Mehmet Belviranli [e-mail]; Comment [e-mail]
Subject: [External] Re: [Ultimaker/Cura] [CURA 4.0.0 BETA] Black screen after 2 minutes with Ryzen 5 1600 and win10 (#5265)

Happy to report that my issues have now been solved.
I had similar issues on my setup, would completely crash and reboot my workstation automatically after a few minutes with any of the CURA versions 4.0+ software started. (Did not need to cut power for it to restart my station, but I do have it set to restore last state when it dies in the bios.)
Also did not matter if I was printing or had a model loaded.
Uninstalling BOTH the Asus AURA and Corsair ICUE Software resolved the issues for me here.
F.Y.I; Using an ASUS motherboard and Ryzen 3800x

Is it still OK, over the last 2 days?

Yep! Since removing Corsair ICUE and Asus AURA, my system is completely stable using Windows 10 over the last 2 days. No reboots. No black screens or crashes.
I was able to upgrade from CURA 4.1 to 4.7.1 without issues and I'm now running the latest version of CURA and running prints over US as long as 12 hours a time since with no issues.
Obviously, I now lost control of any of my system lights and LEDs with ICUE and Aura uninstalled. But I rather have a working 3D printer than strobing motherboard and cooling lights.

I had Aura installed but was not using it, because it was somehow not working anyways with my board.

Will report back in a day or two.

Thanks for the help.

We already confirmed this doesn't solve the problem... but I uninstalled both again and tried with 4.7.1 to reconfirm.

It still crashes within a few minutes of keeping it loaded on a fresh install of Windows 10.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/Ultimaker/Cura/issues/5265#issuecomment-716242356, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ANA5XTLYFZVZYGDV2XHHJBDSMS76HANCNFSM4GT63QFQ.

[Firetop]

Happy to report that my issues have now been solved.
I had similar issues on my setup, would completely crash and reboot my workstation automatically after a few minutes with any of the CURA versions 4.0+ software started. (Did not need to cut power for it to restart my station, but I do have it set to restore last state when it dies in the bios.)
Also did not matter if I was printing or had a model loaded.
Uninstalling BOTH the Asus AURA and Corsair ICUE Software resolved the issues for me here.
F.Y.I; Using an ASUS motherboard and Ryzen 3800x

Is it still OK, over the last 2 days?

Yep! Since removing Corsair ICUE and Asus AURA, my system is completely stable using Windows 10 over the last 2 days. No reboots. No black screens or crashes.
I was able to upgrade from CURA 4.1 to 4.7.1 without issues and I'm now running the latest version of CURA and running prints over US as long as 12 hours a time since with no issues.
Obviously, I now lost control of any of my system lights and LEDs with ICUE and Aura uninstalled. But I rather have a working 3D printer than strobing motherboard and cooling lights.

I had Aura installed but was not using it, because it was somehow not working anyways with my board.
Will report back in a day or two.
Thanks for the help.

We already confirmed this doesn't solve the problem... but I uninstalled both again and tried with 4.7.1 to reconfirm.

It still crashes within a few minutes of keeping it loaded on a fresh install of Windows 10.

Sounds like you have either another software installed doing a similar action as ASUS and ICUE, or an incompatibility that my system doesn't have. As again, I had similar issues above and my system still hasn't crashed over a week later.

Either way, everyone with the issue should have that listed software removed and not reinstall it, seeing it's a known issue.
Everyone should be working the issues down rather than up, I myself had 2 software's giving issues; so in total I had 2 issues on my system.

But it sounds like some of you have 3+ issues on your systems, and removing ICUE and ASUS isn't the only solution.

For hardware compatibilities sake, I have the following motherboard: ASUS Prime X370-Pro on BIOS Version 5220.
But we can instantly rule out a general "RYZEN" incompatibility as the OP lists it, as it does work on some Ryzen systems, such as my own and @merpsquirrel. The question now becomes "What's the difference?"

Here are some related BIOS Settings on my System for comparison:

Advanced\USB Configuration:
Legacy USB Support: Enabled
XHCI hand-off: Enabled

Advanced\Secure Boot:
Enabled
AMD fTPM Configuration: Discrete TPM

Advanced\AMD CPU Configurations:
PSS Support: Enabled
NX Mode: Enabled
SVM Mode: Enabled
SMT Mode: Enabled
Core Leveling Mode: Automatic

Ai Tweaker:
Ai Overclock Tuner: D.O.C.P Standard Profile

Boot\Boot Configuration:
Fast Boot: Enabled
Next Boot After AC Power Loss: Normal Boot

I recommend someone with the issue update their BIOS to the latest version and compare their settings with mine, identify any that are different and try one setting at a time. If none of those work than it's obviously not hardware compatibility more than an underlying software not yet identified.

If the system is a clean re-image with nothing else installed but CURA and has the issue, I highly recommend that person to list their hardware and BIOS version and compare the above settings to list and compare. :)

[merpsquirrel]

So to add, I was the one that enabled AMD-V is called SVM (Secure Virtual Machine) mode and it fixed my issue, I have been running issue free for weeks with 3800x and 1080 GTX. If its just overcoming some issue for a while I do actually have a gigabyte board and other devices with Aura and ICUE running. Have not had issues with these still running. But Possibly disabling these might fix the issue as well. So I think either the issue is virtualization or ICUE/AURA software. Enable AMD-V and disable or remove Software for monitoring/LED control seems would likely be root cause and fix.

[Firetop]

So to add, I was the one that enabled AMD-V is called SVM (Secure Virtual Machine) mode and it fixed my issue, I have been running issue free for weeks with 3800x and 1080 GTX. If its just overcoming some issue for a while I do actually have a gigabyte board and other devices with Aura and ICUE running. Have not had issues with these still running. But Possibly disabling these might fix the issue as well. So I think either the issue is virtualization or ICUE/AURA software. Enable AMD-V and disable or remove Software for monitoring/LED control seems would likely be root cause and fix.

Agreed, they should have their BIOS updated, and then compare their related BIOS settings above to make sure, as well as any of the obvious software removed for testing reasons.

[pjrt]

Success! I uninstalled Corsair iCue (my keyboard was acting up anyways) and restarted. Managed to leave Cura running over night. Woke up to my PC still working.

[Ghostkeeper]

But we can instantly rule out a general "RYZEN" incompatibility as the OP lists it, as it does work on some Ryzen systems, such as my own and @merpsquirrel. The question now becomes "What's the difference?"

Indeed. I have Ryzen too. It has been determined at the very least that it only occurs with Ryzen + ASUS motherboards, so I'll change the title to reflect that.

[belviranli]

I also confirm that I am having this issue with a 2700x+Asus Rog Strix B450-F board.

[spiritedfang]

Hi all! Just wanted to reconfirm that uninstalling iCue / Aura does not work.

I had them both uninstalled with the latest AMD chipset drivers from October 2020 and ASUS BIOS update from August 2020. With nothing running, all overclocking and performance boosting disabled, all virtualization disabled, and all RBG settings disabled, I was able to invoke a kernel power failure within minutes of Cura running in the background.

I created a new ASUS ticket and they have collected my motherboard information to pass to the engineers. Please, if you're having this issue, create a new ASUS support ticket and reference case number N201077865. Say you're having the same problem and would like to fill out a motherboard feedback form. Hopefully they'll figure out what's going on once and for all. Thanks!

[Firetop]

all virtualization disabled

Try turning it on as mentioned in the other comments above :) Compare your BIOS settings to mine which is proven working.

[spiritedfang]

all virtualization disabled

Try turning it on as mentioned in the other comments above :) Compare your BIOS settings to mine which is proven working.

I normally have all of those settings enabled. Sorry - that wasn't clear.

[TYTYTYTY1]

Being honest, I've just lived to accept it at this point. Been happening for three years now with Ryzen 1600x and Asus B350-F, regardless of cura version, bios version, driver, windows update, or barometric pressure.

Just got a new 2700X today and within 5 minutes it happened lmao. C'est la Vie I guess.

Tried everything from aura to power settings to icue to putting a spoon under my pillows and crossing my fingers in my sleep.

Anecdotally, I notice that it really only happens when you expect it to happen. In a weird twist, if I don't expect it to happen, it won't crash. If I think about it, it crashes in the next few minutes. I like to think of it as the little spirit that reminds me of my place in this world. Shit makes no fucking sense but i'm glad I'm not still alone in figuring this shit out.

[spiritedfang]

Being honest, I've just lived to accept it at this point. Been happening for three years now with Ryzen 1600x and Asus B350-F, regardless of cura version, bios version, driver, windows update, or barometric pressure.

Just got a new 2700X today and within 5 minutes it happened lmao. C'est la Vie I guess.

Tried everything from aura to power settings to icue to putting a spoon under my pillows and crossing my fingers in my sleep.

Anecdotally, I notice that it really only happens when you expect it to happen. In a weird twist, if I don't expect it to happen, it won't crash. If I think about it, it crashes in the next few minutes. I like to think of it as the little spirit that reminds me of my place in this world. Shit makes no fucking sense but i'm glad I'm not still alone in figuring this shit out.

I'm in a pretty civil support ticket with ASUS over the matter. Conversation is good, but not promising. If you create a support ticket with ASUS (and please do), reference my case number: N200718349. Even if we flood them with a few tickets, those long-standing open tickets start to become really loud. Off topic: I knew I should never have tried ASUS again after loving my last MSI board.

[derBalou]

Had the same issue on my ASUS ROG Strix B350F with the Ryzen 5 1600.
Fixed it by enabling the "Global C-State Control" Setting in my BIOS. The default value is "Auto" which seems to mean the same as "Disabled" in this case.
Seems to work for now...

[GAQ1961]

I would like to thank fanfan7110 for starting this thread and keeping me sane...
I thought I was going mad with frustration at my system crashing... I checked power module - motherboard - processor - memory - etc etc... After all, NOTHING to do with software could crash a PC so hard you had to switch off at the mains to get it to reboot - - - Could it ?
Then I noticed a pattern... I leave my PC on permanently - and it could run quietly for week after week without a glitch - unless I played with Cura.
My 1700X became a 2700X - No difference at all. My Motherboard became the ASUS prime X470 Pro. No difference at all...
It's a shame I quite like Cura, but now I have to use PrusaSlic3r. This program doesn't cause any problems - Just that I don't like the supports it generates.
I cannot work out how sometimes I could play with Cura for a couple of hours, other times it could be a couple of minutes !
This PC's spec's - Just for the record.
Ryzen 2700X over-clocked to 4GHz and water cooled. (The Ryzen 1700X used to crash as well)
ASUS Prime X470 Pro (Earlier ASUS board changed with the Processor)
nVidia Geforce GTX 1070 (Never changed, I could see the pattern now ! )
32 Gb Memory
M2 slot memory is a Samsung - as is the secondary 'Working file' SSD. (Plus old fashioned spinny disc archive drive)
I do actually have both corsair wired keyboard and mouse - I noted some posts in the thread hinted at possible conflicts with iCue - but this didn't solve anything for me.
I've been building PC's since 1995 (Pentium running windows '95)...
I have NEVER before experienced a crash so complete that wasn't hardware related... But here we are.
This PC was built as it could edit 4K videos better than my old one - So at least it performs its primary goal !
I didn't waste any money on Cura, so I can't really complain as it's free !
But if anyone actually nails the problem and bottoms out the actual cause as to why Cura/Ryzen/ASUS can't play nicely together, then I'm all ears...

[MrGibbs44]

This has been affecting me too the last week! Only new software has been Cura 4.8 and Creality Slicer!

Symptom:
PC freezes/crashes, screen going black, cannot hold power in to turn off, only way to resolve is pulling power out or disconnecting at wall, then turning back on.

Nothing appears in event viewer, no logs, just crashing.

Setup
Windows 10
Ryzen 2600X
GTX 1060 6GB
32GB
ASUS-470 MB with Aura Sync + iCue

Definitely sounds to me like some sort of Motherboard/RAM issue with the way Cura slices the models. Likely causes some sort of memory leak causing power fluc somwhere, but without some serious kit to troubleshoot hard to say.

My one and only solution/workaround currently is turning off my PC between slices/prints

[GAQ1961]

Hi MrGibbs,
I reckon you'll find no issues with Prusa Slic3r. (I certainly haven't, and it's a decent program)
I don't believe you have to do any actual slicing with Cura for it to become an issue with the PC, simply having a model sitting on the bed seems to be enough to crash the system.
Anecdotal evidence would suggest that Ryzen/Asus/nVidia/iCue (As both you and I share) would be the worst scenario for crashes !
I have found that if I reboot the PC following a use of Cura (If I get in quick before it crashes !) then I should be fine and feel like I've got away with such folly of use ! ie I agree with you that if you keep your time with Cura short and follow up with a reboot every time, then you can indeed probably get some decent gcode from Cura... I confess this method has been employed by me, particularly on a model requiring supports.
I just find (Purely from my own evidence/practice only) that Cura supports work better for me, hence I've continued to try each new iteration of the program in the vain hope that something will have improved in the newer version.
Alas, this has yet to be found to be true.

[spiritedfang]

I did it. I found the solution: I'm throwing my ASUS motherboard in the trash.

[MrGibbs44]

Got to admit, as an IT Engineer for full-time job, I've never come across such a random issue as this. Where a piece of simple software completely overwhelms the hardware with no logs stored or acknowledged anyhere.

If anything, this could be used for malicious purposes to potential brick PC's if pulled apart correctly.

I've not really delved to deep into the software, but it probably uses 'hardware acceleration' I'll see if this can be disabled.

Also in terms of using Prusa etc, I prefer Cura as it has a lot more options with ease of access, and additional benefits such as Tree supports, calculating estimated costs etc.

[Ghostkeeper]

I've not really delved to deep into the software, but it probably uses 'hardware acceleration' I'll see if this can be disabled.

"Hardware acceleration" is a marketeer's terminology for using the GPU. Cura uses OpenGL for rendering which by default would select your GPU. This can normally be changed by your operating system if you have other devices that implement OpenGL (like some Intel chips).

As far as we know, GPU rendering has nothing to do with this issue though. The issue reports so far seem to point out that the switching between high CPU workload and low CPU workload causes a bug in the ASUS motherboard with it not supporting a power-save state that the CPU instructs. Maybe some other applications don't have the same power usage patterns (not using all cores due to more thread switching?) and thus are not affected. There are links up in this thread with issue reports at ASUS and AMD for various games and software.

Indeed no userspace application should be able to cause this sort of lock-up. If you ask me, this is a bug in your motherboard's firmware that provides an attack vector for malicious software.

[MrGibbs44]

Indeed no userspace application should be able to cause this sort of lock-up. If you ask me, this is a bug in your motherboard's firmware that provides an attack vector for malicious software.

Well I'm upgrading to a Asus-X570 next month and Ryzen 3600X, so I guess we'll see if it stops then

[GAQ1961]

Hi MrGibbs,
I would hold back on that upgrade if Cura is imortant to you !
After all - I've witnessed this problem with 1700X / ASUS board and it followed me to the 2700X and ASUS X470...
I would not be so sure that upping these to the 3600 and 570 would improve matters.
...
As for multi core and 'Hardware acceleration' utilising the GPU (In my case the nVidia GTX 1070 8Gb)
I have other programs that use this feature without issue... Cyberlink's PowerDirector video editing software to name one example... So why the issue with Cura ?
...
To 'Spiritedfang', Whilst I would find it hard to justify the outlay simply in order to use a program that's supplied as freeware - I would be most interested to hear what happens if you do finally switch motherboards and keep everything else constant !

[GAQ1961]

I am fortunate.
My better half has passed down to me her 'Old' 17inch screen i7 laptop.
OK, it can't match my desktop for any other program I run. Indeed when Cura's not looking and I use it to slice a model before the system hangs, the laptop is far slower to slice as well...
But... If I consider how long the total process from 'slice' to 'finish print' takes - then the total delay is minimal.
If I need to use Cura - I can play with it on the laptop.

[MrGibbs44]

Hi MrGibbs,
I would hold back on that upgrade if Cura is important to you !

It's fine, just decided to run it from a spare laptop I have in the garage for now, no drama :)

To be fair on my PC too it's fine, the crash happens randomly hours after use, never whilst I need it. Just rebooting for now after each large slice just in-case, but just didn't want any damage to my components.