Crash: BMRender\rmode.cpp(5441)
 

I get this crash after only a few minutes of playing ever since I switched to Windows 7 Home Premium 64bit from Vista 32. This happens in all areas, even if I start a new game, but my current save file is in Mehgrad. I'm using the GamersGate version of the game patched to v1.7. The full error is:

.\BMRender\rmode.cpp(5441): DirectX call failed: -1, -1, E_FAIL (An undetermined error occurred inside the Direct3D subsystem)

I run an E8400, 4GB of RAM and an 8800GT 512MB.

I've tried the latest official and several beta versions of NVIDIA drivers as well as several NVIDIA Control Panel settings suggested in various troubleshooting threads (disabling threaded optimization, etc) but the crash persists. I'm also current on DirectX.

I've also found a thread on the Russian forums and tried some troubleshooting as best I could based on the Google translation: http://translate.google.com/translat...80&sl=ru&tl=en

I've also tried reinstalling the game. One page I found said that a desktop/game resolution mismatch could be the problem, but it wasn't.

If u just moved to WIN7 update your directX.

I'm definitely current on DirectX, but the crashes persist.

Well, i havent seen anyone confirming that this game works on 64 bit system. I have Windows7 32 bit and it works fine but 64 is different story.

I've seen some people on the Steam forums say they run it under 64 bit. There's also a person with this same issue, and he's on Vista 32. This is the first game of many that has given me problems.

make sure in the game.ini file that you have -
setf ~r_use_adapter 0

That is set to 0 already. What does that do? Perhaps I'll try it at 1.

I have the exact same problem.

Windows 7 64Bit
Intel E8500
8GB RAM
GeForce GTX280

latest drivers, latest directx runtime are installed.

Same Problem here.

Windows 7 64 Bit Home Premium
Intel I7 920
6 GB RAM
Geforce GTX 275

I tested a few things...

try to disable "Vertical synchronization" in the options, that worked for me.

***edit***

okay it still crashes with 5441 error, but not as frequent as before.

Had the same problem after upgrading my gfx drivers, went back to old version, and the crashes stopped. The graphics will still spazz out at times (will suddenly get low frame rates and objects popping in and out) but it doesn't crash anymore.
So as a stopgap measure, just downgrade the drivers. I went back to the earliest WHQL certified win7x64 drivers, but they don't have to be that old as the drivers I used before I upgraded were only a cpl months old.

I'm still crashing with the WHQL Nvidia driver that came out a week or two ago. Rolling back would be an unfortunate solution as this driver version added support for Flash acceleration.

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.

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

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

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.

Its not about katauri, this drivers are scrwed in general

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.

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.

Yeah, huge pain. I encourage the rest of you to submit support tickets as well. You don't even need an account, just an e-mail address. Here's what I sent them, feel free to just copy it:

http://nvidia.custhelp.com/cgi-bin/n...nduser/ask.php

Registered just so I could add that this occurs under win7 32bit as well (using the RC still though). Ever since the new NV drivers.

The game is unplayable now and it's a shame because I quite liked it :)

Hi there, I got a message from Nvidia support.

I installed the latest beta drivers and this issue is just gone.

Here is a link to them : http://www.nvidia.com/object/win7_wi...5.81_beta.html for 7 and vista x64.

Enjoy :-P

that didn't seem to fix the problem here :(

Ran for a bit but still eventually crashed. I think 1C or the devs should really look into this instead of just hoping Nvidia figures it out. Losing a lot of potential customers.

I'd been wondering if those new beta drivers sorted it out, but kept putting off trying them. That's a shame.

I will see if there is a demo for Legends as I do not have the game. However, I posted a possible fix for Armored Princess, but isue is I cannot change any settings or I crash everytime and have to delete the created ini files starting over. It may work on Legends too (but perhaps requires a different DX dll file not sure yet..)

http://forum.1cpublishing.eu/showthr...ewpost&t=12102

Yeah indeed I played for like an hour and then it crashed again... Better but not what we can call exactly working...

Anyway let's hope for a patch or something.

By the way armored princess is working fine for me, maybe something to look at.

I've got the same problem here (BMRender\rmode.cpp(5441) etc.). Upgrading to NVIDIA beta drivers didn't work, nor did the fix posted in the Armored Princess forum (copying a certain directX dll file). Downgrading NVIDIA drivers is not an option; other games have problems with those (like Left 4 Dead 2). Since I bought the King's Bounty Gold pack from Steam, I'll give Armored Princess a try and see what it does.

The game will sometimes work for hours without any problems, and sometimes it'll crash in seconds. It's the randomness of the crashes that're most annoying.

Win 7 64bit
ASUS GTX275
Phenom II 965
AMD 790GX chipset
8gb RAM

Tried with latest WHQL and beta drivers. First time I was able to play for 1-2 hours before it crashed. Now it crashes more quickly. Usually within a few seconds in the actual menu, or under 10 minutes in game.

9800M GS, Vista 64

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

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.

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 :)

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

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.

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.

same here
Win 7 64bit
Geforce GTS 250

but Armored Princess works fine
:(

KBL crashes, KBAP not
 

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!!

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

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

Nvidai = idiots

Older games will always suffer when driver updates are released. Just something we have to live with I guess. Anyway i'm uninstalling I don't like rolling back drivers.

I played for about an hour with the beta 196.34 and it didn't crash, although I was getting some frame hiccups that I don't remember being there before, but the game is playable other than that.

If you have NVIDIA graphics you should definitely try to downgrade your graphic drivers to version 191.07. Many of the customers resolved the problem this way :cool:

Can anyone post a guide on how to roll back your nvidia driver or uninstall it to install the one that works on windows 7. Im new to windows 7, and I don't know how. Would REALLY like to play this game that I bought! And 1C Company, i must say this really sucks, and i wont be purchasing any more of your games because of this stupid issue.

Good news! The 197.41 drivers work.

Vista/7 64bit
http://www.nvidia.com/object/win7_wi...7.41_whql.html

Vista/7 32bit
http://www.nvidia.com/object/win7_wi...7.41_whql.html

XP 32bit
http://www.nvidia.com/object/winxp_197.41_whql.html