*** PCL Win32 System Exception: At address 00007FFA6E9E663E

Astrostar

Astrostar

Member
I'm running PI Core version 1.8.8-7 x64 (2020-12-17) on the latest instance of Win 10 Pro (x64) an MSI i3 CPU desktop.

This morning I had previously been opening/closing FIT files using the format convertor script as well as the blink process to make an AVI file. I then had one FIT file open to look at its header details. When I closed the header viewer followed by the file, I noticed the following exception indicated in the process console:

Opening 1 file(s):
C:/Users/Study/OneDrive/Share/Project Argus 2/20210218-19 Intelsat 10-02 MEV2/QSI 683 Dataset 4/Intelsat_10-02_MEV2_Lum_10sec_2x2_00127_c.fit
** Warning: Deprecated format: FITS
69 FITS keywords extracted.
Reading FITS image: 32-bit floating point, 1 channel(s), 1663x1252 pixels: done
*** PCL Win32 System Exception: At address 00007FFA6E9E663E with exception code C0000005 :
Access violation: invalid memory read operation at address 000000276E68ACC0

*** Backtrace Information ***
================================================================================
0: in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x0
1: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xAB721150
2: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xAB721150
3: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xAB721150
4: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xAB721150
5: _CxxFrameHandler4 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xAB724040
6: _chkstk in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xB83F1860
7: RtlRaiseException in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xB839B320
8: KiUserExceptionDispatcher in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xB83F0480
9: QImageData::~QImageData in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x6E9E65C0
10: QImage::~QImage in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x6E9E6560
11: QRasterPlatformPixmap::~QRasterPlatformPixmap in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x6EA11050
12: QRasterPlatformPixmap::~QRasterPlatformPixmap in module: C:\Program Files\PixInsight\bin\qt-plugins\platforms\qwindows.dll at address: 0x6EA11050
13: QRasterPlatformPixmap::~QRasterPlatformPixmap at address: 0x6EA11050
14: QRasterPlatformPixmap::~QRasterPlatformPixmap at address: 0x6EA11050
15: QRasterPlatformPixmap::~QRasterPlatformPixmap at address: 0x6EA11050
16: RtlFreeHeap in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xB8365E40
17: QPixmapCache:?:eek:perator= in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x6EA0E010
18: QPixmapCache::totalUsed in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x6EA10060
19: QPixmapCache::find in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x6EA0EC90
20: QPixmapCache::setCacheLimit in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x6EA0FF50
21: QObject::event in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0x6E58A300
22: QApplicationPrivate::notify_helper in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0x74EF4B10
23: QApplication::notify in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0x74EF23F0
24: QApplication::notify in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x74EF23F0
25: QCoreApplication::notifyInternal2 in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0x6E5638C0
26: QEventDispatcherWin32Private::sendTimerEvent in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0x6E5AE150
27: QEventDispatcherWin32::processEvents in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0x6E5AC870
28: CallWindowProcW in module: C:\WINDOWS\System32\USER32.dll at address: 0xB7D3E460
29: DispatchMessageW in module: C:\WINDOWS\System32\USER32.dll at address: 0xB7D3E040
30: QEventDispatcherWin32::processEvents in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0x6E5AC870
31: QEventDispatcherWin32::processEvents in module: C:\Program Files\PixInsight\bin\qt-plugins\platforms\qwindows.dll at address: 0x6E5AC870
32: QEventDispatcherWin32::processEvents at address: 0x6E5AC870
========================================================================
[UNQUOTE]

This, I'm sure, will mean more to you than it does me. PI continued to run but as a precaution I closed and re-started the application.
Regards
Click to expand...
 
This cannot be reproduced. This crash is not a PixInsight bug. Check your graphics drivers and make sure you have the latest versions installed. Also consider a complete, clean reinstall of your operating system.

9: QImageData::~QImageData in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x6E9E65C0

