OK, well, this really needs to get fixed. No point having a build out that crashes all the time for lots of people.
If anyone can get a stack trace with the most recent EXEs above, that would be really handy. If it crashes for you and you're technologically inclined, fire up windbg, attach it to Construct's process, get it to crash, then open a stack trace. (You need the .pdbs next to the EXE to get it to load symbols otherwise it's all just memory addresses.) Paste it here and that's really good information to help solve the problem.