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.