The crash is happening in a routine that cannot fail under normal working conditions. QImageData::~QImageData belongs to the Qt library, and the probability that such a fundamental routine can contain a bug is so small that this crash can be regarded as a machine-specific issue, unless you can provide a repeatable pattern or a data set where the same problem can be reproduced consistently.
 
I have the same issue as above. This is confirmed not a windows or machine problem.

This only happens when I use the PI BLINK module. This has also happened on two prior PI releases and on two different Windows 64-bit OS's machines. This does not happen all the time. I verified on a vanilla start with no other other processes running.

All drivers and system files are current and up-to-date.


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

I have a complete Windows event error log which it says it's an appliction error below this PI backtrace information

*** Backtrace Information *** (from process console)

================================================================================

0: O in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x0

1: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xF2461150

2: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xF2461150

3: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xF2461150

4: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xF2461150

5: _CxxFrameHandler4 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xF2464040

6: _chkstk in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xF74F1860

7: RtlRaiseException in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xF749B320

8: KiUserExceptionDispatcher in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xF74F0480

9: QImageData::~QImageData in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0xAA5D65C0

10: QImage::~QImage in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0xAA5D6560

11: QRasterPlatformPixmap::~QRasterPlatformPixmap in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0xAA601050

12: QRasterPlatformPixmap::~QRasterPlatformPixmap in module: C:\Program Files\PixInsight\bin\qt-plugins\platforms\qwindows.dll at address: 0xAA601050

13: QRasterPlatformPixmap::~QRasterPlatformPixmap at address: 0xAA601050

14: QRasterPlatformPixmap::~QRasterPlatformPixmap at address: 0xAA601050

15: QRasterPlatformPixmap::~QRasterPlatformPixmap at address: 0xAA601050

16: RtlFreeHeap in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xF7465E40

17: QPixmapCache:?:eek:perator= in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0xAA5FE010

18: QPixmapCache::totalUsed in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0xAA600060

19: QPixmapCache::find in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0xAA5FEC90

20: QPixmapCache::setCacheLimit in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0xAA5FFF50

21: QObject::event in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0xA7E0A300

22: QApplicationPrivate::notify_helper in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0xAABE4B10

23: QApplication::notify in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0xAABE23F0

24: QApplication::notify in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0xAABE23F0

25: QCoreApplication::notifyInternal2 in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0xA7DE38C0

26: QEventDispatcherWin32Private::sendTimerEvent in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0xA7E2E150

27: QEventDispatcherWin32::processEvents in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0xA7E2C870

28: CallWindowProcW in module: C:\WINDOWS\System32\USER32.dll at address: 0xF665E460

29: DispatchMessageW in module: C:\WINDOWS\System32\USER32.dll at address: 0xF665E040

30: QEventDispatcherWin32::processEvents in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0xA7E2C870

31: QEventDispatcherWin32::processEvents in module: C:\Program Files\PixInsight\bin\qt-plugins\platforms\qwindows.dll at address: 0xA7E2C870

32: QEventDispatcherWin32::processEvents at address: 0xA7E2C870

================================================================================

The following is from the Windows event viewer

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-02-24T16:20:06.2870738Z" />
<EventRecordID>8632</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>******</Computer> (named removed)
<Security />
</System>
- <EventData>
<Data>PixInsight.exe</Data>
<Data>1.8.8.7</Data>
<Data>5fdb8c78</Data>
<Data>KERNELBASE.dll</Data>
<Data>10.0.19041.804</Data>
<Data>0e9c5eae</Data>
<Data>c0000602</Data>
<Data>000000000010bd5c</Data>
<Data>3550</Data>
<Data>01d70ac8bd6f89f2</Data>
<Data>C:\Program Files\PixInsight\bin\PixInsight.exe</Data>
<Data>C:\WINDOWS\System32\KERNELBASE.dll</Data>
<Data>a393e02e-9a67-42b4-8e85-97d643a3a414</Data>
<Data />
<Data />
</EventData>
</Event>
 

