Recent content by LedoS

jayceon said:

This is the only game that is having issues on my system, so I don't think my GPU is the issue. As I'm now out of the refund window on steam I'd really appreciate some assistance with this as I've paid for software that doesn't work.

Click to expand...

Welcome to bannerlord. ^__^

archaicwarrior said:

Szent probably found a cause and solution - Corrupt AMD driver. Same GPU card as you.

Need More Info - Game crashing when entering town scene, with possible solution

Summary: GPU driver crashes when entering certain town scenes with error message: d3d_device_context_ -> Map at rglGPU_device::lock_texture Failed! The GPU device instance has been suspended How to Reproduce: Have latest AMD drivers. Have any version of Bannerlord. Try entering certain town...

forums.taleworlds.com

Click to expand...

Thank you!

Thanks for not acknowledging that it is a problem on your end. 10/10

denlik said:

Can also try this: regsvr32 ntdll.dll

Click to expand...

Thanks, i've tried both sfc and the dism and even this one, this one returns some error, but the other ones worked and well.. the crash persists, so it must be something else. Thanks for trying <3

denlik said:

Haven't had this issue, but try to give the Bannerlord folder full access in the security tab, out of curiosity - check your event viewer what it says for the "Application" and "System" tabs. Also, it looks like a defender pop-up, maybe check there as well. Let me know if this doesn't help.
Note that I'm not associated with TaleWorlds, hence you can ignore my suggestions.

Click to expand...

Thanks for your reply, first two are from event viewer.

1__

Faulting application name: Radeonsoftware.exe, version: 10.1.2.1996, time stamp: 0x6539ccd8
Faulting module name: ntdll.dll, version: 10.0.19041.3636, time stamp: 0x9b64aa6f
Exception code: 0xc0000409
Fault offset: 0x00000000000bcd86
Faulting process id: 0x26e4
Faulting application start time: 0x01da277ed571ad21
Faulting application path: C:\Program Files\AMD\CNext\CNext\Radeonsoftware.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 0a79c20d-6f9e-4378-b950-02883527dec6
Faulting package full name:
Faulting package-relative application ID:

2__
Display driver amduw23g stopped responding and has successfully recovered.

3) I added steam MnB folder, MnB documents folder and MnB programdata folder into exclusions and no luck, still same crash 100% of time.

Szentgyörgyi said:

Lately I've been experiencing the same crash described in this thread.
Sometimes it happens at the beginning of sieges, more rarely in some battle scenes.
I can trigger it consistently by entering a town scene (Amitatys) from the town menu.

Happens both with and without mods. Also tried a fresh install, shader cache purged, new game, still happens.
Tried increasing the pagefile size (0GB -> 4GB), doesn't make a difference. Should I increase it further?

Specs:
CPU: AMD Ryzen 7 3700X
GPU: AMD Radeon RX 5700 XT
RAM: 32 GB

Click to expand...

Same GPU, i have 32gb on my cache file, it doesn't do a thing.

This has started to have an influence on my gameplay as i can no longer take part in sieges this way. Please help us.

I think it's our amd GPUs that are like this, i also have 5700xt and i receive this same error.

Never installed any mods, my gpu drivers are on the latest version. The crash has that GPU lock texture message, which i've seen you say is hard to reproduce and reason for it is unknown, in various threads around the forum. Please let me know if there is anything at all i can do. Would really love to see this bug eliminated, or at least understand why it happens so i can think of other solutions on my own. :/

I can record you a video and upload to YT if you want to see it, it occurs 100% of time and this town is the only one that i've found that has this happen.
I'm currently reinstalling the whole game from scratch, removed every folder i could find, maybe it'll help because that's the last thing i can think of.
Reinstalling did not help. :/

I've tried this with no luck
1) setting game from fullscreen to borderless
2) deleting shaders cache from programdata MNB2 folder
3) page file is set at 32gb min and max
4) verifying integrity through steam
5) TdrDelay to 60 in regedit
6) Limiting FPS to 30(from 144)
7) Changing gfx settings to preset lowest possible.
8.) cleaning amd shader cache
9) updating drivers to 23.11.1
10) disabling AMD Anti-lag in adrenaline
11) disabling steam overlay
12) disabling amd overlay
13) toggling various AMD options and settings in Adrenaline
14) Pressing the IGNORE button, lmao...
15) This is all i could think of, very sad, bye now.

These are two other same incident reports i've sent before the most recent one marked above:
[24/11/2023 15:38:53][INFO]: 2023-11-24_13.36.51_58cabb6cddbf643eca73bda965464b12.zip
[24/11/2023 15:49:58][INFO]: 2023-11-24_13.48.41_58cabb6cddbf643eca73bda965464b12.zip
also this happens in windows notifications during all the crashes, no clue what that means, never seen it before.

Can you try losing a siege battle and tell me if it works like mine does please?
Im just surprised because losing a field battle does brings up the casualties page but losing a siege battle doesnt.
I just checked and even losing a field battle never brings up the white text, huh... have i been playing the game the wrong way all this time? Or just save scumming too much.

Gorvex said:

It is completely intentional. You retreat, you take penalties to your reputation. The mod doesn't allow for tactical retreats without penalties either, as otherwise it could be exploited with mass archers. Also the reason why the enemy sallies out when you bring too many ranged troops.

Click to expand...

But i don't want to retreat, i just want the white text to pop up that says 'battle is over, you're defeated' which never comes... Enemies just stand there and wait for me to retreat, why? I'm not doing a tactical retreat, me and my men are dead, we LOST a siege, not retreating...

Things ive tried: 1) changing reinforcement waves 2) combat speed 3) disable troop routing 4) battle size 5) reinstall of module and game, verify integrity on steam. No idea what else to do.

Muahahah, finally that stupid stealing feature can be disabled, thanks <3!


Edit: Sadly this "DON'T STEAL" tweak doesn't seem to work at all...