cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - Stay updated on what is happening on the PTC Community by subscribing to PTC Community Announcements. X

crash creo 3.0, have a traceback.log : need help

yann_3577
2-Explorer

crash creo 3.0, have a traceback.log : need help

Hello,

 

My asm worked fine since months and months and since one weeke i have each time i save it, a fatal error with a traceback.log created. Can someone can help me ?  id on't find the solution. Even withthe asm with  all the coponents inhibited, when i save it, i have a fatal error.

Thanks by advance for your help.

traceback.log file is attached to the message. Below the begining of the traceback.log file

-------------------------------------------------
The trace creation timestamp is: mar. juil. 30 07:49:01 19
The executable build timestamp is: lun. juil. 24 15:19:28 17
The datecode is: 2017170
The pro machine type is: x86e_win64
The process ID is: 3380
The traceback type is : CRASH
The logger exit status is: 00003
The release is: 3.0
The external datecode is: M140
The product title is: Creo Parametric
-------------------------------------------------
Exception EXCEPTION_ACCESS_VIOLATION has occurred in the thread 5636.

Main Thread 5636

2 REPLIES 2
TomU
23-Emerald IV
(To:yann_3577)

For traceback logs you will need someone from PTC technical support to look at it.  They have tools to decode what's in the file.  Those of us here on the community do not.  Do you have active maintenance?  If so, create a new case here:  https://support.ptc.com/apps/case_logger_viewer/cs/auth/ssl/log

@yann_3577 

This seems to be specific to assembly as there is not much information in traceback about code triggering the exit. I will echo with @TomU and suggest you to submit a case as this is reproducible on your assembly. 

Announcements
NEW Creo+ Topics: Real-time Collaboration


Top Tags