Need More Info “d3d_device_context_-> Map at rglGPU_device::lock_texture Failed! The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine"

[INSTReese]

SOLVED : I started having the d3d errors on the 1.5 update. FIX - what worked for me was to lower my performance (no preceivable game impact): OPTIONS -> PERFORMANCE -> Overall set to Medium. I can now play the game even with sieges occurring (I noticed that siege bombardment causes this issue for me). Hope this helps. CPU: i7 7700K, 16GB Ram, nVidia 1060 3Gb, Steam/Bannerlord on M2 SSD shouldn't have to lower performance but I like to play so I'll forgo some quality!

 

[Ven119]

i still get the same issue and all of my settings are set to medium

 

[silv27]

Also getting this issue. Tried everything in this thread and nothing works. Here's my full error text from the error log:

[20:59:49.851]
ERROR: d3d_device_context_->Map at rglGPU_device::lock_texture Failed!
The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action.

Last Executed Marker: Only supported with nVidia GPUs and Windows 10.
[20:59:49.851] #FairyTale.Library.pdb@{BC0B47AC5F104B81A7C32D1BB8222519} (1): 0:18981
#FairyTale.Library.pdb@{BC0B47AC5F104B81A7C32D1BB8222519} (1): 0:23834
#Rgl.pdb@{09DC8210B644453287E3A48864F53B31} (1): 0:4330849
#Rgl.pdb@{09DC8210B644453287E3A48864F53B31} (1): 0:1929569
#FairyTale.Library.pdb@{BC0B47AC5F104B81A7C32D1BB8222519} (1): 0:121850
#Rgl.pdb@{09DC8210B644453287E3A48864F53B31} (1): 0:1613773
#Rgl.pdb@{09DC8210B644453287E3A48864F53B31} (1): 0:1674815
#Rgl.pdb@{09DC8210B644453287E3A48864F53B31} (1): 0:3080502
#Rgl.pdb@{09DC8210B644453287E3A48864F53B31} (1): 0:3047678
#Rgl.pdb@{09DC8210B644453287E3A48864F53B31} (1): 0:3028319
#Rgl.pdb@{09DC8210B644453287E3A48864F53B31} (1): 0:3032694
#Rgl.pdb@{09DC8210B644453287E3A48864F53B31} (1): 0:251170
#Rgl.pdb@{09DC8210B644453287E3A48864F53B31} (1): 0:4290011
#Rgl.pdb@{09DC8210B644453287E3A48864F53B31} (1): 0:4293335
#ucrtbase.pdb@{15DCD9554735C5FBF0B28E3E15FBA9E5} (1): 0:134786
#kernel32.pdb@{E5021BC0C818845BB7558654339B0FE8} (1): 0:97236
#ntdll.pdb@{54A4ABD98E75ECCB93B912D274705130} (1): 0:446033
-----------------------------------------------
#TaleWorlds.DotNet.AutoGenerated.pdb@{735ED0F010074BBB935433A710D339E4} (1): 100663315:0

 

[laundrypirate]

Still occurring for me as well.

 

