Anyone seen anything like this before?
306 active files in an Integration but no master file generated???
306 active files in an Integration but no master file generated???
WBPP Weirdness.
Check the log file, your answer will likely be in there.
This hiccup is not a major one though, you can simply load up the ImageIntegration process, load the files from the registered folder and hit go.
This hiccup is not a major one though, you can simply load up the ImageIntegration process, load the files from the registered folder and hit go.
[2025-07-31 00:38:48] Integration of 306 images:
[2025-07-31 00:38:48] Pixel combination .................. Average
[2025-07-31 00:38:48] Output normalization ............... Local
[2025-07-31 00:38:48] Weighting mode ..................... PSF Signal Weight
[2025-07-31 00:38:48] Scale estimator .................... Biweight midvariance
[2025-07-31 00:38:48] Range rejection .................... range_low=0.000000
[2025-07-31 00:38:48] Pixel rejection .................... Linear fit clipping
[2025-07-31 00:38:48] Rejection normalization ............ Local
[2025-07-31 00:38:48] Rejection clippings ................ low=yes high=yes
[2025-07-31 00:38:48] Rejection parameters ............... lfit_low=5.000 lfit_high=3.500
[2025-07-31 00:38:49]
[2025-07-31 00:38:49] * Available physical memory: 72.160 GiB
[2025-07-31 00:38:49] * Allocated pixel buffer: 2180 rows, 9.582 GiB
[2025-07-31 00:38:49] * Using 2180 concurrent pixel stack(s), 38.392 GiB
[2025-07-31 00:38:49]
[2025-07-31 00:38:49] Integrating pixel rows: 0 -> 2179: 60%
[2025-07-31 00:40:08] *** PCL Win32 System Exception: At address 00007FFA56E39F0A with exception code C0000005 :
[2025-07-31 00:40:08] Access violation: invalid memory read operation at address 0000000000000000
[2025-07-31 00:40:08]
[2025-07-31 00:40:08] *** Backtrace Information ***
[2025-07-31 00:40:08] ================================================================================
[2025-07-31 00:40:08] 0: RtlCaptureContext2 in module: C:\Program Files\PixInsight\bin\PixInsight.exe at address: 0x59D067B0
[2025-07-31 00:40:08] 1: RtlCaptureContext2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0x59D067B0
[2025-07-31 00:40:08] 2: RtlCaptureContext2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0x59D067B0
[2025-07-31 00:40:08] 3: RtlCaptureContext2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0x59D067B0
[2025-07-31 00:40:08] 4: RtlCaptureContext2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0x59D067B0
[2025-07-31 00:40:08] 5: RtlCaptureContext2 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0x59D067B0
[2025-07-31 00:40:08] 6: _CxxFrameHandler4 in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0x3E033F70
[2025-07-31 00:40:08] 7: _chkstk in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0x59D46610
[2025-07-31 00:40:08] 8: RtlWow64GetCurrentCpuArea in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0x59C690C0
[2025-07-31 00:40:08] 9: RtlRaiseException in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0x59C68960
[2025-07-31 00:40:08] 10: RaiseException in module: C:\WINDOWS\System32\KERNELBASE.dll at address: 0x56E39E80
[2025-07-31 00:40:08] 11: RaiseException in module: C:\Program Files\PixInsight\bin\VCRUNTIME140_1.dll at address: 0x56E39E80
[2025-07-31 00:40:08] 12: RtlCaptureContext2 in module: C:\WINDOWS\SYSTEM32\ntdll.dll at address: 0x59D067B0
[2025-07-31 00:40:08] 13: RtlCaptureContext2 in module: C:\Program Files\PixInsight\bin\ImageIntegration-pxm.dll at address: 0x59D067B0
[2025-07-31 00:40:08] 14: RtlCaptureContext2 at address: 0x59D067B0
[2025-07-31 00:40:08] 15: RtlCaptureContext2 at address: 0x59D067B0
[2025-07-31 00:40:08] ================================================================================
[2025-07-31 00:40:08] <* failed *>
[2025-07-31 00:40:08] ** Warning: ImageIntegration failed.
[2025-07-31 00:40:08]
[2025-07-31 00:40:08] ************************************************************
[2025-07-31 00:40:08] * End integration of Light frames
[2025-07-31 00:40:08] ***********************************************************
Okay, it was buried in the log file. Looks like a PixInsight internal error happened here.
No idea how to work around or fix it.
Running Image Integration manually still crashes.
I had to remove one of the subs from the stack to get it to integrate.
Weird.
I had to remove one of the subs from the stack to get it to integrate.
Weird.
Hello, from what I see the main issue is revealed in this part of the logs:
[2025-07-31 00:40:08] *** PCL Win32 System Exception: At address 00007FFA56E39F0A with exception code C0000005 :
[2025-07-31 00:40:08] Access violation: invalid memory read operation at address 0000000000000000
That looks like a low-level system error judging by it's exception code "C0000005", which is generally for "Access Violation".
"invalid memory read operation at address 0000000000000000" - Here it seems like Pixinsight tried to read data from memory adress 0 or null. This usually gets triggered by bad or corrupt data.
This does not seem to be a generic memory issue, since your log states you have enough available memory to complete the task.
All of this points me toward a corrupt or "bad" data.
Since you removed that one frame and it integrated, that was the culprit. Either the frame was corrupted during writing to the disk, or simply had bad pixel data.
Even if the frame was not corrupted in any way it can cause this issue if it looks different enough than other frames. It looks like you just ran into an unfortunate bug in the software.
Hope this helps.
Clear Skies, Rene.
[2025-07-31 00:40:08] *** PCL Win32 System Exception: At address 00007FFA56E39F0A with exception code C0000005 :
[2025-07-31 00:40:08] Access violation: invalid memory read operation at address 0000000000000000
That looks like a low-level system error judging by it's exception code "C0000005", which is generally for "Access Violation".
"invalid memory read operation at address 0000000000000000" - Here it seems like Pixinsight tried to read data from memory adress 0 or null. This usually gets triggered by bad or corrupt data.
This does not seem to be a generic memory issue, since your log states you have enough available memory to complete the task.
All of this points me toward a corrupt or "bad" data.
John Stone:
I had to remove one of the subs from the stack to get it to integrate.
Since you removed that one frame and it integrated, that was the culprit. Either the frame was corrupted during writing to the disk, or simply had bad pixel data.
Even if the frame was not corrupted in any way it can cause this issue if it looks different enough than other frames. It looks like you just ran into an unfortunate bug in the software.
Hope this helps.
Clear Skies, Rene.
Well Written Helpful Insightful Engaging
I misspoke earlier when I said I had to remove a sub to get it to work. What I really had to do uncheck the “automatic memory“ checkbox (just used the default values)
That enabled the integration to complete.
I think this is a rare bug in PixInsight since all other filters (besides Blue) worked fine.
That enabled the integration to complete.
I think this is a rare bug in PixInsight since all other filters (besides Blue) worked fine.
Sorry, I am coming late into this game…
I actually had this happen to me 2 weeks ago while stacking just over 1000 subs and as PI dis show green check marks top to bottom, I exited WBPP and only realized I was missing master lights thereafter. In my case it turned out to be a memory problem and I had to throw some money towards more RAM. But not until trying a second time and read casually through the list. Don't ask me how long it took WBPP to run the stack 😖
I did try FastIntegration and there it actually finished the process but left some strange patches in the image. After upgrading from 64GB to 128GB, WBPP stacked all subs without problems.
Personally I wish WBPP would mark the failed process red so that it is visible in the list.
Helpful