Constant Crashing

[Samsquanch]

Was wondering if anyone had an issue of the game constantly crashing. If I boot the game up for the first time in a day, it will be fine for a little while but then the game will just crash out of the blue. After the first crash, once I boot the game back up and play again, it will keep crashing every few minutes. Im running the game on low settings, verified game files, run the game as admin, my drivers are up to date, and turned vsynch on and off. my specs arent bad either, I have a RYZEN 5 5600X and a AMD 6600XT and 16gb of RAM. I love this game and it doesnt even run bad. I will be playing without any issue then the game will just crash out of the blue. If anyone has a fix, please tell and it would be greatly appreciated.

[Wokelander]

Yep, I had the problem at launch and I'm having it still (though less pronounced) even though I was playing on a different rig than last time

[spammdc]

0) Verify your game files.
1)Disable steam cloud saves.
2)Make sure your browser is up to date as well as other Aps such as EA and Battlenet.
3)Make sure Mods are up to date and use the right mod for the game
4)Check MS event viewer and MS Device manger for errors and report them here so people can help you out.
5) I have seen issues reported with fire fox browser so do not use it for this game, steam uses your browser for things.
6) Launch game from your steam library after launching the steam app.
7) Check Bug page for info on how to solve old Unity bug with various peripherals.

Good Luck

[kNif'n n00b]

I've the same problem. No issues a month ago while playing the game, but now it seems to crash at several different dialog menu's after battles in the prologue.

[spammdc]

Verify your game files and disable steam cloud saves.

I have been having strange stuff occur on games where I have steam cloud saves enabled (W40K:RT and Thamuaturge)
Happy Holidays

[Duchess of Kvetch]

Did you get around to checking the event viewer? I am having a lot of recent cutscene/animation related lockups and crashes too, that seem to coincide with a crash in an audio driver used by this game - AkSoundEngine.dll (as reported in the Event viewer). If I can confirm more info I'll post about it here.

[kNif'n n00b]

Originally posted by Duchess of Kvetch:

Did you get around to checking the event viewer? I am having a lot of recent cutscene/animation related lockups and crashes too, that seem to coincide with a crash in an audio driver used by this game - AkSoundEngine.dll (as reported in the Event viewer). If I can confirm more info I'll post about it here.

I can confirm the same issue with event viewer. Looks like an audio driver issue of some kind.

Faulting application name: WH40KRT.exe, version: 2022.3.44.44553, time stamp: 0x66c4fb74
Faulting module name: AkSoundEngine.dll, version: 0.0.0.0, time stamp: 0x66e43646
Exception code: 0xc0000005
Fault offset: 0x00000000001781d0
Faulting process id: 0x0x62B8
Faulting application start time: 0x0x1DB5B8BCBD2B79E

Faulting application path: SteamLibrary\steamapps\common\Warhammer 40,000 Rogue Trader\WH40KRT.exe

Faulting module path: SteamLibrary\steamapps\common\Warhammer 40,000 Rogue Trader\WH40KRT_Data\Plugins\x86_64\AkSoundEngine.dll

I'll note, verifying game files may have fixed the issue. It did find 5 files with issues and the latest crash stopped.

[spammdc]

I would also do a bug report in game to OC as it might be something on there end that they need to fix....or it may not.
Happy Holidays and Good Gaming

[Duchess of Kvetch]

Faulting module path: SteamLibrary\steamapps\common\Warhammer 40,000 Rogue Trader\WH40KRT_Data\Plugins\x86_64\AkSoundEngine.dll

I'll note, verifying game files may have fixed the issue. It did find 5 files with issues and the latest crash stopped.

I saw it fixed one file too, just not sure which one. But at the same time, I lowered the graphics level down to "low" and disabled the cloud saves (though I don't think that last one is related at all). I got past some recent crashes after this.

Unfortunately with regard to graphic and sound driver faults, it doesn't really tell us much, and a completely different sort of bug like memory issues can cascade into blowing up a driver. All we can do is tried various techniques to reduce memory consumption, most of the time, until the devs can isolate or fix the issues.