Meow? Really?
I've run every version of EW since pre release versions of what turned out to be EW 1 back in 2005. On every OS and many beta OSes current at the time of the versions. I've had 2 crashes in EW in all those configurations. 1 was during beta testing the other due to a bad ram chip (crashed other things as well before being replaced.)
To top it of even if someone wanted to help you there is not one single bit of information in your whine that would enable anyone to do so. No product version, no operating system version, no indication of what you are doing that causes it to crash.
The few non-asp.net crash issues that are reported come from either insanely large websites that should be data driven cms or at least make heavy use of include files like the 16,000 page site referenced earlier in this thread. Dreamweaver wouldn't like a site that size any better
Issues with the video driver since EW makes heavy use of the graphics subsystem.
Finally, really, really badly formed HTML code has been known to make EW crash.
I've run every version of Dreamweaver from Ultradev 4 through Creative Cloud. Its crashed more on my Mac than PC but Macromedia - Adobe haven't been perfect anymore than Microsoft. You might have enjoyed my cursing at both of them last week after I updated to the Maverick OS and had to reinstall Java in order to get Dreamweaver to even open.
Let's see Expression Web 4 is free and has been for a long time. During that time I've gone from owning outright CS 5.5 and CS 6 to having to purchase a subscription at $49.95 a month (okay for a short time if you own recent versions of the Creative Suite you can get it for about 60% of that but CC versions no longer support any server side language but PHP). For the cost of what I've spent on Adobe Creative software you could buy a very, very nice computer. Don't like EW or you can't figure out why it I crashing on your system, and it is something about your system then spend your money elsewhere since MS has said there will be no support or further updates to EW. It is possible to count on one hand the number of threads about crashes that are not related to a corrupt or missing asp.net install over the entire life of the product - aka from 2005. You reopened a thread that had been dead since May of 2010 which in itself was a post more than 2 years past the original post. That alone should tell you how few people experience crashing.
FreeExpression Web Tutorials
For an Expression Web forum without the posting issues tryexpressionwebforum.com