In Progress Crashes and freezes on clean install in training camp

Users who are viewing this thread

Version number
1.1.6.26219
Branch
Main
Modded/unmodded
No, I didn't use any mods.
Dump identifier (optional)
2023-09-23_11.35.43_c22dd5b82c573631d1d1203b55b8b831
Summary: On a new PC, built less than a week ago, tried to play old saves of Bannerlord but after couple of hours of smooth gameplay the game started to crash both in world map (in a siege camp) and in battle (the siege itself). I thought that maybe because of the saves being from older version they are corrupted, so I decided to delete all of them, including on the Steam cloud and start a new campaign on a clean install. So I did that, deleted remnant folders from Documents and ProgramData, and reinstalled the game from Steam. However, after character creation I wanted to do the Training Camp tutorial, which I did in the order of ranged (crossbow, bow, javelin) and then on foot battle training. And three times the game crashed around sword/shield/spear training usually by a error popup but once it even completely froze during basic sword training and I got a blue screen of DPC_Watchdog_Violation. And by three times meaning that when I got a crash I wiped everything game related, searched for possible fixes like driver updates, .net core, framework and visual C++ redistributable installs, but they were up to date, nvidia drivers are less than two weeks old, yet the issue still persists.
How to Reproduce: Perform a clean install of the main branch of the game on steam, start new campaign, create a character (Vlandian, if it matters), start doing training camp tutorial, first ranged, then on foot battle and then the crash happens.
Have you used cheats and if so which: no
Scene Name (if related):
Media (Screenshots & Video):
Computer Specs:
OS: Windows 10 pro
GPU: Nvidia GeForce RTX 4070
GPU Driver Version: 31.0.15.3742
CPU: AMD Ryzen 5 7600x
RAM: 32 GB (16x2) DDR5
Motherboard: Gigabyte B650 Aorus Elite AX rev 1.0
Storage Device (HDD/SSD): Netac 1 TB SSD

additional dump:
2023-09-22_20.30.38_c22dd5b82c573631d1d1203b55b8b831
 
Forwarded to the QA team for further investigation. We will reach out again if we need more information. Thanks for reporting and sorry for any inconvenience!
Thank you, I tried to do a clean reinstall once more, to replicate the crash. This time I started with no changes in graphics settings and created a Vlandian character picking all first options and I could complete the training camp with no crashes. Then I set a highest preset in graphics settings and created a new character with different options, and this time the game did crash again at the start of advanced sword training.
Here's a dump: 2023-09-25_13.01.47_c22dd5b82c573631d1d1203b55b8b831
 
Forwarded to the QA team for further investigation. We will reach out again if we need more information. Thanks for reporting and sorry for any inconvenience!
After I had another game crash with the same error code (0xc0000005) I started searching for what might be causing it, and after some time I found out my system drive was corrupted. After using sfc /scannow and scanning and repairing the drive itself, the crash seems to have stopped happening. At least I repeated the same things that before resulted in a crash every time, and now it didn't, twice.

Edit: no, still crashes at the same point
2023-09-26_11.19.24_c22dd5b82c573631d1d1203b55b8b831

Edit2: I did a clean uninstall of GPU drivers using DDU and this seemed to help, again didn't have the crash twice, and on the third time it had, but now with different exception code 0xc000001d, which is almost definitely because of disc corruption and the chkdsk did indeed find errors. So it seems that it indeed is caused by my corrupt system drive.
dump: 2023-09-26_15.56.43_c22dd5b82c573631d1d1203b55b8b831

Edit3: I actually don't know anything, I read a lot of stuff in these days and it seems unlikely that this is a disc error, since my system drive is a ssd. I tried reinstalling drivers (gpu, audio, motherboard), running tests on cpu, gpu and ram (although I din't run an overnight ram test yet, going to do that with memtest86). The game still crashes invariably around melee tutorial, and if loading a save then seemingly randomly after 10-20 minutes.
dumps:
2023-09-27_17.16.41_c22dd5b82c573631d1d1203b55b8b831
2023-09-27_19.50.40_c22dd5b82c573631d1d1203b55b8b831
2023-09-28_09.55.46_c22dd5b82c573631d1d1203b55b8b831
2023-09-28_13.16.36_c22dd5b82c573631d1d1203b55b8b831
 
Last edited:
After I had another game crash with the same error code (0xc0000005) I started searching for what might be causing it, and after some time I found out my system drive was corrupted. After using sfc /scannow and scanning and repairing the drive itself, the crash seems to have stopped happening. At least I repeated the same things that before resulted in a crash every time, and now it didn't, twice.

Edit: no, still crashes at the same point
2023-09-26_11.19.24_c22dd5b82c573631d1d1203b55b8b831

