Resolved Hard lock on alt-tab or quitting game

[celeryion]

Summary: Computer hard-locks when alt-tabbing or quitting the game. No BSOD, but also no graphical update, sound is on short-loop, no keyboard or mouse response. Must hard-power-off PC and reset. Only happens in Bannerlord. For the first 5-15 minutes, this isn't an issue. Even after that, can play the game for hours, saving and loading the game, no problem. Except that as soon as I alt-tab or quit the game, the PC freezes up entirely. Hadn't played the game in about a year, but this issue was never a problem back then. Have updated bios, os, graphics card driver, verified steam cache, disabled all game overlays, run the game from Bannerlord.exe. None of that helped.
How to Reproduce: Play the game for 5-15 mins, then alt-tab or quit the game.
Have you used cheats and if so which: No
Scene Name (if related): N/A
Media (Screenshots & Video): N/A
Computer Specs:
OS: Windows 10.0.19043
GPU: MSI Geforce 2080S
GPU Driver Version: 471.41
CPU: i7-9700KF
RAM: 16GB
Motherboard: MAG 7390 TOMAHAWK
Storage Device (HDD/SSD): SSD

 

[celeryion]

Still using the exact same computer as the previous bug reports. I had recorded the wrong CPU back then.

 

[MArdA TaleWorlds]

Can you try to play the game with borderless fullscreen setting and see if the issue still exists?

 

[celeryion]

Yes, the issue persists whether windowed or in borderless fullscreen. In borderless fullscreen, after the 5-15m, when I click to my second monitor, the entire system locks up.

I don't know what happens when windows switches between the game context and the desktop environment for primary input, but it isn't good.

 

[celeryion]

Any other ideas?

 

[celeryion]

Rolling back Geforce driver to 466.77 didn't help

 

[celeryion]

Rolling back Geforce driver to 461.92 seems to have done the trick. Just had a solid half hour of playing borderless fullscreen without crashing, and didn't crash on quitting.

 

[MArdA TaleWorlds]

Glad to see it is fixed. We have not seen this issue internally yet. We will reach out if we have more to say on this issue.

 

[celeryion]

Glad to see it is fixed. We have not seen this issue internally yet. We will reach out if we have more to say on this issue.

Sorry, looks like I told a lie. Had three sessions where it didn't lock up, which is a marked improvement on the latest driver, but it happened again on the fourth.