[SirHack'nSmash]

Well I've gone from my comment yesterday to a giant red square and 10 legged horse after the branding videos. It's like bannerlord has corrupted itself into a corner and is totally unplayable now.

I encountered the red square of death after installing the modding tools and tried many things without success. Ultimately it was fixed for me by deleting both the folders below:

• C:\ProgramData\Mount and Blade II Bannerlord
• X:\Steam Library\steamapps\common\Mount & Blade II Bannerlord\Shaders

Deleting only the shaders folder in Steam was not enough. There is another shaders folder within the C:\ path above, so delete both. Note the X:\ path will be different on your computer and will depend on where your Steam games are installed. To find it right click the launch icon in steam and select "Browse local files".

 

[uçanbiblo]

Hello, sorry for the late reply. We have fixed a considerable amount of the problems we have encountered so far and improved the game performance with the multiple patches we have released. Please make sure that your game, your drivers, and OS are up to date and the game has necessary permissions over your security software. Please let us know if the problem persists after completing these steps and verifying the integrity of the game files through Steam.

 

[Lornloth00]

I encountered the red square of death after installing the modding tools and tried many things without success. Ultimately it was fixed for me by deleting both the folders below:

• C:\ProgramData\Mount and Blade II Bannerlord
• X:\Steam Library\steamapps\common\Mount & Blade II Bannerlord\Shaders

Deleting only the shaders folder in Steam was not enough. There is another shaders folder within the C:\ path above, so delete both. Note the X:\ path will be different on your computer and will depend on where your Steam games are installed. To find it right click the launch icon in steam and select "Browse local files".

I did this and it solved my graphical artifacts and problem with quick talk in the campaign. I have been having many crashes black screens and blue screens of death that caused my monitor and GPU to stop working together.

Something is up with the shaders. The next patch needs to address this shader problem.

 

[Thors]

I did this and it solved my graphical artifacts and problem with quick talk in the campaign. I have been having many crashes black screens and blue screens of death that caused my monitor and GPU to stop working together.

Something is up with the shaders. The next patch needs to address this shader problem.

ayo wtf its 2021 patch 1.6.1 and i get this same problem like why tf do i have to change **** so i can play?? do i have to change it all back when playing an other game??

 

[Sat_DeliAslan]

the same problem i have exactly when i try to enter trade section at city

 

[ScaryKiwi]

Hello, sorry for the late reply. We have fixed a considerable amount of the problems we have encountered so far and improved the game performance with the multiple patches we have released. Please make sure that your game, your drivers, and OS are up to date and the game has necessary permissions over your security software. Please let us know if the problem persists after completing these steps and verifying the integrity of the game files through Steam.

Hey, done all the suggested here (even though this was a year ago) and done the suggested fix in the common issues and workarounds page here. Still no progress whatsoever and am getting hit with this every five to ten minutes when I load a save. Any other potential solutions floating around?

 

[uçanbiblo]

This crash is a GPU crash. Which is different from the other crashes that can be caused by gameplay actions. While we are still investigating the issue there is not a definite fix that we can offer on this issue at the moment. You can try the workaround below but please note that it is not a solid fix. Thanks for reporting. Sorry for any inconvenience.A possible fix for RGLGPU_DEVICE::LOCK_TEXTURE Crash
If you are crashing in the middle of the game with the “RGLGPU_DEVICE::LOCK_TEXTURE” error, you can try the workaround below to fix it:

• Expanding the swap size on your hard disk. You can find more info regarding this here.

 

[Screminmemes]

Almost 2 years after this last post I am encountering this issue with 1.7 update. I have completely reinstalled Radeon drivers using DDU and fresh driver downloads between instances. Happened in the same battle with a caravan each time. I also verified game files and it found 4 to fix and fixed them (done between instances of this.)

2022-01-20_05.05.26_f41eea992d15cc09612456734a9d36be is my crash submission.

 

[jeep91]

Almost 2 years after this last post I am encountering this issue with 1.7 update. I have completely reinstalled Radeon drivers using DDU and fresh driver downloads between instances. Happened in the same battle with a caravan each time. I also verified game files and it found 4 to fix and fixed them (done between instances of this.)

2022-01-20_05.05.26_f41eea992d15cc09612456734a9d36be is my crash submission.

Yup, same here. Came here hoping there was answers.
I was not having any issues, changed graphic options one day, then all-of-a sudden started getting this issue.
No other games I am affected in. Only Bannerlord.
I can replay the same battle multiple times, sometimes it crashes, sometimes it doesn't.
Tried different graphics options, drivers are up to date,
Come on guys.....Amazing game but this shouldn't be happening this long in without support...

 

[uçanbiblo]

Hey, have you tried this workaround yet? If the issue is persistent please let me know.

A possible fix for RGLGPU_DEVICE::LOCK_TEXTURE Crash
If you are crashing in the middle of the game with the “RGLGPU_DEVICE::LOCK_TEXTURE” error, you can try the workaround below to fix it:

• Expanding the swap size on your hard disk. You can find more info regarding this here.

 

[Tellarion]

Hey, have you tried this workaround yet? If the issue is persistent please let me know.

I am a returning player with about 100 hours in the early days back in 2020, and just getting back into the game on 1.7 now. I am having the same issue as many others, and I can confirm that the page file is not helping. I have 16gb of ram with a gtx 1070, same pc I used two years ago, and my page file is 12GB. Unless you are suggesting that the game needs more than that combined amount of memory(virtual or discrete), there must be something else going on here.

I've also completely reinstalled the game twice, adjusted my graphics settings, and tried deleting various folders(such as shaders), but this crash is still random and persistent. Sometimes I can play for hours, and sometimes I can only play for minutes before the inevitable crash

 

[Fahai Nolove]

Start to have this issue again in 1.8.0.

One of my NPC companions leveled up abnormally, and then it start to really lag. Eventually, the game CTD returns the lock_texture failed error.

 

[Charly30]

After a W10 reinstal it worked perfectly e1.7.2, full setting, 243fps -> Benchmark OK -> Game Crash with this error => same setting but 140fps OK
Then I added Realistic Battle mod OK -> then Raise your torch + raise your banner + Perfect Arrow + Dismemberment Plus -> crash -> unselect all -> still crashing with the same error.
"Expanding the swap size on your hard disk" didn't resolve the problem (32Go RAM => min=1.5*32000=48000Mo and max=32000*4=128000Mo).

 

[xdj1nn]

seems this problem is back in current 1.8

 

[Charly30]

seems this problem is back in current 1.8

I think it's because of their shaders.
Here is my solution, no crash anymore.

 

[xdj1nn]

I think it's because of their shaders.
Here is my solution, no crash anymore.

the most ludicrous part of it is that I've kept the game running fro 400 hours (not always playing) and had no issues until now, late campaign during winter. Something's seriously broken with their shading or particle effects, the issue only happens on campaign map too.

---

didn't work at all.