Google produces lots (probably far too many) of hits for '0xc0000005'.
My best guess is that afoken's post is closest to the mark.
That is, you've come up against some sort of wtf - probably a handle allocated by msvcr80.dll is passed to msvcrt.dll, and msvcrt.dll doesn't know what to do with this handle (... nor should it).