Hi Wolfgang,
From the information you provide it seems clear that this is a memory related problem. You are using a 32-bit operating system with 3 GB of RAM. The problem is that at some point the ImageIntergation process exhausts all of the memory available to applications. You have basically two options:
1. Use a 64-bit operating system and a 64-bit version of PixInsight on a machine with at least 8 GB of RAM. This is definitely your best option. In my opinion, this is in fact your
only option if you want to work seriously with large stacks of relatively big images. All desktop 32-bit operating systems are nowadays obsolete, especially to work with applications like PixInsight.
2. Decrease the value of the
buffer size and
stack size parameters. If you set buffer size to zero this will integrate row by row with a minimal memory consumption at the cost of a severe performance degradation. If you set stack size to zero you'll save even more memory at the cost of degrading parallel execution. I suggest trying with a buffer size of 4 MB (the default is 16 MB), and lowering it if necessary. Bear in mind that there is a buffer size allocated for each image.
That said, now we have to face the fact that you're getting a crash. A crash is a crash after all
Exception code 0x40000015 corresponds to STATUS_FATAL_APP_EXIT. In layman's terms this means that there is an "unknown error" somewhere (isn't it nice when Windows provides us with such helpful information) which has caused the application to terminate in an inelegant way. Note that the module that has raised this exception is btmmhook.dll. This file is
not part of PixInsight, neither PixInsight uses it in
any way. It is not part of the Windows operating system either. btmmhook.dll is the
Multimedia Keys Hook DLL; it is part of a Bluetooth support software created by Broadcom Corporation. See for example:
http://www.exe-dll.com/dll/btmmhook.dll.htmI don't want to scare you but this file has also been involved in malware threats. You can Google this and you'll find more information. In your case I'd run a thorough virus/spyware scan, just for sanity.
