All your logs, VollachR, indicate that the game crashes because there is not enough system memory available.
I just can't see a way for the game to reach the max limit of memory used by itself (~3.5GB), as the biggest scene in the game (Marcuria) will use about ~2.7GB on full graphical settings.
How much memory is your system consuming before you start up the game? Applications like Google Chrome and Firefox with a lot of tabs open take up a bunch of memory.
I can't understand that as well, while I can't account for how much RAM was used when I started DFC last time, I can say that right now as I type (DFC not running) I have about 3.8GB used out of 8GB of RAM (48%) according to the Performance tab of Windows Task Manager, I'm attaching a screenshot.
Now consider that the current RAM usage shown is with Google Chrome opened with 3 tabs, Total Commander File Manager, Steam running in the background and FinalWire's AIDA64 running to monitor my computer temperatures.
If I add MSI Afterburner to display temperature overlay in-game than the RAM usage before launching DFC is 4.1/8.0GB as shown in the 2nd attached picture.
Needless to say that I don't run DFC with 3 opened tabs in Google Chrome, Maximum 1 if any at all, which lower the RAM usage to 3.6GB before launch at maximum.
Either way, I have around 4GB of free RAM which should be more than enough if DFC really takes around 3.5GB, That said, you mentioned Marcuria being the biggest scene in the game, it is also where all the crashes happen, didn't have a single crash in Propast (Europolis) so far.
I wonder if its the windows 8 User Account Control ? If you haven't done so try turning it off ? A bit of a wild stab in the dark this one, but you never know.
I doubt Windows 8 UAC has anything to do with it, UAC doesn't/shouldn't effect the amount of RAM used and it was always on when I played previous books (or any other game for that matter)
Now, FYI, yesterday I started my 2nd run of Book 3, I had less crashes on Chapter 6 than in my first run but I had a single crash in the interlude which I haven't had before, Only difference is the space cleared on my C drive but that can't be the cause for the crashes anymore, I have lots of free space.