SQL DUMPER Error

Hi,

I have a package which reads data from set of tables, goes thru a script component for some data changes and written to a flat file. To speed up the process, I have created 6 threads of this same sequence, but instead of writting to different files, I am joining the outputs of all 6 scripts components using 'UNION ALL' and writting it to a single file. I have to execute this for different input years and so calling this data flow within a 'Foreach loop' container for multiple years. When I ran this package for single year, it ran without any error. But when I ran it for multiple years (in debug mode), after processing 3 years, the package just stopped running. It does not abort, but just created a SQLDUMPER Error log file with the following contents.

07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 2184
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0100C5D0
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
07/08/06 22:59:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
07/08/06 22:59:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:Program Files (x86)Microsoft SQL Server90SharedErrorDumpsSQLDmpr0002.mdmp
07/08/06 22:59:09, ACTION, DtsDebugHost.exe, Watson Invoke: No


I have searched this forum and saw one thread with this error message, but there is no response for that. Do you guys know what could be the problem?

Thanks.