#Constant Crashes from Pakchunk errors.

1 messages · Page 1 of 1 (latest)

echo light
#

I am getting consistent crashing from pak chunk errors (*see figure 1)

Every so often, it can be every time a new map loads or even during a 1v1, but very often (multiple times per day) I will get this error, sometimes the game wont crash, i can close the error box and continue playing (without audio), and sometimes it just crashes the whole game.

I've reinstalled mordhau and verified like it says but nothing is fixing this, please help

Also I will add I recently got a new PC, the data transfer was wack and wasnt actually transferred so I started moving files over to the new drive, perhaps steam was one of them, but I dont want to reinstall steam so please let me know any ideas.

Also, each crash is a different pakchunk, could be 8 could be 20, could be 46.

granite eagle
#

The error is saying exactly what is occurring, files are getting corrupted somehow. There is likely either some sort of hard drive issue or a memory issue occurring, which is a bad sign if this is occurring frequently. You should run a memory test of some kind to rule out an issue there. If you have more than one hard drive, try moving the Mordhau install to that other drive via Steam (you can set up a new library for each drive).

Typically you only need to delete the specific pak file it mentions and then verify to reacquire it. I wouldn't always trust Steam to correctly fix this issue, which is why it's recommended to delete the file it mentions manually.

echo light
#

Hm, maybe i should reinstall steam then? This is only happening with mordhau

#

unless its related to the latest beta lutemod im testing

#

gonna run a memory test first

granite eagle
#

It's definitely worth reinstalling Steam. It can only be happening with Mordhau and still be a hardware issue i'm afraid

#

Other games have issues with file corruption on occasion too, they just don't usually prompt you telling you that it has happened, you just end up crashing for strange reasons instead.

#

Any time you verify a game and it finds files that are corrupted and will be reacquired, the same thing is happening to that game as is happening here

#

if it happens frequently, there's likely some sort of serious issue occuring

eager jasper
#

I have personally never seen this not be a ram issue

#

Whether it be a steam or epic install

#

Doesnt neccasarily mean its a critical issue, but ram can be affected in many different ways

#

a quick fix can be taking out one stick and seeing if its better (after aqquring the missing pak file, etc)

#

if that doesnt work, swap them, but yeah its not a real fix as of course, now youd be down ram

echo light
#

okay just finished 2 memory tests and all looks good on the hardware side

#

im thinking it could be steam related, as when I first started downloading part of steam was from my old drive

#

reinstalling steam now

#

but yeah its weird because no other games crash either, like this specific error is the only issue i've had in a couple months/ since swapping PC's

echo light
#

alrighty, just finished reinstalling mord and steam, will see if this resolves it, if not I suppose its not the end of the world if its just mordhau crashing once in a while

echo light
#

I wonder if it was because I was running mordhau through the application in steam > common... rather than the internet shortcut that is made when saving a shortcut to desktop

steady venture
#

no, that wont cause issues

hexed tapir
#

Yeah I got the same issue. For me it's definitely a hardware fault somewhere. Me personally I think my motherboard is failing as I've replaced my ram sticks a few times with no fix

#

Do you get occasional memory management BSODs?