>At least we know that BUILD EXE command isn't responsible for that problem because it's executed in the separate memory space. :)

Well, until bug fixed or cause of the problem known, it's difficult to assume on that.

The reason I'm saying this is because it's on that line that it generates that error.