Game Crashing

[Leric]

For some odd reason my game has started crashing lately in battles with more than 100 people. It's not a system requirement, (my computer runs the game fine, with no drop in screen rate, regardless of how many people are in a battle).

Within the past few days it just starts crashing and says "Mount & Blade has stopped working, Windows is looking for a fix to the problem".


I have windows vista.


Thanks for the help

 

[SandmanX2]

For some odd reason my game has started crashing lately in battles with more than 100 people. It's not a system requirement, (my computer runs the game fine, with no drop in screen rate, regardless of how many people are in a battle).

Within the past few days it just starts crashing and says "Mount & Blade has stopped working, Windows is looking for a fix to the problem".


I have windows vista.


Thanks for the help

Welcome to Vista and its patches.... I too have had same problem and honestly its not MNB its the compatibility of the game to Vista, and Vista can be a ***** at times. Ive had IE crash, Itunes also randomly crash lately when it never did before, its all in their new patches as of late

 

[jasonxfri13th]

For some odd reason my game has started crashing lately in battles with more than 100 people. It's not a system requirement, (my computer runs the game fine, with no drop in screen rate, regardless of how many people are in a battle).

Within the past few days it just starts crashing and says "Mount & Blade has stopped working, Windows is looking for a fix to the problem".


I have windows vista.


Thanks for the help

Did you change anything when the game started crashing? Try a fresh install or try turning the body limit down.

 

[Mordachai]

I'm wondering if ATI (AMD)'s latest drivers are allergic to M&B?

I had this problem a lot with W7 beta and AMD's official drivers.  But when I did a fresh install of W7 RC1, and stuck with the MS provided drivers, I've had no problems.

Others have complained of this exact issue, and for some, reducing the rag-dolls, and bodies helps.  Obviously reducing the battle sizes helps.  But ultimately, I couldn't fix it... until I redid my whole rig with W7 (I only use x64 versions of the OSes, if that's relevant).

G/L

 

[SandmanX2]

I'm wondering if ATI (AMD)'s latest drivers are allergic to M&B?

I had this problem a lot with W7 beta and AMD's official drivers.  But when I did a fresh install of W7 RC1, and stuck with the MS provided drivers, I've had no problems.

Others have complained of this exact issue, and for some, reducing the rag-dolls, and bodies helps.  Obviously reducing the battle sizes helps.  But ultimately, I couldn't fix it... until I redid my whole rig with W7 (I only use x64 versions of the OSes, if that's relevant).

G/L

I've noticed something that may help too.... Your monitor and Graphics card w/ MNB make sure you set your monitor to best resolution (ie mines 1280 x 1024) and its peaks best at 75hz, I had to make MNB also 1280 x 1024 32 Bit and it seems to help a ton, I havent seen much issues and Im back to DX 9 and over 200 Battlesizer

 

[jasonxfri13th]

I have an ATI graphics card and an AMD processor and I get "mount and blade has stopped working" every once in a while too. I also used to get the vertex buffer error, until I turned off bodies.

But the weird thing is I never used to have problems with my old integrated graphics card, then I upgraded to my 4870 and now it crashed.

 

[SandmanX2]

I have an ATI graphics card and an AMD processor and I get "mount and blade has stopped working" every once in a while too. I also used to get the vertex buffer error, until I turned off bodies.

But the weird thing is I never used to have problems with my old integrated graphics card, then I upgraded to my 4870 and now it crashed.

I use the Ati HD 3870 series graphic card... To be honest I think its more that ati cards have a rough time running MNB compared to Nvidia and some integrated graphic cards. I did FINALLY get ati to reply and all they could say is "download the latest drivers....." Course I let em know, that i am up to date, no I'm back to square one

 

[Mordachai]

Well, my best guess is that M&B leaks resources.  And those accumulate over time, and eventually overwhelms something...

I noticed, when I had this problem a lot, that it almost always happened immediately after the vertex buffer exceeded 512MB.  That's a freaking ton of vertexes... and although the 4870 can handle that size buffer, it was more than a little odd that the "unable to restore vertex buffer" almost always coincided with that particular boundary.
I can't know for sure that I'm not just making it up - that 512MB is of no particular meaning.  OTOH, why crash often at that boundary?  So often in fact, that I'm not sure it ever crashed at any other buffer size?

Its also strange to me that M&B's video buffer size grows continually.  Why doesn't it hit some peak, and stop growing?  Some maximally complex scene for which there is no other scene more complex?  Unless its leaking resources, and so having to grab more and more to make up for the loss?  Maybe ATI's drivers are less forgiving of such sloppy programming?

I don't know.  I wish I had some tools to investigate further.  Does anyone know of any tools for monitoring DX9 application resource usage?