Edit2: I did a clean uninstall of GPU drivers using DDU and this seemed to help, again didn't have the crash twice, and on the third time it had, but now with different exception code 0xc000001d, which is almost definitely because of disc corruption and the chkdsk did indeed find errors. So it seems that it indeed is caused by my corrupt system drive.
dump: 2023-09-26_15.56.43_c22dd5b82c573631d1d1203b55b8b831

Edit3: I actually don't know anything, I read a lot of stuff in these days and it seems unlikely that this is a disc error, since my system drive is a ssd. I tried reinstalling drivers (gpu, audio, motherboard), running tests on cpu, gpu and ram (although I din't run an overnight ram test yet, going to do that with memtest86). The game still crashes invariably around melee tutorial, and if loading a save then seemingly randomly after 10-20 minutes.
dumps:
2023-09-27_17.16.41_c22dd5b82c573631d1d1203b55b8b831
2023-09-27_19.50.40_c22dd5b82c573631d1d1203b55b8b831
2023-09-28_09.55.46_c22dd5b82c573631d1d1203b55b8b831
2023-09-28_13.16.36_c22dd5b82c573631d1d1203b55b8b831
I got a new system ssd, did a completely clean windows install, reinstalled the game and it still crashes.
2023-10-01_06.54.33_c22dd5b82c573631d1d1203b55b8b831
 
Don't use old Saves on a Beta version, that keeps changing, bound to have problems. Start a new game.

If your game is ok on low performance setting but crashes on higher settings, this might be a shader issue. Search these forums for shader problems, there's a few directories BL places shaders, these will probably need to be deleted then a fresh install. As a simple experiment, turn off shadows, see what happens.

Also so try running game in a windows box. ( if you own a 4K monitor, run the game in a 2560 X 1900 window) .
 
Don't use old Saves on a Beta version, that keeps changing, bound to have problems. Start a new game.

If your game is ok on low performance setting but crashes on higher settings, this might be a shader issue. Search these forums for shader problems, there's a few directories BL places shaders, these will probably need to be deleted then a fresh install. As a simple experiment, turn off shadows, see what happens.

Also so try running game in a windows box. ( if you own a 4K monitor, run the game in a 2560 X 1900 window) .
Never played on a beta, but wow, thank you so much for the shadows advice, I put the game on the highest quality preset, but turned down or turned off everything shadow related, and it indeed did not crash. I now at least have a lead on where to look next, so thank you once more.
 
Don't use old Saves on a Beta version, that keeps changing, bound to have problems. Start a new game.

If your game is ok on low performance setting but crashes on higher settings, this might be a shader issue. Search these forums for shader problems, there's a few directories BL places shaders, these will probably need to be deleted then a fresh install. As a simple experiment, turn off shadows, see what happens.

Also so try running game in a windows box. ( if you own a 4K monitor, run the game in a 2560 X 1900 window) .
Seriously, I cannot thank you enough, you are a lifesaver. So, you said that it could be a shader issue, and I thought that there is a shadercache, that is created by steam, but it is located in the steam library folder (which on my pc is not on a system drive, and was never wiped), in which the game is installed, and I never actually cleared it, because I followed the clean install instructions that specified only folders in documents, programdata and steam library common, so all this time I had the same faulty steam generated shader cache. I deleted this cache, and lo and behold: the game didn't crash for more than half an hour on the max settings, where before you couldn't play even for 15 minutes. I probably should test a bit more, to be sure, but it seems that the issue is genuinely solved.

Edit: it still crashed, but this time about an hour into normal gameplay, maybe because I didn't reinstall it completely, just deleted the shadercache folder. I will try to do a clean reinstall once again and see what happens.
 
Last edited:
yeah, if read old posts on this site, shader problems were a real issue 2-3 years ago. Still is an issue for people with older GPUs.

I also had crash issues, crashing every hour or so, had to upgraded my GPU from 8G mem or 24G mem, now no crashes except bugs.
 
yeah, if read old posts on this site, shader problems were a real issue 2-3 years ago. Still is an issue for people with older GPUs.

I also had crash issues, crashing every hour or so, had to upgraded my GPU from 8G mem or 24G mem, now no crashes except bugs.
If indeed I wouldn't be able to fix this on this GPU, then it's really sad, because even 4070 costs a painful amount, and AMD GPU prices here are outright ludicrous, and I guess no Bannerlord for me then.

Edit: did a clean reinstall with deleting shadercache, now I can play for 2 hours before it crashes.
dump: 2023-10-02_14.45.01_c22dd5b82c573631d1d1203b55b8b831
 
Last edited:
I had other games and programs crash, so contacted the seller and they determined that my CPU was faulty and RMAd it. Now I dont have this error, but did get a d3d device context error but that seems to be some GPU driver or cache related issue, since other people are also having it.
 
Back
Top Bottom