Need More Info Crash during siege

Users who are viewing this thread

Version number
1.5.9
Branch
Main
Modded/unmodded
No, I didn't use any mods.

Hadrianus666

Recruit
Every time I get into a siege battle (attacker, in any castle), the game crashes as soon as I get close to the walls. It did not do this before, the game was running very smoothly (Ryzen 5 3500x, 16 gb ddr4, rx 590)

So far I tried reinstalling, using minimal graphics, rolling back to previous versions (still crashes, but oddly, it did not use to crash before 1.0.4 yet now it does even with 1.0.2).

And I just had a crash in a field battle with a very similar dump.

Seems to have to do with a read error with Game.dll



************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 18362 MP (6 procs) Free x64
Product: WinNt, suite: SingleUserTS
18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Debug session time: Sun Apr 5 13:25:44.000 2020 (UTC + 2:00)
System Uptime: not available
Process Uptime: 0 days 0:05:45.000
................................................................
................................................................
................................................
Loading unloaded module list
....
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(20a4.1bf:cool:: Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
ntdll!NtGetContextThread+0x14:
00007ffb`2639de54 c3 ret
0:017> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************

Failed to request MethodData, not in JIT code range
0 is not IP

KEY_VALUES_STRING: 1

Key : AV.Dereference
Value: NullClassPtr

Key : AV.Fault
Value: Read

Key : Analysis.CPU.Sec
Value: 57

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-HI5F76J

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 91

Key : Analysis.Memory.CommitPeak.Mb
Value: 268

Key : Analysis.System
Value: CreateObject

Key : CLR.Engine
Value: CLR

Key : CLR.Version
Value: 4.0.30319.0

Key : Timeline.Process.Start.DeltaSec
Value: 345


ADDITIONAL_XML: 1

NTGLOBALFLAG: 0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS: 0

CONTEXT: (.ecxr)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=00000065a9fffc70 rbp=0000000000000000
r8=ffffffffffffffff r9=0000025a6b800e00 r10=000002591c725068
r11=00000000ffffff00 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206
00000000`00000000 ?? ???
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffada014492 (Game+0x0000000000024492)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000048
Attempt to read from address 0000000000000048

PROCESS_NAME: TaleWorlds.MountAndBlade.Launcher.exe

READ_ADDRESS: 0000000000000048

ERROR_CODE: (NTSTATUS) 0xc0000005 - L'instruction 0x%p emploie l'adresse m moire 0x%p. L' tat de la m moire ne peut pas tre %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000048

MISSING_CLR_SYMBOL: 0

FAULTING_THREAD: ffffffff

STACK_TEXT:
00007ffa`da014492 00007ffa`da014492 Game+0x24492


STACK_COMMAND: .ecxr ; kb ; ** Pseudo Context ** Pseudo ** Value: 20e676693b0 ** ; kb

SYMBOL_NAME: Game+24492

MODULE_NAME: Game

IMAGE_NAME: Game.dll

FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_c0000005_Game.dll!Unknown

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {25c4022a-7ee1-2f94-0e8e-5264fcbd2504}

Followup: MachineOwner
---------

0:017> lmvm Game
Browse full module list
start end module name
00007ffa`d9ff0000 00007ffa`da1c9000 Game (export symbols) Game.dll
Loaded symbol image file: Game.dll
Mapped memory image file: D:\SteamLibrary\steamapps\common\Mount & Blade II Bannerlord\bin\Win64_Shipping_Client\Game.dll
Image path: D:\SteamLibrary\steamapps\common\Mount & Blade II Bannerlord\bin\Win64_Shipping_Client\Game.dll
Image name: Game.dll
Browse all global symbols functions data
Timestamp: Sun Apr 5 10:36:37 2020 (5E899895)
CheckSum: 001D669C
ImageSize: 001D9000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
 
What you are describing is happening to me exactly.. siege is going along fine and then it crashes when I get near the walls ... Ryzen 5 cpu, 16gb, gtx 1060 6gb ... I hadn't tried it prior to 1.0.5 so I can't say whether or not it was working before ... I am going to try without building any siege machines and see if that changes anything...
 
What you are describing is happening to me exactly.. siege is going along fine and then it crashes when I get near the walls ... Ryzen 5 cpu, 16gb, gtx 1060 6gb ... I hadn't tried it prior to 1.0.5 so I can't say whether or not it was working before ... I am going to try without building any siege machines and see if that changes anything...


Let's hope this gets fixed (today's hotfix did not), I am just playig normally and autoresolving every siege situation.
 
