This is the not the first report of this behavior, so this must be a real bug in the software.  But it must be a Windows thing, because I've had 0.81 open in Linux for days without issue.

Unfortunately, these types of crash reports are really not very useful.  I really need the console output from Armory to be able to figure out what happened (which is not available without running Armory from the console).  As such, I'm currently implementing a proper logging system, to go into ... 0.82?  Probably 0.82.1.  Then when Armory crashes, there will be an armorylog.txt file that you can send me.  I've been procrastinating on this for months, but now I think it's finally time to do it. 

While I work on updating 20k lines of python code with proper logging calls, I'll load up Armory in my Windows VM and leave it running to see if I can replicate the behavior in the debugger. 

Hey, at least it works for a couple hours before crashing!  It's obviously not convenient, but it sounds like you still have access to all the features...

Glad to see folks like the new features