Skip to main content
M
MK_97269691-Visitor
1-Visitor
March 28, 2022
Solved

Fatal Errors

  • March 28, 2022
  • 1 reply
  • 3158 views

I am using Creo Parametric Release 8.0 and Datecode8.0.2.0

One of our user's are experiencing issues with "Auto-traceback info" - Fatal error encountered. A traceback has been written to c:\designdatamanager\working\traceback.log Please sent it to technical support.

This keeps erroring intermittently on the user's creo parametric 8 application. I have reinstalled the software but this has not made any difference.


Here are the errors that I faced
-------------------------------------------------
The trace creation timestamp is: Mon Mar 28 09:31:07 22
The executable build timestamp is: Tue Sep 28 10:08:31 21
The datecode is: 2021284
The pro machine type is: x86e_win64
The process ID is: 16884
The traceback type is : CRASH
The logger exit status is: 00003
The Trail is: trail.txt.70
The release is: 8.0
The product version is: 8.0.2.0
The product title is: Creo Parametric
-------------------------------------------------
Exception EXCEPTION_ACCESS_VIOLATION has occurred in the thread 20840.

Main Thread 20840
=====================
0x00007FF7207F5577 NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x289a1f68, 0x4c35c5b8, 0x4c35c5b8, 0x4b16aae8 )
0x00007FF71D4AA4B7 NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x0, 0x86, 0x86, 0x2c461f00 )
0x00007FF71D4F3FB9 NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x0, 0xffffffff, 0x0, 0x0 )
0x00007FFC83084993 NULL (NULL:0) (uitools_sh:0x00007FFC82CA0000) ( 0x4c35c5b8, 0x6573f0c8, 0x4c35c748, 0x4c35c5b8 )
0x00007FF71D5150CA NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x6573f0c8, 0x86, 0x0, 0x1d4aa220 )
0x00007FF71D4F7448 NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x0, 0x9964cb30, 0x9964cb30, 0x289a1f68 )
0x00007FF71D8FE6E2 NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x0, 0xb01af230, 0x0, 0xb01af288 )
0x00007FF71D905749 NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x1, 0x0, 0x9964cb30, 0x0 )
0x00007FF720551F01 NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x1db49b0, 0xffffffff, 0x8a173630, 0x1d1f348 )
0x00007FFC8A101386 NULL (NULL:0) (libui_sh:0x00007FFC89E70000) ( 0x0, 0x3f131dd, 0x800003, 0x4000018 )
0x00007FFC89FF71C5 NULL (NULL:0) (libui_sh:0x00007FFC89E70000) ( 0x800003, 0x0, 0x11bb03, 0x0 )
0x00007FFC8A10C99F NULL (NULL:0) (libui_sh:0x00007FFC89E70000) ( 0x11bb03, 0x4000018, 0x800003, 0xb01af580 )
0x00007FFC89FFB59C NULL (NULL:0) (libui_sh:0x00007FFC89E70000) ( 0x0, 0x0, 0x800003, 0x0 )
0x00007FF7236DC1D7 NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x1, 0x2f, 0xb01af750, 0x28e2f440 )
0x00007FF7236D5A14 NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x7, 0xb01af7f0, 0x0, 0x0 )
0x00007FFCBCE492FB NULL (NULL:0) (coretools_sh:0x00007FFCBCE00000) ( 0x28838c89, 0x8a1ec0a0, 0x3, 0x1f78a33a )
0x00007FF7236DBF89 NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x8a1ec0a0, 0x0, 0x0, 0x20003f )
0x00007FF71D48DA26 NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x7e730458, 0x3, 0x0, 0x0 )
0x00007FF71D3916AA NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x7e730458, 0x0, 0x8a1ec0a0, 0x3 )
0x00007FF725208D1A NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x1, 0xb01af860, 0x7e730458, 0x0 )
0x00007FF725208DCA NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x7e730458, 0x25208d40, 0x7e1b7030, 0xb01afba0 )
0x00007FFC8A0A633C NULL (NULL:0) (libui_sh:0x00007FFC89E70000) ( 0x7e730458, 0x25208d40, 0xb01afba0, 0x0 )
0x00007FFC8A0A7EEF NULL (NULL:0) (libui_sh:0x00007FFC89E70000) ( 0x25208d40, 0x0, 0x0, 0x0 )
0x00007FFC89E8F7ED NULL (NULL:0) (libui_sh:0x00007FFC89E70000) ( 0xa, 0x3, 0x7e730458, 0x0 )
0x00007FF725206322 NULL (NULL:0) (xtop:0x00007FF71C5D0000) ( 0x0, 0x0, 0x0, 0x0 )
0x00007FFCED4C7034 NULL (NULL:0) (KERNEL32:0x00007FFCED4B0000) ( 0x0, 0x0, 0x0, 0x0 )

