PapaPrints3D

I do have multiple displays. I turned off the secondary display and it resolved the issue. I will keep Cura on the primary display. It appears if you drag Cura to the secondary window it crashes again.

OK. This is ridiculous. I created another new user profile and was using Cura. It was fine until I went to change the settings of a job. I changed it from Fine to VeryFine, then it locked up. The Cura log is saying the same thing. It's trying to connect to a com port (5) as in the log I posted above. This might sound stupid, but this all started when I downloaded a 3D item from Cults3D. I tried to load that object in to Cura and the application crashed. It's almost like that item ruined my system.

I found this at the bottom of the Cura log. I can confirm that everytime I let it sit at the frozen screen, it keeps adding these lines over and over, trying to access a port which does not have a printer on it 2023-02-10 17:53:06,824 - DEBUG - [JobQueueWorker [1]] USBPrinting.AutoDetectBaudJob.run [49]: Checking COM5 if baud rate 250000 works. Retry nr: 0. Wait timeout: 3 2023-02-10 17:53:11,328 - DEBUG - [JobQueueWorker [1]] USBPrinting.AutoDetectBaudJob.run [49]: Checking COM5 if baud rate 500000 works. Retry nr: 0. Wait timeout: 3 2023-02-10 17:53:15,831 - DEBUG - [JobQueueWorker [1]] USBPrinting.AutoDetectBaudJob.run [49]: Checking COM5 if baud rate 230400 works. Retry nr: 0. Wait timeout: 3 2023-02-10 17:53:20,335 - DEBUG - [JobQueueWorker [1]] USBPrinting.AutoDetectBaudJob.run [49]: Checking COM5 if baud rate 76800 works. Retry nr: 0. Wait timeout: 3 2023-02-10 17:53:24,838 - DEBUG - [JobQueueWorker [1]] USBPrinting.AutoDetectBaudJob.run [49]: Checking COM5 if baud rate 57600 works. Retry nr: 0. Wait timeout: 3 2023-02-10 17:53:29,341 - DEBUG - [JobQueueWorker [1]] USBPrinting.AutoDetectBaudJob.run [49]: Checking COM5 if baud rate 38400 works. Retry nr: 0. Wait timeout: 3 2023-02-10 17:53:33,846 - DEBUG - [JobQueueWorker [1]] USBPrinting.AutoDetectBaudJob.run [49]: Checking COM5 if baud rate 19200 works. Retry nr: 0. Wait timeout: 3 2023-02-10 17:53:38,350 - DEBUG - [JobQueueWorker [1]] USBPrinting.AutoDetectBaudJob.run [49]: Checking COM5 if baud rate 9600 works. Retry nr: 0. Wait timeout: 3 2023-02-10 17:53:57,853 - DEBUG - [JobQueueWorker [1]] USBPrinting.AutoDetectBaudJob.run [49]: Checking COM5 if baud rate 115200 works. Retry nr: 1. Wait timeout: 15 2023-02-10 17:54:17,860 - DEBUG - [JobQueueWorker [1]] USBPrinting.AutoDetectBaudJob.run [49]: Checking COM5 if baud rate 250000 works. Retry nr: 1. Wait timeout: 15 2023-02-10 17:54:37,867 - DEBUG - [JobQueueWorker [1]] USBPrinting.AutoDetectBaudJob.run [49]: Checking COM5 if baud rate 500000 works. Retry nr: 1. Wait timeout: 15

Faulting application name: CuraEngine.exe, version: 1.0.0.0, time stamp: 0x63cfd8be Faulting module name: ucrtbase.dll, version: 10.0.22621.608, time stamp: 0xf5fc15a3 Exception code: 0xc0000409 Fault offset: 0x000000000007f61e Faulting process id: 0x0x5D88 Faulting application start time: 0x0x1D93D9A484DED3C Faulting application path: E:\Program Files\UltiMaker Cura 5.2.2\CuraEngine.exe Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report Id: fcd73f47-29f0-4c2b-9631-28c8fcafd0ff Faulting package full name: Faulting package-relative application ID:

Found this is the logs Fault bucket 1971460549780171195, type 5 Event Name: BEX64 Response: Not available Cab Id: 0 Problem signature: P1: CuraEngine.exe P2: 1.0.0.0 P3: 63cfd8be P4: ucrtbase.dll P5: 10.0.22621.608 P6: f5fc15a3 P7: 000000000007f61e P8: c0000409 P9: 0000000000000007 P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.28a247dd-59bd-47df-9b19-a107cb596ef3.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9c8df895-6021-487a-93d1-5b8261fc33da.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e0d07592-cdc6-44ca-978d-c81501ffc262.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.01ff7b5c-e0be-4ebd-bea6-84b92a41da67.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.dd2d1548-d377-4045-8fe4-8c82dfd8586d.tmp.xml

I have been using Cura for quite a while and had no issues. Last night I opened six objects at once, multiple windows, and then Cura crashed. I tried to open it again and it would get past the splash screen then sit at a white screen with the hour glass. I uninstalled Cura, reinstalled it, twice, putting it in a different folder.. I made sure all Microsoft updates and graphic drivers were updated. None of this worked. I then created a new user profile, which allowed Cura to start and I was able to do one job. However it crashed again. Now, under that new user profile I can no longer run Cura. It freezes at the white screen again. I'm wondering what might be wrong? Is this a hardware issue? I checked the system temperatures and everything is within parameters. No other errors that I can detect. Thanks!