Please try build 173 from the top of this forum.
It may be a certain file that is causing problems. MC can import by directory. Try splitting the imports into smaller batches to find the file.
I tried b173. Same problems.
What's most frustrating is that the crash is unpredictable. It was crashing repeatedly trying to read in a 200GB directory of a around 30000 files. Then one time it worked, for some unexplained reason.
Now I have a new directory. If I add the files manually, one directory at a time, then it seems to work. But if I add the root directory then it crashes out after finding around 100-150 new files. Of course, the crash is so total that it doesn't add these files incrementally to the database so I can't proceed from there.
The library currently numbers just under 64000 files.
Trying to triage the "problem" directories produces no effect. If I remove them from the root directory then it just crashes on a subsequent directory. MC10b173 can also read the "problem" directories individually with no errors, so I believe these are not in fact problematic at all. The problem lies therefore not with any particular file or directory but with MC10's handling of mass imports.
MC10b173 is also crashing out on three different machines running WinXP when trying a mass import, over the network, either using UNC or mapped drives.
My old MC9 when installed had no problem reading in all the files in a single mass import. I'd revert to that except that I notice the pane update speed in MC10 seems to be massively improved.
It's a pity. One reason I always recommended MC over, say, iTunes to people in the past was how it was stable at handling really large collections while iTunes just withers and dies when faced with big libraries.