Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • "Instruction referenced memory that could not be written. Stata MP2 crashes

    Hi there

    i'm running the -traj- command on stata 14MP2 on a windows box, and i can successfully run a command for a 2-group 3-group and 4 group model, but the (interesting) 5,6,7,and 8 group models are crashing. I have successfully run the code on a sample of 300,000 obs, but now want to run it for 2.5m obs.

    I get an error:

    The instruction at 0xec01790c referenced memory at 0x0000000. The memory could not be written. Click on OK to terminate the program.


    and then Stata 14 MP2 crashes.

    Can anybody suggest ways to reduce this error? Is it a case of needing more RAM to allow the swap-space to write the trajectories, or is there something odd that i need to re-configure? I have reduced the file by deleting redundant fields and using -compress-.

    Interestingly I get this error regardless of whether the program runs on Stata 14 MP installed on a windows 2012 server, or windows 7 machine. The 32gb RAM, and nothing notably running. Files are running from the local drive, rather than across a network.
    Many thanks
    Dan
    Last edited by dan exeter; 20 Nov 2016, 01:00. Reason: Added tags to the list

  • #2
    This is called a null pointer exception, and it is probably a bug in the plugin. Since the plugin isn't from Statacorp, and source for the plugin doesn't seem to be online, you are probably out of luck. The author of the program might be interested in bug reports, or might send you source, but you might consider dividing your data in some way, such as male/female in separate estimations. Still, I would wonder if the bug affected results even when it didn't cause a crash. There is quite a bit of advice on fixing this kind of bug at:

    thttp://stackoverflow.com/questions/2...ow-do-i-fix-it

    but it would require knowledge of the underlying compiler language. There appears to be a SAS version, which might not have the same bug, if you can use that.

    Comment

    Working...
    X