Attachments

  • PI error.jpg
    PI error.jpg
    346.1 KB · Views: 80
Today I experienced another instance of the memory violation, but under slightly different circumstances to my initial report.

Having successfully using 'Blink' to review 225 frames, each 4.073 KB FITs, I then used the 'Close all images' button to conclude the use of 'Blink'. At which time the 'Process Console' report a memory access violation, as detailed in the back trace information given below:

* Blink: Releasing memory...
*** PCL Win32 System Exception: At address 00007FFF59B3663E with exception code C0000005 :
Access violation: invalid memory read operation at address 00000027597DACC0

*** Backtrace Information ***
================================================================================
0: in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x0
1: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0x9B391150
2: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0x9B391150
3: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0x9B391150
4: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0x9B391150
5: _CxxFrameHandler4 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0x9B394040
6: _chkstk in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xA59D1860
7: RtlRaiseException in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xA597B320
8: KiUserExceptionDispatcher in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xA59D0480
9: QImageData::~QImageData in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x59B365C0
10: QImage::~QImage in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x59B36560
11: QImage::~QImage in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x59B36560
12: QImage::~QImage in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x59B36560
13: QImage::~QImage in module: C:\Program Files\PixInsight\bin\Blink-pxm.dll at address: 0x59B36560
14: QImage::~QImage in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x59B36560
15: QImage::~QImage at address: 0x59B36560
16: QImage::~QImage at address: 0x59B36560
================================================================================
 
I'm running the same PC standard as in my initial report, i.e. PI Core version 1.8.8-7 x64 (2020-12-17) under the latest instance of Win 10 Pro (x64) on a MSI i3 duel core CPU desktop.

After experiencing repeated PI memory access violation reports, and having to then re-start the PC due to it destabilising other applications, e.g. Outlook 365, etc, typically causing them to report 'Not Responding', or the PC going into serious snails pace, herewith is the latest example of text from the Process Console:

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

*** Backtrace Information ***
================================================================================
0: in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x0
1: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xDCCA1150
2: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xDCCA1150
3: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xDCCA1150
4: _NLG_Return2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xDCCA1150
5: _CxxFrameHandler4 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0xDCCA4040
6: _chkstk in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xE6A91E50
7: RtlRaiseException in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xE6A41020
8: KiUserExceptionDispatcher in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xE6A90A70
9: QImageData::~QImageData in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x9B4F65C0
10: QImage::~QImage in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x9B4F6560
11: QRasterPlatformPixmap::~QRasterPlatformPixmap in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x9B521050
12: QRasterPlatformPixmap::~QRasterPlatformPixmap in module: C:\Program Files\PixInsight\bin\qt-plugins\platforms\qwindows.dll at address: 0x9B521050
13: QRasterPlatformPixmap::~QRasterPlatformPixmap at address: 0x9B521050
14: QRasterPlatformPixmap::~QRasterPlatformPixmap at address: 0x9B521050
15: QRasterPlatformPixmap::~QRasterPlatformPixmap at address: 0x9B521050
16: RtlFreeHeap in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0xE6A14760
17: QPixmapCache:?:eek:perator= in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x9B51E010
18: QPixmapCache::totalUsed in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x9B520060
19: QPixmapCache::find in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x9B51EC90
20: QPixmapCache::setCacheLimit in module: C:\Program Files\PixInsight\bin\Qt5Gui.dll at address: 0x9B51FF50
21: QObject::event in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0x9AB3A300
22: QApplicationPrivate::notify_helper in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0x9AF24B10
23: QApplication::notify in module: C:\Program Files\PixInsight\bin\Qt5Widgets.dll at address: 0x9AF223F0
24: QApplication::notify in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x9AF223F0
25: QCoreApplication::notifyInternal2 in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0x9AB138C0
26: QEventDispatcherWin32Private::sendTimerEvent in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0x9AB5E150
27: QEventDispatcherWin32::processEvents in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0x9AB5C870
28: CallWindowProcW in module: C:\WINDOWS\System32\USER32.dll at address: 0xE5BFE460
29: DispatchMessageW in module: C:\WINDOWS\System32\USER32.dll at address: 0xE5BFE040
30: QEventDispatcherWin32::processEvents in module: C:\Program Files\PixInsight\bin\Qt5Core.dll at address: 0x9AB5C870
31: QEventDispatcherWin32::processEvents in module: C:\Program Files\PixInsight\bin\qt-plugins\platforms\qwindows.dll at address: 0x9AB5C870
32: QEventDispatcherWin32::processEvents at address: 0x9AB5C870
================================================================================

