Crash: BMRender\rmode.cpp(5441)

[Roy the coy]

Yes the newest one causes a crash. There's no problem to roll back the driver, play the game, and roll back to the new one again, as you don't need to reboot inbetween anymore.

[Sokkratez]

What method are you using to swap back and forth that won't require reboots?

[Roy the coy]

Just doing the regular driver install (from the driver folder, not device manager).
Doesn't ask for a reboot at least.

[Sokkratez]

I rolled back. 191.07 seems to work where 195.62 (and the beta version of it) didn't. I played for a couple of hours. We should try to make Nvidia aware of the issue; I think we're more likely to get a fix from their end than from Katauri's.

[Elwin]

Its not about katauri, this drivers are scrwed in general

[Sokkratez]

I reported the bug to NVidia and Support told me that they're going to try reproducing the bug on their end. I directed them to this thread. Here's hoping we'll see something about King's Bounty in the next driver release notes.

[quidnunc]

yes, Nvidia drivers as of late have been creating problems in many "older" games. It's possible to play the game without crashes using previous drivers, however it's a pain in the ass if the user also plays newer games that benefit from the optimizations in recent drivers.