Author Topic: At address 00007FFA42C97788 with exception code C0000005 : Access violation: inv  (Read 1767 times)

Offline Mick G

  • Newcomer
  • Posts: 26
pixinsight locked up and I got an error message that there was a problem and to report it on the forum.  Something about swapping files.  Then the following error came up "At address 00007FFA42C97788 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000018"  and that I could loose data.

There is also a sign "Please Wait Reading swap files" that is on any place I go on the computer , internet, Word etc.

What should I do???

Mick Groszko
« Last Edit: 2017 February 21 17:19:33 by Mick G »

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Hi Mick,

This may be caused by a sporadic file write error. It's very strange and not reproducible. Can you reproduce it on your machine?
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline zbadger

  • Newcomer
  • Posts: 21
I just received the same message.  Doing a search, it seems like a lot of people have run into this issue.  I am using Windows 10 64 bit and was in the process of using the clone stamp on a cloned image when it occurred.  Now I am stopped cold.

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Are you using a high-dpi touch screen? See this post for a solution to this problem:

https://pixinsight.com/forum/index.php?topic=11053.0

Let me know if this helps.
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline zbadger

  • Newcomer
  • Posts: 21
No - this is a Dell screen with mouse and associated ZT desktop.  No touchscreen.  Just happened again with Clone Stamp.  No other crashes with Pixinsight.

Offline zbadger

  • Newcomer
  • Posts: 21
Juan - I decided to move the file from my desktop to my 1 year old laptop.  The clone stamp did work on one dust moot and executed!  However, when I moved to a second dust moot, I received the C00000005 error on this laptop with the message "invalid memory read operation at address FFFFFFFF8"   So it can't just be my computer if it failed on both my desktop and not my laptop (also not a touch screen).