How to resolve the crash during simulation?

64 views
Skip to first unread message

SUMAN KUMAR

unread,
Sep 24, 2024, 1:06:57 AM9/24/24
to LS-DYNA2
Dear all,

I frequently get this kind of error where the program is crashed and prematurely closed. For your reference, a screenshot is attached. Further, for similar models, the program is normally terminating; however, for a few, it is crashing. Are there any possible suggestions/guidance/ remedial measures available? This will be of great help.

Thank you,
 Suman Kumar

SUMAN KUMAR

unread,
Sep 24, 2024, 1:08:04 AM9/24/24
to LS-DYNA2
Sorry I forget to attach the screenshot. Please find attached here.

Thank you,
Screenshot 2024-09-24 103038.png

James Kennedy

unread,
Sep 24, 2024, 11:23:03 AM9/24/24
to SUMAN KUMAR, LS-DYNA2

Dear Suman,,

 

Access violation 157 is usually due to some kind of memory read/write error. For this

situation, I would suggest contacting your distributor or LSTC support. Of particular

importance, is, please send the model to debug.

 

Sincerely,

James M. Kennedy

KBS2 Inc.

September 24, 2024

 

p.s. Some other thoughts.

 

https://www.researchgate.net/post/How-to-fix-error-forrtl-severe-157-Program-Exception-access-violation-when-use-LS-DYNA-Solver-in-Ansys

 

https://forum.ansys.com/forums/topic/forrtl-severe-157-program-exception-access-violation/

--
You received this message because you are subscribed to the Google Groups "LS-DYNA2" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ls-dyna2+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ls-dyna2/42dcc49d-ad30-46d8-abe8-c54ee14ed210n%40googlegroups.com.

KAĞAN GENÇ

unread,
Sep 25, 2024, 11:08:14 AM9/25/24
to SUMAN KUMAR, LS-DYNA2
Dear Suman,

That's a mysterious error that many users encounter. Therefore, it is not possible to guess where the problem might be without having the story of your problem. I suggest you first tell the story of your model: I am sure some users ın the group have already experienced this error. I also had this error a couple of times. My suggestion is to focus on your contact algorithms since that was the case when I got this error. To solve this kind of problem, I always create simple sub-models to identify which key card causes the problem. After the identification, you can work more on the root cause. That is not an exact answer maybe but I hope it guides you. 

Kind regards

Kagan

SUMAN KUMAR <sum92...@gmail.com>, 24 Eyl 2024 Sal, 07:08 tarihinde şunu yazdı:
--
Reply all
Reply to author
Forward
0 new messages