It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I just purchased KB:TL and pretty much immediately encountered the crashes that give the error message:
\BMRender\rmode.cpp(5441): DirectX call failed: -1, -1, E_FAIL (An undetermined error occurred inside the Direct3D subsystem)
After some research it seems to be a common problem with the Steam version as well. Does anyone know of a sure fix for this? So many suggestions just don't seem to work.
Also, does anyone happen to know if the boxed version has the same issue? Is it simply a 64-bit problem? Does GOG give refunds for issues like this?
No posts in this topic were marked as the solution yet. If you can help, add your reply
It seems it could be a problem with nvidia drivers, assuming you have an nvidia card. I found a thread where the solution seems to be to roll your drivers back to 191.07 or earlier, though some people claim the 197 drivers worked as well so you could try updating to latest first and then rollback if that doesn't work.
Thread link:
[url=]http://forum.1cpublishing.eu/showthread.php?t=11129[/url]
avatar
Ralackk: It seems it could be a problem with nvidia drivers, assuming you have an nvidia card. I found a thread where the solution seems to be to roll your drivers back to 191.07 or earlier, though some people claim the 197 drivers worked as well so you could try updating to latest first and then rollback if that doesn't work.
Thread link:
[url=]http://forum.1cpublishing.eu/showthread.php?t=11129[/url]

I read about that too, but I also read some people who said that the driver changes didn't work either. And I really don't want to mess with that if I don't have to, especially downgrading them.
avatar
JohnJSal: ...

I have yet to work my way thru my game backlog to Kings Bounty but here are some standard things to check / try if you are running Win 7 / Vista 64. Don't know that they will solve your problem but . . . I will offer them anyway . . .=)
Are your video drivers up to date? The very latest?
Click here for ATI
Click here for Nvidia
Did you ...
install as an administrator? (Right click the setup exe, click "Run as an adminstrator")
turn UAC off before installing?
install in a directory outside of Program Files?
right click the game shortcut, click Properties, click the Compatibility tab and check mark "Run this program as an administrator"?
try using different compatibility modes, starting with the newest and working back to the oldest?
If you have a dual / quad core CPU, did you try setting the affinity to a single core? You can do it manually by starting the game, ALT-TAB out of the game, open task manager (CTRL - ALT - DEL ), find the [game name].exe on the Processes tab, right click the exe and click Set affinity . . . on the resulting dialog. Un-check all but the CPU 0 check box. (See attached image) Close the task manager and play the game. If this helps I suggest using RunFirst as it sets the affinity for the game without having to go thru the task manager process each time you play.
If running an AMD dual core CPU, did you try the AMD Dual Core Optimizer ?
If running Win 7 / Vista 64 bit, did you try limiting the memory? (see attached image) It's a pain to do every time you run the game so I'm not a fan of this method but . . . it seems to work for some folks, Win 7 64 seems to confuse some older games concerning memory. Make note of your original setting prior to changing it as you will need to set it back after playing the game . . . if it works for you that is.
If you've tried all of the above I have nothing else . . . =)
Edit: If you did not install as an admin, make sure your uninstall the game and delete all remaining DD directories prior to reinstalling. Good time to install in a directory outside of Program Files as well.
Attachments:
affinity.jpg (180 Kb)
Post edited August 15, 2010 by Stuff
avatar
JohnJSal: Does GOG give refunds for issues like this?

All sales are final, this is the policy from day one. It has been discussed in many threads.
avatar
JohnJSal: I read about that too, but I also read some people who said that the driver changes didn't work either. And I really don't want to mess with that if I don't have to, especially downgrading them.

I've been reading your thread on not recieving a support reply. I saw gog finally replyed and told you to update your directx drivers, which I'll assume you have dx11 already installed. It made me think have you installed directx 9.0c on that computer at any point? If all you've ever installed is directx10 or 11 they will have missed out some of the stuff directx 9.0c has.
I have also had this problem: Win7(64bit), NVidia Geforce GTX260 graphics card. I just updated the graphics card driver, now it´s fine.
I have a problem with this: "work\skyfallen\tbm\BMRender\rmode.cpp(5509): DirectX call failed: -1, -1, code=0x88760870 (-2005530512)"

Game plays ok for a while like 20-30 mins, but then crashes to the desktop and Windows informs that there was something wrong with the graphics card.

I have just updated DirectX ([url=http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=2da43d38-db71-4c1b-bc6a-9b665 2cd92a3]dxwebsetup.exe[/url]), because I had this d3dx9_33.dll problem.

I updated Graphics card drivers couple of weeks ago, so I downloaded 10.08 driver from AMD page.

GPU CCC information:
Device driver version 8.632.1.2-...-ATI
Catalyst version 09.7
2D version 8.01.01.921
Direct3D 8.14.10.0678
OpenGL 6.14.10.8787
CCC version 2010.0803.2125.36577

My system:
HP dv5-1021eo
Athlon X2 QL-60
4 GB RAM
HD 3450
64-bit Win 7

All the other games have been working great so this is quite strange. Any help?
avatar
JohnJSal: I just purchased KB:TL and pretty much immediately encountered the crashes that give the error message:

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

After some research it seems to be a common problem with the Steam version as well. Does anyone know of a sure fix for this? So many suggestions just don't seem to work.

Also, does anyone happen to know if the boxed version has the same issue? Is it simply a 64-bit problem? Does GOG give refunds for issues like this?
I have almost the same problem :

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

I've installed the lattest DirectX Version and my GC drivers seems to be the lattest one.

Any idea how to fix this ?
Post edited November 16, 2013 by NJ-Alucard