Last edited:
Edited my previous post (mistake)


Let's hope this gets fixed (today's hotfix did not), I am just playig normally and autoresolving every siege situation.
 
I just tried a bunch of custom battles, all sieges with the same types of siege weapons and whatnot and it had no problems, no crashes ... so I don't get it ... my campaign game has larger armies, that's about the only difference.. who knows.. I wish it was happening to more people so I felt like it might actually get fixed, but I'll hope for the best ...
 
I'm also having crashes on a siege. It starts and about about 1 minute in it crashes. I've tried very low graphics settings, no persistent dead bodies.

Unfortunately no crash report to send.
win 10 x64 (10.0.18362 b18362)
32gb memory
i7 8700k @ 3.70 GHz
Steam
Bannerlord 1.0.6
Nvidia Geforce RTX 2070 (game ready driver 445.75)


Update (10/4/2020)
Please ignore my report, I figured out it was because of the mod 'Unlimited' default arrows . I was able to fix the mod by recopying the default arrow xml from the source file and replacing the xml in the mod file.
 
Last edited:
I still have this problem (playing singleplayer sandbox/campaign). The siege doesn't even load, as soon as the game tries to bring it up it'll crash. It's not just Chalkaind or if I'm defending or joining, it's any siege at all. (e.1.5.9, no mods, Nvidia Driver 466.27, GTX 1660 Super, 32gb ram)

edit: Crash report ID
2021-05-05_12.31.51_87623708fe272b57cffa7754b28573e6
 
Last edited:
I still have this problem (playing singleplayer sandbox/campaign). The siege doesn't even load, as soon as the game tries to bring it up it'll crash. It's not just Chalkaind or if I'm defending or joining, it's any siege at all. (e.1.5.9, no mods, Nvidia Driver 466.27, GTX 1660 Super, 32gb ram)

edit: Crash report ID
2021-05-05_12.31.51_87623708fe272b57cffa7754b28573e6
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!
 
@Salus Have you tried a clean install to see if it fixes the issue?
Clean Install
The clean install is removing every single game-related file from your computer and installing the game again. Why do you need to remove the game while you just want to remove the modifications? Unfortunately, some of the modifications do not just add a new modules folder but also change or adds contents to the existent modules folder. Without a reinstall, we can't be sure those files are unchanged.

To perform a Clean Install, Uninstall the game. You can do that by right-clicking the game on Steam Library and selecting Delete Local Content. Delete all folders related to the game that remains after the uninstallation. The folders that might have files inside:
Steam: C:\Program Files (x86)\Steam\steamapps\common\Mount & Blade II Bannerlord
Epic: C:\Program Files\Epic Games\Mount & Blade II Bannerlord
C:\Users\USERNAME\Documents\Mount and Blade II Bannerlord
C:\ProgramData\Mount and Blade II Bannerlord

Note: You'll need to allow Windows to display hidden folders and files to see the ProgramData folder and its contents.
 
@Salus Have you tried a clean install to see if it fixes the issue?
I had done a zillion clean installs when the game wouldn't launch due to residual load-order problems. Now the game runs fine, the only problem is it crashes whenever a siege tries to load.
What's worse is I get the memory error now too so I can't go through the crash dumps myself
 
Back
Top Bottom