Hey,
just wondering - have your Grim Dawn become WAAAAY more instable after installing the expansion? Like more frequent crashes in old, base-game areas, and a complete crashfest in new ones - I'm sending crash reports like crazy, only yesteday I got to send 7.
I guess it might have something to do with their new renderer, because the screen often turns black and irresponsive, and only thing to get rid of it is to kill the game process.
So is it general problem, or just a sign that my computer became too weak to handle the game (which would really, really be a pitty).

I played the game for 90 hours and I have only had one issue where the game was stuck on a loading loop. But not a single crash so far. I have installed the full game including the expansion in one go so maybe the game becomes more unstable when you install the expansion seperately. There are also some problems with the new renderer according to crate. Not sure how or if they have handled this. But the new renderer has switched to DirectX 11 and that caused some problems for quite a few players.

But since there are so many different configurations possible it can literally be anything. My advice would be go to the official game forum or try the steam forum and look for answers there.

I have exactly the same problem as you, and my computer is not too weak to handle the game, far from it. I tried to un-install and re-install, without success, I still have a lot of crashes. Sometimes it crash when I launch the game, sometime when it load the characters on the menu screen, sometime when I load a save, sometime when I go through a portal, or get out a cavern, and rarely whithout doing anything in particular...

I did not find a way to avoid that.

Yeah, that sounds like you're having trouble with DX11. Have you tried forcing DX9? use the /d3d9 argument on your executable. Check link below for dev post:

https://steamcommunity.com/app/219990/discussions/0/1488861734124219001/

@OneFiercePuppy - yeah, I tried that, results in endless black screen on game load (the cursor and music are on), but the application doesn't go all unresponsive. What's more interesting tho, it seems there is a difference between -d3d9 and /d3d9. The former doesn't cause the game to hang on the initial load (before the crate logo even appears), but also doesn't seem to do anything.

@Exhodus - it might be just me being paranoid, but due to lack of other options I blame my AMD graphics, because - well - AMD :)
Honestly tho, I already have everything reduced to lowest or turned off, I killed everything that could be running in background (even windows explorer process), and I'm running out of options. And because I know AMD is causing troubles with some games, I believe it rather probable.