Forrtl: severe <157> : program exception -access violation MCNP6

  • Thread starter Thread starter khary23
  • Start date Start date
  • Tags Tags
    Mcnp6 Program
Click For Summary

Discussion Overview

The discussion revolves around an error encountered while running MCNP6, specifically a "forrtl: severe <157> : program exception -access violation." Participants are exploring potential causes for this error, which may relate to coding issues or system configurations.

Discussion Character

  • Technical explanation
  • Debate/contested
  • Exploratory

Main Points Raised

  • One participant reports intermittent access violation errors when running MCNP6 and seeks assistance in diagnosing the issue.
  • Another participant notes a separate error message indicating that 'MNCP' is not recognized, suggesting a possible typographical error in command input.
  • Some participants speculate that the access violation could stem from the program attempting to access invalid memory locations or incorrect subroutine arguments.
  • There is a suggestion to check the code for the specific line where the error occurs, particularly focusing on the output value of cp0.
  • One participant expresses uncertainty about the meaning of cp0 and seeks clarification on its significance in the context of their code.
  • Another participant points out potential issues in the input file, such as duplicate material listings and incorrect fractional amounts for materials, which could contribute to the error.
  • Some participants emphasize the need for the original poster to share their code for more targeted assistance.

Areas of Agreement / Disagreement

Participants do not reach a consensus on the cause of the error, as multiple hypotheses are presented regarding potential coding mistakes and system issues. There is also disagreement on the correct spelling of the program name, with some insisting it should be MCNP6 while others mistakenly refer to it as MNCP.

Contextual Notes

Participants note that the original poster has not provided sufficient information about their code or the specific circumstances under which the error occurs. There are also indications that the problem may have arisen after recent changes, though the exact nature of those changes is unclear.

Who May Find This Useful

This discussion may be useful for users of MCNP6 experiencing similar access violation errors, as well as those interested in troubleshooting coding issues related to Fortran programs.

  • #31
MCNP, you are a thing.

If I run your case on MCNP6.1 I get Windows telling me MCNP has stopped working.

If I use a smaller NPS number, say 400000 instead of 1000000, then it runs to completion.
If I take out the DE4-DF4 data, it runs to completion.

I'm thinking a bug in version 6.1, some kind of memory overflow that only shows up when you reach some kind of limit in FMESH.

Is it an option to step up to version 6.2?
 
Engineering news on Phys.org
  • #32
DEvens said:
MCNP, you are a thing.

If I run your case on MCNP6.1 I get Windows telling me MCNP has stopped working.

If I use a smaller NPS number, say 400000 instead of 1000000, then it runs to completion.
If I take out the DE4-DF4 data, it runs to completion.

I'm thinking a bug in version 6.1, some kind of memory overflow that only shows up when you reach some kind of limit in FMESH.

Is it an option to step up to version 6.2?

I submitted a request for 6.2 last night, but I need to get my data in the next week so that I can write and be finished by January. The confusing thing is that it was running up until Friday.
 
  • #33
Hi
I thing the bug only appears why you try to use a x-windows no ?
 
  • #34
PSRB191921 said:
Hi
I thing the bug only appears why you try to use a x-windows no ?

Using MSWindows here. It hangs.
 
  • #35
PSRB191921 said:
Hi
I thing the bug only appears why you try to use a x-windows no ?

No regular Windows 10
 
  • Like
Likes   Reactions: DEvens
  • #36
khary23 said:
No regular Windows 10
I think s/he meant using some version of Windows.
 
  • #37
WWGD said:
I think s/he meant using some version of Windows.
X-Windows is a unix/linux thing. I have tested entirely on Microsoft Windows based computer and it crashes.
 
  • #38
DEvens said:
X-Windows is a unix/linux thing. I have tested entirely on Microsoft Windows based computer and it crashes.
My bad, maybe I can delete my post.
 
  • #39
Met with someone form our ITS department and he thinks it's one of three issues. Memory allocation, read/write or access/permission.
 

Similar threads

  • · Replies 5 ·
Replies
5
Views
3K
  • · Replies 11 ·
Replies
11
Views
2K
  • · Replies 9 ·
Replies
9
Views
16K
  • · Replies 19 ·
Replies
19
Views
2K
  • · Replies 6 ·
Replies
6
Views
3K
  • · Replies 5 ·
Replies
5
Views
3K
  • · Replies 2 ·
Replies
2
Views
5K
  • · Replies 5 ·
Replies
5
Views
4K
  • · Replies 4 ·
Replies
4
Views
2K
  • Sticky
  • · Replies 48 ·
2
Replies
48
Views
68K