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

  • Thread starter Thread starter khary23
  • Start date Start date
  • Tags Tags
    Mcnp6 Program
Click For Summary
The user encountered a "forrtl: severe <157>: program exception - access violation" error while running MCNP6, which stopped their runs. They also faced a command recognition issue with 'MNCP', indicating potential spelling errors in command input. Suggestions included checking the input file for errors, particularly duplicate material definitions, and ensuring correct paths and installation of MCNP. After reinstalling MCNP6, the user reported that the program now runs but the results are unexpected, prompting further discussion about the input file's material definitions. The conversation highlights the importance of debugging input files and verifying command accuracy in MCNP.
  • #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 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
67K