Internal Crash in 6.50B16 Build 3030

[ciaraldi]

After startup I get these Critical Error Messages:
-------------------------------------
[17:26:36] ERROR AutoPAR: PAR file is Damaged, Unable to Add Parfile: XXX.par2
[17:26:59] ERROR AutoPARPlugin: Repair Failed: XXX.vol1+2.PAR2 PAR Repair: ProcessEx - Bad PAR No main packet
[17:27:00] ERROR AutoPARPlugin: Repair Failed: XXX.vol3+2.PAR2 PAR Repair: ProcessEx - Bad PAR No main packet
[17:27:01] ERROR AutoPARPlugin: Repair Failed: YYY.vol01+02.par2 PAR Repair: ProcessEx - Bad PAR No main packet
[17:27:03] ERROR AutoPARPlugin: Repair Failed: YYY.vol15+10.par2 PAR Repair: ProcessEx - Bad PAR No main packet
[17:27:09] ERROR AutoPARPlugin: UnRAR failed:
[17:27:44] ERROR AutoPARPlugin: Repair Failed: ZZZ.vol0+1.par2 PAR Repair: ProcessEx - Bad PAR No main packet
[17:27:45] ERROR AutoPARPlugin: Repair Failed: ZZZ.vol1+1.par2 PAR Repair: ProcessEx - Bad PAR No main packet
[17:28:07] ERROR FileIOThread - internal crash
[17:28:07] ERROR FileIOThread - internal crash
[17:28:07] ERROR FileIOThread - internal crash
[17:28:07] ERROR FileIOThread - internal crash
[17:28:08] ERROR FileIOThread - internal crash
[17:28:08] ERROR FileIOThread - internal crash
[17:28:08] ERROR FileIOThread - internal crash
-----------------------------
[Note: Filenames changed to protect the innocent. ]

After this, the program seems to run properly (except for the un-pausing problem previously reported, which still exists).
The Downloading files tab shows 144144 files waiting to download.

This is version 6.50B16 Build 3030, running on an AMD A10-6800K with 32 GB RAM under Windows 8 with all the latest patches.

[Quade]

PM me the subject and group. I'll check it out.

It looks like there's some problem accessing your disk drives.

[ciaraldi]

I sent you the info you requested by Private Message. Thanks for looking into this.

I ran chkdsk/f on both drives, and it found no errors.
But the behavior persists.

[Quade]

I tried the files you mentioned and they worked fine for me. I PM'd you about it.

I suggested installing the single core version of the repair DLL.

Multi-core and AMD just don't seem to get along.