Why does Dreamweaver CC keep crashing!!!

Question

Dreamweaver CC keeps crashing!!!
Randomly,  Dreamweaver CC pops up error message.
"Adobe Dreamweaver is not responding" with 3 option.
1. "Check for solution and close program" or 2. "Close program" or 3. "Wait for the progeam to respond". I selected the "Wait" option a couple times. Waited for over 15 minutes and it never recovered. The best option left was to  "Check for solution and close program". The program closed and I lost all my unsaved work. This happens all the time. At least 2-3 times in a 6 hour session. About 6 pages open and doing nowing out of the ordinary. Long time Dreamweaver user.. Nothing much else running in the background. 6 month old laptop and it used to happen on my last laptop.
I'm only working with standard html files with arial font, not {}, not Fluid Grid, and no media queries is css.
Been working on this for over 6 months. Thought CC would get it fixed. The msvcr100.dll is the original version. Double checked. Been deleting the DW cache regularly.. 
Search all adobe support including this one: http://forums.adobe.com/message/5630415#5630415#5630415
Additionally it appears windows 8 is store my adobe files here. C:\Users\David\AppData\Local\Temp\WERE78D.tmp
"C:\Users\David\AppData\Local\Temp\WERE78D.tmp\Dreamweaver.exe.xml"
"C:\Users\David\AppData\Local\Temp\WERE78D.tmp\memory.hdmp"
"C:\Users\David\AppData\Local\Temp\WERE78D.tmp\triagedump.dmp"
"C:\Users\David\AppData\Local\Temp\WERE78D.tmp\WERInternalMetadata.xml"
"C:\Users\David\AppData\Local\Temp\WERE78D.tmp\AppCompat.txt"
"C:\Users\David\AppData\Local\Adobe\XMP\File Info\4.0\work\FileInfoPrefs.xml"
"C:\Users\David\AppData\Local\Adobe\XMP\File Info\4.0\work\FileInfoLibraryPrefs.xml"
"C:\Users\David\AppData\Local\Temp\AdobeDownload\DLM.log"
"C:\Users\David\AppData\Local\Temp\AdobeDownload\DLM_Native.log"
WIndows 8 version 6.2 (build 9200)
64-bit Operating System x64-based processor.
4th generation Intel® Core™ i7-4700MQ Processor
16GB DDR3 System Memory (2 Dimm)
NVIDIA GeForce GT 740M Graphics with 2048MB of dedicated video
1TB 5400 rpm Hard Drive
Below is the error message.
Description:
  A problem caused this program to stop interacting with Windows.
ADOBE REPORT
Problem signature:
  Problem Event Name: AppHangB1
  Application Name: Dreamweaver.exe
  Application Version: 13.2.0.6466
  Application Timestamp: 52a8e373
  Hang Signature: 68d8
  Hang Type: 0
  OS Version: 6.2.9200.2.0.0.768.101
  Locale ID: 1033
  Additional Hang Signature 1: 68d81c0b8c76a928b9599171c1ee38ab
  Additional Hang Signature 2: a04c
  Additional Hang Signature 3: a04c3811fce2b1f51c8b6128fd075f9b
  Additional Hang Signature 4: 68d8
  Additional Hang Signature 5: 68d81c0b8c76a928b9599171c1ee38ab
  Additional Hang Signature 6: a04c
  Additional Hang Signature 7: a04c3811fce2b1f51c8b6128fd075f9b
MICROSOFT REPORT
Description
Faulting Application Path:          C:\Program Files (x86)\Adobe\Adobe Dreamweaver CC\Dreamweaver.exe
Problem signature
Problem Event Name:          APPCRASH
Application Name:          Dreamweaver.exe
Application Version:          13.2.0.6466
Application Timestamp:          52a8e373
Fault Module Name:          MSVCR100.dll
Fault Module Version:          10.0.40219.325
Fault Module Timestamp:          4df2be1e
Exception Code:          40000015
Exception Offset:          0008d6fd
OS Version:          6.2.9200.2.0.0.768.101
Locale ID:          1033
Additional Information 1:          8f36
Additional Information 2:          8f36287b943d1cd6a6f46a3560655074
Additional Information 3:          e3e8
Additional Information 4:          e3e8d866a67186d01ba130d33f96d207

Answer 1

This may be yet another “Broken Brand”!
I feel you Alaska !!!  I feel the same way. I think this Adobe is over it’s head in understanding this cloud technology. They jumped into it making all sorts of fallen promises  just wanting our $49 per month.
You can’t believe how  much work I have put into trying to help them fix these  problems
I’m now afraid to make any changes to my sites using Dreamweaver in fear of another malfunction resulting in messing up an entire site. Last time it crashed I had to reattach the template to  200 pages - one by one.
I don't understand what the people at adobe are thinking.
I finally reached out to Abobe support in this post: http://forums.adobe.com/message/6239493
In this instance, I spent over 6 hour following adobe specific technical directions on how to capture all the log file they suggested I configure to capture the crashing problem I am continually experiencing. Afterwards I forward an Adobe technician  the log file with to response or fix.
Then even worst, I spend more time capturing more logs (because it is now crashing daily) and fully outlining my PC environment and configuration, and sending more log files only to have my emails be rejected.
Now I'm fearing Abode will  just cancel my account for posting these complaints.
But what's a developer to do. I have over 20 sites dependent on this software.
I'm definitely looking at solutions that are less dependent on DW functioning correctly.
Drupal is currently looking like a good solution.
I manage over 20 sites for local customers and it would be a tremendous amount of work but living with DW always crashing is unacceptable. And who knows if the next versions of DW will not experience the same problems. I think they need to spend a few extra dollars and hire some better software engineers. I don't think they quite know what they are doing with this new cloud services environment.
I thinks Google’s top new secret "Cloud Website Development Kit" might end up being a better solution. I think it's going  to be married to Google Webmaster Tools. That's the direction and reason for all the recent rapid Webmaster Tools improvement in the web performance tools site.
Google.. Gota love them.. They seem to always get it right ad fully understand the future of the cloud.
Bottom line: These design tools like DW and PS should be out of the box dependable. Continual crashes with 100’s of complaints is totally unacceptable.
Nothing that diminishes a brands value and kills a company faster than inferior products and lack of support.  "Broken Brands" good read: “How the Tech Parade Passed Sony”  By Hiroko Tabuchi