search

Ultimaker / Cura

3D printer / slicing GUI built on top of the Uranium framework
GNU Lesser General Public License v3.0
6.07k 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

Ghostkeeper 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?

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

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

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

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

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

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

Rodriges-MkII commented 4 years ago

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

Ghostkeeper commented 4 years ago

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

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

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

Skybeat commented 4 years ago

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

nallath commented 4 years ago

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

smartavionics commented 4 years ago

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

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

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

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

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

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

Skybeat commented 4 years ago

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

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

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

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

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

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

Derrin616 commented 4 years ago

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

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

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

KuroChimera commented 4 years ago

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

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

Demadig commented 4 years ago

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

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

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

Ghostkeeper commented 4 years ago

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

goddamnmaddog commented 4 years ago

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

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:

JTensai commented 4 years ago

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

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

JTensai commented 4 years ago

@mahtDFR yes, this is occurring on 4.6.1

mahtDFR commented 4 years ago

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

TheMaskedDeveloper commented 4 years ago

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

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

KuroChimera commented 4 years ago

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

@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

KuroChimera commented 4 years ago

Also here is the requested info:

cura.log DxDiag.txt

Ghostkeeper commented 4 years ago

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

I'm having an identical issue

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

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

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! 20200622_193341 1

fieldOfView commented 4 years ago

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

Razorlights commented 4 years ago

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!