Need More Info Crashing after 78 lovely issue free hours

Users who are viewing this thread

Version number
1.5.5
Branch
Main
Modded/unmodded
No, I didn't use any mods.
Dump identifier (optional)
2020-12-23_02.29.35_7c9e815c9218c88f985a1b086e3c5bb

MB2archer

Recruit
I want to start by saying I have enjoyed this game for 78 hours and am a big fan. Came from the original MB.

Since then MB 2 Bannerlord has become entirely unplayable for me. Randomly, toward the end of 1.5.4 and now in 1.5.5 the game crashes for no reason. I cannot move on the map more than about 15-30 seconds without a crash. Custom battles were working fine but they too crash now.

I have changed nothing on my computer. All drivers are up to date for GPU and OS and everythiing else.

My Specs are: CPU=Ryzen 5 3600, GPU: Nvidia FE 2060S, RAM: Gskill 32g 3200 stable Storage: M.2 NVME SSD 1 tb (crucial).

I have zero mods. All vanilla.

Code is: 2020-12-23_02.29.35_ 7c9e815c9218c88f985a1b086e3c5bb

All of this began out of nowhere after 78 hours of zero issues. Now the game is unplayable. I tried reinstalls and verifications and none of that has worked.
 
Last edited:
Sadly, i can't find any logs with " 7c9e815c9218c88f985a1b086e3c5bb " It should look like this "2020-11-17_15.55.54_f97cee13dddbbac0ba2e1e246a9b9f32" Can you reproduce this again and send us the identifier again?
 
Sadly, i can't find any logs with " 7c9e815c9218c88f985a1b086e3c5bb " It should look like this "2020-11-17_15.55.54_f97cee13dddbbac0ba2e1e246a9b9f32" Can you reproduce this again and send us the identifier again?
Fixed it: 2020-12-23_02.29.35_ 7c9e815c9218c88f985a1b086e3c5bb
 
Are you sure this crash upload is recent? The of this should be live on 1.5.5 version. And the dump you sent is from 1.5.4.

It occurred in both, I sent the first one, though I sent subsequent dumps after too from when it would occur in 1.5.5. I just didn't write down those dump codes because it is virtually the same looking code.

I received a message this bug was fixed and the fix will be pushed out in the next mainline update - 1.5.6... it this true? Will I just have to update the game via my launcher and go from there?

Thanks
 
I am playing 1.5.5. I uploaded numerous dumps for that (the one listed here was the earliest and was 1.5.4.) When you say it is fixed - I haven't even tried because it is frustrating - how can this be so when there is nothing to download? It should just automatically work? I have gotten zero updates for the game via Steam launcher since I've sent this. You're saying this is fixed despite there being no update to download?
 
Oh so it isn't likely fixed at all then because it happened in 1.5.5. too.... that's discouraging. I did upload numerous dumps after I just didn't screenshot the reference numbers - I uploaded about 3 dumps of 1.5.5. early this month/end of December.

I guess I'll boot it up now that the 1.5.6. patch is main and see if it occurs again on a new game. If it happens I'll save the dump info and send it.
 
Back
Top Bottom