Let's keep this thread civil. DravenX, I understand your frustration. Trying to make a large project in construct without knowing what to avoid is at times exasperating, especially with crashes that happen only sometimes.
That said, I also have to disagree. My game has hundreds of objects, is approaching 10,000 events (5000 in one sheet), and has lots of animation. Construct CAN handle it - IF you're very, very careful with it.
Construct 0.x can be best described as kind of delicate. Making a large project with it requires a lot of knowledge of it's quirks and bugs to avoid - variable bugs, or, the memory leak in the image editor, pasting between .caps, etc. Frustratingly, some things aren't obvious, and they may seem to work but turn out to cause crashes later. These things can be worked around, it just requires a lot of knowledge and understanding of construct's rickety areas, and a willingness to quit and ditch your previous hour/day's work if you discover some new quirk when construct does something unusual to be on the safe side.
However, as we all understand, that should not be required of construct's users, hence C2.
DravenX, a couple ideas - are you using 'or' anywhere, or when toggling events off with subevents, if those events have any child events that were toggled, toggling the parent event toggles the child events back on, causing crazy behavior.
Try to find where in the code the problem is. What events are running when it happens? Deactivate code in bits on the crashing sheet as you work on other areas as you try to uncover the problem.