I would like to note that I actually did try the whole "don't fiddle with the window at all while it's starting and loading" (including alt tabbing to it), and it hasn't given me any grief when I remember to do so.  Could be coincidence, could be causal.  Also wonder if I would have no trouble if I played the game in fullscreen mode instead of windowed.  Probably will never test that though unless I get really frustrated with it.

I started the game one day (today) and it took a while to start loading (as usual), and windows thought it was frozen for a while (as usual) and then it finally woke up and showed me the loading bar which slowly and sporadically filled some (as usual), then it hung for a while and then the graphics driver crash happened again.  Here's a new set of logs for you.
I'm still hoping this is an easy fix, like "don't try and move the window while it's loading" or "don't repeatedly alt-tab back and forth to it while it's loading" or something stupid like that. It seems like after it crashes once, it will keep crashing until I restart my PC (note that I actually haven't restarted it yet, but I'm assuming it'll work fine after a reboot).   I also wonder if not performing a warm or cold boot for a while makes this (more likely to) trigger.

crash.dmp
output_log.txt
error.log

Greetings Lee!

Yes, my drivers were and are up to date.  I had this problem several days before where the game would stutter, but by fiddling around with the window I was able to snap it out of it.  Now, if you also use Nvidia, you might notice that soon after I posted this, a new graphics driver became available, which I installed.  After restarting my computer post-update, I was able to load the file properly and haven't had any more issues.  However, given the intermittency of the issue I rather doubt this new driver is the cause of the fix and that it may happen again with some variation thereof in the future. I can't say that with any certainty though--just a bad hunch.

Thanks for the error log interpretation.  Now this laptop is several years old, but as you'll notice the specs are still decent, so my money is either on my laptop's interaction with my external monitor (I have it setup to use g-sync, but supposedly my laptop's model is incapable of using g-sync.  Despite this, after looking around, I'm told that if I can find the g-sync option to turn it on in my driver settings that I am able to use it if I decide to try and turn it on--that it wouldn't show up if I couldn't), or the game has some sort of quirk with my rig or the last driver I was on.  Hopefully it's just option #3... I'll continue to play and see if anything like this happens again and will post more logs if it does.

crash.dmp

error.log

output_log.txt

Here are the files for the first crash.

I'm running on latest game and windows 10 build, i7-4790 CPU, Nvidia 970M, and 16GB of RAM

Oh, and I said the game is supposed to be windowed mode at 1920x1080, but it doesn't seem to be that large of a resolution (I tried adjusting it and it reacted normally so either I'm losing it or they're all a bit smaller than advertised)
Edit: here's the save files in case they matter, but I don't suspect it has anything to do with the file itself ....9 belmorne's pass lambs to the slaughter_20190820193444
9 belmorne's pass lambs to the slaughter....meta