Fluids

Fluids

Topics related to Fluent, CFX, Turbogrid and more.

BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES

TAGGED: ,

    • Yiqing zhang
      Subscriber

      I am calculating a two-phase water vapor flow problem in an open channel, using the VOF model. The error "BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES" is accompanied by "The fl process could not be. This error occurred after I had calculated many steps. After it appeared, all the buttons on the fluent interface could not be used. After I restarted the calculation, the same error was displayed again. How to solve it? I used 2022R1

    • Federico
      Ansys Employee

      Once this error is thrown, your Fluent session will be corrupted and will need to start a new one.

      Does the error always occur at the same iteration? Try to see what happens with your solution before this error is thrown.

    • Yiqing zhang
      Subscriber

       

      Hello, many error files were generated after an error occurred。Other files contain the following information: Abnormal Exit! How to solve?Even if I turn it back on, it's still a repetitive error that can't be calculated.The content of flunt-0-error is as follows:

       

      Node 0 Fatal signal raised sig = Segmentation fault
       30d93010 CX_Primitive_Error
       90e20cc0 seh_filter_exe
       30e35a20 logical_right_shift
       7217eb20 _C_specific_handler
       93572290 _chkstk
       93521030 RtlRaiseException
       93570e90 KiUserExceptionDispatcher
       2e27d930 Dump_Dataship_new
       2e2601d0 Build_Grid
       2e2601d0 Build_Grid
       2ded2050 start_cancel_box
       30e20250 eval
       2dfe7e50 PRF_Command_Start
       2dfea570 PRF_Node_repl
       2dff5fc0 Delay_Error
       30e35a20 logical_right_shift
       92c07330 BaseThreadInitThunk
       93522690 RtlUserThreadStart
       
      Error [node 0] [time 12/5/23 21:44:1] Abnormal Exit!
      Node 0 Fatal signal raised sig = Segmentation fault
       30d93010 CX_Primitive_Error
       90e20cc0 seh_filter_exe
       30e35a20 logical_right_shift
       7217eb20 _C_specific_handler
       93572290 _chkstk
       93521030 RtlRaiseException
       93570e90 KiUserExceptionDispatcher
       2e27d930 Dump_Dataship_new
       2e2601d0 Build_Grid
       2e2601d0 Build_Grid
       2ded2050 start_cancel_box
       30e20250 eval
       2dfe7e50 PRF_Command_Start
       2dfea570 PRF_Node_repl
       2dff5fc0 Delay_Error
       30e35a20 logical_right_shift
       92c07330 BaseThreadInitThunk
       93522690 RtlUserThreadStart
      Node 0 Fatal signal raised sig = Segmentation fault
       8e677b80 CX_Primitive_Error
       90e20cc0 seh_filter_exe
       8e71abb0 logical_right_shift
       7217eb20 _C_specific_handler
       93572290 _chkstk
       93521030 RtlRaiseException
       93570e90 KiUserExceptionDispatcher
       8be1b570 Dump_Dataship_new
       8be02460 Build_Grid
       8be02460 Build_Grid
       8bb42130 Get_Network_Nb
       8e706080 eval
       8bc687a0 PRF_Command_Start
       8bc6afc0 PRF_Node_repl
       8bc6b890 init_rsubrs
       8e71abb0 logical_right_shift
       92c07330 BaseThreadInitThunk
       93522690 RtlUserThreadStart
       
      Error [node 0] [time 12/5/23 21:48:28] Abnormal Exit!
      Node 0 Fatal signal raised sig = Segmentation fault
       8e677b80 CX_Primitive_Error
       90e20cc0 seh_filter_exe
       8e71abb0 logical_right_shift
       7217eb20 _C_specific_handler
       93572290 _chkstk
       93521030 RtlRaiseException
       93570e90 KiUserExceptionDispatcher
       8be1b570 Dump_Dataship_new
       8be02460 Build_Grid
       8be02460 Build_Grid
       8bb42130 Get_Network_Nb
       8e706080 eval
       8bc687a0 PRF_Command_Start
       8bc6afc0 PRF_Node_repl
       8bc6b890 init_rsubrs
       8e71abb0 logical_right_shift
       92c07330 BaseThreadInitThunk
       93522690 RtlUserThreadStart
       
      Error [node 0] [time 12/5/23 21:50:29] Abnormal Exit!
      Node 0 Fatal signal raised sig = Segmentation fault
       30d93010 CX_Primitive_Error
       90e20cc0 seh_filter_exe
       30e35a20 logical_right_shift
       7217eb20 _C_specific_handler
       93572290 _chkstk
       93521030 RtlRaiseException
       93570e90 KiUserExceptionDispatcher
       2e27d930 Dump_Dataship_new
       2e2601d0 Build_Grid
       2e2601d0 Build_Grid
       2ded2050 start_cancel_box
       30e20250 eval
       2dfe7e50 PRF_Command_Start
       2dfea570 PRF_Node_repl
       2dff5fc0 Delay_Error
       30e35a20 logical_right_shift
       92c07330 BaseThreadInitThunk
       93522690 RtlUserThreadStart
       
      Error [node 0] [time 12/5/23 21:53:30] Abnormal Exit!
      Node 0 Fatal signal raised sig = Segmentation fault
       30d93010 CX_Primitive_Error
       90e20cc0 seh_filter_exe
       30e35a20 logical_right_shift
       7217eb20 _C_specific_handler
       93572290 _chkstk
       93521030 RtlRaiseException
       93570e90 KiUserExceptionDispatcher
       2e27d930 Dump_Dataship_new
       2e2601d0 Build_Grid
       2e2601d0 Build_Grid
       2ded2050 start_cancel_box
       30e20250 eval
       2dfe7e50 PRF_Command_Start
       2dfea570 PRF_Node_repl
       2dff5fc0 Delay_Error
       30e35a20 logical_right_shift
       92c07330 BaseThreadInitThunk
       93522690 RtlUserThreadStart
       
      Error [node 0] [time 12/6/23 17:53:4] Abnormal Exit!
       
       

       

       

    • Federico
      Ansys Employee

      The fluent-n-error files are error logs for each CPU used. 

      For the original question, does this error always occur at the same iteration?

      • Yiqing zhang
        Subscriber

        These errors arise when the case is opened. After successfully completing calculations on one computer, upon transitioning to another computer to continue the computation, the issue is encountered upon opening the case. However, other cases listed on this computer do not exhibit this problem.

        • Federico
          Ansys Employee

          Are you using the same version between machines?

          The first screenshot you shared suggests that the issue does not arise when opening the case. The simulation is running.

        • Yiqing zhang
          Subscriber

          I previously performed calculations using the 2021R1 version of Fluent. Subsequently, I attempted to use either the 2022R1 or 2023R1 versions of Fluent, but encountered issues as neither of these versions could be opened. Is it possible that this problem arises from the fact that I initially used a computer with an AMD processor and later switched to a computer with an Intel processor?The error that appeared in the first screenshot has been resolved. This is the second occurrence, happening when I transferred the calculations to another computer to continue the process.

        • Federico
          Ansys Employee

          That is possible. I suggest you make a new dedicated post for this issue, since the original problem is resolved.

Viewing 3 reply threads
  • The topic ‘BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES’ is closed to new replies.