The repeated stoppages are seriously undermining my use of what has up till now been the workhorse of all my image processing. I for one would be most disappointed in having to move away from using PI. :-(

I've heard tell that PI might not clear or release memory or its image cashe when it should; this may be true or purely anecdotal. What I do experience, however, is that if I've had an image open and run but then undone processes on it. When I close the image but still have PI running, I then cannot delete that image from within File Explorer, until after I've closed PI. This does seem to indicate that for whatever reason PI keeps closed image files locked in some way? If I then get this memory access violation problem and thus exit PI, those image file often remain locked until after a PC restart. There is obviously some inter-relationship going on in this regard.

I do hope this isn't regarded as 'not a PI issue', since clearly there is a real problem here albeit a difficult one to find the route cause of.
 
As noted above, this is a machine-specific issue unless you can provide a repeatable pattern or a data set where the same problem can be reproduced consistently. We cannot reproduce it on any of our working and testing machines under normal working conditions.

This might be a bug in your graphics driver, a problem caused by wrong or corrupted system components, or the result of a wrong interaction with some third-party application. We cannot know the reason because we cannot have control over it. I know this is not what you want to read, but we cannot solve a nontrivial problem that we cannot reproduce and understand.

I've heard tell that PI might not clear or release memory or its image cashe when it should; this may be true or purely anecdotal.
Click to expand...
This does seem to indicate that for whatever reason PI keeps closed image files locked in some way?
Click to expand...

Interesting. Again, none of these things have been demonstrated and/or reproduced under normal working conditions.
 
I did have this problem too, yesterday, on my windows laptop. During ImageIntegration. Running Windows 64, and latest update of PI.
*** PCL Win32 System Exception: At address 00007FFF9B4F663E with exception code C0000005 :
Access violation: invalid memory read operation at address 000000269AC3ACC0

(not exactly sure about the 000000269AC3ACC0)

Afterwards it did not happen again, although I worked a lot on the laptop with PI.


On my desktop, I presume it was not the same, as there I had this weekend three complete system crashes, using PI, with the Bug Check 0xBE: ATTEMPTED_WRITE_TO_READONLY_MEMORY

The desktop is a complete new system, new CPU, new disk, new windows.

I have a question running on that problem : https://pixinsight.com/forum/index.php?threads/memory-exhaustion-problems.16474/#post-99578
 
I did have this problem too, yesterday, on my windows laptop. During ImageIntegration. Running Windows 64, and latest update of PI.
*** PCL Win32 System Exception: At address 00007FFF9B4F663E with exception code C0000005 :
Access violation: invalid memory read operation at address 000000269AC3ACC0
Click to expand...

As noted above, this cannot be reproduced. This is a machine-specific issue.

On my desktop, I presume it was not the same, as there I had this weekend three complete system crashes, using PI, with the Bug Check 0xBE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Click to expand...

This one is completely different and has nothing to do with PixInsight. This is a system software problem:

docs.microsoft.com

Bug Check 0xBE ATTEMPTED_WRITE_TO_READONLY_MEMORY - Windows drivers

The ATTEMPTED_WRITE_TO_READONLY_MEMORY bug check has a value of 0x000000BE. This is issued if a driver attempts to write to a read-only memory segment.
docs.microsoft.com

So this problem is being caused by one of your device drivers.
 
You must log in or register to reply here.
Back
Top