[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: Because this issue has gotten some traction and is quite a lot of information to dig through, here is a summary of what has been said so far, in Q&A format.

What are the symptoms of this problem? The CPU freezes, and as result the screen goes black, sound stops and nothing responds any more, not even the power button of the computer.

When does it occur? When using the combination of any Ryzen CPU together with any ASUS motherboard. It has so far only been seen on Windows. It seems to have started with motherboard drivers around the end of 2018.

Other hardware doesn't seem to matter. There is no discernible pattern of usage in Cura that triggers this.

What is the underlying cause? Nobody truly knows. However most sources online point at a communication problem between the CPU and motherboard about CPU power states. Apparently the CPU instructs the motherboard to reduce the power intake when Cura is idle, and the motherboard doesn't understand this. However the CPU decides this based on its own internal predictions given by the operating system, not by Cura's instructions.

Is only Cura affected? No, a number of applications and games have reported this issue. Cura seems to get the issue quite frequently for some people (after a couple of minutes) but quite rarely for others (every couple of weeks of daily usage) and for some people never even if they have the broken combination of hardware in their computer.

With which Cura version did this issue start? As far as we know, all Cura versions have this issue. It has been reported as far back as 2.3.

Is Ultimaker going to fix this issue? If there is something we can change we'd gladly do it, but at this moment nobody knows a solution, not even ASUS or AMD. ASUS and AMD seem to be blaming each other on who is at fault here. From Cura's perspective, we're just executing Python and C++ code. No single application should be able to crash the whole CPU; that would be a massive security issue. So there is no single instruction you can find in Cura or its source code that causes this issue, making this a hard problem to fix even if the hardware frequently reproduces the issue. If we hear of something that can be done we'll be sure to merge it and share the solution with ASUS (who seems to be the main culprit, more than AMD).

Are there any known workarounds? People have reported the following workarounds with varying degrees of success:

• Change the computer's power settings to "performance" rather than "power saving".
• Run Cura in a Virtual Machine. A Linux virtual machine seems to prevent the issue 100%, but is a hassle.
• Run something else in the background that uses 100% CPU power, such as a video encoding or just a spin script.
• Disable C-states in the BIOS settings (the screen before Windows starts).
• Uninstall ASUS monitoring software "AI Suite" and "AURA".
• Uninstall the Arduino drivers (or don't install them when Cura gets installed). This prevents printing via USB cable from Cura, or disable the USB printing plug-in (see here for instructions if Cura can't be started at all).
• RMA the CPU. Sometimes a new CPU doesn't have the issue, apparently, even if it's the same model.

(Last update: 2022-1-17)

[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.