Crash: BMRender\rmode.cpp(5441)

[Fireblade]

Using Windows 7 64-bit, had these rmode.cpp crashes myself about every 5-30 minutes while using the current (195.62) NVIDIA drivers. Tried the 195.81 beta drivers, that didn't fix it. Rolling back to the previous release (191.07) seems to have fixed it just fine.

[Sokkratez]

Originally Posted by quidnunc

Anyhow, I rolled back to 185.85 and there are no crashes

You should be safe to go as far as 191 with no crashes.

[quidnunc]

Originally Posted by Sokkratez

You should be safe to go as far as 191 with no crashes.

I went back to 185 because there's also an issue in Fallout with later drivers. So I'm playing King's Bounty and Point Lookout on these drivers before I go back to 19x and other games

[Sokkratez]

Originally Posted by quidnunc

I went back to 185 because there's also an issue in Fallout with later drivers. So I'm playing King's Bounty and Point Lookout on these drivers before I go back to 19x and other games

Oh, that's good to know. I still have Point Lookout and some other Fo3 add-ons on my agenda.

[Messymitch]

Just purchased this game on Steam. I should of checked these forums first, I wouldn't of purchased it... Anyways any other fixes besides rolling back drivers? I tried taking off AL and V-Sync, crashes don't happen as often but they still do.

[Sokkratez]

Using 191 or earlier seems to be all that works. There's an NVIDIA driver that's been in beta for almost a month, but I'm not sure if it's going to have a fix or not. Someone earlier in the thread tried it and it still crashed, but the final version may be different.

[kouta]

same here
Win 7 64bit
Geforce GTS 250

but Armored Princess works fine

[Marshmellow]

Hello,

here the same issue.
Kings Bounty: Legend crashes with heavy framerate ups and downs while running. The game crashes often, using the 195 and the new 196 drivers.

Kings Bounty: Armoured Princess is running steadily on 60fps, due to my config (60 hz screen) and has no at problem at all.

my rig:
E8400
8800GT 512
8 GB Memory
X-Fi

Katauri should really be able to fix this problem with a patch, as it the same engine is used in KB:AP, probably with minor changes. Cmon guys, why is this takin forever?


PS:
I tried a lot of suggeted fixes, like doing some settings in the game.ini and turn off AA or Vsync, turn off threaded optimization, etc,
but none of them seemed to work. I tried almost but only with the 195 and 196 drivers.

But in two cases randomly the game runs steadily on 60 fps, and then no crash occurs. First time after i tried with vista compatibility mode, second after running with threaded optimizations off and setting
setf ~r_fsaa from 0 to 1. I think the changes i did before running the game in both cases are not related, and it didnt prevent the error from occuring after starting the game again with the same settings.
the game seems to run randomly correct. Therefore this should be no error on the driver side, but on within the game itself. Katauri should really try to find a solution.

Anyone to confirm that the game runs randomly without errors. In my case, the game is running good, when the fps via fraps show NO ups and downs (~20-45/60), but are steadily showing 59/60fps.

PS: Even when running steadily at 60 fps the game crashed the for first time after playing 30 mins. ...enough for completing 2 quests!!

[Sokkratez]

A new NVIDIA driver was just released. There's no King's Bounty fix that I see in the release notes, but it's worth trying. I finished the game using 191, so I don't have it installed anymore, so it'd be great if someone else could try these new drivers with the game. If it still happens and you haven't reported the bug to NVIDIA, try to do that.

Link for non-XP 64-bit: http://www.nvidia.com/object/win7_wi...6.21_whql.html

[NStriker]

Tested 196.21 on Win7 64bit. No good. Same problem.