Please Help: Cura 4.8.0 Freezes During Launch

[MCReaper13 0]

I have been printing now for a little over a year and have almost exclusively used Cura as my slicer. About 4 weeks ago I got a stronger laptop for work from home and for printing. Cura 4.7.x, 4.8.0 Beta, and finally 4.8.0 worked great when I first installed them on the new computer. I later uninstalled the default MacAfee antivirus and loaded Kaspersky total security (previously paid for the service on another machine). I don't know if this has anything to do with it but this is one of the things I noticed around the timeframe. Shortly after that, I am unable to open Cura. When I go to the launch the program it cycles through GUI but as soon as the program itself opens, it freezes part way through loading. I could uninstall the program and reinstall it and get about another 2-3 slices from the program before it would begin to freeze again. I have also tried other slicers like Prusaslicer and that too after a time will eventually freeze. I am able to run Creo and NX without issue on my new computer. Any help or guidance you all could provide would be greatly appreciated! See below for computer specs and previously tested resolutions. I will be sure to respond to any questions or comments!

 

Computer: Dell G5, i7 @2.6Ghz (4.1OC), 500Gb NVMe M.2, GTX 1660Ti, 16Gb RAM, Windows 10 64-bit

 

I've tried:

• Restarting the computer
• Uninstalling and re-installing Cura (will work for a minute and then eventually freeze)
• Pausing internet security while uninstall/reinstall/running
• Deleting the Cura folders from the Appdata/Local and Appdata/Roaming and restarting
• Run as admin (works for a minute so I can uncheck "send anon print information" but eventually freezes before you can slice a file)
• Troubleshoot compatibility, both standard and windows 7/8 modes

[gr5 2,330]

One possibility is that there are too many triangles in your STL file.  Try slicing something simple like a cube with only 12 triangles.  Or something that you have sliced before that sliced quickly.  Meshlab tells you how many triangles/faces there are the moment it loads your STL and can decimate them to fewer triangles as well if you want.  This is just a guess but it's all I can think of right now.

[MCReaper13 0]

@gr5 Thank you for your reply. The problem that I am having is that I am not able to even open Cura to load a model for slicing. 

[gr5 2,330]

I misunderstood.  locate the log file and post it here.  Also look at it - it may have clues towards the end.

 

On my windows10 computer it is here: C:\Users\gr5\AppData\Roaming\cura\4.8
On linux is here:   /home/gr5/.local/share/cura/master

 

%APPDATA%\cura\<Cura version>\cura.log (Windows), or usually C:\Users\\<your username>\AppData\Roaming\cura\<Cura version>\cura.log
$USER/Library/Application Support/cura/<Cura version>/cura.log (OSX)
$USER/.local/share/cura/<Cura version>/cura.log (Ubuntu/Linux)
 

[MCReaper13 0]

1 hour ago, gr5 said:

I misunderstood.  locate the log file and post it here.  Also look at it - it may have clues towards the end.

 

On my windows10 computer it is here: C:\Users\gr5\AppData\Roaming\cura\4.8
On linux is here:   /home/gr5/.local/share/cura/master

 

%APPDATA%\cura\<Cura version>\cura.log (Windows), or usually C:\Users\\<your username>\AppData\Roaming\cura\<Cura version>\cura.log
$USER/Library/Application Support/cura/<Cura version>/cura.log (OSX)
$USER/.local/share/cura/<Cura version>/cura.log (Ubuntu/Linux)
 

Not a problem, thank you for taking the time to help out! I greatly appreciate it. Attached is the .log file.

 

cura.log

[gr5 2,330]

So it isn't exactly crashing - it's just slow.  "just".  Definitely shut off kaspersky completey - 100% off - and try it once without kaspersky running.  I remember something about that from past posts.

 

How many megabytes is the STL you sliced?

 

 Did you install cura on a network drive?

 

So there have been issues with cura slowing to a crawl due to - I forget what exactly but I think maybe:

searching through USB devices

searching through online printers

searching through networked drives (dropbox?  NAS drives?)

 

Try disconnecting your network cable and then launching cura - see if that helps.

 

In google type "site:ultimaker.com cura slow".  The "site:" will only give you answers from the ultimaker web site which is ideal.  There have been other people where cura was too slow to use and they got things figured out.

 

