Jump to content

crazy1pilot

Member
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

Personal Information

  • Field of Work
    Engineering
  1. I currently have 3.2.1 installed, I tried pretty much every version of Cura 3.x.x and Cura 2.x.x with similar issues. However, the legacy version of Cura 15.04.3 never had any issues. 15.04.3 doesn't have a lot of the features I would like to use like 3.2.1 does. I even went as far as formatting my system completely and the first program I installed was Cura 3.2.1, on its first boot up it still crashed..... I can try uninstalling 3.2.1 and clearing the directories and reinstalling again. I will report back. I would love to use Cura as my primary slicer, but its not looking promising. Thanks again for the direction and help trying to figure this issue out.
  2. Here is what was generated. Also below is the link where the full log is located. Full Log2 File
  3. Would you be able to create a post on GitHub reporting the issue? You would be able to explain the issue much better then I would. If not, I can give it a shot. I haven't been able to find any other post on this issue, but maybe I'm looking in the wrong spot.
  4. What would be the best way to try and resolve this issue? Is it even possible to fix on my end or does there need to be a Cura update? This would explain why the crashes are inconsistent in nature but always happen. Thank you for the information.
  5. Thopiekar, I downloaded Dependancy Walker and ran Cura. This is what came back, I am not sure if you have a specific command you would like me to run but I just ran a generic script. C:\>A:\Downloads\Depends22_x64\depends.exe /c /f:1 /pb /pp:1 /pg:1 /ot:Log.txt "C:\Program Files\Ultimaker Cura 3.2\Cura.exe" It returned this information below, also there is a link to the full .txt file. GetProcAddress(0x00007FF9E3EB0000 [MKL_AVX2.DLL], "mkl_lapack_ps_avx2_dgetrs_small") called from "MKL_CORE.DLL" at address 0x00007FF9E6309BF8 and returned 0x00007FF9E4582E30. GetProcAddress(0x00007FF9EBF80000 [OPENGL32.DLL], "glTexImage1D") called from "QWINDOWS.DLL" at address 0x00007FF9EC0D6DB8 and returned 0x00007FF9EC0570B0. GetProcAddress(0x00007FFA31860000 [KERNEL32.DLL], "GetSystemTimes") called from "NVOGLV64.DLL" at address 0x000000006BDC4C08 and returned 0x00007FFA318819F0. qml: TableViewSelection: index out of range qml: TableViewSelection: index out of range Second chance exception 0xC0000005 (Access Violation) occurred in "QT5QML.DLL" at address 0x000000006DBB2470. Exited "CURA.EXE" (process 0x4BAC) with code -1073741819 (0xC0000005). Full Log File
  6. The file is in its correct spot. if you are able to describe the steps to use a dependency walker to diagnose the issue farther I would give it a shot. I thought formatting my computer with a fresh install of Win10 Pro would fix the issue but it is still the same as before. thank you for the help.
  7. I have a feeling it is related to a graphics card issue. If and when Cura doesn't immediately crash, its easy to get it to hang up by scrolling through the Setting page fast, it cant load the settings quick enough and will crash every time. I have a: NVIDIA GeForce GTX 980 Ti Driver: 391.01 I have rolled back the a driver from April of 2017 Driver: 381.89 No luck, it still showed the same issues.
  8. Update: I have since formatted my computer with a fresh install of Win10. the first program I installed was Cura 3.2.1,, the same problem still exists and Event Viewer still shows the Qt5Qml.dll. I am not sure what to do next. I thought for sure a fresh install was going to fix my issues. I have run as Admin and Compatibility Mode nothing has helped. Same issues is still present, is there anything else I can do that would help diagnose the issue? All drivers are up to date and I have even rolled back my graphics driver to the earliest one NVidia had, no luck.
  9. Hi all, This is my first time posting to the Ultimaker forums and hopefully I am in the correct place. I have been using Cura as my primary slicer since I started 3D printing back in 2013, the last Cura build I used was the legacy version 15.04.6 and a little bit of 2.1.3 which had always worked well and I never made the move over to the newest versions of Cura. Cura 2.1.3 use to work well but sometime last year it became unstable and I continued to use 15.04.6 without issues. I decided to give the latest 3.2.1 build a go to see it no longer crashed with no luck. I am trying to figure out why the 2.x.x and 3.x.x versions of Cura always crash. (ive tried them all) I am assuming there was a windows update or a driver update that is creating all of these issues. 15.04.6 still works and never had any issues however it has been uninstalled while I try and solve the 3.2.1 crash issue. The crashes are very inconsistent in nature but ALWAYS happen, I have yet to have a session of Cura end without issue. I believe the problem is from a faulty .dll file but I have not been able to resolve the issue. Any help would be really appreciated. I attached the cura.log file and below is what the Event View shows. Event Viewer: Fault bucket 2186857364538711821, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Cura.exe P2: 0.0.0.0 P3: 5a562cae P4: Qt5Qml.dll P5: 5.8.0.0 P6: 587fe2fc P7: c0000005 P8: 0000000000172470 P9: P10: Faulting application name: Cura.exe, version: 0.0.0.0, time stamp: 0x5a562cae Faulting module name: Qt5Qml.dll, version: 5.8.0.0, time stamp: 0x587fe2fc Exception code: 0xc0000005 Fault offset: 0x0000000000172470 Faulting process id: 0x3e90 Faulting application start time: 0x01d3ac31e5bd3458 Faulting application path: C:\Program Files\Ultimaker Cura 3.2\Cura.exe Faulting module path: C:\Program Files\Ultimaker Cura 3.2\Qt5Qml.dll Report Id: 75e40b38-f4a7-4bf6-b8cc-f982144f9394 Faulting package full name: Faulting package-relative application ID: Any thoughts? cura.log
×
×
  • Create New...

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!