Sadly, you posted a crash dump file that corresponds to the previous viewer release, and I never keep around the enormous symbol files for old releases (so I cannot exploit it to find the crash site)... You will need to post a dump file corresponding to the current release (v1.30.2.15, as of writing this).
However, you should first and foremost ensure you configured Windows to use a
fixed size swap file, since this
Mickey Mouse OS reports NULL pointers on memory allocations done by programs while it expands or shrinks down its swap file (causing a crash, of course), and the description of your issue pretty much fits high memory demand and variations that could cause this... See
this Micro$oft article.