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

Razorlights 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

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

Hookedon3D commented 4 years ago

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

disneytoy commented 4 years ago

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

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

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

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.

spiritedsnowcat commented 4 years ago

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

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

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

Ghostkeeper commented 4 years ago

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

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

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

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

Ghostkeeper commented 4 years ago

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.

spiritedsnowcat commented 4 years ago

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.

spiritedsnowcat commented 4 years ago

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

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.

spiritedsnowcat commented 4 years ago

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

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

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.

KuroChimera commented 4 years ago

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.

spiritedsnowcat commented 4 years ago

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

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

raydemay commented 4 years ago

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

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.

spiritedsnowcat commented 4 years ago

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

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

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

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

Ghostkeeper commented 3 years ago

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

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

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.

spiritedsnowcat commented 3 years ago

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.

ExtremeFiretop commented 3 years ago

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

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?

ExtremeFiretop commented 3 years ago

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

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.

spiritedsnowcat commented 3 years ago

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

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

From: Spirited notifications@github.com Sent: Sunday, October 25, 2020 6:35:47 PM To: Ultimaker/Cura Cura@noreply.github.com Cc: Mehmet Belviranli belviranli@mines.edu; Comment comment@noreply.github.com 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.

ExtremeFiretop commented 3 years ago

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

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.

ExtremeFiretop commented 3 years ago

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

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

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

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

spiritedsnowcat commented 3 years ago

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!

ExtremeFiretop commented 3 years ago

all virtualization disabled

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

spiritedsnowcat commented 3 years ago

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

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.

spiritedsnowcat commented 3 years ago

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.