AI Assistant
forrtl: severe (157...
 
Notifications
Clear all

forrtl: severe (157): Program Exception - access violation (LS-DYNA)

3 Posts
3 Users
0 Reactions
8,566 Views
Posts: 1
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@edeplessness)
Unpaid Intern
Joined: 5 years ago
[#259]

Hello, everyone

I took this error when i run a numerical model about compression after impact of composites. I read to possible solutions to solve this error (possible contact problems etc.) but i could not solve. If anyone can help me, i will be so gratitude for this.

 error

Topic Tags
2 Replies




Negative Volume
Posts: 681
Admin
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@negativevolume)
CEO
Joined: 8 years ago

Hi @edeplessness

This is a commonly discussed issue here. I'm just going to like a topic that links to other topics which may help you. 

If none of that helps, feel free to ask more questions. 

https://feassistant.com/forums/ls-dyna/error-severe-157-program-exception-access-violation/#post-643


Reply




Posts: 1
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@kerwin2222)
Unpaid Intern
Joined: 4 years ago

Hi edeplessness,

 

I am simulating compression after impact of composites as well and encountered the same error when restarting the compression analysis. Have you figured out the cause of this issue?


Reply







Share: