Resolved Crash entering Smithy

Users who are viewing this thread

Version number
1.6.4
Branch
Main
Modded/unmodded
No, I didn't use any mods.
Dump identifier (optional)
2021-10-26_16.52.54_a250b5e5c587b4d042c81fc57d9bb960
Summary: When entering the smithy from any city on a new save with no mods, game will crash and exit. I have posted the crash log (which is reproducible) below
How to Reproduce: Enter Smithy
Have you used cheats and if so which: No
Scene Name (if related):prt_crafting_scene
Media (Screenshots & Video):
[12:40:33.125] Loading xml file: $BASE/Modules/SandBox/SceneObj/crafting_menu_outdoor/scene.xscene.
[12:40:33.130] Loading xml file: $BASE/Modules/SandBox/SceneObj/crafting_menu_outdoor/atmosphere.xml.
[12:40:33.132] Unable to find particle system with name prt_crafting_scene
[12:40:33.133] Emitter hierarchy does not match invalid_particle-invalid_particle[12:40:33.139] SandBox.GauntletUI.CraftingGauntletScreen::HandleActivate

[12:40:33.139] SandBox.GauntletUI.CraftingGauntletScreen::HandleResume

[12:40:34.567]
<##########################################################################################>

[12:40:34.567]
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.
[12:40:34.567] #TaleWorlds.Native.pdb@{B20B47E70D674737B8A16DDD1412C898} (1): 0:6701453
#TaleWorlds.Native.pdb@{B20B47E70D674737B8A16DDD1412C898} (1): 0:984374
#TaleWorlds.Native.pdb@{B20B47E70D674737B8A16DDD1412C898} (1): 0:426523
#TaleWorlds.Native.pdb@{B20B47E70D674737B8A16DDD1412C898} (1): 0:6600730
#TaleWorlds.Native.pdb@{B20B47E70D674737B8A16DDD1412C898} (1): 0:2162284
#TaleWorlds.Native.pdb@{B20B47E70D674737B8A16DDD1412C898} (1): 0:1482920
#TaleWorlds.Native.pdb@{B20B47E70D674737B8A16DDD1412C898} (1): 0:817946
#TaleWorlds.Native.pdb@{B20B47E70D674737B8A16DDD1412C898} (1): 0:783950
#TaleWorlds.Native.pdb@{B20B47E70D674737B8A16DDD1412C898} (1): 0:2065393
#TaleWorlds.Native.pdb@{B20B47E70D674737B8A16DDD1412C898} (1): 0:2069523
#TaleWorlds.Native.pdb@{B20B47E70D674737B8A16DDD1412C898} (1): 0:2091317
#TaleWorlds.Native.pdb@{B20B47E70D674737B8A16DDD1412C898} (1): 0:2088763
#TaleWorlds.Native.pdb@{B20B47E70D674737B8A16DDD1412C898} (1): 0:2092663
#ucrtbase.pdb@{152B3C4F5E1CE0FE6BC36E9F0F2B10E6} (1): 0:138162
#kernel32.pdb@{1DEB36EBC19F93893E14684776D19DB3} (1): 0:94260
#ntdll.pdb@{96EF4ED537402DAAA51D4A4212EA4B2C} (1): 0:337489
-----------------------------------------------
#TaleWorlds.DotNet.AutoGenerated.pdb@{200AA35C646D48B8AE90FA59DFF9A963} (1): 100663315:0
Computer Specs:
OS: Windows 10
GPU: RTX 2070 Super
GPU Driver Version: 456.71 (note: smithy works on various 440.00 drivers, though all of them have visual artifacts and tearing)
CPU: Ryzen 3600
RAM: 16gb
Motherboard: b450
Storage Device (HDD/SSD): SSD
 
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.
 
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.
Thank you for your response. I've expanded my swap size, increased ram speed from 2400mhz to 3000mhz, and reverted to Nvidia GPU driver 442.74. This has eliminated the d3d crash. Minor visual artifacts/tearing.
 
New fix, updated drivers 460.00 and above required downclock of -500mhz to memory and gpu, fixed previous crash and graphical issues. Might possibly be an underperforming/dying card on my end.
 
Back
Top Bottom