Thread 11148
=====================
0x00007FFCEBEAA104 NULL (NULL:0) (win32u:0x00007FFCEBEA0000) ( 0x0, 0x0, 0x0, 0x0 )
0x00007FFCEC67078E NULL (NULL:0) (USER32:0x00007FFCEC650000) ( 0xbcc49ba0, 0x7c63e320, 0x0, 0x0 )
0x00007FFCBCC49503 NULL (NULL:0) (asyncoremt:0x00007FFCBCC10000) ( 0x7c63e320, 0x7c63e320, 0x7e410220, 0x7be00870 )
0x00007FFCBCC43676 NULL (NULL:0) (asyncoremt:0x00007FFCBCC10000) ( 0x7c63e320, 0x7e4245e0, 0x7e692f98, 0xd3bffe13 )
0x00007FFCBCC433DA NULL (NULL:0) (asyncoremt:0x00007FFCBCC10000) ( 0x7e4245e0, 0x7c6108f0, 0x0, 0x7e4245e0 )
0x00007FFCBCC437AF NULL (NULL:0) (asyncoremt:0x00007FFCBCC10000) ( 0x7e1d3a50, 0x0, 0x0, 0x0 )
0x00007FFCEB681BB2 NULL (NULL:0) (ucrtbase:0x00007FFCEB660000) ( 0x0, 0x0, 0x0, 0x0 )
0x00007FFCED4C7034 NULL (NULL:0) (KERNEL32:0x00007FFCED4B0000) ( 0x0, 0x0, 0x0, 0x0 )

Thread 11044
=====================
0x00007FFCEDFAD8C4 NULL (NULL:0) (ntdll:0x00007FFCEDF10000) ( 0x10, 0x68040004, 0x306e2200, 0xb110f760 )
0x00007FFCEBC1CB20 NULL (NULL:0) (KERNELBASE:0x00007FFCEBBD0000) ( 0xffffffff, 0x7c63e480, 0x7e944ed8, 0xb110f990 )
0x00007FFCBCC11946 NULL (NULL:0) (asyncoremt:0x00007FFCBCC10000) ( 0x2bf690a1, 0x2bf690a1, 0x1, 0x7c63e480 )
0x00007FFCBCC19204 NULL (NULL:0) (asyncoremt:0x00007FFCBCC10000) ( 0x1, 0x7c63e430, 0x3, 0x0 )
0x00007FFCBCC4955E NULL (NULL:0) (asyncoremt:0x00007FFCBCC10000) ( 0x7e692f98, 0xd3c00f12, 0x7c3c0870, 0x7c3c0870 )
0x00007FFCBCC43676 NULL (NULL:0) (asyncoremt:0x00007FFCBCC10000) ( 0x7c63e430, 0x7e424aa0, 0x7e692f98, 0xd3bffe13 )

Best answer by sacquarone

Hello @MK_9726969 

 