Let me know if you tried: 1) kaspersky 2) network 3)size of stl 4) installation disk

 

 

[MCReaper13 0]

21 hours ago, gr5 said:

So it isn't exactly crashing - it's just slow.  "just".  Definitely shut off kaspersky completey - 100% off - and try it once without kaspersky running.  I remember something about that from past posts.

 

How many megabytes is the STL you sliced?

 

 Did you install cura on a network drive?

 

So there have been issues with cura slowing to a crawl due to - I forget what exactly but I think maybe:

searching through USB devices

searching through online printers

searching through networked drives (dropbox?  NAS drives?)

 

Try disconnecting your network cable and then launching cura - see if that helps.

 

In google type "site:ultimaker.com cura slow".  The "site:" will only give you answers from the ultimaker web site which is ideal.  There have been other people where cura was too slow to use and they got things figured out.

 

Let me know if you tried: 1) kaspersky 2) network 3)size of stl 4) installation disk

 

 

Thank you for the response.

 

1. I closed out of my AV, cleared the local and roaming cura folders and tried to load Cura as an admin. It still acts as if it was frozen.

1a. After I closed Cura from my first test, i went through the trouble shooting app and selected recommended settings and it failed again. I sent the information to Microsoft and it came back saying "Incompatible Program - Not Fixed"

2. My network is via WiFi, there is no network cable

2a. After I closed Cur from the second test, I then turned off my WiFi and tried opening it again as an admin.

3. When I am able to actually open Cura and get it to slice (My problem), I was able to slice a single item that was 1.08MB

4. Cura is installed locally on my machine (C Drive - 500GB NVMe ). My printer is not connected to my cura.logr and I use the SD card to transfer information to the printer.

 

I have attached my .log file for this round of testing as well if it helps. Thank you again for taking the time to review this!

cura.log

[tinkergnome 929]

My recommendation is:

1. Cura runs in compatibility mode and uses the on-board Intel graphics card. I would try to select the NVIDIA driver instead. The procedure depends on your operating system and/or graphics driver version. For example:
   https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/select-gpu-to-use-by-specific-applications/eb671f52-5c24-428d-a7a0-02a36e91ee2f
    
2. Start Cura one more time with disabled network, open the preferences window and disable "Check for updates on start" and "Send (anonymous) print information" (at the bottom of the dialog).
   Disable "Restore window position on start", if you use more than one monitor.
3. Disable bundled plugins that you do not use (in "Marketplace") e.g.:
   - Firmware Update Checker
   - UM3 Network Printing
   - USB Printing
   - Update Checker
4. Restart Cura, enable the network connection and check if it makes a difference.
   ("start as Administrator" should not be necessary)

 

Or better do one step at a time to find the root cause.

Good luck!

Edited January 29, 2021 by tinkergnome

[MCReaper13 0]

20 hours ago, tinkergnome said:

My recommendation is:

1. Cura runs in compatibility mode and uses the on-board Intel graphics card. I would try to select the NVIDIA driver instead. The procedure depends on your operating system and/or graphics driver version. For example:
   https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/select-gpu-to-use-by-specific-applications/eb671f52-5c24-428d-a7a0-02a36e91ee2f
    
2. Start Cura one more time with disabled network, open the preferences window and disable "Check for updates on start" and "Send (anonymous) print information" (at the bottom of the dialog).
   Disable "Restore window position on start", if you use more than one monitor.
3. Disable bundled plugins that you do not use (in "Marketplace") e.g.:
   - Firmware Update Checker
   - UM3 Network Printing
   - USB Printing
   - Update Checker
4. Restart Cura, enable the network connection and check if it makes a difference.
   ("start as Administrator" should not be necessary)

 

Or better do one step at a time to find the root cause.

Good luck!

So, I changed the forced cura to use the GPU. I was able to get into cura long enough for me to select and change out the settings for Print information, restore window, and check for updates. Those are now all unchecked. Testing it without the AV and not on the internet, I was able to get in, load a flle, and slice it, but the moment I tried to go into the settings file, it "locked up" again.

 

