Invalid memory read operation on two seperate windows machines

[mhellaby]

I'm running PI on two seperate windows 10 machines (Desktop and laptop)

Both have been running no issues for months then suddenly I'm getting and invalid memory read operation on several processes and scripts.

It is happening on both machines.

I've gone through some of the post on here and checked I have latests drivers for graphics card, updated to 1.8.8-5 but the issue still happens

Any suggestions really welcome

*** PCL Win32 System Exception: At address 00007FFCC2E7A78C with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000008

*** Backtrace Information ***
================================================================================
  0: KiUserExceptionDispatcher in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x2085FE40
  1: _C_specific_handler in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x14F9B860
  2: is_exception_typeof in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x14F922E0
  3: is_exception_typeof in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x14F922E0
  4: is_exception_typeof in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x14F922E0
  5: _CxxFrameHandler3 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x14F9C100
  6: _chkstk in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0x208610E0
  7: RtlRaiseException in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0x20829EF0
  8: KiUserExceptionDispatcher in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0x2085FE40
  9: KiUserExceptionDispatcher in module: C:\Program Files\PixInsight\bin\ImageCalibration-pxm.dll at address: 0x2085FE40

[mhellaby]

Just as a follow up - there are a few people mentioning this on a Facebook PI group - it seems to be linked to the integration step either within WBPP or when run as a separate process

[Juan Conejero]

I have not been able to reproduce this problem after many intensive tests. However, the '0000000000000008' access violation error is similar to the same problem that was reproducible in version 1.8.8-4 after recent Windows updates. This problem has been avoided in version 1.8.8-5, although obviously not completely, as this report demonstrates.

There is little more I can do to prevent these problems from happening for now. These access violations don't originate from our code, and there is no way to reproduce them consistently. This does not happen on FreeBSD, Linux and macOS executing exactly the same code, and most of the time it doesn't happen on Windows either. I am very sorry for these issues, and will keep doing my best trying to solve them. For maximum stability and performance, I recommend running PixInsight 1.8.8-5 on Linux.

[mhellaby]

Thanks for your reply I guess it’s just bad luck that it’s happening on both of my machines - I’ll have a read up to see what I can do Linux wise on my PC if not I do have an older Mac laptop just a pain when I set up a high spec windows device purely for PI and processing