Interesting traceback log file. I analyzed it and share my views below. Please consider however before going on reading that this kind of service is usually not proposed in the community. So that if you need guidance in the future on random (but frequent) unexpected exits, we suggest you to open a case to PTC Technical Support to get views from PTC on this kind of investigation.

 

This Traceback has the following signature:

  • MdlTreeActRepeatComp
  • MdlTreeActExec
  • TreeActionExec
  • TreeToolExecAction
  • MdlTreeDoAction
  • CmdTreeToolEditNodes
  • ProFeatOperation
  • ProCmdActionRepeatComp
  • _uicmd_cmd_execute
  • _ui_krn_process_command
  • process_command_action
  • promenu_action_until
  • main_thread_promenu_action
  • MainThread_do_task
  • promenu_action
  • promenu_toplevel_action

 

In other words, soemthing related to the Model Tree (maybe some columns in some specific situation, or somle action laucnhed from the Model Tree). Related to this signature, we have article 65390 linked to it. There is an ongoing SPR 13705296 whose Creo 7.0, 8.0 & 9.0 tasks are in "Fix Ready" (but not yet submitted).

 

A very recent note from our developers mention what follows:

we've fixed this a couple times, and I expect we'll need a reproducible case to really know what's going on.

 

Considering above background, here are the steps I suggest to you:

  1. Subscribe to above article, so that you will be notified in the (probable near) future when it will be modified (will be modified, once resolution will be posted by R&D, validated by QA, and successivly documented accordingly in this article)
  2. Wen you'll get the info, update to the relevant Creo Parametric 8.0 datdcode
  3. As R&D identified the cause of the exit in the code and will fix it, but without being sure this will affect ALL the use cases leading in this kind of exit,  if unexpected exits will somehow persist for this impacted user, please open a case to PTC TS, and describe if possible what was being done when issue was faced (to try to identify a common pattern)

 

Regards,

 

Serge

1 reply

S
sacquarone21-Topaz IAnswer
21-Topaz I
March 28, 2022

Hello @MK_9726969 

 

Interesting traceback log file. I analyzed it and share my views below. Please consider however before going on reading that this kind of service is usually not proposed in the community. So that if you need guidance in the future on random (but frequent) unexpected exits, we suggest you to open a case to PTC Technical Support to get views from PTC on this kind of investigation.

 

This Traceback has the following signature:

  • MdlTreeActRepeatComp
  • MdlTreeActExec
  • TreeActionExec
  • TreeToolExecAction
  • MdlTreeDoAction
  • CmdTreeToolEditNodes
  • ProFeatOperation
  • ProCmdActionRepeatComp
  • _uicmd_cmd_execute
  • _ui_krn_process_command
  • process_command_action
  • promenu_action_until
  • main_thread_promenu_action
  • MainThread_do_task
  • promenu_action
  • promenu_toplevel_action

 

In other words, soemthing related to the Model Tree (maybe some columns in some specific situation, or somle action laucnhed from the Model Tree). Related to this signature, we have article 65390 linked to it. There is an ongoing SPR 13705296 whose Creo 7.0, 8.0 & 9.0 tasks are in "Fix Ready" (but not yet submitted).

 

A very recent note from our developers mention what follows:

we've fixed this a couple times, and I expect we'll need a reproducible case to really know what's going on.

 

Considering above background, here are the steps I suggest to you:

  1. Subscribe to above article, so that you will be notified in the (probable near) future when it will be modified (will be modified, once resolution will be posted by R&D, validated by QA, and successivly documented accordingly in this article)
  2. Wen you'll get the info, update to the relevant Creo Parametric 8.0 datdcode
  3. As R&D identified the cause of the exit in the code and will fix it, but without being sure this will affect ALL the use cases leading in this kind of exit,  if unexpected exits will somehow persist for this impacted user, please open a case to PTC TS, and describe if possible what was being done when issue was faced (to try to identify a common pattern)

 

Regards,

 

Serge

Terms & ConditionsCookie settingsAccessibility statement