search

Ultimaker / Cura

3D printer / slicing GUI built on top of the Uranium framework
GNU Lesser General Public License v3.0
6.04k stars 2.06k forks source link

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

Open fanfan7110 opened 5 years ago

fanfan7110 commented 5 years ago

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

barthelby commented 4 years ago

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

smartavionics commented 4 years ago

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 commented 4 years ago

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

janrg commented 4 years ago

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

FluffyTheWalrus commented 4 years ago

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

smartavionics commented 4 years ago

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 commented 4 years ago

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

FluffyTheWalrus commented 4 years ago

Will use Ubuntu

smartavionics commented 4 years ago

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

FluffyTheWalrus commented 4 years ago

No crashes on Linux same hardware

sipos84 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

Ghostkeeper commented 4 years ago

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 commented 4 years ago

@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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

Ninnog43 commented 4 years ago

@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 commented 4 years ago

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 commented 4 years ago

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

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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.

Derrin616 commented 4 years ago

But who makes Software without a log folder?

fieldOfView commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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.