Much more game crash after 1.2.1 update

[li.yuxing272]

Hei, just getting more game crash now, usually it happens after a certain time play, which seems memory leak. I already submit the crash report. Plz fix it ASAP, just start a new build :O :)

[yaka]

same problem here

[Bludbonez]

When launching the game. Which launch build are you using?

[Evilplay]

Are you using any mods? I had this problem too and resolved this by deleting all mods. All the mods need to be updated now since the game update and so far using any old mods for previous game version gives you crashes and black screen.

[li.yuxing272]

The launch option is by default just "Play Grim dawn", I guess it's X64 on my computer.
And I don't have any mods

[Blake]

I've been playing around 50 hrs or so over last 4 weeks and not had a single crash. (Only had 1 crash in 6 years of playing nearly 2600 hours)

Does this crash in certain areas or is it random?
Could be a hardware issue especially if you have overclocked CPU or RAM.

[KillingYouGuy]

This game has been crashing since its release for many many players, it crashes mostly when moving to other areas. It is not hardware related, none of the recommended fixes work for most players. I suspect certain CPUs (multi-core) have not been properly coded by the devs nor RAM utilization, you know basic dev responsibilities. I wish they would stop making massive changes to this game as it has been out nearly a decade, they should try fixing the crashes more and forcing toon re-builds due to micro-changes less.

[Voodoojedizin]

Honestly I don't understand this problem, 600 hours and I don't think I can remember any crashes at all and I purchased a game way back like when it first came out.
I just started a new play through 15 hours in after the new patch and the game runs fine no crashes This has to be computer related in some way I mean this game will run on a toaster practically.

[Blake]

Originally posted by KillingYouGuy:

I suspect certain CPUs (multi-core) have not been properly coded by the devs nor RAM utilization, you know basic dev responsibilities.

Runs fine for me on current AMD 5800x and previous 2 builds (last one was AMD 3700 and prior to that was Intel something or other, can't remember)

But I also run a very clean system. No cracked rubbish, spyware, adult stuff, streaming app nonsense, facebook, tiktok crap etc. you know basic user responsibilities

Downside to PC gaming are the number of possible system combinations and driver/hardware variants.

I've just been lucky I guess...

[Deathbit]

Freezing and crashing for me as well... have never had it freeze before.. usually just hard crashes. Have auto item compare off .. upnp ect. Seems to be new with the patch.

[KillingYouGuy]

Originally posted by Blake:

Originally posted by KillingYouGuy:

I suspect certain CPUs (multi-core) have not been properly coded by the devs nor RAM utilization, you know basic dev responsibilities.

Runs fine for me on current AMD 5800x and previous 2 builds (last one was AMD 3700 and prior to that was Intel something or other, can't remember)

But I also run a very clean system. No cracked rubbish, spyware, adult stuff, streaming app nonsense, facebook, tiktok crap etc. you know basic user responsibilities

Downside to PC gaming are the number of possible system combinations and driver/hardware variants.

I've just been lucky I guess...

I am running a Corsair Vengeance i8100 stock/no overclock, it's a straight up single use gaming rig. No apps, nothing but Steam and similar programs. I've played the game on two other rigs, same issues. I've just been unlucky I guess...

[Blake]

Does it show anything in Event viewer when it crashed?

[KillingYouGuy]

Originally posted by Blake:

Does it show anything in Event viewer when it crashed?

No, the only thing out there was the gaming service double install issue which was hosing iCue, but I fixed that. I updated Rainbow Filter when the update dropped, but I may try uninstalling that for a bit. Problem is the crashes have always happened for me in every version and rig I have played and I only recently started using RF.

[Rune]

Try change the launch option to x64 mode (play Grim Dawn x64) and switch the fullscreen option to "windowed borderless" instead. I had issues with the game freezing when zoning on the last major patch that came out a while ago and these two changes may've fixed it for me, *knock on wood.* Played for over 8 hours so far without issues on a new character build. This game engine is old and it seems it has some issues on new hardware and operatingsystems, similarly to Titan Quest. For starters I think it has issues hooking itself on high refresh rate vrr displays, or at least I never got it to work properly in this game. It's also primarily running on a single core, so the Windows thread scheduler has some weird tasking behavior on where to run it on my hybrid intel cpu. Guess this is typical when running something old on something that's new.

[gNuff!~©~gNom3™]

after a new update verify game files *do this even if steam claims it did so on its on
right click Grim Dawn in steam library, properties, installed files, "verify integrity of game files"

if using *any* mods disable or update them, then try again, there can be a bunch of back curtain conflicts sometimes where mods have to be updated, and sometimes people forgot they were even using a mod

still crashing frequent, try use the repair tool in game install folder (it resets settings)
*also check you're not somehow running uncapped frames after the update, hardware/the game really doesn't seem to like this just be able to run wild

make an exclusion/whitelist grim dawn game and save folder in your antivirus, sometimes after an update AVs can tend to flag Grim Dawn and not play nice with it, also even if it doesn't outright block it, stuff like active shield protection or background scans while playing have been known to cause crashes

another thing can be to manually reinstall c++ visual studio redistributables, also even if steam claimed it did so on the update/verify, sometimes it's a corrupt or missing file that needs to be pulled manually


those should usually be the main ones if it's post update/new crashing

[KillingYouGuy]

Originally posted by Rune:

Try change the launch option to x64 mode (play Grim Dawn x64) and switch the fullscreen option to "windowed borderless" instead. I had issues with the game freezing when zoning on the last major patch that came out a while ago and these two changes may've fixed it for me, *knock on wood.* Played for over 8 hours so far without issues on a new character build. This game engine is old and it seems it has some issues on new hardware and operatingsystems, similarly to Titan Quest. For starters I think it has issues hooking itself on high refresh rate vrr displays, or at least I never got it to work properly in this game. It's also primarily running on a single core, so the Windows thread scheduler has some weird tasking behavior on where to run it on my hybrid intel cpu. Guess this is typical when running something old on something that's new.

Thanks Rune, I have tried every single solution you can imagine. Nothing works, it keeps on crashing. If it were just me, I would chalk it up to bad luck. While PC gaming is very complex in that many users will have vastly varying rigs, I cannot think of another game that has vexed me so.