Jump to content
Ultimaker Community of 3D Printing Experts

Control Eng

Dormant
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

Personal Information

  • Country
    GB
  • Industry
    Engineering

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I cannot see any dll errors in your log (other than the ones that exist in running Cura logs). In my opinion your crash looks similar to mine when some of the Cura files were corrupted. I downloaded the latest version of Cura yesterday and noticed that the error reporting has been significantly enhanced. It also now has an option to reset the configuration files when a crash occurs. Having said that, the first time I ran the newly installed Cura it immediately crashed! I would recommend that you download the latest version of Cura 3.2.1.
  2. Sorry for not replying earlier, I got so frustrated with Cura that I had a play with IceSL! Returned to Cura today and managed to find what my problems were. When Cura crashes it leaves corrupted (incomplete) files in its' cache directory. On the next run Cura crashes while trying to parse these incomplete files due to 'uncaught exception' deficiencies in the Cura exe. The files are in your user_name/AppData/Roaming/Cura/3.2 - delete the directory with all contents to fix (need to select show hidden files). depends shows far more information if 'Log DllMain calls for all oth
  3. I have a laptop on which I can select whether an application uses the Processor HD4400 graphics or a NVidia GT750M. With the HD4400 Cura crashes with the same error as you have posted. Using the GT750M Cura crashes while trying to parse the printer definition file prior to initialising the graphics. In my opinion there is nothing that you can do to resolve the issue. Cura requires a manifest so that the OS can ensure the relevant environment for it to run. That can only be provided by the developer.
  4. These crashes are NOT due to missing ddls - they are caused by an inconsistent compliment of dlls. When an application does not specify its dll dependencies, the dll loader checks whether calls issued by it can be satisfied by an already memory resident dll (to save memory by not having to load a new copy of a dll). If the already loaded dll is not the same version as that used during linking this application the result is unpredictable. This was a major problem with the early versions of windows. So when an application hasn't specified its dll dependencies it is pot lu
×
×
  • Create New...