Then.... and here's the kicker, I unplugged everything from my laptop and tried again and it works flawlessly (so far). I even changed most of the settings back to original and it still came up clean. So I believe it has to do with one of my USB ports or displays. It is a hodge podge because I use my laptop for work from home but I have a 3rd party USB-C docking station plugged in to my laptop that runs 2 monitors and has another USB 3.0 hub splitter attached which connects a phone charger, USB wireless keyboard, printer, and external hard drive.

 

Not sure which one of those is causing the issue with Cura but one of them or all of them are contributing somehow. I do seem to have a workaround, it is just a little inconvenient. But I would rather be able to use it than not. If you see something that could cause it from that list let me know and I'll try that too!

[gr5 2,330]

USB makes complete sense.  It's looking for a 3d printer on all the USB ports.  Sometimes I think cura has too many features.  You are going to have to unplug and plug in each USB device to figure it out I think.  It's possible that the "bad" device has to be connected when you first start cura and if you connect it later cura might not notice.  Not sure.

[Jimmy01 0]

My mate have a Ryzen 2600x with the Asus prime x470 pro. with the same issue.
I have a 1600x with the prime x370 pro, but i don't have the issue.

I think the issue is "DIGI + VRM" under Ai Tweaker tab.
you need to set "CPU power phase control" and "SOC power phase control" to extreme

I have it this way, and never have any issue with cura.

since my mate change this setting hasn't experience any issue, still testing but looks promising.

 

just made an account to answering this post, sorry for my english.

[halr9000 0]

Been having a severe hang issue as well. Attaching my error log. I just went to graphics settings and told it to use my GPU in high performance mode and problem INITIALLY went away. I just restarted Cura and it's stalling again. :<

 

System details:

 

Processor    AMD Ryzen 5 5600X 6-Core Processor                3.70 GHz
Installed RAM    16.0 GB

 

nvidia 3060 with details attached.
 

stderr.log NVIDIA System Information 03-02-2022 22-23-49.log

Edited March 3, 2022 by halr9000

[Geniickbruch 0]

Same Problem here.. tried everything i could find. Still doesn't work.

I included my Log down below.

 

cura.log

[Mixasko 0]

On 7/20/2023 at 3:24 PM, Geniickbruch said:

Same Problem here.. tried everything i could find. Still doesn't work.

I included my Log down below.

 

cura.log 4.89 MB · 0 downloads

Mine freezes on loading "build something", but if i disconnect from the internet, it loads just fine. Or if I turn off Kaspersky AV and VPN it loads as well. Kaspersky has no clue why it is happening. 

[Slashee_the_Cow 619]

1 hour ago, Mixasko said:

Mine freezes on loading "build something", but if i disconnect from the internet, it loads just fine. Or if I turn off Kaspersky AV and VPN it loads as well. Kaspersky has no clue why it is happening. 

Try going to Preferences > Configure Cura... go down to the bottom of the first page and make sure Send (anonymous) print information is turned off. If that doesn't work, to be thorough you might also want to try turning off Send engine crash reports, Check for updates on start and Get notifications for plugin updates. If the problem is internet related that covers most of your bases (just make sure not to log in with an UltiMaker account when you set up Cura).

 

Kaspersky might not have any clue why it's happening but considering the majority of people aren't using their software and not having this problem, it's quite likely it's something their software is doing.

[PapaPrints3D 0]

So I had this same problem with Cura and I basically stopped using it. I would prefer to use it, but I could never get anyone to resolve it. The work around was to create a new profile on my windows machine. To give you an example of what keeps happening - 

 

I left my computer on and left it is sleep mode. The printer is not connected to my machine.

When I came home, the page said that I needed to reconnect to Cura, so I clicked on the icon and it tried to connect but it froze up. This is after I printed over 40 print jobs, so Cura had been working fine.

After it locked up, I could never get it to start again. I shut down everything, rebooted, and tried again, but it still locks up.

 

Now it doesn't work anymore. I have to create a new user profile in order to get Cura to work again.

 

Checking the application logs in windows shows -

 

Log Name:      Application
Source:        Application Hang
Date:          2/13/2025 6:57:34 PM
Event ID:      1002
Task Category: Hanging Events
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      HomeRoot
Description:
The program UltiMaker-Cura.exe version 0.0.0.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

 

 

 

 

