How much system memory do you have available (hit cntrl-i it will show you)? Trying to access memory that isn't there will send you to the desk top, and the fact that the release notes asks you to manually check the available system memory, suggests the program doesn't.
I assume the program finds textures by hard coded offsets (maybe not, but that would be the most efficient), and if you choose to load textures without enough sys memory, it will hit an address error when you meet certain textures. That could account for sporatic ctd's. Dunno.