Author Topic: Error with Last Pixinsight 1.8.8-3  (Read 2111 times)

Offline JCPHILIPPE

  • Newcomer
  • Posts: 1
Error with Last Pixinsight 1.8.8-3
« on: 2020 January 05 01:35:54 »
Hi
Before last update i never had bug or crash with PI /

Below with an image integration minimum :

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

*** Backtrace Information ***
================================================================================
  0: RtlCaptureContext in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x163E00E0
  1: _C_specific_handler in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x1F9B860
  2: is_exception_typeof in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x1F922E0
  3: is_exception_typeof in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x1F922E0
  4: is_exception_typeof in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x1F922E0
  5: _CxxFrameHandler3 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x1F9C100
  6: _chkstk in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0x163E10E0
  7: RtlRaiseException in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0x163A9EF0
  8: RtlRaiseException in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0x163A9EF0
  9: RaiseException in module: C:\WINDOWS\System32\KERNELBASE.dll at address: 0x134EA7D0
 10: is_exception_typeof in module: C:\Program Files\PixInsight\bin\VCRUNTIME140.dll at address: 0x1F922E0
 11: RtlCaptureContext in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0x163E00E0
 12: RtlCaptureContext in module: C:\Program Files\PixInsight\bin\ImageIntegration-pxm.dll at address: 0x163E00E0
 13: RtlCaptureContext at address: 0x163E00E0
================================================================================
<* failed *>

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: Error with Last Pixinsight 1.8.8-3
« Reply #1 on: 2020 January 05 03:32:52 »
This cannot be reproduced on any platform, on any of our working and testing machines. This has not been reported before either.

Which Windows version are you using? Can you please provide a data set where this problem can be reproduced?
Juan Conejero
PixInsight Development Team
http://pixinsight.com/

Offline astrocaller1@gmail.com

  • Newcomer
  • Posts: 1
Re: Error with Last Pixinsight 1.8.8-3
« Reply #2 on: 2020 January 28 14:05:29 »
Im having the same issue! only had this since my update to 1.8.8.4, I see a lot of people complaining online since they updated, i see comments from PT team about graphics card , etc however I don't use my graphics card, which I disagree with, my PC specification as followed.

i9 900K(5Ghz)
64Gb Ram
Windows 10 Professional.

iv lost my project twice since Sunday, thats many hours of processing gone 

Offline Juan Conejero

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 7111
    • http://pixinsight.com/
Re: Error with Last Pixinsight 1.8.8-3
« Reply #3 on: 2020 January 29 04:00:02 »
Quote
i9 900K(5Ghz)

I assume your machine uses an Intel Core i9-9900K processor. You are always using a graphics adapter on any machine where you get graphics output. If you have disabled the discrete graphics card in your computer, then you are using the Intel UHD Graphics 630 adapter integrated in your processor.

Integrated Intel (U)HD graphics drivers have been causing many problems on Windows with the latest versions of PixInsight, basically since version 1.8.6 of the core application, for a variety of reasons. This may include bad OpenGL implementations, wrong Windows OpenGL support, and lack of standards compliance that cause incompatibilities with some Qt components. Most of these problems get fixed by simply installing the latest versions of the Intel HD graphics drivers available for Windows 10. Another, more effective way to solve most of these problems is disabling the integrated Intel graphics adapter (at the BIOS level, preferably) and using a discrete graphics card (NVIDIA, AMD, ...). There are more, much more efficient ways to solve all of these issues, but are not what Windows users normally want to hear.

Anyway, the OP has reported a backtrace that does not correspond, at least directly, to graphics issues. It shows a completely different problem, which is being triggered by the ImageIntegration process, and is related to memory access. Such problem cannot be reproduced under normal working conditions, and we have not received other similar reports.
Juan Conejero
PixInsight Development Team
http://pixinsight.com/