Log Name:      Application
Source:        Application Error
Date:          2/13/2025 6:57:36 PM
Event ID:      1000
Task Category: Application Crashing Events
Level:         Error
Keywords:      
User:          HomeRoot\020625
Computer:      HomeRoot
Description:
Faulting application name: CuraEngine.exe, version: 1.0.0.0, time stamp: 0x67374020
Faulting module name: ucrtbase.dll, version: 10.0.26100.3037, time stamp: 0x8481217d
Exception code: 0xc0000409
Fault offset: 0x00000000000a4c2e
Faulting process id: 0x5744

 

(edit)

 

I uninstalled Cura and installed it again, on a different drive. It didn't work.

I uninstalled Cura and then went through the registry and removed all reference to it. I then installed it again, but it didn't work.

 

I then noticed the following error

 

Fault bucket 1754446133477147820, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: CuraEngine.exe
P2: 1.0.0.0
P3: 67374020
P4: ucrtbase.dll
P5: 10.0.26100.3037
P6: 8481217d
P7: 00000000000a4c2e
P8: c0000409
P9: 0000000000000007
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.15b2d344-a77d-4fe2-b2a2-155240ae91eb.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.ad3fa9d9-5700-44e3-bb81-a7a8aef0d198.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b65b9887-43d2-4a23-977f-498389f60bd6.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1f01c6c0-44bc-43b8-b0b0-4e5b40828caa.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a94404ee-9e6a-4b16-9887-d1bd8c95d8f4.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_CuraEngine.exe_67daf91035fd635e6331e53ce2dc7a8a8a24d3_230309c5_27394e9c-ed47-496e-a49e-9bfd7b4fb3ab

Analysis symbol: 
Rechecking for solution: 0
Report Id: cba112b8-61fb-4894-ab1f-35b7ea857eb5
Report Status: 268435456
Hashed bucket: bcb7c828c66bb67dd8590b76837684ac
Cab Guid: 0

 

 

 

Faulting application name: CuraEngine.exe, version: 1.0.0.0, time stamp: 0x67374020
Faulting module name: ucrtbase.dll, version: 10.0.26100.3037, time stamp: 0x8481217d
Exception code: 0xc0000409
Fault offset: 0x00000000000a4c2e
Faulting process id: 0x6BE4
Faulting application start time: 0x1DB7E7F07E43427
Faulting application path: J:\Ultimaker Cura\CuraEngine.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: cba112b8-61fb-4894-ab1f-35b7ea857eb5
Faulting package full name: 
Faulting package-relative application ID: 

 

 

 

Faulting application name: CuraEngine.exe, version: 1.0.0.0, time stamp: 0x67374020
Faulting module name: ucrtbase.dll, version: 10.0.26100.3037, time stamp: 0x8481217d
Exception code: 0xc0000409
Fault offset: 0x00000000000a4c2e
Faulting process id: 0x1228
Faulting application start time: 0x1DB7E7EE0E0231C
Faulting application path: J:\Ultimaker Cura\CuraEngine.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: a908ea09-0b22-4bb9-970e-3f183616a0fa
Faulting package full name: 
Faulting package-relative application ID: 

Edited February 14 by PapaPrints3D

[gr5 2,330]

Are you somehow printing from cura to the printer?  Most people slice and then save the gcode to an SD card, then put the SD card in their printer.  Is that what you are doing?  Do you mean you saved 60 gcode files to an SD card and then when you tried to save the 61st gcode file, cura crashed?

 

And you "create a profile" - what does that even mean. Is that something in Cura or in windows?

 

[Slashee_the_Cow 619]

@PapaPrints3D: On your main user account, go to %APPDATA% and there should be a cura folder there. Try renaming it (anything will work, cura_, cura2, Cura - Copy, it doesn't matter) and launch Cura. It should launch fine since working fine as another user probably means the configuration files (which are stored per user), although it will be in a "blank slate" state - like the first time you used it. Once it's working, you can start copying things like quality profiles over from the old folder as needed (which is why we renamed it instead of deleting it). Just don't copy too much over at once, and test frequently so you can isolate what the problem could be.

 

@gr5 - The problem seems to be in CuraEngine and not Cura itself (which is why ucrtbase.dll is involved, it's part of Visual C++ which it's entirely possible is used to compile CuraEngine on Windows). Probably made Cura itself crash and put something invalid in a configuration file or something.