-
-
November 20, 2023 at 2:53 am
Yiqing zhang
SubscriberI 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
-
November 20, 2023 at 1:23 pm
Federico
Ansys EmployeeOnce 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.
-
December 6, 2023 at 12:00 pm
Yiqing zhang
SubscriberHello, 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 fault30d93010 CX_Primitive_Error90e20cc0 seh_filter_exe30e35a20 logical_right_shift7217eb20 _C_specific_handler93572290 _chkstk93521030 RtlRaiseException93570e90 KiUserExceptionDispatcher2e27d930 Dump_Dataship_new2e2601d0 Build_Grid2e2601d0 Build_Grid2ded2050 start_cancel_box30e20250 eval2dfe7e50 PRF_Command_Start2dfea570 PRF_Node_repl2dff5fc0 Delay_Error30e35a20 logical_right_shift92c07330 BaseThreadInitThunk93522690 RtlUserThreadStartError [node 0] [time 12/5/23 21:44:1] Abnormal Exit!Node 0 Fatal signal raised sig = Segmentation fault30d93010 CX_Primitive_Error90e20cc0 seh_filter_exe30e35a20 logical_right_shift7217eb20 _C_specific_handler93572290 _chkstk93521030 RtlRaiseException93570e90 KiUserExceptionDispatcher2e27d930 Dump_Dataship_new2e2601d0 Build_Grid2e2601d0 Build_Grid2ded2050 start_cancel_box30e20250 eval2dfe7e50 PRF_Command_Start2dfea570 PRF_Node_repl2dff5fc0 Delay_Error30e35a20 logical_right_shift92c07330 BaseThreadInitThunk93522690 RtlUserThreadStartNode 0 Fatal signal raised sig = Segmentation fault8e677b80 CX_Primitive_Error90e20cc0 seh_filter_exe8e71abb0 logical_right_shift7217eb20 _C_specific_handler93572290 _chkstk93521030 RtlRaiseException93570e90 KiUserExceptionDispatcher8be1b570 Dump_Dataship_new8be02460 Build_Grid8be02460 Build_Grid8bb42130 Get_Network_Nb8e706080 eval8bc687a0 PRF_Command_Start8bc6afc0 PRF_Node_repl8bc6b890 init_rsubrs8e71abb0 logical_right_shift92c07330 BaseThreadInitThunk93522690 RtlUserThreadStartError [node 0] [time 12/5/23 21:48:28] Abnormal Exit!Node 0 Fatal signal raised sig = Segmentation fault8e677b80 CX_Primitive_Error90e20cc0 seh_filter_exe8e71abb0 logical_right_shift7217eb20 _C_specific_handler93572290 _chkstk93521030 RtlRaiseException93570e90 KiUserExceptionDispatcher8be1b570 Dump_Dataship_new8be02460 Build_Grid8be02460 Build_Grid8bb42130 Get_Network_Nb8e706080 eval8bc687a0 PRF_Command_Start8bc6afc0 PRF_Node_repl8bc6b890 init_rsubrs8e71abb0 logical_right_shift92c07330 BaseThreadInitThunk93522690 RtlUserThreadStartError [node 0] [time 12/5/23 21:50:29] Abnormal Exit!Node 0 Fatal signal raised sig = Segmentation fault30d93010 CX_Primitive_Error90e20cc0 seh_filter_exe30e35a20 logical_right_shift7217eb20 _C_specific_handler93572290 _chkstk93521030 RtlRaiseException93570e90 KiUserExceptionDispatcher2e27d930 Dump_Dataship_new2e2601d0 Build_Grid2e2601d0 Build_Grid2ded2050 start_cancel_box30e20250 eval2dfe7e50 PRF_Command_Start2dfea570 PRF_Node_repl2dff5fc0 Delay_Error30e35a20 logical_right_shift92c07330 BaseThreadInitThunk93522690 RtlUserThreadStartError [node 0] [time 12/5/23 21:53:30] Abnormal Exit!Node 0 Fatal signal raised sig = Segmentation fault30d93010 CX_Primitive_Error90e20cc0 seh_filter_exe30e35a20 logical_right_shift7217eb20 _C_specific_handler93572290 _chkstk93521030 RtlRaiseException93570e90 KiUserExceptionDispatcher2e27d930 Dump_Dataship_new2e2601d0 Build_Grid2e2601d0 Build_Grid2ded2050 start_cancel_box30e20250 eval2dfe7e50 PRF_Command_Start2dfea570 PRF_Node_repl2dff5fc0 Delay_Error30e35a20 logical_right_shift92c07330 BaseThreadInitThunk93522690 RtlUserThreadStartError [node 0] [time 12/6/23 17:53:4] Abnormal Exit! -
December 6, 2023 at 1:27 pm
Federico
Ansys EmployeeThe fluent-n-error files are error logs for each CPU used.
For the original question, does this error always occur at the same iteration?
-
December 7, 2023 at 8:00 am
Yiqing zhang
SubscriberThese 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.
-
December 7, 2023 at 2:10 pm
Federico
Ansys EmployeeAre 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.
-
December 9, 2023 at 10:36 am
Yiqing zhang
SubscriberI 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.
-
December 11, 2023 at 1:04 pm
Federico
Ansys EmployeeThat is possible. I suggest you make a new dedicated post for this issue, since the original problem is resolved.
-
-
-
- The topic ‘BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES’ is closed to new replies.
-
2788
-
965
-
851
-
599
-
591
© 2025 Copyright ANSYS, Inc. All rights reserved.